From rad-seo-optimizer
AEO, AI visibility, AI search optimization, generative engine optimization, LLM seeding, AI citations, answer engine optimization, brand presence in ChatGPT/Perplexity/Google AI Overviews. This skill optimizes the user's OWN content structure and distribution for AI-extractability. It does NOT measure actual AI citation rates — that requires direct AI-platform API integration (Path B).
How this skill is triggered — by the user, by Claude, or both
Slash command
/rad-seo-optimizer:aeo-optimizer [brand name or URL] [--non-interactive] [--resume <run-id>][brand name or URL] [--non-interactive] [--resume <run-id>]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Make the target brand's content more extractable, recommended, and accurately represented by AI search engines. This skill owns what you can actually *do* about AEO — reformat your content for AI extractability, fix consistency across your owned profiles, seed authoritative sources, and build co-citation patterns. It does NOT pretend to measure how often ChatGPT/Perplexity/Gemini cite you, beca...
Make the target brand's content more extractable, recommended, and accurately represented by AI search engines. This skill owns what you can actually do about AEO — reformat your content for AI extractability, fix consistency across your owned profiles, seed authoritative sources, and build co-citation patterns. It does NOT pretend to measure how often ChatGPT/Perplexity/Gemini cite you, because that measurement requires those platforms' APIs (Path B).
Traditional SEO gets a site ranked on Google. AEO gets the brand recommended by AI. When a user asks ChatGPT "What's the best project management tool?" or Perplexity "Compare CRM platforms" — AEO determines whether the brand appears, how it is described, and whether it is positioned favorably. This skill produces the content patterns and distribution plan that tend to earn those citations. Whether they actually materialize requires separate measurement.
Works identically on current Opus / Sonnet / Haiku models. Opus/Sonnet should batch reference loads + multi-page content Reads + parallel WebSearch for consistency checks into parallel bursts. Haiku may follow phase order sequentially if parallel batching misbehaves.
Read references/CAPABILITIES.md before running. Core facts:
--non-interactive — Skip user-approval gates. Produce best-effort output, commit artifacts, emit trailing JSON with awaiting_user_review items.--resume <run-id> — Load .seo/state/<run-id>.json and continue from the last saved phase.Save state to .seo/state/<run-id>.json at these transitions: after Phase 0 (crawl access gate), after Phase 1 (structure audit), after Phase 3 (consistency audit), after Phase 4 (content conversion), after Phase 5 (co-citation map), after output plan.
Checkpoint schema (shared with other rad-seo multi-phase skills):
{
"run_id": "string",
"skill": "aeo-optimizer | full-seo-audit | competitor-intelligence | content-strategist",
"phase": "string",
"started_at": "ISO-8601",
"last_saved": "ISO-8601",
"model": "opus | sonnet | haiku",
"target": "string — brand name or URL",
"phase_outputs": {},
"measurement_gaps": ["string"],
"awaiting_user_review": ["string"]
}
Before optimizing content for AI extraction, verify AI systems can fetch it at all.
Run the deterministic check (knowledge in references/ai-crawl-access.md):
python scripts/audit-ai-access.py --origin https://example.com --check-fetch --json
Gate logic:
This replaces the fabricated "AI Visibility Scorecard" from v1.x. Instead of pretending to query ChatGPT/Perplexity/Gemini (which WebSearch cannot actually do), this phase scores the user's own content structure on observable signals that correlate with AI citation: question headings, direct-answer leads, quotable stats, FAQ schema, comparison tables, semantic chunking.
Target for audit:
Score each page on a 0-10 scale:
| # | Dimension | Observable Signal |
|---|---|---|
| 1 | Question-Format Headings | Ratio of H2s phrased as questions / total H2s |
| 2 | Direct-Answer Leads | First 1-2 sentences after each heading directly answer the implied question |
| 3 | Quotable Stats / Bolded Data | Presence of specific numbers + bold formatting or <strong> on key claims |
| 4 | FAQ Schema Presence | Valid FAQPage JSON-LD on pages with Q&A structure (an AI-parsing aid only — Google retired FAQ rich results entirely in May 2026; never promise rich-result appearance) |
| 5 | Comparison / Structured Data | Tables, feature matrices, pro/con lists |
| 6 | Semantic Chunking | Short paragraphs (2-4 sentences), logical subsection density, not wall-of-text |
Tiers (structural readiness, NOT actual AI visibility):
| Score | Tier | Interpretation |
|---|---|---|
| 0-12 | Illegible to AI | Wall-of-text, no structural signals — AI would struggle to extract anything |
| 13-24 | Partially extractable | Some structure; AI could extract a few quotes but not full answers |
| 25-36 | Extractable | Structure supports most extraction; add FAQ schema + bold stats to push higher |
| 37-48 | Highly extractable | Most signals present; content is ready for AI to cite cleanly |
| 49-60 | AI-native | Content is structurally optimal for AI extraction — actual citation depends on authority + consensus (Phases 2-8) |
references/CAPABILITIES.md)For each page, identify:
These findings become the Phase 4 conversion queue.
Evidence basis: the strongest published result on generative-engine visibility (Princeton GEO study, KDD 2024, ~10k queries) found that adding statistics, quotations, and source citations lifted visibility ~30-40%, while keyword stuffing did nothing — which is why dimensions 2-3 weight direct answers and quotable data. Industry citation studies converge on the same signals plus freshness and self-contained chunks (AI Mode retrieves at passage level via query fan-out, not page level).
AI models learn from the open web. Control where and how brand information appears to influence what LLMs absorb.
Publish brand-relevant content on these platforms, ordered by observed LLM training influence (exact weight varies by model and version, but the relative order is well-observed):
| Priority | Platform | Why It Matters | Action |
|---|---|---|---|
| 1 | The Brand Website | Primary source of truth. Must be crawlable, well-structured, fast. | Ensure clean HTML, proper schema markup, no JS-only rendering. |
| 2 | Wikipedia / Wikidata | High-authority factual source for most LLMs. | Create or improve the Wikipedia page (only if notability criteria are met). Add Wikidata entity. |
| 3 | Heavily weighted in many LLM training corpora. Authentic discussions. | Engage genuinely in relevant subreddits. Never astroturf. | |
| 4 | Stack Overflow / Quora | Q&A format is ideal for LLM extraction. | Answer questions where your product is genuinely the solution. |
| 5 | Medium / Substack / LinkedIn | Long-form platforms LLMs crawl regularly. | Publish thought leadership, case studies, tutorials. |
| 6 | Industry Publications | Authoritative third-party validation. | Guest posts, contributed articles, expert commentary. |
| 7 | Review Platforms (G2, Trustpilot, Capterra) | LLMs use reviews for sentiment and feature extraction. | Actively collect reviews. Respond to all reviews. |
| 8 | GitHub | Critical for developer/technical products. | Maintain active repos, quality READMEs, community engagement. |
| 9 | News Sites | Recency signal. LLMs with web access pull recent news. | Digital PR, press releases, newsworthy launches. |
These content formats tend to be disproportionately extracted and cited by LLMs:
1. Structured "Best Of" Lists — Always include testing methodology to establish authority.
2. Comparison Tables — LLMs extract tabular data cleanly.
3. FAQ-Style Content — Q&A is training data gold:
## What is [Brand]?
[Brand] is [direct 1-sentence definition]. It [key differentiator].
## How much does [Brand] cost?
[Brand] pricing starts at [price] for [tier]. [Additional detail].
## How does [Brand] compare to [Competitor]?
[Brand] excels at [strengths] while [Competitor] is better for [their strengths].
4. Original Data and Statistics — Make statistics bold and quotable:
"X% of teams using [Brand] reported a Y improvement in [metric]" (Only publish numbers you've actually measured. Fabricated statistics damage long-term authority.)
5. Free Tools, Calculators, Templates — Utility content earns natural mentions and links.
6. Branded Strategies with Memorable Names — Coin a methodology with a name. Example: "The RAPID Framework for Content Optimization." LLMs remember named frameworks.
AI models recommend brands when multiple independent sources agree on the same facts. Inconsistency creates uncertainty, and uncertain LLMs hedge or omit.
Check that the following information is identical across all platforms:
| Data Point | Sources to Check |
|---|---|
| Company name and spelling | Website, social profiles, directories, Wikipedia |
| Founding date | About page, Crunchbase, LinkedIn, Wikipedia |
| Product description | Homepage, G2, Capterra, LinkedIn, press releases |
| Pricing | Pricing page, G2, Capterra, review sites |
| Feature list | Product pages, comparison sites, documentation |
| Leadership / founders | About page, LinkedIn, Crunchbase, press mentions |
| Company size / metrics | About page, LinkedIn, Crunchbase, press releases |
| Contact information | Website, Google Business, directories |
| Category / industry | All profiles and listings |
For every inconsistency found:
Transform existing content so LLMs can extract clean, quotable answers. Queue comes from Phase 1 findings.
Rule 1: Convert H2 Headings to Question Format
BEFORE: ## Our Pricing Plans
AFTER: ## How Much Does [Brand] Cost?
Rule 2: Lead Every Section with a Direct Answer
BEFORE:
## How Much Does Acme Cost?
When it comes to choosing the right plan, there are many factors to consider.
Our flexible pricing is designed to scale with your needs...
AFTER:
## How Much Does Acme Cost?
Acme costs $29/month for individuals and $99/month for teams of up to 10.
Enterprise pricing starts at $499/month with custom configuration.
Rule 3: Make Statistics Bold and Quotable
**Acme processes over 2 million requests per day with 99.97% uptime.**
(Only publish numbers you can actually verify.)
Rule 4: Add FAQ Schema Markup — generate valid FAQPage JSON-LD for any Q&A content.
Rule 5: Build Comparison Tables for pricing, features, brand-vs-competitor.
Rule 6: Use Semantic Chunking — paragraphs 2-4 sentences, descriptive headings, bulleted lists for features, numbered lists for steps.
Rule 7: Add Speakable Schema for voice-assistant content:
{
"@context": "https://schema.org",
"@type": "WebPage",
"speakable": {
"@type": "SpeakableSpecification",
"cssSelector": [".summary", ".key-answer", ".product-description"]
}
}
# Audit a page for AI-extractability
claude "Read [URL/FILE] and score it for AI extractability using the Phase 1 six
dimensions. Check: heading format, answer directness, quotable stats,
schema markup, paragraph length, and semantic structure. Provide specific rewrites."
# Bulk convert headings to question format
claude "Scan all content files in [DIRECTORY]. Convert every H2 that isn't a
question into question format. Preserve meaning."
# Add FAQ schema to existing content
claude "Read [FILE] and generate FAQPage schema markup based on the existing Q&A
content. Output the JSON-LD script tag."
LLMs associate brands that appear together frequently. Get the target brand mentioned alongside industry leaders to inherit authority signal.
claude "Search for '[BRAND]' and identify which other brands it is most
frequently mentioned alongside in review sites and comparison articles.
Map the observable co-citation network. Identify gaps where [BRAND]
should appear but doesn't. Note: this is observable from WebSearch —
NOT a measurement of what AI chat engines actually say, which would
require direct platform API integration."
For detailed phase-by-phase execution steps for Phases 6-8, consult references/aeo-phases.md.
Each AI platform has different data sources and ranking signals. Optimize for Google AI Overviews (structured data + top-10 rankings), ChatGPT (high-authority factual sources + Reddit + training data), Perplexity (real-time web search + citations), Claude (depth + original research), and Microsoft Copilot (Bing index + social signals).
For detailed platform-by-platform signal tables and audit commands, consult references/aeo-phases.md.
Optimize visuals for AI interpretation: real product screenshots, descriptive full-sentence captions, keyword-rich alt text, infographics with embedded text, video transcripts.
For detailed image optimization rules and code examples, consult references/aeo-phases.md.
Systematic content distribution to maximize AI training data coverage across UGC platforms, digital PR, affiliate/review coverage, expert quote placement, and content syndication.
For detailed distribution tactics and platform-specific strategies, consult references/aeo-phases.md.
After completing all phases, generate a prioritized action plan organized by time horizon.
{
"aeo_complete": true,
"run_id": "string",
"target": "string",
"phase_1_extractability": {
"pages_audited": 0,
"avg_score": 0,
"tier": "illegible | partially | extractable | highly | ai_native",
"conversion_queue_size": 0
},
"phase_3_consistency": {
"sources_checked": 0,
"inconsistencies_found": 0
},
"phase_4_conversions": {
"pages_rewritten": 0
},
"action_plan_path": "string",
"measurement_gaps": [
"actual AI citation rates require Path B AI-platform API integration",
"brand sentiment scoring across AI chat responses requires direct platform APIs",
"accuracy measurement of AI responses requires querying each AI chat interface directly"
],
"escalation_required": false,
"awaiting_user_review": ["string"]
}
Track AEO progress with:
references/CAPABILITIES.md). Without that, you're measuring structural readiness to be cited, not actual citations.Metrics you CAN track:
Metrics you CANNOT track without Path B:
npx claudepluginhub radorigin-llc/rad-claude-skills --plugin rad-seo-optimizerProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.