Google Drops FAQ Rich Results: Keep the Schema, Audit the Dashboards
On May 7, 2026, Google removed FAQ rich results from Search without a blog post or formal webmaster notice — a quiet edit to the structured data documentation was the only signal. If your reporting dashboards still track FAQ rich result impressions, or your automation queries the FAQ report, the cutoff clock is already running.
Are FAQ Rich Results Gone From Google Search?
Yes. As of May 7, 2026, FAQ rich results no longer appear in Google Search across all site types. FAQPage remains a valid Schema.org type and Google confirmed it will continue to parse the markup to understand page content. Only the visible SERP feature has been removed; the schema itself is not deprecated.
The Deprecation Timeline
The rollback is happening in stages. Google’s documentation outlines three cutoffs practitioners need to map to their tooling:
| Date | What changes |
|---|---|
| May 7, 2026 | FAQ rich results stop appearing in Google Search, all site types |
| Through June 2026 | Google removes the FAQ search-appearance filter, the FAQ rich result report in Search Console, and Rich Results Test support for FAQ |
| August 2026 | Search Console API support for pulling FAQ rich result data ends |
The May cutoff is already past. The June window means any dashboard that surfaces the FAQ rich result report will lose its data source this month. The August cutoff hits any scripts or integrations that pull structured-data performance from the Search Console API. Neither cutoff affects how Google reads FAQPage markup on your pages.
Part of a Longer Pattern, Not an Isolated Change
The FAQ removal follows an established sequence. Google pulled HowTo rich results from desktop results in 2023. In June 2025, it removed seven additional structured-data types from search appearance in a single batch. The FAQ removal followed this same low-key pattern: no formal announcement, just a documentation note and a staged wind-down.
The practical conclusion is that Google is narrowing which structured-data types get dedicated SERP real estate. That is not the same as saying schema is becoming less important. Google has confirmed it still parses FAQPage markup to understand page content: the change is to the SERP display, not to how the markup is read. What it means is that the specific display feature attached to any given type can be retired at any point. An SEO program built around earning a particular rich result carries a structural dependency that can disappear without warning.
For a current map of which schema types still carry active SERP features, the Schema Markup Guide covers the full implementation landscape including JSON-LD structure and testing procedures.
What to Actually Do
Three actions, in order of urgency:
- Keep FAQPage schema in place. Google is still parsing it to understand page structure and content relationships. Removing it trades parsing signal for nothing in return. If the FAQ content is genuinely structured as questions and answers on the page, the markup should stay.
- Audit dashboards and reporting before end of June. The FAQ rich result report in Search Console is being removed this month. Any report, alert, or client deliverable built on that filter will start returning null data or simply disappear. Identify and disable those data pulls now, before they go silent without explanation.
- Audit API integrations before August. If you query the Search Console API for FAQ rich result data, that endpoint stops returning data in August 2026. Update those integrations to prevent broken monitoring pipelines and false-negative alerts that could mask other indexing issues.
There is no SEO penalty for retaining FAQPage markup after this change. The sole consequence is that the page no longer generates expanded FAQ entries in the SERP. For most sites that deployed FAQ schema primarily to capture that real estate, the honest accounting is straightforward: the feature is gone, the schema overhead is low, and there is no argument for removing it.
The broader principle holds: page elements that support machine understanding of content tend to outlast any individual SERP feature built on top of them. For the complete framework on structuring on-page signals for both search engines and users, the on-page SEO guide covers every layer from title tags to Core Web Vitals.
