`/seo-content`

Backed by `.claude/context/ai-seo/playbook/05-content.md` (carries ~16 verbatim course prompts) + `prompts/`.

Placeholders like ACME Agency, <id> and you@example.com mark values that are per-agency — your install fills them with YOUR clients and accounts. If a section references a helper script you don't have yet, it ships with that workflow's install.

Backed by .claude/context/ai-seo/playbook/05-content.md (carries ~16 verbatim course prompts) + prompts/.

When to trigger

"Write the service page for water heater repair", "write 3 supporting articles for X", "rewrite our homepage for SEO", "/seo-content".
After /seo-site-structure hands you a page plan — write the pages here. For a page rewrite, pass --url.

Two modes

Create (default): write a new page/article for a --topic and --type.
Rewrite: pass --url <existing page> → run the playbook's 6-prompt Page Analysis Rewrite sequence (needs Search Console queries; if you don't have the CSV, ask the user to paste the top queries + positions for that URL, or proceed with on-page-only improvements and say so).

Step-by-Step

1. Parse

First positional = client/business. Flags: --topic, --type (service|category|blog|landing|supporting), --url (rewrite mode), --location, --dry-run.

2. Gather context

node ACME Agency/scripts/seo_run.mjs --skill content --mode gather --client "<name>" --url "<site or page url>" --location "<city>"

Read the CONTEXT for brand/voice + (in rewrite mode) the existing page content.

3. Read the method

Read .claude/context/ai-seo/playbook/05-content.md fully — it contains the verbatim prompts (keyword variations, outline, article writing with the banned-words list, GBP-landing rewrite, metadata, and the 6-step Page Analysis Rewrite). Use the relevant prompt(s) for the requested type/mode rather than improvising.

4. Produce the content (markdown)

Follow the playbook's pipeline for the page type:

Keyword(s) — primary + LSI/semantic variations (Keyword Variations prompt).
Outline — per the Outline prompt (intro hook, H2/H3s, FAQ from People-Also-Ask).
Draft — full body via the Article/Service/Landing prompt: first-person expert voice, natural language, LSI woven in, content-type matched to intent. Hit the playbook word counts for the page type.
Metadata — title tag + meta description (their prompts; CTR-optimized).
Links — internal anchor-text suggestions (the exact anchor rules) + 1-2 outbound authority links.
Human-edit pass — apply the playbook's edit checklist to remove AI-tells; for HR/BS clients, also enforce the no-em-dash / no-AI-tell rules from root CLAUDE.md.

In rewrite mode, instead run the 6-prompt Page Analysis sequence and output the marked-up changes + new FAQ + suggested new articles. Write to ACME Agency/clients/<Client>/SEO/content-<slug>.md (or /tmp).

5. Save + report

node ACME Agency/scripts/seo_run.mjs --skill content --mode save --client "<name>" \
  --in "<content.md>" --title "SEO Content — <topic> — <Client>" \
  --slack "*SEO Content — <Client>*
<type> page for '<topic>' (~<N> words) + metadata + link plan ready."

Add --dry-run to skip Drive/Slack. Output the Doc link.

Guardrails

Use the course prompts, not generic AI writing — that's the whole point of this method.
Human-edit is mandatory — never ship a raw AI draft; run the de-tell pass.
Croatian/Bosnian copy: no em-dashes, no two-word fragments, no literal English-isms.

/seo-content

/seo-content — AI SEO Content & Page Rewrites