export declare const CONTENT_ENGINE = "# /content-engine \u2014 Organic Content & SEO/GEO Engine\n\n## What This Does\n\nDefines topic clusters from buyer research, generates pillar and spoke content with SEO/GEO optimization, creates schema markup, builds a content calendar, and establishes AI visibility baselines. Produces the full organic content infrastructure parallel to paid traffic.\n\n## Trigger Context\nAfter `/deploy` completes and `/qa` clears. Runs parallel with `/traffic-strategy` \u2014 not gated on paid traffic decisions. Can also run standalone after buyer research + building blocks + product architecture are complete.\n\n## Prerequisites\n- Therapeutic Buyer Research Package (from /research): Pain Architecture, Language Bank\n- Building Blocks (from /build-blocks): Named frameworks, mechanism, offer stack\n- Product Architecture Blueprint (from /product): Module structure, deliverables\n- Name Lock Registry (from /name-lock): All locked names for brand attribution\n\nAll four REQUIRED. If any are missing:\n```\nSTAGE_BLOCKED \u2014 Prerequisites not met.\n\nMissing stages:\n  - [stage]: status is \"[current]\", needs \"complete\"\n\nRun these first:\n  1. /research (if buyer research incomplete)\n  2. /build-blocks (if building blocks incomplete)\n  3. /product (if product architecture incomplete)\n  4. /name-lock (if names not locked)\n```\n\n## Execution Protocol\n\n**DELEGATE TO SUBAGENT: `content-strategist` (task_type: \"topic_cluster_research\")**\n\n### Step 0: Check Learnings\nSilently check `learnings.json` for patterns tagged `seo`, `content`, `organic`, `geo`. If relevant patterns exist, pass them to the subagent as context.\n\n### Step 1: Gather Inputs\nCollect and pass to subagent:\n- Pain Architecture (top 5 pain points with severity scores)\n- Building Blocks named frameworks (Block 6 \u2014 named system/method)\n- Product Blueprint module structure\n- Name Lock Registry (brand name, product name, mechanism name)\n- Language Bank (buyer's exact phrases)\n- Market intel competitive landscape\n- Any existing content assets\n\n### Step 2: Topic Cluster Definition (Subagent \u2014 10-15 keyword searches)\nThe subagent runs 10-15 web searches (5-8 for primary keywords, 5-7 for adjacent topic discovery):\n- \"[market] best practices [current year]\"\n- \"[primary pain point] how to [current year]\"\n- \"[market] guide for [target buyer]\"\n- \"[competitor name] content strategy\"\n- \"[pain point] vs [pain point] comparison\"\n- \"[market] frequently asked questions\"\n- \"[mechanism/method name] explained\"\n- \"[market] tools templates resources\"\n\nFrom search data + Pain Architecture, define 3-5 pillar themes:\n\n```\nTOPIC CLUSTER MAP\n\nPILLAR 1: [Theme from top pain point]\n  URL: /[pillar-slug]/\n  Target keyword: [primary keyword]\n  Search intent: [informational/commercial/transactional]\n  \u251C\u2500\u2500 Spoke 1.1: [Sub-topic from product module]\n  \u2502   URL: /[spoke-slug]/\n  \u2502   Target keyword: [long-tail keyword]\n  \u251C\u2500\u2500 Spoke 1.2: [Sub-topic from FAQ/objection]\n  \u2502   URL: /[spoke-slug]/\n  \u2502   Target keyword: [long-tail keyword]\n  \u251C\u2500\u2500 Spoke 1.3: [Sub-topic from failed solutions]\n  \u2502   URL: /[spoke-slug]/\n  \u2502   Target keyword: [long-tail keyword]\n  \u2514\u2500\u2500 Sub-page 1.1.1: [Deep-dive supporting page]\n      URL: /[sub-page-slug]/\n\nPILLAR 2: [Theme from mechanism/method]\n  ...\n\nPILLAR 3: [Theme from transformation narrative]\n  ...\n```\n\nSave to `assets/[market-name]/content/topic-cluster-map.md`\n\n**Content Priority Matrix (SEO x GEO):** Score each pillar and spoke by quadrant to determine publishing order:\n\n```\n\u250C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u252C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510\n\u2502 HIGH SEO +       \u2502 Pillar guides, original research, \u2502\n\u2502 HIGH GEO         \u2502 definitive \"What is X\" pages,     \u2502\n\u2502 (publish FIRST)  \u2502 data-driven trend roundups         \u2502\n\u251C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u253C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2524\n\u2502 HIGH SEO +       \u2502 How-to tutorials, comparison       \u2502\n\u2502 MEDIUM GEO       \u2502 pages (X vs Y), tool reviews       \u2502\n\u2502 (publish SECOND) \u2502                                    \u2502\n\u251C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u253C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2524\n\u2502 MEDIUM SEO +     \u2502 Thought leadership, expert          \u2502\n\u2502 HIGH GEO         \u2502 commentary, contrarian takes        \u2502\n\u2502 (publish THIRD)  \u2502 with data                           \u2502\n\u251C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u253C\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2524\n\u2502 BRAND BUILDING   \u2502 Behind-the-scenes, founder          \u2502\n\u2502 (supports both)  \u2502 stories, community content          \u2502\n\u2502 (publish FOURTH) \u2502                                    \u2502\n\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2534\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518\n```\n\n**Scoring criteria:**\n- **SEO potential** = search volume + keyword difficulty + search intent alignment\n- **GEO potential** = citability (contains quotable definitions, named frameworks, specific stats) + AI query match (answers questions AI platforms are asked)\n- **Pain alignment** from buyer research is the tie-breaker within each quadrant\n\nSort the content calendar by this priority matrix \u2014 highest-impact pieces publish in Month 1.\n\n### Step 2.5: Generate Definitive \"What is [Framework]?\" Page (FIRST PRIORITY)\n\nBefore generating any other pillar content, create ONE definitive page answering \"What is [Named Framework from Building Block 6]?\"\n\nThis is the **single highest GEO-value page** in your entire content library. When someone asks ChatGPT or Perplexity \"What is [Your Method]?\", this page is the canonical source they cite.\n\n**Requirements:**\n- H1: \"What is [Named Framework]? The Complete Guide\"\n- First paragraph: One-sentence quotable definition (AI-citable verbatim)\n- First 200 words: definition + origin story + specific stat + brand name\n- Body: how it works (step-by-step), who it's for, results/proof, FAQ\n- Citation magnets: at least 3 (the definition itself, a specific stat, a named sub-process)\n- Schema: FAQ schema + Article schema + HowTo schema (if step-by-step process)\n- Internal links: link to every pillar as \"the [Named Framework] applied to [topic]\"\n\nSave to `assets/[market-name]/content/pillar/what-is-[framework-slug].md` \u2014 this is published FIRST in the content calendar, before any other pillar.\n\n### Step 3: Pillar Content Generation (Subagent \u2014 0 searches)\nFor each remaining pillar, generate a 2,000-4,000 word guide:\n\n**First-200-Words Rule (MANDATORY):**\nThe first 200 words of every pillar page must contain:\n1. A specific stat or data point (from market intel research)\n2. The primary value proposition\n3. The brand/product name (from Name Lock Registry)\n4. A clear statement of what the reader will learn\n\nThis front-loads the information AI models extract for citations.\n\n**Citation Magnets (at least 2 per pillar):**\n- Named framework from Building Block 6 (e.g., \"The [Name] Method\")\n- Original statistic or data synthesis from market intel\n- Quotable definition that AI models can cite verbatim\n- Proprietary model or process diagram description\n\n**EEAT Signals:**\n- Author byline with credentials\n- \"Last updated: [date]\" prominently placed\n- Links to primary sources\n- Experience markers (\"Based on [X] clients/projects/years\")\n\n**Structure:**\n- H1: Primary keyword + compelling angle\n- H2s: Framed as questions (featured snippet optimization)\n- H3s: Specific sub-answers\n- Internal links to spoke pages (2-3 per pillar)\n- FAQ section at bottom (maps to FAQ schema)\n- **Image alt text:** All images use format `\"[keyword] \u2014 [description]\"` (e.g., `\"email marketing funnel \u2014 5-step conversion diagram\"`)\n\nSave each pillar to `assets/[market-name]/content/pillar/[slug].md`\n\n### Step 4: Spoke Page Generation (Subagent \u2014 0 searches)\nFor each spoke, generate 1,000-2,000 words:\n\n- Same first-200-words rule (stat + value prop + brand name)\n- Same citation magnet requirement (at least 1 per spoke)\n- Link back to parent pillar page\n- Link to 1-2 adjacent spokes (topic cluster interlinking)\n- H2/H3 as questions\n- Practical, actionable content derived from product modules\n- **Image alt text:** `\"[keyword] \u2014 [description]\"` format on all images\n\nSave each spoke to `assets/[market-name]/content/spokes/[slug].md`\n\n### Step 5: Schema Markup Generation\nGenerate JSON-LD schema files for each page:\n\n**Organization Schema** (site-wide):\n```json\n{\n  \"@context\": \"https://schema.org\",\n  \"@type\": \"Organization\",\n  \"name\": \"[Brand Name from Name Lock]\",\n  \"url\": \"[site URL]\",\n  \"description\": \"[from Building Blocks]\",\n  \"sameAs\": [\"[social profile URLs]\"]\n}\n```\n\n**Article Schema** (per pillar/spoke):\n```json\n{\n  \"@context\": \"https://schema.org\",\n  \"@type\": \"Article\",\n  \"headline\": \"[page title]\",\n  \"author\": {\"@type\": \"Person\", \"name\": \"[author]\"},\n  \"datePublished\": \"[date]\",\n  \"dateModified\": \"[date]\",\n  \"description\": \"[meta description]\"\n}\n```\n\n**FAQ Schema** (per page with FAQ section):\n```json\n{\n  \"@context\": \"https://schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\"@type\": \"Question\", \"name\": \"[Q]\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"[A]\"}}\n  ]\n}\n```\n\n**HowTo Schema** (if product has step-by-step process)\n**Product Schema** (for product/offer pages)\n\nSave to `assets/[market-name]/content/schema/[page-slug]-schema.json`\n\n### Step 6: Brand Signal Checklist & SEO Config\nGenerate:\n\n**robots.txt:**\n```\nUser-agent: *\nAllow: /\n\nUser-agent: GPTBot\nAllow: /\n\nUser-agent: PerplexityBot\nAllow: /\n\nUser-agent: ClaudeBot\nAllow: /\n\nUser-agent: Googlebot\nAllow: /\n\nSitemap: [site-url]/sitemap.xml\n```\n\n**sitemap.xml** \u2014 auto-generated list of all pages with lastmod dates\n\n**Brand Signal Checklist:**\n```\nBRAND SIGNAL CHECKLIST \u2014 [Brand Name]\n\n\u2610 Google Business Profile created and verified\n\u2610 Social profiles created (LinkedIn, Twitter/X, YouTube) with consistent NAP\n\u2610 robots.txt uploaded with AI crawler permissions\n\u2610 XML sitemap submitted to Google Search Console\n\u2610 XML sitemap submitted to Bing Webmaster Tools\n\u2610 NAP (Name, Address, Phone) consistent across all listings\n\u2610 Organization schema deployed on homepage\n\u2610 Twitter Card tags on all pages (twitter:card, twitter:title, twitter:description, twitter:image)\n\u2610 Author pages created with credentials\n\u2610 About page with EEAT signals\n```\n\nSave to `assets/[market-name]/content/seo-config/`\n\n### Step 7: Content Calendar\nGenerate a 6-month content calendar:\n\n```\nCONTENT CALENDAR \u2014 [Market Name]\n\nMONTH 1:\n  Week 1: PUBLISH \u2014 Pillar 1 + Spoke 1.1\n  Week 2: REPURPOSE \u2014 Run /content-repurpose on Pillar 1\n  Week 3: PUBLISH \u2014 Spoke 1.2 + Spoke 1.3\n  Week 4: AUDIT \u2014 AI visibility check (manual prompts below)\n\nMONTH 2:\n  Week 1: PUBLISH \u2014 Pillar 2 + Spoke 2.1\n  Week 2: REPURPOSE \u2014 Run /content-repurpose on Pillar 2\n  Week 3: PUBLISH \u2014 Spoke 2.2 + Spoke 2.3\n  Week 4: AUDIT \u2014 Run /seo-check (first monthly audit)\n\nMONTH 3:\n  Week 1: PUBLISH \u2014 Pillar 3 + Spoke 3.1\n  Week 2: REPURPOSE \u2014 Run /content-repurpose on Pillar 3\n  Week 3: ORIGINAL RESEARCH \u2014 Publish 1 data piece (aggregate pipeline data:\n           market intel stats, validation results, buyer survey findings).\n           This is your strongest GEO asset. Format as citable statistics\n           that other sites and AI models reference.\n  Week 4: AUDIT \u2014 Run /seo-check\n\nMONTHS 4-5:\n  [Continue pillar/spoke/repurpose pattern]\n  [Refresh cycle begins Month 4 \u2014 revisit Month 1 content for decay]\n\nMONTH 6:\n  Week 1: PUBLISH \u2014 Remaining spokes\n  Week 2: REPURPOSE \u2014 Final batch\n  Week 3: ORIGINAL RESEARCH \u2014 Second data piece (aggregated results,\n           updated stats, case study with specific numbers)\n  Week 4: AUDIT \u2014 Run /seo-check --mode deep (quarterly deep dive)\n```\n\nSave to `assets/[market-name]/content/content-calendar.md`\n\n### Step 8: AI Visibility Baseline\nGenerate prompt templates for manual AI citation checks:\n\n```\nAI VISIBILITY BASELINE \u2014 [Market Name]\n\nCHECK MONTHLY (5 minutes):\n\nChatGPT Prompts:\n  1. \"What is [named framework from Block 6]?\"\n  2. \"Best [solution category] for [target buyer]?\"\n  3. \"How to [primary pain point transformation]?\"\n\nPerplexity Prompts:\n  1. \"[Brand name] review\"\n  2. \"[Primary keyword] guide\"\n  3. \"Best [product category] [current year]\"\n\nGoogle AI Overview:\n  1. Search \"[primary keyword]\" \u2014 check if AI Overview appears, check if cited\n  2. Search \"[named framework]\" \u2014 check if brand is mentioned\n  3. Search \"[pain point] solution\" \u2014 check if content appears\n\nBing Copilot:\n  1. Ask \"[primary keyword] guide [current year]\"\n  2. Ask \"What is [named framework]?\"\n\nMeta AI:\n  1. Ask \"Best [solution category] for [target buyer]?\"\n\nTRACKING:\nDate: ___  ChatGPT: Y/N  Perplexity: Y/N  AI Overview: Y/N  Bing Copilot: Y/N  Meta AI: Y/N  Citation copy: ___\nDate: ___  ChatGPT: Y/N  Perplexity: Y/N  AI Overview: Y/N  Bing Copilot: Y/N  Meta AI: Y/N  Citation copy: ___\n```\n\nSave to `assets/[market-name]/content/ai-visibility-baseline.md`\n\n### Step 9: Save Everything and Update State\n\nUpdate pipeline-state.json with organic_growth section:\n```json\n{\n  \"organic_growth\": {\n    \"status\": \"content_engine_complete\",\n    \"content_engine\": {\n      \"status\": \"complete\",\n      \"completed_at\": \"[timestamp]\",\n      \"topic_clusters\": [N],\n      \"pillar_pages\": [N],\n      \"spoke_pages\": [N],\n      \"schema_files\": [N]\n    },\n    \"content_repurpose\": {\n      \"status\": \"pending\",\n      \"batches_completed\": 0\n    },\n    \"seo_checks\": {\n      \"last_check\": null,\n      \"next_check\": \"[date \u2014 30 days from now]\",\n      \"checks_completed\": 0\n    },\n    \"ai_visibility\": {\n      \"baseline_created\": true,\n      \"last_check\": null,\n      \"chatgpt_mentioned\": null,\n      \"perplexity_mentioned\": null,\n      \"ai_overview_appeared\": null\n    },\n    \"content_calendar\": {\n      \"months_planned\": 6,\n      \"current_month\": 1,\n      \"pieces_published\": 0,\n      \"pieces_repurposed\": 0\n    },\n    \"output_files\": [\n      \"assets/[market-name]/content/topic-cluster-map.md\",\n      \"assets/[market-name]/content/content-calendar.md\",\n      \"assets/[market-name]/content/ai-visibility-baseline.md\"\n    ]\n  }\n}\n```\n\n## Autonomy\nTier 1 \u2014 Full Auto for topic cluster research, content generation, schema generation.\nTier 2 \u2014 Notify & Proceed for presenting the content strategy and calendar.\nTier 2 \u2014 **Publish gate:** Content generation is Tier 1, but marking content as \"ready to publish\" (adding to the live site) requires user approval. Present each batch of generated content for review before it goes live. This prevents mass-producing AI content without human oversight.\nTier 3 \u2014 Recommend & Wait for topic cluster selection when pain points score similarly.\n\n## Output\nComplete content package in `assets/[market-name]/content/`. Topic cluster map, pillar pages, spoke pages, schema markup, SEO config, content calendar, AI visibility baseline.\n\n## Next Step\nRun `/content-repurpose` on the first pillar page \u2192 Run `/seo-check` at Month 1 Week 4 \u2192 Continue calendar cadence.";
//# sourceMappingURL=content-engine.d.ts.map