Effect sizes, not vibes: what controlled studies say about the page elements ChatGPT, Perplexity and Google's AI features quote, and an annotated anatomy you can copy.
AI assistants cite pages built as extraction targets: a 40 to 60 word direct answer at the top, one-idea paragraphs under question-style headings, at least one data table, an FAQ in real buyer phrasing, statistics linked to primary sources, and a visible update date. Measured lifts run 28 to 41 percent. Schema markup supports this structure but cannot replace it.
Most structure advice for AI search is folklore. But this is one of the few corners of GEO with actual controlled experiments behind it, and the results are specific: the content AI assistants cite shares a small set of structural traits, and each trait has a measured effect size. This guide walks through the evidence first, then assembles it into a page anatomy you can apply today.
If you already rank on Google but never show up in AI answers, structure is the usual suspect. We covered the diagnosis in You rank #1 on Google but ChatGPT ignores you; this page is the fix at the page level.
The strongest structural levers are adding quotations (+41%), statistics (+31%), source citations (+30%) and fluency (+28%), while keyword stuffing and unusual wording produce little to no improvement. Those numbers come from the Princeton GEO study, a 10,000-query benchmark accepted at KDD 2024, and they have held up as the field's reference point.
The Princeton GEO paper (Aggarwal et al., KDD 2024) tested nine page modifications against generative engines and measured position-adjusted visibility in the generated answers. The headline: the right changes boost visibility by up to 40 percent, and none of the winners are traditional SEO tricks.
| Structure element | Study | Measured effect |
|---|---|---|
| Quotations from primary sources | Princeton GEO (KDD 2024), 10,000-query benchmark | +41% visibility |
| Statistics added to the page | Princeton GEO (KDD 2024) | +31% visibility |
| Inline citations to sources | Princeton GEO (KDD 2024) | +30% visibility |
| Fluency rewrite (clearer sentences) | Princeton GEO (KDD 2024) | +28% visibility |
| Easy-to-understand rewrite | Princeton GEO (KDD 2024) | +13% visibility |
| Keyword stuffing | Princeton GEO (KDD 2024) | Little to no improvement |
| Unique or rare wording | Princeton GEO (KDD 2024) | Little to no improvement |
| Adding JSON-LD schema to existing pages | Ahrefs experiment, 1,885 pages (2025 to 2026) | No citation lift vs. controls |
| Fresh, visibly updated content | Ahrefs, 17M citations (2025) | Cited pages 25.7% fresher |
Read the pattern, not just the rows. Every winning method makes a passage easier to lift verbatim into an answer: a quote, a number, a source, a cleaner sentence. Every losing method optimizes for a ranking algorithm that generative engines do not use. That single distinction explains most of what follows.
Listicles win 21.9 percent of AI citations, articles 16.7 percent, and product pages 13.7 percent. Together those three formats take 52 percent of all citations, and query intent, not industry or model, best predicts which format gets picked. For commercial-intent questions, listicles alone capture 40 percent.
Those figures come from the Wix AI Search Lab study, which analyzed 75,000 AI answers and over one million citations across ChatGPT, Google AI Mode and Perplexity. The engines differ at the margins: ChatGPT leans hardest into articles and informational content, Google AI Mode spreads citations most evenly, and Perplexity sends about 17 percent of its citations to discussions such as Reddit threads.
The practical takeaway: match format to intent before you write a word. A "best X for Y" question wants a ranked list with a comparison table; a "how do I" question wants numbered steps; a "what is" question wants a definition block up top. Structure is the format contract the engine expects for that query type.
Generative engines answer by retrieving and quoting individual passages, so each section of your page competes on its own. A section that answers one question completely in a few sentences can be cited even if the rest of the page is mediocre; a brilliant page with no liftable block often is not.
This is visible in how the systems describe themselves. Google's documentation says its AI features use "query fan-out" techniques: multiple related searches, with supporting pages assembled per sub-question. ChatGPT search works from an index too; Seer Interactive found 87 percent of SearchGPT citations matched Bing's top results, and OpenAI's crawler, OAI-SearchBot, fetches pages for exactly this passage-level use. (Structure only pays off if the page is retrievable at all: register it in Bing Webmaster Tools and ping IndexNow on publish. The playbook covers that step in full.)
Write every H2 section as if it will be read alone, because it will be. Open each section with a 40 to 60 word standalone answer to the heading's implied question, then elaborate. If a section only makes sense after reading the three sections above it, it cannot be lifted, and passages that cannot be lifted do not get cited.
A citable page stacks seven elements: a direct-answer block, atomic sections with standalone openers, a data table, sourced statistics, an FAQ in real question phrasing, a visible update date, and JSON-LD that mirrors the visible text. Here is the wireframe, annotated with why each block earns its place.
Sits immediately under the H1. Answers the target question completely in one self-contained paragraph. This is the single most liftable block on the page and mirrors the +41% quotation effect: you are handing the engine its quote.
Each H2 reads like the question a buyer asks, and its first paragraph answers it in 40 to 60 words before any detail. One idea per paragraph, 2 to 4 lines each. This is passage-level retrieval, served.
Tables compress many facts into one extractable block. In the Wix data, list and comparison formats dominate citations; a table is the densest version of that structure.
Numbers with named, linked sources carry the +31% statistics effect and the +30% citation effect at once. "41 percent (Princeton, KDD 2024)" beats "a lot" every time.
Assistants match conversational queries. An FAQ whose questions repeat how people actually phrase the ask ("What kind of content do AI assistants actually cite?") gives the engine an exact-match passage.
Freshness is checked by engines and by readers. A visible date near the top plus a real content refresh feeds the 25.7% freshness edge documented across 17M citations.
Article and FAQPage schema with datePublished and dateModified. Not a citation lever on its own (see below), but it keeps machine-readable metadata consistent with what is on the page.
Notice what is absent: word-count targets, keyword density, synonym sprinkling. Density beats length. A 1,500-word page with six liftable blocks outperforms a 4,000-word page with one, and padding actively buries the answer the engine came for.
The best current evidence says adding JSON-LD does not, by itself, increase AI citations. It is still worth including, for narrower reasons: consistency of metadata, machine-readable dates, and eligibility for classic search features. Treat schema as plumbing that mirrors your structure, never as a substitute for it.
Two sources anchor that verdict. First, Ahrefs tracked 1,885 pages that added JSON-LD between August 2025 and March 2026 against roughly 4,000 matched controls, across Google AI Overviews, AI Mode and ChatGPT: citations barely moved, with the AI Overviews cohort 4.6 percent below controls. Second, Google's own AI features documentation is unambiguous: "There's also no special schema.org structured data that you need to add," while still advising that structured data match the visible text.
So why does our anatomy keep element 07? Because dateModified in schema is how you make freshness machine-readable, because FAQPage markup keeps your Q&A content consistent, and because classic rich results still exist. The honest framing: structure earns the citation; schema files the paperwork.
AI-cited pages are measurably newer than organic results: 25.7 percent fresher on average, with cited URLs averaging about 2.9 years old versus 3.9 for organic Google results, and roughly half of cited pages published or updated within the previous 13 weeks. If your page shows no date, engines and readers assume the worst.
The numbers come from Ahrefs' analysis of 17 million AI citations. The bias is strongest where buyers ask commercial questions: pricing, comparisons and market data rot fast, so engines prefer the page updated this quarter.
Operationally: a visible "Last updated" line near the top, dateModified in your Article schema, and a real refresh behind the date (re-verify statistics, prices and examples). A bumped date over stale content is the pattern engines are built to discount.
Three tactics fail on the evidence. Keyword stuffing and unique wording showed little to no improvement in the Princeton benchmark. Schema-as-magic showed no citation lift in the Ahrefs experiment. And padding for word count dilutes the liftable blocks that citations depend on, while making truncation more likely when engines fetch your page.
Direct answer in 40 to 60 words up top. Question-shaped H2s, each opening with a standalone answer. One data table minimum. Every stat linked to its primary source. FAQ in buyer phrasing. Visible update date plus dateModified in schema. No stuffing, no padding. That is the whole playbook for this step.
We built GEOHATS around exactly the anatomy above. It tracks which pages get cited for your buyers' questions across ChatGPT, Claude, Perplexity, Gemini and Grok, then writes pages that pass a quality gate enforcing this checklist automatically: answer-first block, table or FAQ present, sourced claims, dateModified, no filler. If you want tools that write rather than just score, we compared the field in GEO tools that write the content.
See GEOHATS pricingMore answers