aeo-visibility

AEO — being citable, not just rankable

Classic SEO gets you ranked. AEO gets you quoted. The mechanics differ: answer engines extract self-contained claims from crawlable text, and they weight consistency of facts about an entity across the whole web.

1. Let the crawlers in — deliberately

• src/app/robots.ts decides this. Answer-engine crawlers include GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, PerplexityBot, Google-Extended, CCBot, Bytespider.
• Ask the user before changing this. "Be cited by AI" and "don't train on my content" are different goals with different bots: training crawlers (GPTBot, ClaudeBot, CCBot, Google-Extended) versus live search/citation crawlers (OAI-SearchBot, Claude-SearchBot, PerplexityBot). Blocking the training set while allowing the search set is a coherent position; blocking everything and expecting citations is not.
• Verify server-side rendering: answer-engine crawlers are far less reliable at executing JavaScript than Googlebot. Anything client-rendered may be invisible to them. In this starter, content is server-rendered and animations only animate — keep it that way.

2. llms.txt

A plain-markdown map of the site at /llms.txt for language models. Serve it from src/app/llms.txt/route.ts (a Route Handler returning text/plain) so it stays in sync with real routes rather than rotting as a static file.

# <Site name>
> One-sentence description of what the company does and for whom.

## Core pages
- [Services](https://example.com/services): what is offered, to whom
- [About](https://example.com/about): who the company is, founded, location

## Key facts
- Founded: 2019 · HQ: Berlin · Focus: <specifics>

Keep it factual and short. It is a summary for a machine, not a marketing page.

3. Structure content so it can be extracted

• Answer first. Lead each section with the direct claim in one or two sentences, then support it. Content that builds to a conclusion gets skipped.
• One idea per heading, and phrase headings as the questions people ask.
• Self-contained sentences. "Our approach is faster" is unusable out of context; "Textura ships marketing sites in four weeks" survives extraction.
• Concrete specifics — numbers, dates, named methods, prices where possible. Vague marketing language is unquotable.
• Comparison and definition content punches above its weight: "X vs Y", "What is X", pricing pages, and genuine FAQs.
• Mark FAQs up with FAQPage (see the schema-markup skill).