Google added a deprecation notice on May 7, 2026, and FAQ rich results stopped appearing in Google Search results entirely — the FAQ search-appearance filter, the FAQ rich result report in Search Console, and Rich Results Test support for it were all removed by June, with the FAQ data disappearing from the Search Console API by August. If you’ve been adding FAQ sections and FAQPage schema to content expecting expandable search snippets, that specific visual payoff is gone.
Why Google Actually Did This
This wasn’t a sudden move — Google had already restricted FAQ rich results back in August 2023, limiting them to well-known authoritative government and health sites specifically. The pattern behind both restrictions is the same: when a rich result feature gets aggressively scaled by SEO tooling and stops faithfully describing the actual page content, Google narrows eligibility to a specific vertical and eventually removes the feature outright rather than keep policing widespread misuse.
The Part That’s Actually Good News
FAQPage as a Schema.org type remains entirely valid, and existing markup on your pages doesn’t need to be removed — unused structured data doesn’t negatively affect search performance, so a site with FAQ schema still in place won’t see rankings collapse or face any penalty for keeping it. The change removes a specific SERP visual feature; it doesn’t invalidate the underlying practice of structuring FAQ content clearly.
Why FAQ Content Still Matters, Just for a Different Reason
AI assistants and generative answer systems draw their responses from exactly this kind of clearly structured Q&A content — FAQPage schema formatting frequently asked questions is still directly useful for capturing AI citations and featured-snippet-style positions, and it remains particularly relevant for voice search, where a clean, direct question-and-answer structure is exactly what these systems are built to extract from. The audience for well-structured FAQ content has shifted from “Google’s rich-result rendering engine” to “AI systems generating an answer,” not disappeared.
What This Means for Your Actual Strategy
- Keep writing genuine FAQ content, but stop treating FAQ rich-result eligibility in classic search as the goal — it’s no longer a real outcome to optimize toward.
- Keep FAQPage schema in place where it accurately describes real Q&A content — it costs nothing to leave and still serves AI-citation and voice-search purposes.
- Don’t add FAQ schema to content that isn’t genuinely a clear Q&A format just to try to capture a rich result — that specific incentive no longer exists, and mismatched schema was already a quality-signal risk independent of this change.
- Prioritize implementing FAQ/speakable schema on service and finance pages specifically, where voice search and generative-answer capture have the most practical business value.
This directly updates the practice we’ve followed across this blog — see WordPress AI Content & E-E-A-T: What Actually Matters for Rankings in 2026 for the broader content-structure picture. Want your site’s schema strategy reviewed post-FAQ-deprecation? Get in touch.
Frequently Asked Questions
Should I remove FAQ schema from my existing pages?
No — unused structured data doesn’t hurt search performance, so leaving accurate FAQPage schema in place is harmless and still useful for AI-answer and voice-search extraction, even without the classic rich-result display.
Does this mean structured data in general is becoming less important?
No — this is specific to the FAQ rich result feature. Schema markup generally remains close to a baseline SEO requirement, and other schema types (Product, Article, LocalBusiness, and more) are unaffected by this specific change.
Why did Google remove it instead of just restricting it further?
The pattern (restrict first, then remove) mirrors what happened with FAQ rich results in 2023 — when a feature keeps being scaled by SEO tooling in ways that stop faithfully representing actual page content, full removal becomes the more durable fix than continued narrowing.
Featured image: original illustration.