[placeholders] — structure and
intent preserved so they stay copy-paste-ready). Grouped by task category.
Placeholder key: [client] = the account/company · [domain] = client site ·
[partner] = a partner brand to co-rank · [competitor] = a rival · [keyword] ·
[product] · [region] · [month] = cycle month tag (e.g. jul'26).
Provenance is the source org slug + approximate month. It is metadata for us, not part of the prompt — drop it when you copy a prompt.
1. Keyword research & planning
1.1 — Pick the most winnable keywords from a tagged pool
Does: narrows a month’s candidate keywords down to a small, winnable test set.1.2 — Full monthly keyword selection run (the canonical workflow)
Does: runs the end-to-end monthly keyword pipeline — explore, evaluate, SERP-cliff, cannibalization check, tag.1.3 — Keyword discovery scoped to gaps, with cannibalization guard
Does: finds keywords with no existing LP, audits them, dedupes for cannibalization, iterates.1.4 — “Keyword vs content-idea” correction (the most-repeated coaching)
Does: rejects head-term/content-idea entries and forces true keywords usable for both LP and blog.1.5 — Turn queries into keywords, then tie content ideas back
Does: converts blog-idea queries into taggable keywords and attaches the query as a content idea.1.6 — SERP-cliff + “are we already ranking?” verdict pass
Does: decides keep/drop/optimize per keyword based on cliff position and whether client already ranks.1.7 — Crawl a competitor/product page for keyword candidates
Does: harvests product names off a live page as net-new keyword candidates.1.8 — Tag and file, with research attached to notes
Does: commits the accepted keywords with correct tags and the supporting research in notes.1.9 — Build the keyword ladder / dendrogram
Does: maps head terms to their long-tail supporters so the cluster structure is visible.1.10 — Challenge the strategy before executing
Does: pressure-tests whether the keyword direction matches the client’s actual ICP and stated goals.2. Landing pages (pillar, generation, alignment, refiners)
2.1 — Align the LP generator to a compliance guideline
Does: updates the LP prompt and supporting files so future pages are generated compliant.2.2 — Drive LP content from a CSV source of truth
Does: treats an uploaded CSV as authoritative and reconciles the pages to it.2.3 — Align all LPs to an ICP/positioning brief
Does: rewrites LP files, prompt, and refiners against a pasted ICP + positioning brief.2.4 — Position hero copy for a fake-door / lead-gen page
Does: works the on-page text for a validation page that intentionally has no real deliverable.2.5 — Write a build prompt for an external page builder
Does: produces a ready-to-paste prompt for a no-code builder to adjust a page.3. Blog content (writing, editing, refiners)
3.1 — Audit all unpublished blogs for accuracy + link validity
Does: verifies facts as-of-today and checks every internal link on the unpublished backlog./goals to run one blog at a time.
3.2 — Fully specified blog audit with domain guardrails
Does: audits a named set of articles against explicit factual rules and forbidden fabrications.3.3 — Enforce brand ordering in metadescriptions
Does: guarantees the client is named first (ahead of competitors) in every meta description.3.4 — Enforce ranked ordering across title, content, slug, and meta
Does: locks a consistent competitive ordering everywhere the list appears, and syncs the count.3.5 — Fix titles / metadescriptions to lead with the brand
Does: targeted follow-up to correct titles once the audit surfaces mismatches.3.6 — Compliance-check blogs one by one with /goals
Does: runs each blog individually through the compliance guideline and retries failures.4. Publishing & distribution
4.1 — Confirm the canonical domain before fixing links
Does: checks which host variant is canonical before rewriting internal links across content.4.2 — Bulk-fix stale internal links to the live URL structure
Does: rewrites outdated/broken internal links to the correct current paths across all blogs.4.3 — Weave partner/backlink anchors into existing content
Does: inserts subtle anchor-text links to partner pages using their top GSC performers.4.4 — Decide next move after losing share of voice
Does: asks for a strategic recommendation (e.g. link building) after a competitive-loss audit.Coverage note: press-release and formal indexing-submission prompts are thin in the sampled chats. Distribution activity concentrated on internal linking, canonical/link hygiene, and partner-anchor link building rather than PR or index-ping workflows.
5. Analytics & review
5.1 — Read-only analytics onboarding exploration
Does: gets acquainted with a newly connected analytics account without changing anything.5.2 — Scope which events to own, and protect the rest
Does: picks the events to instrument for organic/AI visibility and records ownership boundaries.5.3 — Profile who converts, exploratory
Does: breaks lead-form submitters down by attributes to characterize the buyer.5.4 — Attribution / impact validation
Does: tests whether specific content (blogs, /uses pages) drove measurable growth.5.5 — Pull a GSC keyword report into the strategy
Does: feeds a GSC export in as context for keyword and content decisions.5.6 — Prep a client review, aligned to the last review
Does: summarizes findings so they line up with what was agreed in the prior review call.6. Account setup & memory
6.1 — Feed a review/call transcript to set direction
Does: hands Pi the meeting transcript so the next cycle’s strategy inherits what was agreed.6.2 — Correct the product/org info, precisely
Does: makes targeted factual corrections to the org’s product info fields.6.3 — Build ICP hypotheses from the ground up
Does: derives who searches and why, grounded in transcripts and research rather than keywords.6.4 — Set up the image generator and default refiners
Does: configures per-account image generation and the default refiner set.6.5 — Image-generation prompt spec grounded in ICP + real product
Does: produces per-keyword image prompts that reflect the actual product and buyer perception.6.6 — Fix links inside the product bible and memory
Does: corrects stale URLs in the account’s persistent context files, not just the content.6.7 — Diagnose before acting (audit-first)
Does: demands a root-cause audit before any fix when performance drops.Recurring operator patterns (for Part 3 SOPs)
- Audit / explore before acting. Operators routinely open with “don’t add or write anything yet”, “have you run an audit — diagnose why”, “do a full exploration first”. Read-only reconnaissance precedes any change, especially on a newly onboarded account.
- Cannibalization is checked twice — within the set AND against existing LPs. Almost every keyword run asks Pi to dedupe the selected keywords against each other and against pages the client already ranks for. This is the single most-repeated guardrail, and operators re-flag it when Pi forgets (“you casually forget about cannibalization… file a ticket about this”).
- “Keyword vs content-idea” is the top coaching correction. Operators repeatedly reject head-terms / “best X” / “how to Y” as keywords, insisting keywords must serve BOTH a landing page and a blog, and teach the fix by example (add a modifier to turn a query into a keyword; attach the query as the blog idea for that keyword).
- SERP-cliff + “are we already ranking?” verdict rubric. Keep/drop/optimize decisions are driven by (a) the SERP cliff position and (b) whether the client already ranks: drop if already #1–#2, keep if not ranked, optimize the existing page if in striking distance (pos ~8–20).
-
Monthly cycle tagging. Selected keywords are tagged by cycle month (
jun'26,jul'26); the rest are parked (“we’ll come back another month”) rather than deleted. The month tag is the backbone of the month-to-month strategy. - Brand ordering enforced across ALL surfaces. Client must appear #1 (partner #2) ahead of competitors in title, body, slug, AND meta description — and the listicle count must match across all of them. Operators sweep the whole unpublished backlog for this.
- Grounding trio: ICP doc + product bible + review transcript. Strategy is anchored to these three, and operators paste call/review transcripts directly into chat to set direction. “Start from the ICP, not the keywords” is a recurring redirect.
-
Pre-publish sweep is a standing ritual. “Check all unpublished blogs — accurate as of today
(verify on the web), all internal links valid, no 404s” recurs almost verbatim across every
account, usually run one-by-one via
/goalswith explicit retry of failed subagents. - Fix the generator, then the backlog. For compliance/link/positioning issues, operators fix the upstream prompt / refiners / product bible first so errors stop regenerating, then audit and fix the existing pages.
- Research is filed to notes; ownership is written to memory. Accepted keywords carry their supporting research in notes; on shared tools (analytics) operators tell Pi to “save to memory what we own and not to touch” so later sessions don’t clobber the client’s own setup.
- Confirm completion and demand honesty. Operators close loops explicitly (“all blogs fixed?”, “were all fixed?”) and repeatedly ask for candor (“be honest: do these align with the direction we discussed?”) rather than accepting the first answer.
- File a ticket on repeat mistakes. When Pi makes the same error twice (e.g. cannibalization), operators ask it to file a ticket in-line — feeding the product-improvement / feedback loop.