Google finally did what a lot of us in SEO could see coming from a mile away: it killed FAQ rich results for normal websites.
If you built part of your click-through strategy around those expandable FAQ snippets, the party is over. But I do not think this is bad news unless your SEO plan depended on cosmetic SERP tricks more than real content quality.
After more than 20 years in SEO, I have seen this cycle again and again. Google surfaces a feature, the industry over-optimizes around it, and then Google tightens the rules once abuse becomes more common than value. That is exactly what happened with FAQPage markup.
Google’s official FAQ documentation now says FAQ rich results are only available for well-known, authoritative government-focused or health-focused websites, and Google’s documentation updates page says the feature will no longer appear in Search starting May 7, 2026. Search Engine Land also reported that Google will remove the FAQ search appearance, rich result report, and Rich Results Test support in June 2026, with Search Console API support removed in August 2026.
“Going forward, FAQ (from FAQPage structured data) rich results will only be shown for well-known, authoritative government and health websites.”
That 2023 announcement was the warning shot. The May 2026 documentation update was the final obituary.
What Google Actually Changed
The timeline matters, because a lot of marketers will misread this as a sudden reversal when it was really a slow-motion shutdown.
- August 2023: Google announced that FAQ rich results would only be shown regularly for authoritative government and health websites. For everyone else, visibility would be reduced or disappear altogether.
- May 7, 2026: Google stopped showing FAQ rich results in Search.
- May 8, 2026: Google added the deprecation notice to its FAQPage documentation and documentation updates log.
- June 2026: Google is dropping the FAQ search appearance, the rich result report, and support in the Rich Results Test.
- August 2026: Support for the FAQ rich result in the Search Console API is scheduled to be removed.
If you are managing SEO reporting pipelines, that last point matters more than people think. Once the API support disappears, dashboards and internal scripts that still expect FAQ rich result reporting will break or start returning incomplete data.
Why Google Killed FAQ Rich Results
My opinion is simple: Google killed FAQ rich results because too many sites were using them to inflate SERP real estate instead of improve search quality.
I have audited enough websites to know how this played out in the real world. A ton of FAQ sections were not written because users genuinely needed them. They were written because agencies wanted more pixels in the search result.
That led to the same problems we see whenever a markup tactic gets popular:
- boilerplate questions copied across dozens of pages
- weak answers that existed only to justify schema
- local service sites stuffing every service page with generic FAQ blocks
- publishers optimizing for click-bait presentation instead of information gain
Google has been moving toward cleaner, less cluttered search results for a while. In that context, this change is not surprising at all. It is part of the broader shift away from low-value rich-result decoration and toward stronger trust, clearer entities, and better source quality.
The Big Mistake SEOs Will Make Next
The wrong reaction is to panic-delete every FAQ section on your site.
Google said back in 2023 that you do not need to proactively remove the markup. Structured data that is not being used does not cause problems for Search, even if it has no visible effect in Google’s results. Search Engine Land also noted that other search engines may still use it.
So the real question is not, “Should I nuke every FAQ?”
The better question is, “Does this FAQ section genuinely help the visitor, or was it only there for Google?”
If the FAQ content is repetitive, thin, or obviously stuffed onto the page, I would cut or rewrite it. If the FAQ section genuinely reduces friction, addresses objections, or helps a buyer move forward, keep the content even if Google no longer rewards it with a special search treatment.
What Still Matters in Structured Data
This is the part too many people will miss: Google did not kill structured data. Google killed one overused visual outcome of structured data.
That is a huge difference.
For most businesses, the schema work that still matters includes:
- Organization schema for brand clarity
- LocalBusiness schema for local trust and entity consistency
- Article and BlogPosting schema for content understanding
- Product and Review schema where the page genuinely qualifies
- DiscussionForumPosting and QAPage markup where user-generated content actually exists
I have been writing for a while now that the bigger game is not “how do I win one more snippet?” The bigger game is helping Google, ChatGPT, Gemini, Perplexity, and every other retrieval layer understand who you are, what your site covers, and why your page deserves to be cited.
That is why articles like Schema Markup Explained: How Structured Data Gets You More Clicks, Structured Data for Service Businesses: The Schema Types That Actually Get Rich Results, and Advanced Schema Markup: Going Beyond the Basics to Win Rich Results matter more now, not less.
What I Would Do on jonalonso.com Right Now
If this were my site strategy meeting, here would be the practical to-do list.
Immediate To-Do List
- Audit every FAQ section on the site. Separate useful FAQs from filler FAQs written for SERP expansion.
- Keep helpful FAQ content, but stop treating FAQPage markup as a traffic lever. The content can still help conversions even if the snippet is gone.
- Update any SEO reporting or Looker Studio dashboards. Remove dependencies on FAQ rich result reporting before the June and August 2026 removals create broken widgets or bad trendlines.
- Shift schema effort into stronger entity signals. Tighten Organization, LocalBusiness, Article, and any valid review or product markup.
- Rewrite weak service-page FAQs into stronger buyer-focused sections. Better objections, better trust language, better examples.
- Double down on information gain. If two competitors have the same service page, the one that says something more useful, more specific, and more credible is going to win more clicks.
- Use internal linking to reinforce the new strategy. Connect this topic with pieces on brand authority, E-E-A-T, internal linking, and entity-driven SEO.
That last point matters a lot. This article should naturally support and be supported by broader pieces on SEO in 2026, how to rank on Google in 2026, and authority-focused content about trust, structure, and site clarity.
What Service Businesses Should Learn From This
If you are a contractor, med spa, law firm, dentist, or local service brand, here is the uncomfortable truth: FAQ schema was never going to save a weak page.
A strong local SEO page still needs the same fundamentals:
- clear intent targeting
- credible experience and proof
- entity consistency across site and profiles
- good internal links
- clean UX and trustworthy conversion language
I am actually glad Google made this change, because it forces marketers back toward fundamentals. And fundamentals age better than hacks.
FAQ About the FAQ Rich Results Deprecation
Should I remove FAQPage schema from my website?
Not automatically. Google said there is no need to proactively remove structured data that is no longer being used. I would decide based on whether the underlying FAQ content still helps users and whether the markup still serves any non-Google purpose.
Will removing FAQ schema hurt my rankings?
Google said the FAQ rich result change should not be considered a ranking change. What may change is click-through rate or search appearance, not the core ranking algorithm itself.
Does FAQ content still have value if the rich result is gone?
Yes, if it improves the page for humans. Good FAQ content can still address objections, reduce confusion, and improve conversion quality. Bad FAQ content should be cut regardless of markup.
What structured data should I focus on now?
For most businesses, prioritize Organization, LocalBusiness, Article, Product, Review, and any other markup type that accurately reflects the page and still maps to Google-supported outcomes.
What happens in Search Console next?
Per Search Engine Land’s reporting on Google’s documentation notice, Google is removing the FAQ search appearance, rich result report, and Rich Results Test support in June 2026, with Search Console API support removed in August 2026. If you report on FAQ performance today, update those systems now.
Final Take
FAQ rich results are dead, but the lesson is bigger than one feature.
The future of SEO does not belong to people stuffing markup onto average pages and hoping for bigger snippets. It belongs to people building sites that are easier to understand, easier to trust, and harder to ignore.
That means better structure, better entities, better content, and better judgment.
Honestly, that is a healthier version of SEO anyway.
Sources: Google FAQPage documentation, Google Search Central Blog announcement, Google Search documentation updates, Search Engine Land coverage.
