Thesis
Generative engines cite sources that are retrievable, self-contained and unambiguous — not simply the highest-ranking pages.
Citation happens after retrieval, not after ranking
A generative engine answers a question in stages. It interprets the question, retrieves a set of candidate passages, composes an answer from them, and attributes that answer to the sources it used. Ranking influences which documents are available to the retrieval step. It does not decide which passage gets quoted.
This is why a page can hold a strong classical search position and still never appear in an AI answer. The page was reachable. The passage inside it was not usable.
Three properties make a passage usable
A passage is retrievable when a crawler can reach it, render it and read it as text. Content locked behind client-side rendering, interaction or access controls fails at this step regardless of quality.
A passage is self-contained when it answers the question without requiring the surrounding page. A definition that begins with "this" or "our approach" carries a dependency the engine cannot resolve once the passage is lifted out of context.
A passage is unambiguous when the things it refers to are named explicitly. "The platform integrates with major providers" names nothing. "[Company] integrates with [named systems]" gives the engine entities it can match, verify and attribute.
Why ranking and citation diverge
Classical search rewards a page as a whole — its authority, its links, its overall topical fit. Generative retrieval operates at passage level. The unit of competition is smaller, and the qualities that win are different.
A long page that covers a topic comprehensively can rank well precisely because it is comprehensive, and be quoted rarely because no single part of it stands alone. A shorter page with one clean, direct, well-named answer can lose the ranking and win the citation.
What this changes about content work
The practical shift is from optimizing pages to optimizing passages. Every question a buyer might ask should have a passage somewhere on your site that answers it in full, in its own words, with its entities named.
That passage should appear near a heading that states the question, because headings are one of the strongest structural signals available to a retrieval system reading your HTML.
Key findings
- Citation is decided at the passage level, not the page level.
- Retrievability, self-containment and entity clarity are the properties that make a passage quotable.
- A page can rank well and still be structurally unquotable.
- Headings that state the question improve the odds that the passage beneath them is selected.
Evidence and sources
The positions above are drawn from repeated retrieval and citation tests we run against public pages across generative engines, and from the structural patterns shared by the passages those engines return. Test protocol and captured results: [EVIDENCE].
- 01[SOURCE TITLE][PUBLISHER] — [URL]
- 02[SOURCE TITLE][PUBLISHER] — [URL]
What to do with this
- 1Audit content by question, not by page — find questions with no self-contained answer anywhere on the site.
- 2Rewrite the highest-value definitions first; they are the passages engines reach for most.
- 3Measure citation separately from ranking, because the two can move in opposite directions.
Conclusion
Being findable and being quotable are different problems. Ranking work makes you available to the retrieval step. Passage-level work decides whether you are what gets used.
Ready to improve your traction?