Somewhere between "add schema markup" and "get cited by ChatGPT" a lot of advice quietly inserts a step that doesn't exist. The pitch is usually some version of: implement the right structured data and AI Overviews will start citing you. It's a tidy claim, it sounds technical enough to be true, and it isn't what Google's own documentation says.
What Google actually requires for AI Overviews
Google's current public documentation on AI Overviews and AI Mode is direct about eligibility: there are no special extra technical requirements beyond being indexed and eligible to appear in ordinary Google Search with a snippet. Not a schema type. Not a markup vocabulary. Not a checklist item labeled "AI Overviews" anywhere in Google's structured data guidelines.
That's worth sitting with, because it forecloses a specific, common claim. There is no "AI schema" to add. If a vendor is selling you a structured-data package specifically for AI Overviews eligibility, they are selling you something Google has never said exists.
So why does structured data get talked about in the same breath as AI answers at all
Because it's genuinely useful for something adjacent, and the two things get merged in a lot of marketing copy until they sound like one thing.
Schema markup's documented job is helping a search engine parse a page's meaning more precisely — this is a product, here is its price, this organization is who it claims to be, this block of text answers this question, this article has this structure. That precision is what makes a page eligible for ordinary rich results in classic Google Search: star ratings, price ranges, FAQ dropdowns, breadcrumbs. None of that is new or AI-specific — it's the same mechanism structured data has always served.
Google's actual stated requirement isn't that the markup exists. It's that
the markup is accurate and consistent with what's visibly on the page. A
Product schema block claiming a 4.8-star rating on a page that shows no
reviews at all isn't a growth hack, it's a policy violation, and it's treated
as one.
The inference worth making carefully
Here's the part that actually justifies writing a post about this, because if the answer were simply "schema does nothing for AI," there'd be nothing else to say.
We've already established, in our comparison of ChatGPT, Google AI Overviews and Perplexity, that AI Overviews doesn't run its own independent retrieval system. It sits on top of Google's existing web index — the same one that ranks ordinary search results — with authority and freshness signals layered on top. It isn't a separate product reading a separate corpus; it's a feature inside Google Search, drawing on the index Google Search already built.
Follow that through and a reasonable inference falls out: anything that helps Google's systems parse and trust a page more precisely — including accurate, consistent schema markup — plausibly supports the same underlying signals AI Overviews draws from, even though no AI-specific markup exists to add. Not because schema has an AI mode, but because AI Overviews is drawing on the same index that schema was always helping Google understand.
Notice the hedging in that paragraph, because it's load-bearing. "Plausibly supports" is not "causes." We have no controlled study showing that adding schema markup increases how often AI Overviews cites a given page. What we have is a documented mechanism (schema improves parsing) and a documented architecture fact (AI Overviews sits on the index that parsing feeds), and a chain of reasoning between them that we have not seen tested. That's a different, weaker claim than "schema gets you cited by AI," and marketing copy that skips the hedge is overstating what's known.
Where this breaks down: FAQPage schema specifically
This is the case where the temptation to conflate the two things is strongest, so it's worth being explicit rather than implicit about it.
FAQPage schema is real and it does something documented: implemented correctly, it can earn an expandable FAQ dropdown directly in Google's search results, next to your listing. That's a legitimate, specific, well-documented rich-result feature. Nobody is disputing it.
What it is not is a citation tactic for AI assistants. We've said this plainly elsewhere on this site, in our free AI-readable-site tool: we have seen no evidence that adding FAQ markup produces a lift in how often an assistant cites you, and we're not going to imply otherwise here either. The FAQ dropdown in classic search results and being quoted by an AI assistant are two different outcomes, and a lot of "schema for AI visibility" content treats getting one as evidence you're working toward the other. It isn't. Implement FAQPage schema if you want the search-results dropdown — that's a real, achievable thing. Don't implement it believing it's an AI-citation lever, because nothing we've seen supports that being true.
A concrete example of taking schema seriously without the AI angle
We run structured data on every product page on this site, and the reason
has nothing to do with AI citation. Product names, taglines and descriptions
on LetsLaunch are supplied by makers — user-generated content we don't
control the contents of. If you serialize that straight into a
<script type="application/ld+json"> tag with a plain JSON.stringify, a
maker whose product name happens to contain a literal </script sequence
breaks out of the script block, because an HTML parser closes a <script>
tag at the first literal </script it sees regardless of what the
surrounding JSON says. That's not a hypothetical — it's the kind of thing
that shows up the first time somebody pastes a tagline with the wrong
characters in it.
That's why every piece of JSON-LD on this site goes through a function
called serializeJsonLd, which escapes <, > and & (and a couple of
line-terminator characters that are legal JSON but not legal
mid-statement in older JavaScript) before anything reaches the page. It's
defensive engineering against user-supplied content breaking a page, not a
citation-boosting tactic. We mention it here because it's the honest
version of "we take structured data seriously" — the reason is correctness
and security, and any downstream SEO benefit is a side effect of doing the
markup right, not the reason we did it.
The actual sequence, in order
- Structured data should be accurate and match what's visibly on the page. That's Google's stated requirement, and it's also just not lying to a parser that other systems (possibly including AI ones) may lean on later.
- Implement schema for what it's actually documented to do — rich results in classic search — not for an AI-specific eligibility gate that doesn't exist.
- Treat any AI-citation benefit as a plausible side effect of a page being better understood by the same index AI Overviews sits on top of, not as a measured, provable outcome you can point to.
- If you want an assistant to describe your product accurately, the more defensible lever remains describing it the same way everywhere it appears — your own site, and any independent page that lists you, including a LetsLaunch listing if you want one more. We've written about why an assistant needs to actually receive that text in the first place before any of this matters at all.
Does adding schema markup get you cited by ChatGPT or AI Overviews?
There's no evidence of a direct, measured effect, and Google's own documentation names no AI-Overviews-specific markup to add in the first place. What's defensible is a chain of inference: schema helps Google parse a page more precisely, and AI Overviews sits on top of the same index that parsing feeds — so accurate schema plausibly supports the same underlying signals, without anyone having measured a specific AI-citation lift from it.
Is FAQPage schema worth implementing?
Yes, for what it actually does: it's a real, documented way to earn an expandable FAQ dropdown in ordinary Google search results. It is not a shown way to get an AI assistant to cite you more often — we've stated that directly elsewhere on this site and we're repeating it here rather than softening it.
Do I need special schema markup to be eligible for Google's AI Overviews?
No. Google's current documentation states there are no special extra technical requirements for AI Overviews or AI Mode eligibility beyond being indexed and eligible to appear in ordinary Google Search with a snippet. There is no AI-Overviews-specific schema type or vocabulary to add.