Why Google Killing FAQ Rich Results Makes FAQs More Important
More news posts coming soon.
- Google updated its Search Central documentation on May 7, 2026, confirming that FAQ rich results have stopped appearing in Google Search for all websites — including the government and health sites that retained them after the 2023 restriction.
- The deprecation rolls out in three phases: rich results gone now, Search Console reporting retired in June 2026, Search Console API support removed in August 2026.
- Google explicitly stated it will continue to use FAQPage structured data to better understand pages, even after the visual feature is gone — a distinction almost all coverage has understated.
- Pages with FAQPage schema are 3.2 times more likely to appear in Google AI Overviews, according to a Frase study of citation rates across structured data types.
- A Relixir analysis of 50 sites found pages with FAQPage markup achieved a 41% AI citation rate versus 15% for pages without it — a 2.7 times difference.
- The correct strategic response is not to remove FAQ schema — it is to stop treating FAQs as SERP decoration and start building them as machine-readable answer infrastructure for AI retrieval systems.
Google updated its FAQ structured data documentation on May 7, 2026, with a deprecation notice that ends a feature most of the web lost access to three years ago. FAQ rich results — the expandable question-and-answer dropdowns that appeared directly in search results — are no longer appearing in Google Search for any website. The announcement is short, the reasoning is unexplained, and most coverage has focused on the wrong half of it.
The half that matters is buried in the final line of Google’s deprecation notice: the company confirmed it will continue to use FAQPage structured data to better understand pages, even though the visible rich result feature is gone. For SaaS content teams and SEOs who have spent the past three years wondering whether FAQ schema is still worth implementing, that line is the answer — and it points in the opposite direction from what the headline suggests.
What Google Actually Announced
Google’s deprecation notice, posted directly to its Search Central developer documentation on May 7, 2026, reads: “FAQ rich results are no longer appearing in Google Search. We will be dropping the FAQ search appearance, rich result report, and support in the Rich results test in June 2026. To allow time for adjusting your API calls, support for the FAQ rich result in the Search Console API will be removed in August 2026.” The company did not publish a blog post, provide a rationale, or offer any explanation beyond the documentation update itself. The announcement is also notable for what it does not say: it does not instruct site owners to remove their FAQ structured data.
The deprecation has three concrete dates for SEO and content teams to track. The visual feature — the accordion dropdowns that appeared in search results — was already gone as of May 7. The Search Console reporting layer, including the rich result status report and the Rich Results Test support for FAQ markup, disappears in June. Developers who have built monitoring workflows or dashboards that pull FAQ rich result data via the Search Console API have until August before that API access is retired. Any team tracking FAQ impressions as a key performance indicator in a live dashboard should update those reports before August; the underlying data will simply stop being reported.
Why the Timing Is Not a Coincidence
The May 2026 deprecation completes a process that began in August 2023, when Google restricted FAQ rich results to government and health sites after widespread abuse of the feature. Sites had been manufacturing artificial FAQ sections — questions that did not reflect real user intent and answers written solely to occupy more SERP pixels — to inflate their visible real estate in search results. Google’s initial response was surgical: keep the feature for sites where FAQ content serves genuine public information needs, remove it for everyone else. The 2026 announcement removes it for the remaining qualifying sites too, closing the loop on a feature that had been functionally dead for most of the web for nearly three years.
The timing of the full removal aligns with a broader shift in how Google is managing its search result page. AI Overviews — the AI-generated summaries that now appear at the top of roughly 50 to 60 percent of US searches — have fundamentally changed what the SERP looks like and what types of content it surfaces. A system built to generate synthesised answers from multiple sources has less need for individual page features that expand content directly in search results. The accordion dropdown was always a display feature; the underlying data it represented — a page containing structured question-and-answer pairs — is exactly what AI retrieval systems are optimised to find and extract. Google removed the display mechanism. The data function continues.
Between 2020 and 2023, FAQ schema became one of the most aggressively manipulated structured data types in SEO. The value proposition was clear and visible: implement FAQPage markup correctly, and your search result could expand to show multiple question-and-answer pairs directly in the SERP, pushing competitor results further down the page. Some pages were adding ten or more FAQ items, each occupying additional vertical space. The quality of the content was irrelevant to whether the rich result appeared — only technical validity mattered. This created a direct incentive to manufacture FAQ content with no relationship to real user questions. By the time Google announced the August 2023 restriction, it was responding to a signal problem of its own creation: a rich result that had been designed to surface useful content had instead become a mechanism for displacing it. The restriction to government and health sites was not an acknowledgment that FAQ content was inherently low quality — it was an acknowledgment that the incentive structure had produced a crop of FAQ sections that were written for machines, not readers. The May 2026 full deprecation extends that logic to the last remaining sites with access. Whether government and health FAQ content was materially better than commercial FAQ content is an open question; what is clear is that Google’s cleanup of the SERP feature is now complete.
The Difference Between a Rich Result and a Comprehension Signal
Two functions, one schema type
FAQPage schema has always served two distinct functions that most practitioners conflated because the rich result was visible and the comprehension function was not. A rich result is a display feature — it takes structured data and renders a visual element in the search results page. A comprehension signal is something different: it is machine-readable markup that tells Google what a page is about, how its content is organised, and what relationships exist between the entities on the page. Rich results are the visible payoff of some structured data types. Comprehension is the underlying value that exists independently of whether any visible feature is rendered. Google’s deprecation notice makes this distinction explicit. The line that removes the rich result and the line that confirms the schema continues to be used for page understanding are both in the same short notice. They are not in tension — they are describing two separate things that happen to share a markup type.
For a page that has implemented FAQPage markup correctly — meaning visible question-and-answer content on the page that matches what the schema describes — nothing functionally changes on May 7 except the disappearance of a SERP feature that most sites had already lost in 2023. The markup continues to tell Google that the page contains a structured set of question-and-answer pairs. That signal feeds into how Google classifies the page, how it matches the page to user queries, and — critically — how it determines whether the page is a suitable source for extracting an answer in an AI-generated response. The display mechanism is gone. The data remains.
With FAQ rich results gone, what is your FAQ schema strategy?
Based on 1,240 reader votes
“FAQ rich results are no longer appearing in Google Search. We will be dropping the FAQ search appearance, rich result report, and support in the Rich results test in June 2026. [Google] will continue to use FAQ structured data to better understand pages.
— Google Search Central Documentation, May 7, 2026
What the Data Says About FAQ Schema and AI Citations
The evidence base for FAQ schema as an AI citation driver has been building independently of the rich results conversation. A Frase study of citation rates across structured data types found that pages with FAQPage markup are 3.2 times more likely to appear in Google AI Overviews than pages without it. A Relixir analysis of 50 sites found that pages using FAQPage schema achieved a 41% AI citation rate compared to 15% for pages without the markup — a 2.7 times difference. Research from AirOps found that pages combining clean heading structure with FAQPage schema earned 2.8 times higher AI citation rates than poorly structured pages. These are not marginal gains. They reflect a structural advantage that comes from giving AI retrieval systems exactly what they are optimised to find: clearly delimited question-and-answer pairs with machine-readable labels on what the question is and what the answer is.
The caveat that belongs here is also important. Research from SE Ranking found that pages with FAQ schema averaged 4.9 AI Mode citations versus 4.4 for pages without it — a real but modest lift. AirOps found that FAQ and Q&A schema appeared in only 10.5% of AI-cited pages despite aligning closely with how answer engines retrieve information. The data does not support treating FAQ schema as a guarantee of AI citation. What it supports is the position that FAQ schema, when applied to genuine question-and-answer content, contributes a meaningful signal to the pool of inputs that AI retrieval systems use to evaluate and select sources. The schema alone does not win citations. The schema combined with substantive, well-structured answers to questions that reflect real user intent is what earns them. This is, incidentally, the same standard that good FAQ content should have met all along — the deprecation of the rich result has simply removed the incentive to fake it.
FAQPage schema and QAPage schema address different content structures and have been treated differently by Google through the deprecation process. FAQPage schema is designed for pages where the site itself authors both the question and the definitive answer — a single, controlled answer per question, written by the publisher. This is the schema type used on product pages, service pages, help documentation, and dedicated FAQ sections. It is also the type that Google deprecated on May 7, 2026. QAPage schema is designed for community-driven question-and-answer formats where multiple users can submit competing answers to a single question — the structure used by Stack Overflow, Quora, Reddit, and similar platforms. QAPage has not been restricted in the same way as FAQPage. For SaaS content teams, the practical distinction is straightforward: if your FAQ section contains questions you wrote and answers you control, FAQPage is the correct schema type, and it is the one Google has committed to continuing to use for page comprehension even after removing the rich result. If your site hosts user-submitted Q&A content with multiple competing answers, QAPage applies instead. The deprecation announcement does not affect QAPage schema or the sites that use it.
The Infrastructure Beneath the SERP Feature
To understand why FAQ schema retains value after the rich result is gone, it helps to understand how AI answer engines actually extract and select content. Systems like Google AI Overviews, ChatGPT and Claude, and Perplexity do not scrape random text from pages — they retrieve content by matching page signals to the structure of a user’s query. A conversational query — “what is the difference between an AI agent and a chatbot” — is structurally a question looking for a structured answer. A page that has explicitly marked up its content as a question paired with an answer has removed interpretive burden from the retrieval system. The schema is telling the machine: this part is the question, this part is the answer, they belong together. A page without that markup forces the retrieval system to infer those relationships from layout, language patterns, and heading hierarchy — a less reliable process that introduces more opportunity for the answer to be extracted from the wrong place or attributed to the wrong question.
An Ahrefs study of 863,000 keyword SERPs published in February 2026 found that only 38% of pages cited in AI Overviews ranked in the organic top 10 — down from 76% in mid-2025. Pages without traditional domain authority can win AI citations if they are structured clearly enough for AI extraction. This is the most significant finding in the AI search data of the past twelve months, and it is directly relevant to how FAQ schema should be understood after May 7. The visibility competition is no longer only about ranking. It is about whether a retrieval system can parse your content quickly, trust its structure, and extract a useful answer. FAQ schema contributes to all three. The rich result was never the point; it was a secondary benefit of having done the work correctly. Now it is gone, and the underlying work still matters — arguably more than before, because the AI surface area it influences is larger than the SERP feature it replaced.
No spam. Unsubscribe anytime.
The Inversion Nobody Noticed
Here is what the coverage of this story has mostly missed: the deprecation of FAQ rich results has not reduced the value of FAQ schema — it has clarified it. For the entire period between 2019 and 2023, the reason most SaaS sites and publishers implemented FAQPage schema was the accordion dropdown. The visible real estate gain was the motivation. The comprehension signal was incidental. This meant that FAQ schema was evaluated as a SERP feature investment — something you did to get a specific, measurable visual outcome. When the rich result disappeared for most sites in 2023, many teams concluded the investment was no longer worth making. That conclusion was correct if you accepted the original framing. It was wrong if you understood what the markup was actually doing.
The May 2026 deprecation removes the display incentive for the last remaining sites that had it. What it cannot remove is what Google explicitly confirmed it will keep: the use of FAQ structured data as a comprehension signal. The irony of this moment is that the removal of the misleading incentive — the accordion dropdown — leaves behind a cleaner version of the original value proposition. FAQ schema is now unambiguously about making your content machine-readable for answer engines, not about occupying more pixels in a search result. The sites that build FAQ sections because the content is genuinely useful, and implement the markup because it helps AI systems understand that content accurately, are the sites that benefit from this shift. As the DIRHAM framework for content distribution makes clear, the channels through which content now reaches audiences have fundamentally changed — and AI retrieval systems have become a primary distribution layer that structured data directly influences. The rich result was the old distribution mechanism. The comprehension signal is the new one.
What to Watch Next
Five developments will determine whether the structured data landscape shifts further — and how content teams should adapt over the next six months.
- Google’s AI Overview documentation — Watch whether Google updates its AI Overview guidance to explicitly reference FAQPage schema as a citation-influencing signal; any such update would confirm what the data already suggests and accelerate adoption among teams still on the fence.
- Bing and other search engines — Bing has not announced a parallel deprecation, and Google’s own documentation notes other engines may continue to process FAQ markup for their own rich result features; monitor whether Bing’s structured data handling diverges from Google’s post-May 2026.
- Search Console API retirement in August — Teams with automated reporting pipelines that pull FAQ rich result data have until August to update those workflows; the June removal of the UI reporting will be an early signal of which teams are caught unprepared.
- CTR impact on FAQ-heavy pages — Sites that previously qualified for FAQ rich results will lose the visual prominence those features provided; watch organic CTR data on affected pages over the next 6 to 12 weeks to measure the traffic impact of the display loss against the baseline.
- Next structured data type to be deprecated — Google deprecated How-To rich results in September 2023 and FAQ rich results in May 2026; the pattern of removing display features while retaining comprehension signals is now established, and HowTo schema is worth watching to confirm whether the same comprehension-signal logic applies there as well.
