How AI search actually chooses what to cite — and the five layers that decide

AI search engines rarely cite the page that ranks first. Google's own patents describe rewriting a single question into a fan of related queries, gathering the documents that answer the whole fan, ranking them by trust signals such as author and domain, then attaching a citation to each sentence a source can verify. Citation is earned at the sentence, not the keyword.

That distinction is the whole game, and most marketing teams are still playing the old one. They track a blue-link rank for a head term while the engine quietly runs five other searches the team never sees, reads the results, and decides — sentence by sentence — which sources to name. This piece traces how that decision is made, using the primary sources that describe it: Google's patent filings, the peer-reviewed retrieval-attribution literature, and the controlled study that measured which content changes actually move the needle. It closes with a single mental model — the Citation Selection Stack — and an honest account of what the evidence does not yet prove.

How does an AI engine turn one question into a search?

It does not search your exact question. It searches a fan of related questions and pools the results.

Google's “Search with stateful chat” patent (US20240289407A1) describes a “first” large language model generating additional queries — “alternative query suggestions, supplemental queries, rewritten versions of the user’s query, and/or ‘drill down’ queries” — from one user query.[1] The SEO community calls this query fan-out; the term itself does not appear in the filing, and the patent is written in the permissive “may be” language of a disclosed method, not a confirmation of what ships in production. But the mechanism it documents is unambiguous, and it reorders everything downstream.

Why it matters: the patent describes selecting documents that are responsive to both the original query and the generated additional queries for inclusion in the candidate set.[2] A page that answers the literal question but none of the adjacent ones competes for a single slice of the fan. A page that covers the intent — the comparison, the price, the reliability question, the alternative — shows up across the fan and accumulates more chances to be cited. You are no longer optimizing for a keyword. You are optimizing for coverage of an intent.

Watch it play out. Each synthetic query builds its own candidate set; the page that wins is the one present across the most of them — not the one that ranks first for the words the user typed:

Which sources clear the trust bar?

Retrieval produces too many candidates to cite. Something has to filter them, and the patent is specific about what.

It describes “query-independent measures” that include a trustworthiness measure for a document “generated based on an author thereof, a domain thereof, and/or inbound link(s) thereto.”[3] Read that carefully. Query-independent means these signals attach to the page before anyone asks a question — they are properties of who published it, where, and who vouches for it. That is the patent-level shadow of the same idea Google states plainly in its public guidance: create people-first, helpful content that demonstrates experience, expertise, authoritativeness, and trustworthiness.[13] The patent says “trustworthiness,” not E-E-A-T; the labels are the industry's, the signal is the engine's.

A source identifier appearing before and/or after a portion of the NL based summary can indicate that the SRD, corresponding to the source identifier, verifies the portion.

That line — the patent's description of how citations are attached — is the most important sentence in the whole filing.[4] The engine is not citing a page because the page is “good.” It is attaching a source to a portion of its own answer because that source verifies the portion. Verification is the unit of citation. Authority gets you into the candidate set; verifiability gets your URL printed next to a sentence.

How does the model decide what it can attribute?

Here the primary sources stop being patents and start being peer review — and they are humbling.

The ALCE benchmark, the first systematic evaluation of LLM citation quality, found that on long-form questions “even the best models lack complete citation support 50% of the time.”[5] Half. The models that power answer engines routinely write sentences their own cited sources do not fully support. This is why the same brand, asked the same question twice, can get two different citation sets: attribution is probabilistic, not deterministic.

The research response has been to bolt verification onto generation. RARR — Retrofit Attribution using Research and Revision — “automatically finds attribution for the output of any text generation model” and then “post-edits the output to fix unsupported content while preserving the original output as much as possible.”[6] And the bottleneck is not the writer; it is the reader. Work on verifiable generation emphasizes “the critical role of retrieval accuracy”: a model can only attribute to what retrieval surfaced.[7]

This is the layer marketers most underestimate. They obsess over being authoritative and ignore being retrievable and verifiable — crawlable, fresh, structured, and written in sentences a machine can match to a claim.

What does the evidence say actually moves visibility?

Mechanism is one thing; measured effect is another. The strongest causal evidence comes from the GEO study by a team at Princeton and IIT Delhi, presented at KDD 2024, which ran controlled content modifications across a 10,000-query benchmark and a live engine.

It reported that Generative Engine Optimization “can boost visibility by up to 40% in generative engine responses.”[8] But the which matters more than the headline. The three top-performing methods — Cite Sources, Quotation Addition, and Statistics Addition — “achieved a relative improvement of 30-40% on the Position-Adjusted Word Count metric,” with the best methods beating baseline by 41%.[9] And the control condition is the punchline for anyone still running a 2015 playbook: classic keyword stuffing “[did not] perform well,” while statistics and quotations “show strong performance improvements across all metrics.”[10]

Two further findings reframe the strategy entirely. The Cite Sources method “led to a substantial 115.1% increase in visibility for websites ranked fifth in SERP, while on average, the visibility of the top-ranked website decreased by 30.3%.”[11] Generative-engine visibility does not mirror classic ranking — it can invert it. And the lifts were not only simulated: the study validated its methods on Perplexity.ai, a real-world engine, and “demonstrate[d] visibility improvements up to 37%.”[12]

The Citation Selection Stack

Put the sources together and a single model falls out. Five layers sit between a question and a printed citation, and each has exactly one lever a publisher controls.

To make that concrete, take a single factual sentence you might publish and run it down the stack — what the engine does at each layer, and the one lever you control to survive it:

Most teams pour their effort into layer two — be indexed, be fast — and treat the rest as luck. The pages that get cited are built backwards from layer five: easy to verify, easy to quote, easy to attribute. The practical translation is almost rude in its simplicity. Write the sentence the engine would want to quote, make it true, and make it cheap to check.

What this means for the work

Three shifts follow directly from the evidence, in order of effort-to-impact.

Write to be quoted, not to rank. Every section should open with a self-contained, factual sentence a source could verify — the GEO study's strongest levers were statistics, quotations, and citations, not keywords. If a paragraph cannot be lifted out and still be true, the engine cannot lift it either.

Make verification cheap. Expose the structure that lets an engine map a sentence to its source without guessing. Schema.org Claim and FAQPage markup, a visible last-updated date, and one outbound citation per claim turn an expensive verification into a cheap one. The page below this one does exactly that — every factual sentence here is wrapped as a machine-readable claim:

{
  "@context": "https://schema.org",
  "@type": "Claim",
  "text": "Keyword stuffing did not transfer to generative engines; statistics and quotations did.",
  "appearance": { "@type": "WebPage", "@id": "https://martech.llc/research/how-ai-search-chooses-citations" },
  "firstAppearance": { "@type": "CreativeWork", "url": "https://arxiv.org/abs/2311.09735" }
}

Measure the surface you can now see. The engines are starting to report it. In February 2026, Bing introduced AI performance reporting in Webmaster Tools, surfacing how pages appear inside AI answers.[14] Treat citation share like a rank: probe the questions your buyers ask, log which sources get named, and watch the set move.

Where the evidence runs out

A serious reading has to mark its own edges. The Google patent is a disclosed method in permissive drafting language — it documents what the system can do, not a sworn description of production AI Overviews, and the terms “query fan-out,” “AI Mode,” and “E-E-A-T” are commentary, not patent text. The GEO results ran on 2023–24 engines and a Perplexity snapshot; whether the exact lifts hold on a 2026 frontier model is genuinely open. And no vendor — not Perplexity, not Bing, not Google — has published a precise, current account of how its live system chooses citations, so the engine-specific mechanics here lean on Google's patent and on academic RAG research applied by analogy.

What survives all of that is the shape of the thing. Engines fan out, retrieve, rank by trust, and cite by verification. The signals that win are credibility signals — statistics, quotations, sources — and they reward the verifiable page over the merely high-ranked one. Optimize for the question after the question, write sentences worth quoting, and make them cheap to check. That work compounds no matter which engine reads it next.

— Sundar Ramesh Kumar · martech.llc