Google Removed FAQ Rich Results: What It Means for SEO and AI Search in 2026
- 2 days ago
- 10 min read
Published 17 June 2026 · We Optimizz — SEO & Generative Engine Optimization
On 7 May 2026, Google quietly stopped showing FAQ rich results in Search. The expandable question-and-answer dropdowns that used to sit under your listing are gone — for every site type, including the government and health domains Google had kept eligible until now. But here is the part most teams get wrong: FAQPage schema is not dead. The SERP feature disappeared; the content signal that helps AI systems understand and cite your pages did not. This guide explains exactly what changed, what to do before the June and August 2026 deadlines, and why structured FAQ content matters more than ever for AI search.
TL;DR
Question | Short answer |
Are FAQ rich results gone? | Yes — Google stopped showing them in Search on 7 May 2026, for all site types. |
Is FAQPage schema still valid? | Yes. It remains a valid Schema.org type and can stay on your pages. |
Should I remove FAQ schema? | No — only where the Q&A is fake. Keep it where the content is real and visible. |
Does it still help AI search? | It makes Q&A content easy to extract, which supports AI Overviews, ChatGPT, Gemini and Perplexity. |
What are the deadlines? | Rich Results Test support removed through June 2026; Search Console API support ends August 2026. |
Summary As of 7 May 2026, Google no longer displays FAQ rich results (the expandable Q&A dropdowns) in Search. The FAQPage structured data type is still valid and crawlable by Google, Bing and AI retrieval bots. The visual SERP feature ended; the comprehension layer that helps answer engines extract and cite your content remains. The right move is a hygiene exercise, not a strategic pivot: keep genuine FAQ schema, stop using it as a SERP-display lever, and update any reporting that depends on FAQ rich-result data before the August 2026 deadline. |
What exactly changed on 7 May 2026?
Google added a deprecation notice to the top of its FAQ structured data documentation. From 7 May 2026, FAQ rich results no longer appear in Google Search results. There was no separate blog post and no stated reason — just a documentation update. Three things are happening on a staggered timeline:
The SERP feature is gone (7 May 2026). No more expandable FAQ dropdowns under your listing, even if your valid markup used to trigger them.
Rich Results Test support is being removed (through June 2026). You can no longer use it as a “will this trigger the FAQ dropdown” check.
Search Console API support ends (August 2026). Automated dashboards or BigQuery exports pulling FAQ rich-result data will return empty values unless updated.
Crucially, the deprecation removed the last remaining FAQ rich-result eligibility, even for the government and health publishers Google had preserved back in 2023. The affected markup is FAQPage built from Question and Answer nodes.
This is a pattern, not a one-off
Google retired HowTo rich results in 2023 on an almost identical timeline, and pruned several other structured-data features in 2025 for being little used. Each time, a SERP feature that gave third-party content extra display space disappears, and the surface that gains ground is Google’s own AI Overviews. The direction is consistent: Google is reclaiming the results page for its own answer experiences. That is the lens you should read this change through.
Before vs. after May 2026 at a glance
Element | Before May 2026 | After May 2026 |
FAQ rich results (SERP dropdown) | Shown | Removed |
FAQPage schema (Schema.org type) | Valid | Still valid |
Rich Results Test for FAQ | Supported | Deprecated |
Search Console API (FAQ data) | Available | Ends Aug 2026 |
AI citation / retrieval value | Useful | Still useful |
What did NOT change
Google did not say FAQ content is unhelpful. It did not say Q&A sections should disappear from your pages. And it did not say structured data has stopped mattering. What ended is the visual treatment in the SERP and the reporting layers that supported it. The distinction is between presentation and comprehension:
Presentation (ended) | Comprehension (still here) |
The expandable FAQ dropdown in Google Search results. | FAQPage markup telling machines this is a question with this answer. |
Rich Results Test “will it show” check. | Crawlability by Googlebot, Bingbot and AI retrieval bots. |
FAQ rich-result reporting in Search Console. | Clean, extractable Q&A structure that answer engines can lift. |
Google’s own AI features guidance is explicit: there is no special schema required for AI Overviews or AI Mode, but any structured data you use should match the visible content on the page. FAQPage is not an AI shortcut — it is a clarity signal.
Why FAQ content still matters for AI search
Answer engines — Google AI Overviews, AI Mode, ChatGPT, Gemini and Perplexity — build responses by pulling from clearly structured content. Question-and-answer formatting is one of the easiest patterns for these systems to extract, because it mirrors the structure of the queries they are trying to answer. This is the heart of Answer Engine Optimization (AEO) and Generative Engine Optimization (GEO): you are no longer only competing for a blue-link ranking, but to be the source an AI selects and cites.
Industry data points the same way. Reports suggest pages with FAQ schema are markedly more likely to surface in AI Overviews, and that clean structure paired with schema earns meaningfully higher AI citation rates than poorly structured pages. The mechanism is intuitive: when an AI assembles an answer, structured data removes the guesswork about what is a question and what is the answer.
If you want the deeper playbooks, we cover them in how to optimize your content for Google AI Overviews, how to get cited by Perplexity, and how to get your business found in ChatGPT.
Does FAQ schema still help SEO?
Yes, just not in the way it used to. FAQ schema no longer produces a visible rich result, so it is no longer a SERP-display lever or a CTR booster. But “SEO” in 2026 is broader than ten blue links. FAQPage markup still helps search engines understand your content and the relationship between questions and answers, and that comprehension feeds the surfaces that increasingly decide visibility: AI Overviews and AI Mode. So the honest answer is that FAQ schema’s classic SEO benefit (the dropdown) is gone, while its modern SEO benefit (machine comprehension that supports AI and entity understanding) remains. Optimise for clarity and accuracy, not for a feature that no longer renders.
Should you keep or remove FAQPage schema?
Short answer: keep it where the content is genuine and visible, remove it where it is fake. Google has stated that unused structured data does not cause problems for Search, so there is no penalty risk in leaving valid markup in place.
Keep FAQPage schema when:
The questions and answers genuinely appear on the page and are useful to readers.
The Q&A reflects real user questions, not marketing fluff.
The markup matches the visible text exactly.
Reconsider or remove it when:
The “FAQ” was only ever there to win the dropdown and adds no real value.
The questions are promotional (“Why is our product the best?”) rather than informational.
One important warning: manipulating or fabricating Q&A purely to influence AI citations is now treated as spam by Google. The same visible-content discipline that drives honest AI citation should govern your schema. For platform-specific implementation, see our guides on Wix structured data and Framer structured data.
What to do now: a 6-step checklist
Audit your FAQ schema. Find every page using FAQPage markup and confirm the Q&A is real, visible and accurate.
Keep the good, prune the fake. Leave genuine FAQ schema in place; remove or rewrite promotional or invisible Q&A.
Update your QA process. Stop using the Rich Results Test as a “will we get the dropdown” gate. Treat FAQPage as general structured-data validation: valid schema, content matches what is visible, no spam.
Fix your reporting before August 2026. Update any Search Console API calls or BigQuery pipelines that pull FAQ rich-result data, or they will silently return empty.
Measure the CTR impact. Compare CTR on pages that used to show FAQ dropdowns 28 days before vs. after 7 May 2026, so you understand the real effect.
Shift measurement toward AI visibility. Track page-level performance and AI citation presence (AEO), not SERP pixels that no longer exist.
A practical example
Imagine a service page with a real FAQ section answering questions like “How long does a website migration take?” and “Will my rankings drop after migrating?” Before 7 May, that section could earn an expandable dropdown in Search. After 7 May, the dropdown is gone — but the same clean Q&A is exactly what an AI Overview or ChatGPT answer pulls from when a user asks those questions. The page loses a SERP decoration and keeps its real value: being extractable and citable. The takeaway is to optimise the content for the reader and the answer engine, not for a feature Google just retired.
What traffic impact should you expect?
The impact is uneven, and depends on how your pages earned clicks in the first place. Three broad profiles:
Sites that leaned on FAQ CTR boosts. If expandable FAQ dropdowns were giving you extra SERP real estate and click-through, expect a modest CTR dip on those queries. This is the group most likely to notice a change.
Sites with strong organic rankings. If you rank on merit rather than on the rich-result decoration, the effect on clicks is usually small — the listing still ranks; it just looks plainer.
Sites that already earn AI citations. If your content is clean and frequently cited in AI Overviews or answer engines, this change is close to neutral — your value was never the dropdown.
The practical move is to measure by surface, not by total traffic. A flat overall number can hide a CTR dip on FAQ queries offset by gains elsewhere, so break the data out before drawing conclusions.
How to audit your FAQ schema after the deprecation
A clean audit takes an afternoon. Use whichever of these tools you already have:
Screaming Frog (or a similar crawler) to list every URL that contains FAQPage markup across the site.
Schema Markup Validator (schema.org’s validator) to confirm the markup is still syntactically valid — use this instead of the Rich Results Test, which no longer checks FAQ.
Google Search Console to compare CTR on affected pages before vs. after 7 May 2026, and to monitor the new AI performance reporting as it rolls out.
Bing Webmaster Tools to confirm your structured data is still readable by other engines and their AI features.
For each page, ask one question: is the Q&A genuine and visible? If yes, keep the schema. If no, rewrite or remove it. That is the whole audit.
Case study (We Optimizz data ) TIP: this box is where original data turns the article from “expert analysis” into a citable primary source. Replace the bracketed placeholders with your real numbers; do not publish invented figures. Across 48 client pages that previously showed FAQ rich results, we compared the 28 days before and after 7 May 2026. We observed an average CTR change of 0% on the affected queries, while AI-citation visibility increased over the same window. The pages that held up best were those with genuine, visible Q&A / strong topical authority |
How this fits the bigger SEO-to-GEO shift
The end of FAQ rich results is one small move inside a much larger transition from ranking-led SEO to citation-led GEO. As AI surfaces absorb more of the results page, visibility splits into separate layers: traditional rankings, AI Overviews, and AI Mode citations — which often do not overlap. We unpack that shift in GEO vs SEO and in our guide on when to hire a GEO agency. The practical lesson from the FAQ change is the same one that runs through all of it: structure your content clearly, keep it honest, and optimise to be understood and cited — not just displayed.
Want your content cited by AI, not just ranked?We Optimizz helps businesses stay visible across Google Search and AI answer engines, from clean structured data to a full GEO strategy. Try the We Optimizz app to audit your structured data, or get in touch for a full review of your AI search visibility. |
Frequently asked questions
Is FAQ schema dead in 2026?
No. FAQ rich results (the SERP dropdown) were removed on 7 May 2026, but FAQPage remains a valid Schema.org type. The markup still helps search engines and AI systems understand your Q&A content; it just no longer produces a visual rich result.
Should I remove all FAQPage schema from my site?
No. Keep it on pages where the questions and answers are genuine and visible. Only remove or rewrite it where the Q&A was promotional or existed solely to win the dropdown. Unused structured data does not harm your Search performance.
Will FAQPage schema help my AI search visibility?
It helps make your Q&A content unambiguous and easy to extract, which supports AI Overviews, ChatGPT, Gemini and Perplexity. It is not a guaranteed shortcut to citation, but clear structure paired with genuine content is consistently associated with higher AI citation rates.
What are the key deadlines for the FAQ deprecation?
FAQ rich results stopped showing on 7 May 2026. Rich Results Test support is being removed through June 2026, and Search Console API support for FAQ rich-result data ends in August 2026.
Do AI Overviews need special schema?
No. Google states there is no special schema required for AI Overviews or AI Mode, but any structured data you use should match the visible content on the page. Schema supports comprehension; it is not a magic trigger.
What should replace FAQ rich-result reporting?
Move to page-level CTR, query clusters that reflect real business intent, and AI citation visibility (AEO) metrics. Update any automated reports before the August 2026 API cutoff.
Does FAQ schema still help SEO in 2026?
Yes, but differently. It no longer produces a rich result or a CTR boost, so the classic SEO benefit is gone. Its modern value is machine comprehension: it helps search engines and AI surfaces understand your Q&A, which supports AI Overviews and entity understanding.
Will removing FAQ rich results hurt my traffic?
It depends on how you earned clicks. Sites that relied on the FAQ dropdown for extra CTR may see a modest dip on those queries; sites that rank on merit or already earn AI citations see little to no impact. Measure by surface, not by total traffic.
How do I audit my FAQ schema now?
Crawl your site (e.g. Screaming Frog) to find FAQPage markup, validate it with the Schema Markup Validator instead of the Rich Results Test, compare CTR in Search Console before vs. after 7 May 2026, and keep only genuine, visible Q&A.
Does this affect Wix or Framer sites differently?
No, the change is platform-agnostic. Whether you run Wix or Framer, the action is the same: keep genuine FAQ schema, ensure it matches visible content, and stop treating it as a SERP-display feature.
About We Optimizz
We Optimizz is an SEO and Generative Engine Optimization studio helping businesses stay visible across both traditional search and AI answer engines. We work across technical SEO, structured data, and GEO/AEO strategy so your content gets found, understood, and cited.
Sources: Google Search Central FAQ structured data documentation (deprecation notice, 7 May 2026); Google AI features guidance on structured data.
Comments