aeo
Answer Engine Optimization (AEO): optimize content to be cited by LLMs (ChatGPT, Claude, Perplexity, Gemini, Copilot) when they answer user questions. Use when designing content strategy for the LLM-citation era, auditing existing content for LLM citability, structuring Q&A schema for AI surfaces, tracking which content gets cited and where, or measuring AEO performance against competitors. Distinct from our `ai-seo` skill — that one is about ranking in AI search results (Perplexity, Google AI Overviews); this one is about being the source LLMs cite in their answers.
What this skill does
# Answer Engine Optimization (AEO) End-to-end practice of optimizing content to be cited by LLMs when they generate answers. Covers the technical foundations (how LLMs select sources), content structuring patterns (Q&A schema, citation-worthy patterns), measurement (which content gets cited, by which LLM, how often), and the strategic positioning that differentiates AEO from traditional SEO and from AI-SEO. This skill is provider-aware but provider-agnostic: works for content optimized for ChatGPT, Claude, Perplexity, Gemini, Copilot, and emerging AI surfaces. --- ## When to use this skill | Situation | Skill applies | |-----------|---------------| | Designing content strategy that targets LLM citation | Yes — start with **AEO fundamentals** | | Auditing existing content for LLM citability | Yes — `scripts/aeo_content_auditor.py` | | Adding Q&A schema to content | Yes — `scripts/schema_qa_generator.py` | | Tracking which content gets cited by LLMs | Yes — `scripts/citation_extractor.py` | | Choosing between AEO and traditional SEO investment | Yes — see **AEO vs SEO vs AI-SEO** | | Ranking in Perplexity / Google AI Overviews | Use `marketing/ai-seo` | | Traditional SEO (rank in Google search results) | Use `marketing/seo-specialist` | --- ## AEO vs SEO vs AI-SEO Three distinct (but overlapping) practices. Confusing them leads to wasted investment. | Practice | Optimizes for | Surface | Success metric | |----------|---------------|---------|----------------| | **Traditional SEO** | Google / Bing rankings | SERPs (organic blue links) | Position, clicks | | **AI-SEO** | AI search engines | Perplexity, Google AI Overviews, You.com | Position in AI search results, traffic from citations | | **AEO (this skill)** | LLM citation in answers | ChatGPT, Claude, Gemini, Copilot answers | Citation rate, brand mention in LLM outputs | ### Strategic positioning For most B2B brands: - **Traditional SEO**: still 50-70% of organic traffic. Don't abandon. - **AI-SEO**: emerging 10-20% of search-driven engagement. Growing fast. - **AEO**: 5-15% of LLM-mediated user discovery. Largest growth potential. Optimize content for all three simultaneously; the techniques substantially overlap. --- ## The AEO funnel Users find brands through LLMs in a different funnel than search: ``` Traditional search: AEO funnel: 1. User types query 1. User asks LLM a question 2. SERPs show ~10 results 2. LLM generates answer 3. User clicks one 3. LLM cites N sources (1-10) 4. User reads page 4. User reads answer; may click cited source 5. User converts 5. User attributes answer to LLM (less so to cited brand) ``` Key implications: - **Citation is the new click.** When LLM cites your content, you don't always get a visit — but you get attribution. - **Brand-as-source becomes the goal.** Even without click, being cited builds brand association. - **Quality > volume.** LLMs cite a small number of sources; quality of citation matters more than ranking position. - **Trust signals matter more.** LLMs avoid citing low-authority sources. See [references/aeo-fundamentals.md](references/aeo-fundamentals.md) for the deep mechanics of how LLMs select sources, the citation models per provider, and the trust signals that drive selection. --- ## The 5 content patterns that get cited After analysis of LLM citation behavior, five content patterns dominate: ### Pattern 1: Definitional content with clear claims LLMs cite sources for definitions, facts, and short claims. Pages that answer "What is X?" with a clean 2-3 sentence definition followed by elaboration get cited often. **Structure:** ``` [Term] is [crisp definition in 1-2 sentences]. [Elaboration with context and nuance — 1-3 paragraphs]. [Related concepts / scope / boundaries — optional]. ``` ### Pattern 2: Comparative tables LLMs use tables to extract comparisons. Markdown tables in published content (or HTML equivalents) get cited when users ask "X vs Y." ```markdown | Feature | Product A | Product B | |---------|-----------|-----------| | Price | $X | $Y | | Speed | Z ms | W ms | | Support | 24/7 | Business hours | ``` ### Pattern 3: Step-by-step procedural content "How to [task]" content with explicit numbered steps. LLMs reproduce procedural steps; the cited source becomes the authoritative reference. ### Pattern 4: Statistics + data with sources LLMs cite content that provides numerical facts with attribution. "According to [your study], X% of [thing] does Y" is repeatable and citable. ### Pattern 5: Lists with explanations "Top N approaches to X" with each item explained gets cited when users ask comparative or enumeration questions. See [references/llm-content-structuring.md](references/llm-content-structuring.md) for deep patterns including FAQ schema, citation hooks, voice-search optimization, and LLM-readable structure markers. --- ## Quick start 1. **Audit existing content**: `python3 scripts/aeo_content_auditor.py --path ./content` 2. **Add Q&A schema to high-value pages**: `python3 scripts/schema_qa_generator.py --content article.md` 3. **Track citations from competitors**: `python3 scripts/citation_extractor.py --query "What is X?" --brand "Your Brand"` 4. **Iterate**: monthly content review with AEO scoring --- ## End-to-end workflows ### Workflow: AEO content strategy from scratch 1. **Identify target queries** — what questions do potential customers ask LLMs about your category? 2. **Audit competitor citations** — which brands get cited for those queries? `scripts/citation_extractor.py` 3. **Audit your existing content** — score current content for AEO patterns: `scripts/aeo_content_auditor.py` 4. **Prioritize 10-20 high-value pages** — those that should be the canonical source 5. **Restructure per AEO patterns** — definitional content, tables, step-by-step, statistics 6. **Add structured data** — `scripts/schema_qa_generator.py` generates FAQ schema 7. **Build authority signals** — backlinks, citations, mentions 8. **Monitor monthly** — track citation rate trend ### Workflow: Audit individual content piece 1. Run `scripts/aeo_content_auditor.py --path article.md --format markdown` 2. Review per-pattern scoring (5 patterns above) 3. Identify gaps: missing definition, no table, no clear steps, no stats, no list 4. Restructure to add 2-3 missing patterns 5. Add FAQ schema with `scripts/schema_qa_generator.py` 6. Re-audit to confirm improvements ### Workflow: Competitive citation analysis 1. Identify 10-20 key queries in your category 2. Query each LLM (ChatGPT, Claude, Perplexity, Gemini) with those questions 3. Record citations + brands mentioned 4. Analyze: which brands dominate? what content do they have? 5. Identify white-space queries (no clear dominant source yet) 6. Prioritize content creation for white-space queries ### Workflow: Measure AEO performance 1. **Citation rate**: % of queries where your brand is cited (target: 30%+ for category leaders) 2. **Brand mention rate**: % of queries where your brand is mentioned (cited or not) 3. **Source quality**: are you cited as primary source or supporting? 4. **Click-through from citations**: traffic attributable to LLM citations (requires source tracking) 5. **Voice tracking**: how is your brand characterized (positive / neutral / negative attributes) See [references/citation-tracking-and-measurement.md](references/citation-tracking-and-measurement.md) for measurement methodologies, attribution challenges, and competitive benchmarking. --- ## Common AEO failures - **Optimizing only for Google SERP**: misses the LLM citation surface entirely - **Generic content without specific claims**: LLMs prefer specific, factual content over generic explanation - **No structure markers** (headings, lists, tables): LLMs can't extract specific information - **No FAQ schema**: missed opportunity for Q&A surfacing in AI Overviews - **Stuffed keyword content**: LLMs prefer natural languag
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".