Structured data for AI search - what still matters in 2026

2026-08-16 updated 2026-09-21 3 min read Augustyn Głowacki

Platform documentation does not claim that schema.org markup improves AI citations. Ahrefs compared 1,885 pages that added JSON-LD with roughly 4,000 similar pages and measured a -4.6% change in Google AI Overviews, +2.4% in Google AI Mode and +2.2% in ChatGPT. The last two results were statistically indistinguishable from noise (Ahrefs, 11 May 2026). Use structured data for Google's supported search features and to describe facts already visible on the page.

Does Google say schema helps AI Overviews or AI Mode?

No. “There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary,” and “there’s also no special schema.org structured data that you need to add” (Google, AI features documentation). Google’s May 2026 AI optimization guide repeats it under a section literally titled “Overfocusing on structured data”: keep using schema for rich-result eligibility, not because it does anything for generative AI search.

Do AI systems actually read JSON-LD at all?

In a one-page test, searchVIU exposed eight product prices through different methods and queried ChatGPT, Claude, Gemini, Perplexity and Google AI Mode five to ten times each. None reported a price stored only in JSON-LD. ChatGPT, Gemini and Google AI Mode read prices in visible HTML. Every system also missed prices added to JSON-LD with client-side JavaScript (searchVIU, October 2025). This single page limits how widely the result can be applied.

What happened to FAQPage and HowTo?

Google deprecated HowTo on 13 September 2023. FAQ rich results stopped appearing in Google Search on 7 May 2026, and Search Console support ended during June 2026 (Search Engine Journal, “Google Drops FAQ Rich Results From Search”). No engine has stated that FAQPage affects AI citations, and the controlled JSON-LD test found no positive effect. Google says unused structured data causes no Search problems and has no visible effect.

Which parts of this are documented, tested, or my own judgment?

Documented platform behaviour. Google states that no special structured data is needed for AI Overviews or AI Mode (Google, AI features documentation), that Organization markup aids brand disambiguation (Google, Organization docs), and that HowTo was deprecated on 13 September 2023 while FAQ rich results stopped appearing on 7 May 2026 (Search Engine Journal). These are first-party statements with dates on them.
Measured, with a control group. Ahrefs compared 1,885 pages that added JSON-LD with roughly 4,000 matched pages. AI Overviews changed by -4.6%. The results for AI Mode and ChatGPT were statistically indistinguishable from noise (Ahrefs, 11 May 2026). searchVIU tested one page, so its result needs more testing.
My recommendation. Use the three schema types below where they help conventional search, and make sure marked-up facts also appear in visible text. The studies did not test this recommendation directly.

So what’s actually worth shipping?

I recommend Organization with sameAs on the main page because Google says it helps identify a brand in search results. Google also says Article or BlogPosting helps it understand an editorial page’s title, image and dates and can feed Google News. I add a Person node with sameAs inside article bylines to identify the author. These are recommendations for conventional search. The studies above found no AI citation benefit.

How do you keep the markup and the visible page saying the same thing?

Put each marked-up fact in visible page text too. To check a page:

List every value in the JSON-LD that a buyer would care about - price, rating, availability, date, author, location.
Find each one in the rendered HTML as text a reader can select. If it is not there, either add it to the page or drop it from the markup.
Use View Source. In the searchVIU test, prices injected into JSON-LD by client-side JavaScript scored zero on every system, including Gemini, which renders JavaScript.
Compare the visible date against dateModified, and only move dateModified when the content actually changed.
Re-run the two steps above after a template or content change. A refactor can move a price into a client-rendered component without changing the copy.