In May 2026, Google quietly added a note to the top of its FAQ structured data documentation: FAQ Rich Results were no longer appearing in search. No blog post, no fanfare on social media — just one technical line that ended nearly a decade of established SEO practice. For thousands of sites that had invested in this schema.org markup, the question is now unavoidable: should you rip it all out, or is there still a reason to keep it?
This change fits a broader pattern: Google is steadily reclaiming SERP real estate for its own experiences — AI Overviews above all — by retiring features that used to give third-party snippets extra visual space. Here’s what actually happened, and more importantly, what to do about it.
What Actually Changed (and What Didn’t)
The deprecation rolled out in three distinct phases, and it matters to separate them clearly.
The Full Timeline
- May 7, 2026: FAQ Rich Results stopped appearing visually in Google Search results, for every site regardless of authority or niche.
- June 2026: FAQ-related Search Console reports and Rich Results Test support were removed.
- August 2026: Support for this data via the Search Console API was withdrawn as well, completing the retirement.
What Stayed the Same
The FAQPage schema type is still a perfectly valid Schema.org type. The markup doesn’t trigger any errors, penalties, or negative signals if it stays on your pages. What disappeared is purely the enriched visual display in search results — the presentation layer, not the content comprehension layer.
It’s also worth remembering that Google never confirmed FAQ markup as a direct ranking factor. Its value always came from the extra visibility it earned in search results, not from a hidden algorithmic boost.
Why Google Made This Call
A Trend That Started in 2023
This removal isn’t a sudden shock for anyone who had been tracking the issue closely. Back in August 2023, Google had already rolled FAQ Rich Results visibility back to a narrow class of government and health sites deemed especially authoritative. The 2026 retirement simply completes a trajectory that started three years earlier.
The Fight for SERP Real Estate
The real structural reason lies elsewhere: every rich block occupied by a third-party snippet is a block Google can’t use for its own AI-generated answers. With AI Overviews expanding, Google needs that visual space back. Removing FAQ Rich Results — one of the most vertically expensive features in the SERP — mechanically frees up room for AI summaries.
An Anti-Manipulation Signal Too
FAQ markup had also become a playground for aggressive over-optimization: sites stacked dozens of generic questions purely to inflate their visual footprint in search results, with little genuine content behind them. This cleanup cuts down on that kind of manipulation.
What to Actually Do on Your Site
1. Don’t Delete the FAQ Content — Just Drop the Reflex to Markup Everything
The consensus recommendation among SEO experts is clear: keep the visible content (the actual questions and answers), since it still helps visitors and can still be cited by generative AI tools. Only keep the schema markup if it costs nothing to maintain — it no longer causes harm, but it no longer earns a rich result either.
2. Redirect Your Markup Effort Toward Types That Still Work
Plenty of structured data types still earn rich results in 2026: Product, Article, Review, Event, LocalBusiness, and Organization among others. If your markup budget was concentrated on FAQ, redeploy it toward these types, which still deliver real visibility gains in traditional SERPs.
3. Think Q&A Format for Generative Engines, Not for Schema
AI systems — Google AI Overviews, ChatGPT, Perplexity, Gemini — generate answers by pulling from clearly structured content, and question-and-answer formatting remains one of the easiest patterns for these systems to extract. The difference: it’s no longer the JSON-LD markup that matters, it’s the visible HTML structure (H3 headings phrased as questions, with a concise answer right below).
4. Audit Your Old Search Console Reports
If you were tracking FAQ performance through Search Console, those reports disappeared in June 2026 and the API followed in August. Shift your tracking to other metrics instead: organic traffic on the affected pages, rankings on informational queries, overall click-through rate.
5. Don’t React in a Panic
There’s no urgency to mass-remove FAQPage markup from your site. That cleanup is a technical cost for zero benefit — leave it in place if it’s already there, and simply stop treating it as a priority going forward.
What This Change Says About SEO in 2026
This retirement illustrates a broader shift: chasing SERP features (rich snippets, featured snippets, FAQ blocks) is giving way to a harder requirement — genuinely useful content that can be understood and cited by both human readers and generative engines. Optimizing for a visual badge in search results matters less than optimizing for structural clarity and real informational value.
The sites that come out ahead won’t be the ones with the most markup — they’ll be the ones whose content most clearly answers the questions users, human or AI, are actually asking.
Real-world impact: what sites saw after the change
A B2B SaaS company that had built 40+ FAQ pages targeting long-tail support queries saw their impressions drop by 18% in the two weeks following May 7, 2026. But their click-through rate stayed flat, and organic traffic to those pages only declined by 3% — proof that the visibility loss came from the visual real estate shrinkage, not from a ranking penalty.
They restructured the content into a knowledge base format with clear H2 question headings and concise answers at the top of each section. Three months later, their pages started appearing as citations inside AI Overviews for the same queries, recovering part of the lost visibility through a different channel.
FAQ: Common questions about the FAQ Rich Results retirement
Should I delete all my FAQPage schema markup?
No. It doesn’t hurt to leave it in place, and some third-party tools or future features might still use it. Just don’t invest new development time adding it to pages where it’s missing.
Will FAQ content still help with AI Overviews and ChatGPT?
Yes, but it’s the visible HTML structure that matters, not the JSON-LD markup. Format your questions as H2 or H3 headings with clear, standalone answers directly below. That’s what generative engines extract.
Are there any schema types that might get deprecated next?
No confirmed list, but HowTo schema is rumored to be under review. The pattern is clear: if a rich result type becomes heavily spammed or conflicts with Google’s AI-driven SERP strategy, it’s at risk. Focus on schema types tied to transactional or local intent (Product, LocalBusiness, Event), which are harder for AI to replace.
Can I still use FAQ content for SEO, just without the markup?
Absolutely. Well-written Q&A content is one of the best formats for matching informational search intent and earning featured snippets or AI citations. The markup was never the valuable part — the content was.
Conclusion: Audit Your Structured Data Before It’s Too Late
The disappearance of FAQ Rich Results isn’t an isolated drama — it’s a warning sign about how fast SEO’s rules of the game keep shifting. Sites that passively follow five-year-old best practices quietly fall behind those that continuously adjust their strategy.
Want to know whether your structured data is still aligned with today’s Google and generative-AI standards? The team at seoforge.io offers a complete SEO audit that pinpoints exactly these technical blind spots and helps you prioritize the actions that actually matter in 2026. Discover our tools and support at seoforge.io.
