A page can rank and still never appear in an answer. The usual diagnosis is “we need more GEO.” Often the claim is smeared: a half-definition on the homepage, a metaphor in a newsletter, a third version on a book page, none of them a sentence a machine can lift without inventing you.
How answer engines select sources is the selection article: crawl, understand, extract, trust. This page is the architecture of the thing they would extract.
One claim, one URL
AEO is the craft of one URL. A direct answer near the top. Named entities. Visible sources. No invented FAQ schema.
If you cannot point at the sentence that owns the claim, you do not have a page. You have a theme.
Write the claim in one line. Put it on one address. Link the rest of the site to that address. Do not rewrite it six times in six tones and hope the engine picks the least wrong one.
That is also the first move in CITATION: a page worth quoting is discoverable, attributed, answer-shaped, evidenced, and actually used. Search eligibility is not enough. The engine lifts the first clean capsule it can verify.
A smeared claim, then one owner
Suppose the claim is: an AI agent holds a goal, uses tools, and continues across steps under a charter.
Smeared, it lives as a slogan on the homepage, a looser paragraph in a newsletter, and a third wording on a book page. None of them is the sentence. An engine that quotes you has to invent the short form.
Owned, it lives on What is an AI agent?. The homepage links there. The newsletter links there. The book page links there. The glossary capsule agrees. One URL. One first screen. The rest of the site is a path, not a remix.
That is architecture. Selection is a different job, already written.
Name the entity, do not make the machine guess
Attribution fails when the machine cannot tell who you are.
Give the person and the organization stable names. Repeat them. Point sameAs at the profiles you actually control. If you define a term, give it a DefinedTerm page with one definition, not a slogan.
Structured data can carry that identity. Google is explicit that markup does not guarantee a rich result and is not required for generative search. Use it to stop the engine inventing a second you. Do not use it as a citation spell.
Do not ship FAQPage for rich results. Ordinary FAQ rich results ended on 7 May 2026. A visible question-and-answer block can still help a reader. It is not a current rich-result tactic. The selection article already sources that.
llms.txt is a convenience file. It does not replace crawlable HTML. Do not treat it as a ranking lever.
The first screen is the capsule
A tired reader, and a machine, should be able to use the page without a scroll of throat-clearing.
- One sentence that states the claim, with its conditions.
- The named person or organization.
- The source a stranger could check.
- Then depth. Length is allowed. Hiding the claim in paragraph nine is not.
If the first screen is a brand manifesto, you asked the engine to write your definition for you.
Gates before lift
A capsule that cannot survive a fact-check is not architecture. It is a faster way to be wrong in someone else’s answer.
BooksOS is the live production system in The Agentic Author: evidence, quotation, voice, figures, bilingual parity, typesetting, and a refusal to ship below threshold. Agents draft. Gates decide. If a claim would fail those gates, do not put it in the first screen and call it AEO.
The Findability Engine is the book that treats this as an operating system: identity, evidence, retrieval-ready content, proof assets. It is in production, English first. It is not for sale. The standard is already how this site is built: one glossary row, one framework URL, one person sameAs list, no manuscript books in the sitemap.
GEO is the system around the page. This article is the page.
A fifteen-minute audit
Pick the claim you most want cited.
| Step | Pass looks like | Fail looks like |
|---|---|---|
| 1. One sentence | You can read it aloud | A theme, a vibe, three versions |
| 2. One URL | You paste a single address | You need two tabs |
| 3. Named entity | sameAs resolves | 404, or a nickname the rest of the web does not use |
| 4. Checkable source | A stranger can open it | “Leading study,” no link |
| 5. Schema honesty | Identity markup, no FAQPage for a dead rich result | FAQ schema as a citation spell |
If step 2 or 4 is blank, stop buying “GEO retainers.” Fix the page. The engine cannot lift what you refused to state once.