Google Drops FAQ Rich Results: The SEO Implications Most Are Missing

On May 7, 2026, Google quietly added a deprecation notice to the top of its FAQ structured data developer documentation. The notice itself is short, almost anticlimactic for something that has been part of the SEO playbook since 2019. The implications, however, are not. FAQ rich results, the expandable question-and-answer dropdowns that used to take up half the screen on certain organic listings, are gone. For every site. Permanently.

If you have FAQ schema deployed across product pages, service pages, blog posts, or category templates (and most agencies do), this update has already changed how those pages appear in Search. It has also reopened a much larger conversation about what structured data is actually for in 2026, and where the value of FAQ markup has quietly migrated to.

Here is exactly what changed, what did not, and what your team should do between now and August.

What Google Actually Announced

The official notice now sitting at the top of Google’s FAQ structured data documentation reads, in part: “As of May 7, 2026, 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.”

In plain English, three things are happening on three different timelines:

1. Now (May 2026): FAQ rich results no longer render in Google Search, anywhere, for any site.
2. June 2026: The FAQ rich result report in Search Console goes away. The Rich Results Test will no longer validate FAQ markup as something that can produce a rich result.
3. August 2026: The Search Console API stops returning FAQ rich result data. Any automated dashboard, BigQuery pipeline, or custom report pulling that data will silently break unless you update it.

The deprecation completes a phase-out that has been underway for nearly three years. Crucially, Google has not removed FAQPage as a valid schema.org type, and the markup itself can stay on your pages without causing errors or penalties.

How We Got Here: The Three-Year Phase-Out

To understand the May 2026 change, you have to look at the timeline.

May 2019: Google launched FAQ rich results. Within months, FAQ schema became one of the most aggressively deployed structured data types on the web, because the SERP feature it produced was unusually generous. A standard blue link could suddenly carry five expandable questions, links inside answers, and double the vertical real estate of a competing result. SEO teams added FAQ sections to almost every commercial page, whether the page genuinely answered FAQs or not.

August 2023: John Mueller announced on the Google Search Central blog that FAQ rich results would, going forward, only show for “well-known, authoritative government and health websites.” For every other site on the web, the expandable dropdowns disappeared within weeks. The 2023 restriction was, in ALM Corp’s detailed analysis of the change, explicitly framed as a response to widespread schema abuse: sites adding artificial FAQ sections to inflate their SERP real estate with questions that did not match user intent.

March 2026: Google’s March 2026 core update accelerated the cut. Tracked sites showed FAQ rich result impressions falling by roughly half compared to the post-2023 baseline. Even the government and health sites that had retained eligibility saw substantial loss. If you want a deeper read on the broader update, our breakdown of what the March 2026 core update actually means for your website covers the wider picture.

May 7, 2026: Google ends FAQ rich result support entirely. There is no longer any category of site that can earn the SERP dropdown. The May 2026 announcement is not a surprise. It is the logical endpoint of a process that began in 2023 and has been visible to anyone watching the data.

What Did Not Change: The Most Important Part

The single line in Google’s documentation that has been most underreported is also the most consequential. Google has explicitly stated it will continue to use FAQ structured data to better understand pages, even though the rich result feature is gone.

That is not a throwaway note. Schema markup and rich results have always been two different things. Schema markup tells Google what a page is about in machine-readable form. Rich results are a display feature that uses some of that structured data to render visual SERP elements. Only one of those jobs ended on May 7.

In practice, this means:

• FAQPage remains a valid schema.org type.
• Google still parses and uses the markup as a comprehension signal.
• AI search engines (ChatGPT, Perplexity, Google AI Overviews, Gemini) continue to actively use FAQ structured data to extract and cite answers.
• Removing your existing FAQ schema gains you nothing and costs you potential AI citations.

If you are reading SEO Twitter or LinkedIn right now and seeing takes that range from “FAQ schema is dead, strip it from your site” to “FAQ schema is more important than ever,” neither is fully right. The truth is in the middle: the visual SERP feature is dead, the underlying markup still does useful work, and the strategic centre of gravity has moved.

Why Google Made This Change

Google has not directly addressed why it chose now to end the residual government and health eligibility, but the broader pattern is clear. The 2023 restriction was a response to schema abuse, and the same pattern has repeated across other rich result types. HowTo rich results followed exactly the same arc: a launch, widespread abuse, a restriction, then a full deprecation.

When teams add structured data primarily to capture a SERP display feature rather than to genuinely describe their content, the format produces more noise than signal. Google’s preferred response over the last three years has been to remove the display feature entirely rather than try to police individual implementations. That is a meaningful pattern for anyone planning structured data strategy in 2026.

The Real Implications for SEO

The May 2026 update breaks down into three layers of impact, and the order matters.

1. Click-Through Rate

If your pages previously benefited from the FAQ dropdown taking up extra vertical space in the SERP, the loss of that treatment will likely reduce click-through rate even if rankings stay stable. Pages with five expanded FAQs occupying half the screen had a visible advantage over plain blue links beneath them. That advantage is gone.

For most sites, this effect has already played out across the 2023 to 2026 phase-out. If you saw a CTR drop in 2023 and another in March 2026, the May 2026 change will land more softly because the feature was already mostly absent. If you are a government or health site that retained eligibility, expect a more visible impact in your Search Console data over the next few weeks.

2. Reporting and Tooling

This is the operational layer most agencies are underestimating. Three things break on Google’s timeline:

• In June 2026, the FAQ rich result report inside Search Console disappears. Any monthly SEO report that pulls FAQ rich result impressions will return nothing.
• In June 2026, the Rich Results Test stops validating FAQ markup as a rich-result-eligible type. QA processes that used the test as a “will this trigger the FAQ dropdown” check need to be replaced with general structured data validation.
• In August 2026, the Search Console API stops returning FAQ rich result data. Automated dashboards, BigQuery pipelines, Looker Studio reports, and custom client dashboards that pull this data will silently fail unless updated.

If your team uses any kind of automated SEO reporting (and most modern agencies do), there is a hygiene job that needs to be on someone’s calendar before August. Identify every report, dashboard, or pipeline that includes FAQ rich result metrics and either remove the references or update them to pull different data. This kind of update work is part of why ongoing SEO management matters more than one-off audits.

3. The Bigger Strategic Shift

This is where the conversation actually gets interesting. The May 2026 change closes one chapter and opens another. As Launchcodex’s analysis of the deprecation put it, “Google removed a display feature, not a schema type.” FAQPage markup has effectively switched jobs. It used to be a SERP-feature tool. It is now, primarily, an AI citation tool.

The AI Search Angle: Why FAQ Schema Matters More Than Ever

The same three-year period that saw FAQ rich results phased out also saw the rise of generative search. Google AI Overviews now appear on a growing share of queries, ChatGPT browses the live web, Perplexity has carved out a meaningful audience, and Gemini is increasingly cited as a primary search interface.

These systems all share one architectural similarity: they parse, extract, and cite. Content that is explicitly labelled as a question and its corresponding answer, in machine-readable form, is easier for an extraction layer to process with high confidence. That is exactly what FAQPage schema provides.

According to Roar Digital’s analysis of FAQ schema’s role in 2026, pages with FAQPage schema are 3.2 times more likely to appear in Google AI Overviews than pages without. That figure should be read with appropriate caution (it is a correlational benchmark, not a Google-confirmed ranking factor), but the underlying logic is sound. AI search runs on structured comprehension, and FAQ markup is one of the clearest structural signals you can give it.

This is the shift our SEO team has been writing about under the broader heading of Generative Engine Optimisation (GEO). The set of techniques that earned you a rich result in 2022 is not the same set of techniques that earns you a citation inside an AI Overview in 2026. FAQ schema sits squarely in the new playbook, even though it is exiting the old one.

What You Should Actually Do Now

The action items are smaller than most coverage of this announcement suggests. In order of priority:

1. Do not remove existing FAQ schema. Google explicitly says it will continue to use the markup for comprehension. AI search engines actively use it for citation. The cost of leaving it in place is zero. The cost of removing it is invisible but real.

2. Audit your FAQ content for genuine usefulness. If you have FAQ blocks on pages where the questions are clearly engineered for SERP real estate rather than for actual users, this is the moment to either rewrite them or remove them. The bar moving forward is whether a real human would ask that question of your business. Anything that does not pass that bar is now pure liability.

3. Update your reporting and QA before August. Identify everywhere FAQ rich result data flows through your stack. Remove or replace references in Search Console reports, Looker Studio dashboards, BigQuery queries, and any custom API integrations. Replace the Rich Results Test validation step in your QA process with general structured data validation.

4. Treat FAQ markup as part of your AEO and GEO strategy, not your rich-results strategy. That means writing answers that are self-contained, factually specific, and 40 to 60 words long. AI extraction layers reward direct, complete answers. They penalise hedging, padding, and answers that require additional context from elsewhere on the page.

5. Adjust your CTR expectations on affected templates. If product pages or category pages previously benefited from FAQ dropdowns, expect baseline CTR to drop on those templates. Compensate with stronger title tags, descriptive meta descriptions, and other structured data types that still produce rich results: Product, Review, Recipe, Event, Video, and Breadcrumb among them.

The Real Lesson

The May 2026 announcement is, in a sense, the latest example of a recurring pattern in SEO and how Google’s algorithm has evolved. Tactics that are built around a specific SERP feature have a half-life. The feature gets exploited, Google restricts or removes it, and the teams that treated the feature as a strategy lose visibility. The teams that treated the underlying signal as a strategy keep working.

FAQ schema is no longer a way to capture an expandable dropdown in Google Search. It is a way to make your page’s most important questions and answers legible to every system that now decides what gets cited, summarised, and surfaced. That second job is more valuable than the first one ever was, but only for teams who understand the difference.

The expandable FAQ dropdown is gone. The work it represented, building pages that genuinely answer real questions in machine-readable form, has never mattered more.

If you need help auditing your current schema implementation, updating your reporting pipelines before August, or building out a content strategy that is set up for AI search rather than legacy SERP features, that is exactly the kind of work our SEO team does every day.