Answer Engine Optimization
Does Schema Help AI Citations? The Honest Answer
Structured data is cheap, tidy, and almost universally recommended for AI search. It is also, on the best evidence we have, not the citation lever people think it is. Here is what the controlled tests actually found, what schema is still genuinely good for, and what correlates with getting cited instead.
Key takeaways
- In Ahrefs' difference-in-differences analysis, adding structured data barely moved AI citations: AI Overviews citations fell 4.6%, AI Mode rose 2.4%, and ChatGPT rose 2.2% — a net effect close to zero and inconsistent in direction.
- A separate single-variable test backs this up: a practitioner who added FAQPage JSON-LD to two pages and changed nothing else reported 0 out of 6 citations, identical to the no-schema baseline.
- This does not make schema useless. It aids machine-readability, keeps your entity and product data unambiguous, unlocks traditional rich results, and is cheap to add. It is worth doing for correctness.
- The honest claim is narrow: adding schema is not the main thing that earns an AI citation, even though a lot of AEO advice implies it is.
- What does correlate is content-level: a clear answer capsule (present in 72.4% of cited posts, per Search Engine Land), higher key-fact coverage (31% vs 24%, per Surfer), and freshness (AI assistants cite content ~458 days fresher, per Ahrefs).
- Treat schema as table-stakes hygiene, then put your real effort into the measure, fix, and re-measure loop on the questions that actually name a competitor.
Ask most AEO checklists how to get cited by AI and structured data will be near the top of the list, usually with an implied promise: mark up your pages with JSON-LD and the answer engines will understand you better and cite you more. It is an appealing idea. Schema is concrete, it is fully under your control, and it feels like the kind of technical edge that separates the teams who get it from the teams who don't. There is just one problem. When people have run controlled tests, the citation lift from adding schema is close to nothing.
This is not an argument against structured data. It is an argument against mis-spending your best hours on it. Schema earns its place for reasons that have little to do with AI citations, and the evidence is clear enough on both halves of that sentence that it is worth walking through carefully.
1Does schema help AI citations? The short answer
On the best evidence available today, adding schema does not meaningfully increase how often AI answer engines cite you. The lift in the controlled tests is small and does not point consistently in one direction, which is what you would expect from noise rather than a real effect. That is the finding. Everything else in this article is the nuance around it, because the finding is easy to over-read in either direction.
The wrong takeaway is "schema is a scam, rip it out." The right takeaway is that structured data is machine-readability hygiene you should get right and then stop obsessing over, while the work that actually moves citations happens at the level of what your content says and where it is said.
2What did the controlled test actually find?
The strongest data point comes from Ahrefs, which ran a difference-in-differences analysis on pages that added structured data and compared them against pages that did not, measuring the change in AI citations across three surfaces. Difference-in-differences is the useful part of the method here: instead of just checking whether pages with schema get cited more (they might, for reasons that have nothing to do with the schema), it isolates the change caused by adding schema by netting out the trend everything else was on anyway.
Source: Ahrefs, "Does schema markup affect AI citations?"
Read those numbers together, not one at a time. One surface went slightly down, two went slightly up, and none of the moves is large. If schema were a real citation lever you would expect a consistent, sizeable lift across engines; instead you get a wash. Ahrefs' own conclusion is that adding schema had essentially no effect on how often the pages were cited. That is a single study, from one dataset, and it deserves the usual caveats. But it is a genuinely controlled test, and it points the opposite way from the checklist consensus.
3The one-variable test that says the same thing
Large studies are one kind of evidence; a clean single-variable experiment is another, and the two lining up is more convincing than either alone. A practitioner running a week-by-week citation test documented exactly that. They held everything constant, changed one thing, and watched the result:
“Week 2 variable: I added FAQPage JSON-LD schema to two pages... Result: 0/6. The same as the Week 1 baseline.”
Zero citations before the schema, zero after. This is a tiny sample and the author would be the first to say so, but the shape of the result matches the large-scale finding: isolate schema, change nothing else, and the citation needle does not move. It is also a small masterclass in method. By changing one variable at a time, they could actually attribute the (non-)result to the schema rather than guessing. That discipline is the whole point of the last section of this article.
4Why is the schema-equals-citations belief so sticky?
If the data is this unambiguous, why is structured data still near the top of nearly every AEO guide? Because it has three properties that make advice spread regardless of whether it works.
- It is concrete. "Add FAQPage schema" is a task with a clear start and finish. "Become the source a model trusts" is not. Concrete tasks win checklist real estate.
- It is fully in your control. You can ship schema without anyone else's cooperation. Earning third-party mentions or restructuring content to answer a question directly is slower and messier, so the controllable task gets over-weighted.
- It is familiar. A decade of SEO trained everyone that structured data unlocks rich results, so extending that intuition to AI citations feels obvious. It just happens not to hold up when tested.
None of that is a knock on the people repeating the advice. It is a reminder that intuitive, tidy, controllable recommendations survive in the wild whether or not the evidence supports them, which is exactly why a measured test beats a plausible-sounding checklist.
5What is schema still genuinely good for?
Here is the balance the contrarian headline can obscure: schema is still worth adding. The evidence says it is not a citation lever, not that it is worthless. Those are different claims, and conflating them leads teams to strip out markup that is quietly doing useful work.
| What schema does well | Why it still matters |
|---|---|
| Machine-readability | It lets any parser, search or AI, extract your facts reliably instead of inferring them from prose. Unambiguous input is strictly better than ambiguous input, even if it is not what tips a citation. |
| Entity and product clarity | Organization, Product, and sameAs markup keep your identity consistent across the surfaces a model reads. Clear identity is a real AI-search advantage; it just comes from consistency, not the markup format alone. |
| Eligibility for rich results | FAQ, HowTo, Product, and Review schema still drive traditional rich results and knowledge-panel eligibility. That value is independent of the AI-citation question. |
| Low cost, low risk | Valid schema is cheap to add, and there is no evidence it hurts AI citations. Table-stakes hygiene you do once and maintain, not a lever you keep pulling. |
So do it. Mark up your pages, keep the markup valid, keep your entity data consistent. Just file it under correctness and machine-readability, not under "how we get cited." The moment schema starts consuming the hours that should go to content and third-party presence, it has been mis-prioritized.
6What actually correlates with getting cited?
If not markup, then what? The studies that look at what cited pages have in common keep landing on content-level signals, not technical ones. Three show up repeatedly and are worth internalizing because they are where your effort compounds.
Sources: Search Engine Land citation research, Surfer's key-facts study, and Ahrefs on freshness.
The pattern is consistent. Answer engines lift passages that answer the question directly, that are dense with the specific facts the question needs, and that are recent enough to trust. Search Engine Land found a clear answer capsule, a self-contained block that states the answer up front, in 72.4% of cited posts. Surfer found cited pages carry noticeably higher key-fact coverage than uncited ones, 31% against 24%. Ahrefs found AI assistants systematically prefer fresher content. Notice what is absent from that list: the presence of a JSON-LD block.
7Where should you spend the effort instead?
The reason this debate matters is not academic; it is about where a finite amount of time goes. If your team spends its AEO hours adding and re-adding schema, those hours are not going to the work the data says actually moves citations. The alternative is a loop, run one buying question at a time, that treats every change as a hypothesis to be tested rather than a checklist item to be ticked.
| Step | What you do |
|---|---|
| 1. Measure | Ask the real buying question on the engine you care about and record the answer: who is cited, which sources it drew from, and whether you appear at all. |
| 2. Read the evidence | For a question a competitor wins, look at the exact sources cited. Note whether the winning pages lead with an answer capsule, cover the key facts, and are fresh. |
| 3. Fix one variable | Change one thing grounded in what you observed, most often the content, occasionally the markup, never both at once, so you can attribute the result. |
| 4. Re-measure | Re-ask the same question after the sources update and compare. Did the cited set change? That, not a checklist, tells you what worked. |
This is the same discipline that let the single-variable schema test reach a trustworthy verdict: isolate the change, then re-measure. It is also the honest posture for a field where no one controls the output. You are not guaranteeing a citation; you are shifting the odds and verifying the shift. If you want the fuller method, the guides to getting cited by Perplexity and ChatGPT and getting recommended by AI walk the whole loop end to end.
Test what moves your citations, one question at a time
Add valid schema once, keep it healthy, and move on. Then put your real hours where the evidence points: a clear answer up top, the facts the question needs, content kept current, and presence on the third-party sources answers are built from. Structured data is a good habit. It is not the shortcut it is sold as.
Part of the whole picture
Frequently asked questions
Does schema markup help you get cited by AI?+
On the evidence available, not much on its own. Ahrefs ran a difference-in-differences analysis on adding structured data and found the effect on AI citations was close to zero and inconsistent in direction: AI Overviews citations fell 4.6%, AI Mode rose 2.4%, and ChatGPT rose 2.2%. A separate single-variable community test that added FAQPage JSON-LD to pages reported no change in citations either. Schema is still worth having for other reasons, but the data does not support treating it as the main way to earn AI citations.
So is structured data useless for AI search?+
No. Schema helps machines parse your page reliably, keeps your entity and product information unambiguous, and is required for many traditional rich results and eligibility surfaces. It is cheap to add and rarely hurts. The narrower claim the data supports is that adding schema is not the citation lever many guides imply. Do it for correctness and machine-readability, not as your primary bet for getting named in an answer.
Why do so many guides say schema is critical for AEO?+
Because it is concrete, controllable, and familiar from a decade of SEO. Structured data is one of the few things you can ship in an afternoon and check off a list, so it gets over-weighted relative to messier work like earning third-party mentions or rewriting content to answer the question directly. The belief is intuitive; it just is not what the controlled experiments show moves citations.
What actually correlates with getting cited by AI?+
Content-level signals do most of the work. Search Engine Land found 72.4% of cited posts contain a clear answer capsule, a self-contained passage that answers the question directly. Surfer found cited pages average 31% key-fact coverage versus 24% for uncited ones. Ahrefs found AI assistants cite content that is on average 458 days fresher than the web at large. Answer directly, cover the facts, and keep it current before you worry about markup.
Should I remove schema I already have?+
No. There is no evidence that schema hurts AI citations, and it still supports traditional rich results, entity clarity, and reliable machine parsing. Keep valid schema in place. The point is not to strip it out; it is to stop spending your best hours adding more of it in the hope of moving AI citations, when that effort is better spent on answer capsules, fact coverage, and third-party presence.
How do I know if a change actually improved my citations?+
Measure the specific question before and after. Ask the buying question on the engine you care about, record who gets cited and whether you appear, make one change at a time, then re-ask the same question and compare. Testing one variable at a time is exactly how the community test above isolated schema and found no lift. A closed measure, fix, and re-measure loop is the only way to separate what worked from what merely felt productive.
Related guides
- How to Get Recommended by AI: B2B SaaS Guide
- What Makes AI Answer Engines Cite Your Content
- How to Get Cited by Perplexity and ChatGPT
- Does llms.txt Actually Work? The Honest Verdict
- Your Page Ranks on Google But Is Not Cited by AI
- How to Measure AI Search Visibility (Honestly)
- Answer Radar: Answer Engine Optimization