Upcoming deprecation: As of 7 May 2026, FAQ rich results are no longer appearing in Google Search. The FAQ rich result report will be removed in June 2026.
Google confirmed it on May 7, 2026: FAQ rich results — those expandable question-and-answer dropdowns that appeared directly in search results — are gone. The extra SERP real estate they provided has been removed, and the remaining reporting and testing support is being phased out over the coming months. If you’ve been using FAQ schema as a visibility tactic, that specific play is over.
But here’s the distinction that matters — and it’s one a lot of people are going to get wrong over the next few weeks: FAQ rich results are dead. FAQ content and structured data are not. These are completely different things, and confusing them will lead you to make bad decisions in either direction.
Let me break down exactly what changed, what didn’t, and the six practical things you should do about it right now.
What Google Actually Confirmed
From May 7, 2026, FAQ rich results — the expandable SERP features that showed individual questions and answers directly beneath a search result — stopped appearing. Google has confirmed this is permanent, not a bug or a temporary rollback. The reporting in Search Console will continue for a few months (it takes time to drain the historical data), and API support for FAQ appearance data ends in August 2026. If you have dashboards tracking FAQ rich result impressions, migrate those now — the data will disappear in June.
This isn’t entirely surprising. Google has been quietly reducing the prominence of FAQ rich results since 2023, when they limited them to a maximum of two per page and removed them from most non-authoritative sources. The May 2026 removal is the formal end of a feature that had already been significantly curtailed.
Why Google Removed Them
The pattern here is consistent with a broader direction Google has been moving in for several years: removing “visual SEO gimmicks” — SERP features that rewarded schema implementation rather than content quality — and replacing them with signals that indicate a page actually resolves intent well enough for AI systems to trust and summarise.
FAQ rich results became a victim of their own popularity. When every site started mass-producing thin FAQ blocks — five keyword-stuffed questions slapped on the bottom of every page purely to get the expandable dropdown — the feature stopped being a useful signal. Google’s response, as it usually is, was to remove the incentive entirely.
This is the same logic that killed exact-match anchor text manipulation, keyword density as a ranking factor, and the early versions of featured snippet optimisation. When something becomes a trick rather than a signal, it gets removed.
6 Things to Do Now
1. Stop Treating FAQ Schema as a CTR Hack
The original case for FAQ schema was straightforward: it expanded your SERP footprint, pushed competitors further down the page, and lifted click-through rate without any improvement to the underlying content. That specific use case is gone. If FAQ schema is in your toolkit purely as a visibility mechanism, remove it from your thinking entirely.
Practically: if a page only has FAQ blocks for SEO decoration — questions that don’t match real user intent, answers that are thin or keyword-stuffed, content that doesn’t actually appear visibly on the page — those FAQs should be removed or consolidated into genuine on-page content. The schema without the substance was always the wrong approach; now there’s no visual reward to justify the laziness.
2. Keep FAQs That Genuinely Help Users
This is the part that will get lost in the “FAQ schema is dead” take — and it’s the most important nuance. Useful FAQ content on a page still does real work. It answers objections before they turn into bounce. It captures long-tail query traffic. It reduces pre-sale friction. It improves conversion rates. It gives AI systems the semantic context they need to cite your page accurately.
The frame shift is from SERP decoration to UX content. FAQs were always primarily a user experience tool — they just got misused as an SEO shortcut. Now that the shortcut is closed, the legitimate purpose reasserts itself. A well-written FAQ section on a service page, answering the five questions every prospective client actually asks, is more valuable today than it was last month. It just doesn’t get a visual bonus in search results for it.
Think of your FAQ content in three new frames: UX content (reduces friction), semantic clarity (helps AI understand your page’s scope), and AI retrieval support (makes your answers citable in AI Overviews and conversational search). None of those functions disappeared on May 7.
3. Keep FAQPage Schema Selectively — Don’t Panic-Remove It
Google has explicitly stated there’s no need to proactively remove FAQPage schema. The structured data itself isn’t being penalised — only the visual rich result it previously triggered has been removed. The schema still contributes to machine understanding of your content, which matters more for AI-driven search than it ever did for traditional blue-link results.
The sensible approach:
- Keep FAQPage schema if: the FAQ is visibly present on the page, the questions reflect genuine user intent, and the answers are unique and substantive
- Remove it if: it’s auto-generated, keyword-stuffed, duplicated identically across multiple pages, or completely disconnected from what users actually ask
The filter is simple: would this FAQ section be useful to a real visitor who landed on this page with a genuine question? If yes, keep the schema. If it exists only to game SERP features that no longer exist, remove the content and the schema together.
4. Shift Effort Toward Schema Types That Still Drive Rich Results
FAQ schema was never the highest-value structured data anyway. The schema types that still directly affect SERP appearance and machine understanding should be getting more of your attention:
- Article schema — signals content type and expertise for blog posts and editorial content
- Product schema — price, availability, and review data in product results
- Review and AggregateRating schema — star ratings in SERPs, still very much alive
- LocalBusiness schema — critical for local search visibility and Google Business integration
- BreadcrumbList schema — clean URL structure signals in results
- Video schema — video carousels and key moments features
- Organization and Person schema — entity authority signals, increasingly important for AI systems that need to understand who is publishing content and why they’re credible
If FAQ schema was taking disproportionate time and resource in your workflow, this is a good moment to redistribute that effort.
5. Build for AI Retrieval, Not SERP Decoration
The removal of FAQ rich results is a symptom of a larger structural shift in how search works. Google is reducing features that reward schema tricks and increasing features that reward pages that AI systems can confidently summarise and cite. AI Overviews, conversational search, and synthesised answers are the growth surface in search right now — and they have completely different requirements than traditional rich results.
What AI retrieval rewards:
- Concise, direct answers — questions answered in the first 1–2 sentences, then expanded below
- Expert commentary — genuine perspective and analysis, not summaries of what other sources have said
- First-hand experience — content that demonstrates the author has actually done the thing they’re writing about
- Citations and data — specific statistics, dates, and references that AI systems can verify
- Strong topical structure — clear headings, logical flow, comprehensive coverage of the topic
Here’s the irony worth sitting with: good FAQ content — real questions, substantive answers, written by someone with genuine expertise — may become more valuable in an AI search world even as the SERP feature that highlighted it disappears. The content that was genuinely useful to users is exactly what AI systems are looking for to synthesise answers from. The thin, decorative FAQ blocks that dominated the space were never good content — they were just good at gaming a specific SERP feature. That specific game is over.
6. Update Your Reporting Workflows Now
The practical housekeeping: if you have dashboards, client reports, or API integrations that track FAQ rich result impressions, clicks, or appearance rates — start migrating them immediately. The data disappears from Search Console in June 2026 and API support ends in August 2026. Don’t wait for those deadlines; the migration work is better done now when you have the reference data to calibrate against.
For agencies reporting on FAQ performance to clients, this is also a good moment to reset expectations about rich results as a vanity metric. FAQ impressions were often impressive-looking numbers that didn’t translate cleanly to business outcomes. Replacing them with more meaningful engagement metrics — time on page, conversion rate from organic, question-specific landing page performance — is a more defensible reporting framework anyway.
The Bigger Signal
Pull back and look at this change in context. Over the past three years, Google has removed or reduced: exact-match keyword signals, several types of rich result features, the prominence of meta keywords, and various structured data types that rewarded implementation over content quality. Each removal follows the same logic — when a feature becomes primarily a vehicle for gaming rather than a signal of genuine quality, it gets cut.
The direction of travel is clear: Google is building a search system optimised for AI-driven answer synthesis, not for the visual architecture of a traditional results page. The signals that survive are those that accurately reflect content quality, expertise, and intent-resolution — because those are the signals that make AI search work.
For businesses and marketers, the adjustment is a mindset shift rather than a technical one. Build content that answers real questions thoroughly and credibly. Implement structured data that accurately describes what your content is and who produced it. Stop chasing SERP features as the primary goal. The sites that do those things well will be positioned for the search landscape that’s emerging — not the one that’s ending.
Need help auditing your structured data or content strategy in light of these changes? Get in touch — this is exactly the kind of transition planning I work through with clients.
FAQ
Do I need to remove FAQPage schema from my site?
No — Google has explicitly said there’s no need to proactively remove FAQPage schema. The structured data isn’t being penalised; only the visual rich result feature has been removed. If your FAQ content is genuine and useful, keep both the content and the schema. Only remove it if the FAQ blocks were purely decorative, thin, or keyword-stuffed with no real user value.
When does FAQ rich result data disappear from Search Console?
FAQ appearance data stops being reported in Search Console in June 2026. API support for FAQ rich result data ends in August 2026. If you rely on either for reporting, migrate your dashboards before June to preserve historical reference points.
Does FAQ content still help with Google AI Overviews?
Yes — arguably more than it helped with traditional rich results. AI Overviews pull from pages that directly and clearly answer specific questions. Well-written FAQ content, with concise and substantive answers to genuine user queries, is highly citable for AI systems. The difference is that the reward now comes through AI citation rather than a visual SERP feature. The content strategy is the same; the display mechanism has shifted.
Which schema types should I focus on instead of FAQ schema?
Prioritise schema types that still drive rich results or contribute to entity understanding: Article, Product, Review/AggregateRating, LocalBusiness, BreadcrumbList, Video, Organization, and Person schema. These continue to influence SERP appearance and — critically — help AI systems understand your content’s context, authorship, and credibility.
Should I stop writing FAQ sections on my pages?
No — stop writing thin, decorative FAQ sections written for SERP features rather than users. Genuine FAQ sections — answering the real questions your audience has, with substantive answers that reflect actual expertise — remain valuable for user experience, conversion optimisation, long-tail search traffic, and AI retrieval. The removal of FAQ rich results removes a bad reason to write FAQs, not a good one.