Every second post on this question opens with a confident yes. Schema markup, we are told, is how you feed the machines, how you get cited in AI Overviews, how ChatGPT understands your business.
I went looking for the source of that claim. Not for a study or an agency case study, but for one sentence from Google, OpenAI, Anthropic or Perplexity saying structured data affects whether an AI system cites you. I did not find one, and the shape of what is missing is more useful than another opinion.
Does Google say schema helps with AI Overviews?
No. The relevant page says close to the opposite.
Google’s documentation on AI features and your website states: “There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary.” AI features are grounded in the same index built by ordinary crawling, and the advice attached is the same advice as for regular search.
The structured data documentation makes a narrower claim than people repeat. Its stated benefit is eligibility for richer presentation: “Adding structured data can enable search results that are more engaging to users”, which is what rich results are. Rich results are a search appearance feature. That is a real and measurable benefit, and it is not a claim about AI citation.
Notice what has to happen for “schema helps with AI search” to be true from these two documents. You have to assume that AI systems weigh structured data separately, and neither page says that.
What has anyone at Google actually said?
The most specific thing on record came from John Mueller in a Reddit thread on r/TechSEO in January 2026, and he labelled it as not official guidance, which means it is worth quoting carefully and not treating as documentation.
His opening was “This question will stick with us for the next year and longer, and the short answer is yes, no, and it depends.” The part that carried real information was where he drew the line: “Pricing, shipping, availability for shopping is basically impossible to read in high fidelity and accurately from a text page.” That is a case for markup on facts that are hard to parse from prose. Volatile, precise, machine-consumed values.
And then the part that gets left out of the posts quoting him: “there’s a lot of wishful thinking in the SEO world when it comes to structured data. Your ‘best geo insurance comparison site’ isn’t going to rank better by adding insurance markup.”
Read together, that is a fairly narrow claim. Markup helps where the data is genuinely hard to extract from text. It does not make an ordinary article more citable.
The strongest supportive statement I could find from any search engine came from Microsoft rather than Google, when Fabrice Canel said at SMX Munich in March 2025 that schema markup helps Microsoft’s LLMs understand content. That is a real signal, and it is also a conference remark from one engine, not documentation. I am flagging it as reported speech and not building a recommendation on it.
The absence is the finding
Here is the check that changed how I answer this question. I went through the crawler documentation of the three biggest AI companies looking for the word schema.
OpenAI’s bot documentation, Anthropic’s crawler documentation and Perplexity’s bot documentation all cover the same ground: which user agents they send, how to allow or block them in robots.txt, published IP ranges, and how to stop your firewall blocking them by accident. Access, all of it.
None of them mention JSON-LD, schema.org or structured data at all.
If structured data were a meaningful input to how these systems select and cite sources, the documentation aimed squarely at publishers who want to be crawled well would be the obvious place to say so. It is a striking silence across three independent companies. It is not proof of absence, and I am not claiming it as one. It does mean that anyone telling you schema is how ChatGPT understands your page is not quoting anybody.
What those docs care about is whether the crawler can reach the page at all, which is a question about robots.txt and rendering rather than markup.
Quoted wording from Google Search Central on AI features and structured data, John Mueller on r/TechSEO in January 2026, and reported coverage of SMX Munich 2025. Crawler documentation checked directly.
So is schema markup a waste of time?
No, and this is where the honest answer gets more useful than the confident one.
Schema pays in things you can put a number on, in a report, this quarter:
- Rich results. Review stars, FAQ, breadcrumbs, product details, event dates. These change how your result looks and they are documented as the purpose of the markup.
- The rich result reports in Search Console. Valid, Warning and Invalid counts per type, with a history. A deployment either moves those numbers or it did not work.
- The Search Appearance dimension in the Performance report, which lets you compare clicks and impressions for results with a given enhancement against the rest.
That is a measurable case. Notice it does not require any claim about AI at all, which is exactly why it holds up when a client’s developer pushes back on the work.
Where I would spend markup effort first, following the one distinction with any evidence behind it: facts that are precise, volatile and painful to parse from prose. Prices, stock status, shipping and returns, event dates and times, opening hours. If your page’s value is an argument or an explanation, markup is not what makes it citable, and no amount of Article schema will change that.
How do I verify Google actually read it?
The step almost everyone skips, and the reason plenty of markup silently does nothing.
The Rich Results Test tells you the markup is valid. It does not tell you Google parsed it on your live page after rendering, and those come apart on JavaScript-injected JSON-LD in particular. Use URL Inspection on the live URL and look for “Rich results detected on the page”. That line is Google telling you it read your markup in the page it actually crawled, which is a different and stronger statement.
Then watch the Valid count in the matching rich result report over the following days. A count that never moves after deploy is your answer.
Two failure modes are worth knowing before you go looking. JSON-LD written as a JavaScript object rather than valid JSON fails silently, which I have written up in Googlebot does not parse JavaScript objects as JSON. And escaping inside JSON-LD has caught people out recently, covered in the JSON-LD escaping change.
What I tell clients
If the question is “will schema get me into AI Overviews”, the answer is that nobody at Google, OpenAI, Anthropic or Perplexity has said so, and Google’s AI documentation says there is nothing special to do. If the question is “should we implement schema”, the answer is yes, for rich results, measured in Search Console, on the pages where the facts are structured.
Do not let the second one be sold on the strength of the first. When the AI citation claim fails to show up in any report, it takes the legitimate work down with it.
For the broader version of this question, do I need to optimize for AI Overviews covers what does appear to matter, and the AI search visibility guide is the longer treatment.
Sources
- Google Search Central, AI features and your website, for “There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary”, checked 7 September 2026
- Google Search Central, Intro to how structured data markup works, for the rich results claim and scope, checked 7 September 2026
- John Mueller, comment on r/TechSEO, January 2026, explicitly labelled by him as not official guidance, for the quoted remarks on shopping data and wishful thinking. Reported speech, cited as such
- Search Engine Land coverage of SMX Munich, March 2025, for Fabrice Canel’s remark on schema and Microsoft’s LLMs. Reported speech, cited as such
- OpenAI bot documentation, Anthropic crawler documentation and Perplexity bot documentation, checked 7 September 2026 for any mention of schema, JSON-LD or structured data. None found
- Google Search Console, rich result reports and the URL Inspection tool, for the verification chain, checked 7 September 2026