FAQ Schema in 2026: What Google's Deprecation Actually Changed

If you've still got FAQPage markup sitting on your site, you might have noticed something: it stopped doing anything. Not broken, not flagged in Search Console — just quietly ignored. That's not a bug on your end. Google removed FAQ rich results from Search in May 2026, and it did so without much of an announcement. This is what actually changed, what it means for the markup already on your pages, and why the argument that FAQ schema still earns its keep with AI answer engines doesn't survive contact with the evidence.

What actually changed, and when

The timeline is short and mostly undramatic. Google's own Search Central changelog added a deprecation notice on May 8, 2026, stating the feature "will no longer appear in Google Search starting May 7, 2026." On June 15, 2026, Google removed the FAQ rich result documentation page entirely, replacing it with a one-line note that the feature is gone.

The Search Console side of the removal is a bit less officially documented. The page that reportedly listed those dates is gone, and the Wayback Machine doesn't have a usable snapshot.

Search Engine Land and Search Engine Journal both reported, independently, that Google told them the FAQ search-appearance filter, the FAQ rich result report, and Rich Results Test support for the feature would drop in June 2026. Search Console API access followed in August. Two outlets, same underlying Google statement — treat it as one well-corroborated fact, not two.

This didn't come out of nowhere

May 2026 is the punchline, not the story. The setup was August 8, 2023, when Google restricted FAQ rich results to "a select set of well-known, authoritative government and health websites," saying it wanted "a cleaner and more consistent search experience." Everyone else lost their FAQ rich result that day; May 2026 just finished the job for the sites Google had left alone.

Google never published an official reason for the 2026 removal — both Search Engine Land and Search Engine Journal note the same silence. But Google's own John Mueller had already said the quiet part out loud, three years earlier, on Mastodon.

If your FAQ schema was doing its job — extra vertical space on the results page, a bigger visual footprint than a plain blue link — that's exactly the thing Google decided it didn't want anymore. Four years is a long runway for a feature to lose favor. If you were still waiting for the rich result to come back, that decision was already made in 2023.

FAQ schema and AI answer engines: the case doesn't hold up

A common pitch for keeping FAQ schema goes something like this: even without the Google rich result, the markup helps you get cited by AI Overviews, ChatGPT, or Perplexity. The evidence for that claim is thin, and the strongest study available points the other way.

Ahrefs tracked 1,885 pages that added JSON-LD schema between August 2025 and March 2026, against roughly 4,000 matched pages that didn't. It measured citation rates in Google AI Mode, Google AI Overviews, and ChatGPT.

The result: no statistically significant change in AI Mode (+2.4%) or ChatGPT (+2.2%) citations. AI Overviews citations actually declined — a small but statistically significant −4.6%.

One caveat matters here. The study pooled every schema type together — Article, Product, HowTo, FAQPage, and more. It can't tell you FAQPage specifically does nothing. It can tell you that "just add schema" isn't the citation lever a lot of SEO advice claims it is.

Search Engine Land's separate coverage draws the same line between what's confirmed and what's guessed: Google and Bing Copilot have both made general public statements that structured data "gives an advantage" — but neither statement is FAQ-specific, and neither is tied to the 2026 deprecation. What ChatGPT's and Perplexity's own systems actually do with schema markup, as opposed to the visible text on a page, isn't publicly documented anywhere. That's a real gap, not a rounding error, and it's worth saying plainly: that's unmeasured, and anyone publishing confident percentages about it is guessing.

One data point leans toward "these systems read text, not schema." A practitioner test covered by Search Engine Roundtable planted a fake company address inside deliberately invalid JSON-LD — markup that shouldn't parse at all. ChatGPT and Perplexity both extracted the address anyway. That's one test, not a study, but it lines up with what you'd expect if these tools are reading pages as text rather than validating your @type declarations the way Google's Rich Results Test does. If a large language model can pull your fake address out of broken JSON, it isn't reading your schema — it's reading your page like everyone else, typos and all.

Should you remove it? No

Google's own structured data guidance is direct on this: unused markup doesn't hurt your site. There's no penalty, no crawl-budget tax, no "clean up your JSON-LD or else." If FAQPage schema is already on your pages — run the Schema Validator if you're not sure it's still well-formed — ripping it out is work with no measurable upside.

The data backs that up in a way that's almost funny given the timing. HTTP Archive's Web Almanac measured FAQPage adoption on desktop pages at 0.2% in 2022, rising to 0.6% in 2024 — after the 2023 restriction, not before it. Most site owners never got the memo that FAQ rich results were being phased out, and adoption kept climbing anyway. If you remove your markup now, you'd be doing something most of the web still hasn't caught up on, in response to a change most of the web hasn't noticed either.

What's actually worth your time:

1. Leave existing FAQPage markup in place. It costs nothing to keep and nothing to remove.
2. Stop building new FAQ schema specifically to chase a Google rich result — that result doesn't exist anymore, for anyone.
3. Keep writing real, visible FAQ content on the page. That's what a reader — human or AI — actually consumes; the schema was always a wrapper around it, never a substitute for it.
4. For clean FAQPage JSON-LD — for other search engines, for testing, or because a client asks for it — our FAQ Schema Generator builds valid markup from your existing questions and answers in the browser, nothing sent to a server.
5. Not sure what's already live on a page? Paste the URL into the Schema Validator and see what markup is actually there before deciding anything.

Frequently asked questions