How Generative AI Actually
Chooses What to Cite

Sources note: The 4-stage RAG pipeline description draws on ZipTie's analysis of 10,000+ AI responses (2025-2026). The information gain framework is based on arXiv:2509.12765v1 (2025). Cross-platform citation overlap data (11%) is from The Digital Bloom's analysis of 680M+ citations (2025). Platform-specific citation percentages in the table below are derived from publicly available measurement studies by ZipTie, AI search tracker, and SEO tooling vendor panels as of Q1 2026; specific percentages vary by query type and category. Chunking citation findings reference the general RAG research literature (Lewis et al. 2020, Gao et al. 2023); fabrication rate estimates (8-15%) are based on published citation grounding studies including NCI's citation verification benchmark (2024).

When ChatGPT cites a source, most people assume it works like Google: index the page, rank it by relevance, display it. The reality is structurally different. LLMs do not crawl the web in real time for every answer. They operate through a layered pipeline — retrieval, ranking, synthesis, and verification — and each layer applies a different set of filters that determines whether your content surfaces as a citation. Understanding these filters at the mechanism level is the difference between guessing at your AI visibility strategy and engineering it.

The 4-Stage RAG Pipeline

Retrieval-Augmented Generation sounds like a single operation, but it is actually a pipeline of four distinct stages, each with its own selection criteria. ZipTie's analysis of citation behavior across major LLMs, drawing on data from 10,000+ AI responses, breaks the pipeline down as follows.

Stage 1: Query Analysis and Intent Extraction

Before any document is retrieved, the model parses the user's prompt to extract the core informational need. This is not keyword matching. The model identifies entities, relationships, and the expected response format — definition, comparison, instruction, or evaluation. Perplexity, for example, runs a live web query for every prompt and explicitly classifies the question type to determine which retrieval strategy to use. Google's AI Overviews go further with query fan-out: a single question about "how to fix lawns" triggers concurrent sub-queries about herbicides, chemical-free removal, weed prevention, and soil treatment. The model synthesizes across all of them before generating a response.

Stage 2: Document Retrieval via Vector Embeddings

The retrieval system searches its index using vector embeddings — mathematical representations of semantic meaning, not exact keyword matches. A page about "reducing employee turnover" can be retrieved for a query about "how to keep staff from quitting" even if those exact words never appear on the page. The embedding model maps both the query and the document into the same high-dimensional vector space, then retrieves the closest matches using cosine similarity or inner product distance.

This stage is where chunking strategy matters most. Documents are split into passages before embedding, typically in the range of 100 to 500 tokens per chunk. Research on citation precision shows that finer chunks (100-200 tokens) improve the model's ability to pinpoint the exact sentence supporting a claim, while coarser chunks (500+ tokens) increase context but reduce citation accuracy. Most production RAG systems use overlapping chunks — typically 200 tokens with 50 tokens of overlap — to capture sentence boundaries and paragraph transitions that a rigid split would sever.

Stage 3: Re-Ranking by Relevance, Authority, and Information Gain

Vector retrieval returns a broad set of candidate documents, typically 20 to 30 per query. The re-ranking stage applies additional filters to narrow this set to the 3 to 6 sources that will actually be cited. The ranker evaluates each candidate on three dimensions: semantic relevance to the query, source authority (derived from training data prevalence and cross-source agreement), and information gain — the unique value a document adds beyond other retrieved sources.

Information gain is the least understood but most consequential filter. Research published on Document Information Gain (arXiv:2509.12765v1) showed that scoring documents by their marginal contribution — what a source adds that no other source in the candidate set already covers — improved exact match accuracy by 17.9% over naive RAG systems. This mechanism structurally penalizes content that merely repeats what other sources say. A blog post that paraphrases an industry report adds zero information gain and will be filtered out regardless of how well it is written. Original research, unique data, and novel analysis receive higher scores, creating a competitive moat that aggregator content cannot replicate.

Stage 4: Citation Generation and Post-Generation Verification

Once the top-ranked sources are selected, the model generates the answer with inline citations — typically numbered markers like [1], [2] that map to specific source chunks. The sequence in which sources are cited is determined not just by relevance rank but by how the model weaves them into its narrative. Sources that provide definitional grounding tend to be cited first; sources that provide supporting evidence appear later.

Post-generation verification is an emerging practice that checks whether each cited claim actually appears in the attributed source. Citation grounding research shows that even with perfect retrieval, GPT-4-class models fabricate details in 8-15% of responses. Verification systems that check token alignment between the generated output and the source text reduce fabrication rates to under 3%. Perplexity's entire product is built around this verification loop — it explicitly ties each sentence to a source and allows users to inspect the original context. ChatGPT and Claude have added similar verification in their 2025-2026 releases, though with different levels of transparency.

Platform-Specific Retrieval Architectures

The 4-stage pipeline is the general framework, but each major AI platform implements it differently. The differences are not cosmetic — they produce citation sets that overlap by as little as 11% between platforms. The same source URL cited by ChatGPT has only an 11% chance of being cited by Perplexity for the same query, according to an analysis of 680 million+ citations published by The Digital Bloom in 2025.

The architectural split between citation-first and conversation-first platforms explains most of the variance. Perplexity was built as a citation-first search engine — it runs a live query for every prompt, selects sources dynamically, and ties every claim to a specific source in 78% of complex research questions. ChatGPT was built as a conversational AI that later gained search capability. As one practitioner on r/perplexity_ai put it: "Perplexity was specifically built as a citation-first search engine from the ground up, while ChatGPT's web search is more like search bolted onto a conversational AI." This design-level difference produces the measurable citation gap.

Claude sits in the middle. It uses Brave Search to retrieve the top 5-10 results, then applies a conservative citation filter that favors long-form editorial content, technical documentation, and well-established publications. Claude almost never cites forums or social media. For B2B brands with detailed technical content, this makes Claude the most predictable platform — if your page is well-structured and authoritative, Claude will cite it. But Claude's smaller candidate pool means your content must rank in Brave's top results to be considered at all.

Chunking, Embeddings, and the Hidden Determinants

Two factors that content teams rarely consider — chunking strategy and embedding model selection — directly determine whether a page gets cited. The chunking approach controls how the model slices your page into retrievable units. A page with clear heading hierarchies, numbered sections, and self-contained paragraphs produces better chunks than a page with dense prose and no structural breaks.

Embedding model selection introduces another layer of variance. Different LLM providers use different embedding models with different dimensional spaces (OpenAI's text-embedding-ada-002 uses 1536 dimensions; Sentence Transformers models commonly use 384 or 768). The same query mapped through different embedding spaces retrieves different documents. This is part of why cross-platform citation overlap is so low — the same content, embedded by different models, lands in different semantic neighborhoods.

Passage-level extractability — the property of a page that determines whether a specific paragraph can be cleanly extracted and cited — is the closest thing to a universal signal. A self-contained answer block of 40-60 words that defines a concept, answers a question, or states a statistic is optimal for all platforms because it minimizes the extraction work the model must do. Pages organized into such blocks consistently outperform narrative prose in citation frequency, regardless of the platform or embedding model.

Information Gain as a Citation Filter

The information gain mechanism deserves emphasis because it is the filter most misaligned with traditional content strategy. SEO-driven content tends toward comprehensiveness — covering every angle of a topic to capture multiple keyword variants. But comprehensive content that aggregates known information adds low information gain per source. The RAG ranker sees a page that covers ground already covered by other sources and deprioritizes it, regardless of how well it is written.

The content that survives the information gain filter shares three characteristics: it contains original data or research, it takes a position that differs from the consensus (and supports it with evidence), or it covers a niche so specific that no other source in the retrieval set addresses it. Comparison content excels here because every "X vs Y" page is by definition unique — the specific feature-by-feature comparison between two named products does not exist anywhere else in the retrieval set, giving it high information gain by default.

What This Means for Content Engineering

Understanding the pipeline at this level of detail changes how you build content. Instead of writing for a hypothetical "AI audience," you optimize for specific pipeline stages.

For vector retrieval: optimize entity density and self-contained passages. Each paragraph should be extractable on its own. Avoid anaphora that relies on earlier sections — if a paragraph references "this framework" without defining it, it loses retrieval value when chunked independently.

For re-ranking: prioritize original data. Every statistic, benchmark, or comparison that exists uniquely on your page increases your information gain score. Synthesized content without new data will be filtered out regardless of vector similarity rank.

For citation synthesis: structure for extraction. 40-60 word answer blocks, FAQ sections with Schema.org markup, and comparison tables are the most citable formats because they minimize the model's extraction work. A well-structured FAQ page with Schema markup gets cited roughly 2x more than identical content without structure.

For post-generation verification: ensure every claim on your page can be traced to a specific source within the same page. Models performing token alignment verification are more likely to cite pages where the relationship between claims and evidence is clear and contained.