Google Officially Retires FAQ Rich Results: What It Means for Your SEO
Google has quietly closed the book on one of its longest-running rich result features. FAQ snippets — the expandable question-and-answer boxes that used to appear under search listings — no longer show up in Google Search, and the supporting tools behind them are being phased out over the next few months.
What actually changed
Google added a deprecation notice to its FAQ structured data documentation confirming the rollout is happening in three stages:
- 7 May 2026 – FAQ rich results stopped appearing in Google Search results.
- June 2026 – The FAQ search appearance filter, the FAQ rich result report in Search Console, and FAQ support in the Rich Results Test are being removed.
- August 2026 – Support for FAQ data in the Search Console API ends.
There was no big blog post or announcement video — just a notice added directly to the developer documentation, which is how Google often handles feature retirements these days.
This has been coming for a while
FAQ rich results launched back in 2019 and were quickly overused: businesses bolted generic Q&A blocks onto pages purely to grab extra space in the search results. Google responded in August 2023 by limiting the feature to a narrow set of authoritative government and health sites. For almost every commercial website, FAQ rich results have effectively been invisible since then. May 2026 just removes the last bit of eligibility, even for the sites that kept it.
Do you need to remove your FAQ schema?
No. Google has been clear that FAQPage structured data is still a valid schema type, and that it will keep using it to better understand page content — it simply won’t render it as a visible SERP feature anymore. Other search engines and AI crawlers can still read and use it too.
What we’d recommend instead:
- Leave well-written, genuinely useful FAQ content in place. It still helps answer long-tail questions and supports AI Overviews and AI search tools, which pull from clear Q&A content regardless of whether schema is attached.
- Remove thin, templated FAQ blocks that were only ever added to win extra pixels and don’t reflect real user questions.
- Export your historical FAQ performance data from Search Console before the June changes, if you want a baseline for any future comparisons.
- Update any automated reporting or API pipelines pulling FAQ rich result data before the August cutoff, so dashboards don’t quietly break.
The bigger picture
This fits a pattern we’ve seen from Google over the past couple of years — HowTo rich results were deprecated in 2023, and several more structured data types (Course Info, Claim Review, Vehicle Listing, and others) were retired in June 2025. Google is steadily trimming SERP enhancements in favour of a simpler results page, while shifting more attention toward AI-driven search experiences like AI Overviews and AI Mode.
For website owners, the takeaway isn’t “schema is dead” — it’s that schema was never the thing doing the heavy lifting. The content was. As Google’s own search features keep evolving, clear, well-structured, genuinely useful content remains the safest long-term investment, whether or not it earns a rich result badge along the way.
What about AEO and AI search?
It’s worth separating two things that often get lumped together: the FAQ schema and the FAQ rich result. The rich result was a presentation layer — a visual treatment in classic Google Search. The schema is a comprehension layer — a way of telling any system reading your page that a section is structured as questions and answers. Losing the first doesn’t touch the second. AI Overviews and AI Mode don’t give special weight to FAQPage markup when deciding what to cite; they pull from clearly written, well-organised Q&A content whether or not schema is attached to it. So if your FAQ sections were built to genuinely answer what customers ask, this change costs you a SERP badge, not a comprehension signal.
The practical risk sits more on the reporting side than the content side. Teams running dashboards, BigQuery exports, or automated reporting against the Search Console API for FAQ data should plan that work around the August cutoff rather than the May one — silent null returns in a pipeline tend to surface much later than expected, usually right when someone asks for a quarterly comparison. If FAQ visibility was ever part of a client-facing report or KPI, this is a good moment to flag the change proactively rather than let a number quietly disappear from next quarter’s figures.
This article is based on Google’s own Search Central documentation updates published in May and June 2026.
