Structured data makes a page eligible for certain enhanced results, but no platform promises those results will appear, and Google’s own documentation says there is no special schema you need for AI Overviews or AI Mode. On this site, nine months of analytics show zero sessions from an AI assistant referrer, so none of this is written from a position of having cracked AI citations. It is written from checking what the platform documentation actually commits to, which is less than most “add schema for AI visibility” advice implies.
I added Article schema to this site’s posts the same way most people do: a plugin, a few fields, done. Somewhere along the way the justification shifted from “this helps Google show a better result” to “this helps AI tools cite you.” I wanted to know whether that second claim is something a platform actually states, or something the SEO industry backfilled onto an existing practice. So I read the source documentation instead of the summaries of it, and I checked this site’s own data against the claim.
That second justification is easy to find and hard to source. Search for “schema markup AI citations” and you’ll get dozens of posts asserting a connection, almost none of them linking to a primary statement from the company that would know. Plugin changelogs and course modules repeat the claim until it reads as settled fact. It isn’t settled. It’s an inference stacked on top of a real but separate fact — that AI answer engines do cite structured, well-organized content — generalized into a claim about markup specifically that the source material doesn’t support.
What the platform documentation actually says
Four pages from Google Search Central cover this directly, and they are more conservative than the advice built on top of them.
First, structured data creates eligibility, not an outcome. Google’s own explainer on how structured data works says you must include the required properties for an object “to be eligible for appearance in Google Search with enhanced display.” Recommended properties make a result “more likely” to appear. Likely is not the same as certain, and eligible is not the same as shown.
Second, Google states this outright rather than leaving it implied. The general structured data guidelines include this line: “Google does not guarantee that your structured data will show up in search results, even if your page is marked up correctly according to the Rich Results Test.” That sentence is doing a lot of work. It is Google telling you, in its own policy document, that correct markup is necessary but not sufficient.
Third, for the specific schema type most blogs use, the requirements are thin. The Article structured data page states “there are no required properties; instead, add the properties that apply to your content.” The stated benefit is narrow too: it can help Google “understand more about the web page and show better title text, images, and date information.” Nothing on that page claims an effect on AI features, Discover inclusion, or ranking.
Fourth, and this is the one that matters most for the question I started with: Google’s page on AI features and your website says “there are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary,” and adds, explicitly, “there’s also no special schema.org structured data that you need to add.” That is the platform that runs the AI feature, stating in its own documentation that structured data is not the lever for appearing in it. I’ve looked at this question from the citation side too, in does schema markup help AI citations, and the documentation trail lands in the same place both times: no stated requirement, no stated guarantee.
What independent evidence shows
Platform documentation tells you what a company claims it rewards. It does not tell you what the rest of the web is actually doing. For that, the HTTP Archive’s Web Almanac 2024 is useful because it crawls real pages rather than summarizing a vendor’s talking points. Its structured data chapter reports that JSON-LD adoption “continues its upward trajectory, increasing from 34% in 2022 to 41% in 2024” of mobile pages. That is real, independently measured growth. It just is not evidence of an AI-citation effect, because the Almanac measures adoption, not downstream outcomes. Treat the two facts as separate: more sites are adding JSON-LD, and no platform has published a number connecting that markup to AI citation rates.
A practical checklist
None of this means skip structured data. It means add it for the reasons the documentation actually supports, and stop there.
- Add Article (or NewsArticle/BlogPosting) schema for the stated benefit: better title, image, and date handling in Google’s own results. That benefit is documented; an AI-citation benefit is not.
- If you’re adding this on WordPress for the first time, the plugin and field mechanics are covered separately in my WordPress schema markup guide, so I won’t repeat the setup steps here.
- Don’t add FAQPage or HowTo markup specifically chasing AI visibility. Google scaled back rich-result display for both in 2023–2024, and no current platform documentation ties either type to AI feature inclusion.
- Write the kind of direct, extractable opening paragraph described in writing answer capsules — the capsule at the top of this post follows that same pattern. That’s a content and structure choice, not a schema one, and it’s the closest thing to a documented lever either platform has described for extractable answers.
- If you’re trying to position this work inside a broader strategy, the distinctions in GEO vs SEO vs AEO are worth reading before you decide where structured data fits in your priority list. It sits closer to the SEO column than the AI-citation one.
- Track outcomes instead of assuming them. If you want a method for checking whether any of this is moving AI citations for your own site, see how to measure AI citations.
The honest limits of current evidence
I’ll report this site’s own numbers rather than skip past them. In Google Analytics, across sessions from January 1 through October 4, 2026, no AI assistant domain — not chatgpt.com, not perplexity.ai, not claude.ai, not copilot.microsoft.com, not gemini.google.com — appears anywhere in the session-source breakdown. The top sources are direct traffic, Google search, and GitHub referrals. Zero AI-assistant sessions is the honest number, not a rounding artifact.
In Search Console, the related post on whether schema markup helps AI citations has logged 2 impressions and 0 clicks over the same window, at an average position of 12.5. That’s a small, unimpressive, real data point, and I’d rather show it than leave this section abstract.
There are also gaps I looked for and couldn’t close. No platform — Google, OpenAI, Perplexity, or Microsoft — publishes a figure for what share of AI citations come from pages with structured data. No independent study I could verify live measured that relationship directly. And neither Perplexity nor Bing Copilot publishes documentation detailed enough to support a specific claim about how either system uses schema.org markup internally. Those are open questions, not settled ones, and the honest move is to say so rather than filling the gap with a number from a secondary source I couldn’t trace back to a primary one.
So: add Article schema because Google documents a real, if narrow, benefit for it. Don’t add it, or anything else, on the premise that it’s a documented AI-citation lever, because as of this writing, it isn’t one — not according to the people who run the systems in question.
Leave a Reply