seo-aeo-geo

Name: seo-aeo-geo
Author: rampstackco/claude-skills

$npx mdskill add rampstackco/claude-skills/seo-aeo-geo

Optimize content for AI-driven search and LLM citations.

User wants content cited by AI assistants or in AI overviews.
Depends on llms.txt, structured data, and extraction-friendly formats.
Analyzes content structure, clarity, and relevance for AI extraction.
Provides actionable recommendations for llms.txt and content optimization.

SKILL.md

.github/skills/seo-aeo-geoView on GitHub ↗

---
name: seo-aeo-geo
description: "Optimize content and site structure for AI-driven search experiences including AI overviews, large language model citations, generative answer engines, and AI assistants. Use this skill whenever the user wants to optimize for AI search, get cited by language models, appear in AI overviews, build llms.txt, structure content for AI extraction, or future-proof their SEO for the shift from blue links to AI answers. Triggers on AEO, GEO, AI search, AI SEO, AI overview, generative search, LLM optimization, llms.txt, AI citation, ChatGPT search, Perplexity, Gemini, Claude search, AI assistant optimization, answer engine. Also triggers when the user expresses concern about AI eating their organic traffic or wants to understand how to remain visible as search shifts."
category: seo-foundation
catalog_summary: "AI search optimization, llms.txt, extraction-friendly content"
display_order: 7
---

# AEO and GEO

Answer Engine Optimization (AEO) and Generative Engine Optimization (GEO). Make content discoverable, extractable, and citable by AI search experiences.

This skill encodes principles. AI search products evolve fast. The principles age slower than the products.

---

## When to use

- Optimizing content for AI overviews and generative answer engines
- Building or updating llms.txt
- Structuring content so AI assistants can extract and cite it correctly
- Future-proofing a site as search shifts from blue links to AI answers
- Auditing whether existing content is AI-friendly
- Adding signals that help AI assistants identify the site as a trustworthy source

## When NOT to use

- Traditional on-page or technical SEO (use `seo-onpage` or `seo-technical`)
- Keyword research (use `seo-keyword`)
- Off-page authority and link building (use `seo-offpage`)

This skill stacks on top of those. Strong AEO/GEO requires strong fundamental SEO underneath.

---

## Required inputs

- The site or page to optimize
- The topic area or query types AI should cite the site for
- Access to inspect rendered HTML and structured data

---

## The framework: 5 layers

AI search visibility comes from five stacked layers. Each layer compounds.

### 1. Extractable content structure

AI systems extract facts and pull citations from content. Make extraction easy.

- **Direct answers.** Open major sections with a definitive 1 to 3 sentence answer to the question that section addresses. AI extracts the first answer it sees.
- **Question-headers.** Use H2s and H3s phrased as questions when natural. Mirrors how people prompt AI.
- **Atomic facts.** When stating a fact, state it once, clearly, with the supporting context next to it. AI struggles when claims are spread across paragraphs.
- **Tables and lists.** AI parses these reliably. Use them for comparisons, specs, steps, and data.
- **Definitions early.** When introducing a concept, define it inline. Do not assume the reader (or AI) saw a definition three pages ago.
- **Numbered steps.** For procedural content, number every step. Avoid prose disguised as instructions.

### 2. Citation worthiness

AI cites sources it considers authoritative. Earn that consideration.

- **Original data.** Surveys, studies, proprietary research, internal benchmarks. AI prefers primary sources over restatements.
- **Specific numbers.** "Roughly 40 percent" beats "many." Specific stats with sources beat round-number generalizations.
- **Named experts.** Author bios with credentials, links to professional profiles, schema-marked-up Person entities.
- **Date stamps.** Publication date AND last-updated date, both visible AND in schema. AI heavily weights recency for time-sensitive queries.
- **Methodology disclosure.** When stating a finding, briefly note how it was reached. AI rewards transparency.
- **Citations of other sources.** Linking to authoritative sources you used builds reciprocal credibility.

### 3. Structured data depth

Schema is how you speak machine-readable language. AI assistants parse it heavily.

- **Schema.org types** appropriate to content (Article, FAQPage, HowTo, Recipe, Product, Organization, Person, LocalBusiness, etc.)
- **Required AND recommended properties** filled in (most sites only fill required, leaving signal on the table)
- **Person schema** for authors, with `sameAs` links to verifiable profiles
- **Organization schema** on the homepage with logo, contact, social links
- **FAQPage schema** for content with genuine question-answer pairs
- **HowTo schema** for procedural content
- **BreadcrumbList schema** site-wide
- Validates in Schema.org Validator AND Rich Results Test (some properties differ)

### 4. AI-readable accessibility

Beyond traditional SEO, AI tools need access patterns of their own.

- **llms.txt at the site root.** A markdown file at `/llms.txt` describing the site's content, key URLs, and what topics the site covers. See [`references/llms-txt-guide.md`](references/llms-txt-guide.md).
- **llms-full.txt** (optional) - a complete content dump for AI training and context, if the site permits it.
- **robots.txt allowing AI crawlers.** Decide explicitly which AI crawlers to allow (GPTBot, ClaudeBot, Google-Extended, PerplexityBot, etc.) or disallow. Do not block by default if visibility matters.
- **Clean HTML semantics.** Semantic tags (`article`, `section`, `nav`, `main`) help AI parse structure.
- **Avoid client-side-only rendering for critical content.** Many AI crawlers render less reliably than Googlebot.

### 5. Real-world entity signals

AI builds knowledge graphs and prefers entities with multiple consistent signals.

- **Wikipedia entry** if the brand or person qualifies for notability (do not force this; it requires genuine notability)
- **Wikidata entry** for the entity, with consistent properties
- **Consistent NAP** (Name, Address, Phone) across all citations
- **Brand mentions across multiple authoritative sources.** AI cross-references entity claims across the open web.
- **Social profile schema** linking owned profiles via `sameAs` properties
- **Reviews and reputation signals.** Aggregate ratings on Google Business, Trustpilot, industry-specific review sites where applicable

---

## Workflow

1. **Audit current state.** Run the 5-layer framework against the existing site. Score each.
2. **Identify the priority queries.** What questions should AI cite this site for? List 10 to 20.
3. **Test current AI visibility.** Query each of the major AI products (those relevant to the audience) with the priority questions. Note which sources they cite.
4. **Identify gaps.** Is the site cited? On which queries? Why does it lose to the cited sources?
5. **Layer-by-layer plan.**
- Fix extractable structure on top 20 priority pages
- Add citation-worthy signals (original data, expert authorship, methodology)
- Deepen schema implementation
- Build/update llms.txt
- Strengthen entity signals
6. **Implement and re-test.** AI products update frequently. Re-test priority queries quarterly.

---

## Failure patterns

- **Treating AEO/GEO as separate from SEO.** Strong fundamental SEO is a prerequisite. AI cites pages, not magic.
- **Stuffing FAQ schema on pages that have no genuine FAQs.** Search engines and AI alike penalize manufactured FAQ blocks.
- **Hiding key content behind heavy JavaScript.** AI crawlers render less reliably. Server-render or pre-render critical content.
- **Optimizing for one AI product only.** Different products use different ranking and citation logic. Optimize for the principles, not for one product's quirks.
- **Ignoring entity strength.** Content alone, with no real-world entity signals, will not get cited reliably for branded or expertise-related queries.
- **Treating llms.txt as a magic bullet.** It helps, but it is one of many signals.
- **Static optimization.** AI products evolve faster than search algorithms historically did. Re-audit at least quarterly.

---

## Output format

Default output is a markdown plan at `aeo-geo-strategy.md`. Structure:

1. Current AI visibility audit (which queries cite the site, which do not)
2. 5-layer scorecard
3. Priority queries (the 10 to 20 the site should be cited for)
4. Layer-by-layer remediation plan
5. Implementation roadmap
6. Re-test schedule (quarterly)

---

## Reference files

- [`references/llms-txt-guide.md`](references/llms-txt-guide.md) - How to write a useful llms.txt, with examples.
- [`references/extraction-friendly-patterns.md`](references/extraction-friendly-patterns.md) - Content patterns that AI extracts cleanly, with before/after examples.

More from rampstackco/claude-skills

Skill	Description
ads-creative-development	How to produce ad creative that converts at performance scale. Hook patterns, format selection, video pacing, variation systems, sequential testing methodology, fatigue detection, brand-voice alignment without conversion dilution, and platform-specific creative norms. Triggers on ad creative, ad design, hook patterns, ad video pacing, creative testing, ad variations, creative refresh, creative fatigue, refresh ad creative, video ads for Meta, TikTok creative, LinkedIn ad creative, ad asset library. Also triggers when a team is producing creative at scale, planning a creative test cycle, or auditing why creative is not converting.
ads-performance-analytics	How to read paid media dashboards without fooling yourself. Attribution models, platform reporting quirks, multi-platform reconciliation, ROAS vs LTV horizon traps, statistical noise in performance metrics, incrementality testing, and the failure modes that produce expensive lessons. Triggers on read paid media dashboard, attribution analysis, ROAS vs LTV, multi-platform reconciliation, ad incrementality, geo holdout, conversion lift study, ghost bidding, paid media reporting, board-deck paid media metrics, blended CAC, MMM, MTA, last-click attribution. Also triggers when a marketer is about to scale, kill, or rebudget a campaign based on platform metrics, or when reconciling platform reports against warehouse revenue.
after-action-report	Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.
ai-content-collaboration	How humans and AI compose in content workflows. Where AI legitimately participates, where humans must own, hybrid workflow patterns, voice ownership preservation, the AI slop problem, disclosure and transparency, team calibration, and the ethics of intellectually honest AI-assisted content production. Triggers on AI content workflow, AI-assisted writing, hybrid content production, AI in editorial, AI slop, AI disclosure, AI usage policy, AI content ethics, voice preservation with AI, team AI calibration. Also triggers when content feels generic despite quality tools, when team AI usage has drifted into inconsistency, or when a regulated or trust-sensitive context requires explicit AI policy.
analytics-strategy	Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement. Triggers on analytics strategy, measurement plan, event taxonomy, tracking plan, KPI framework, dashboard design, north star metric, attribution model, conversion tracking, GA4 setup, Mixpanel setup, analytics audit. Also triggers when the user has data but no clear way to use it, or wants to make decisions but doesn't know what to track.
art-direction	Direct visual and creative work for campaigns, photography, illustration, video, and branded experiences. Use this skill whenever the user wants to brief a photographer, direct illustrators, plan a creative campaign, develop visual concepts, write a creative direction document, or evaluate creative work for fit. Triggers on art direction, photo brief, photography brief, illustration brief, campaign concept, creative concept, visual direction, mood board, look and feel, visual treatment, video direction. Also triggers when the user has approved brand identity but needs to extend it into specific creative deliverables.
backup-and-disaster-recovery	Plan and run backups, set recovery objectives, and run disaster recovery drills. Use this skill when defining RPO/RTO targets, designing backup architecture, deciding what to back up and how often, planning for full-region or platform outages, or running a restoration drill. Triggers on backup, restore, RPO, RTO, disaster recovery, DR, business continuity, what if the database is gone, what if our hosting goes down, recovery drill, ransomware planning. Also triggers when an incident reveals a gap in restoration capability.
beta-program-management	Running closed and open betas that produce real signal. Beta participant selection, structured feedback collection, beta-to-GA decision criteria, and the difference between soft-launch (no structure, no signal), kitchen-sink (everyone in, no actionable feedback), and structured beta (calibrated cohort, intentional feedback loops, clear graduation criteria). Triggers on beta program, alpha test, beta cohort, beta participant, beta feedback, beta to GA decision, design partner, early access program, closed beta, open beta, RC release. Also triggers when a feature is approaching launch and the team needs structured pre-GA validation, when prior betas produced noise rather than signal, or when the team has soft-launched before but wants more structured feedback this time.
brand-archetype-system	Apply pre-composed aesthetic archetype defaults to jumpstart brand design work covering color, typography, layout, voice, and imagery direction. Use this skill whenever the user wants a starting point for brand visual and verbal direction, references a brand they want to design near (for example 'something like Stripe' or 'editorial like Linear'), needs to converge faster from many directions to one, or wants known-good defaults for a specific industry vertical. Triggers on archetype, design archetype, brand archetype, near to (brand), in the style of, similar aesthetic, design starting point, brand template, vertical-typical, industry-typical. Also triggers when the user has a brief and wants to map it to a known aesthetic family rather than design from first principles.
brand-discovery	Run upstream brand discovery covering audience research, competitive landscape, category dynamics, problem space, and positioning territory exploration. Use this skill at the very start of a brand or website project when the user needs to understand who they're for, who they compete with, what the audience actually needs, and where the brand could plausibly stand. Triggers on brand discovery, audience research, market research, competitive scan, category research, customer research, who is this for, who are we, positioning research, intake, kickoff. Also triggers when a creative brief is requested but the upstream inputs (audience, competitors, problem space) are not yet clear.