Google ends FAQ rich results in Search: what changed in May 2026 and what disappears next

What Google says is happening to FAQ rich results

Google’s public FAQ structured data documentation now carries an explicit deprecation notice: as of May 7, 2026, FAQ rich results are no longer appearing in Google Search. That sentence is the clearest possible line between “this markup used to earn a visible SERP treatment” and “that treatment is gone,” regardless of site category.

The same notice adds a product cleanup schedule: Google will drop the FAQ search appearance, the rich result report, and Rich Results Test support for this feature in June 2026, then remove FAQ rich result support from the Search Console API in August 2026—with the later API date framed as extra time for teams to adjust automated reporting. Those dates matter for engineering roadmaps, not just for SEO headlines.

What “FAQ rich results” meant in plain language

Rich results are enhanced search listings built from structured data—machine-readable hints (often JSON-LD) that describe page content. For FAQs, publishers used FAQPage markup to pair questions with single authoritative answers. When eligible, Google could show an expandable Q&A block directly in results, which sometimes increased visible footprint and clicks for informational queries.

That visibility was always conditional: structured data can be valid yet still not produce a rich result, because Google treats eligibility as a policy and quality decision, not a guarantee. The May 2026 change is different: it retires the FAQ rich result as a Search feature, independent of whether your markup syntax is perfect.

The August 2023 restriction was the first big squeeze

None of this dropped from a clear blue sky. In August 2023, Google Search Central announced it was reducing FAQ rich result visibility and would show them only for well-known, authoritative government and health websites going forward. For most commercial publishers, the FAQ rich result effectively disappeared years before the 2026 retirement, which is why many teams stopped treating FAQ schema as a CTR hack.

Google framed that 2023 shift as a search appearance change, not a ranking change—meaning it was not billed as a core algorithmic penalty against pages that kept markup. The broader motivation, as discussed publicly at the time, was to tidy results and curb low-value markup patterns that inflated SERP clutter without helping users.

May 2026 completes the retirement for the remaining eligible sites

After 2023, a narrower slice of the web could still qualify—government-focused and health-focused sites that met Google’s authority bar. The May 7, 2026 line in documentation ends the visual FAQ rich result for that remaining population too. Practically, if your organization is public-sector or clinical, you should assume users will not see the expandable FAQ block in Google Search even if historical pages still contain FAQPage JSON-LD.

Documentation pages can lag slightly behind reality in wording: you may still see legacy paragraphs describing eligibility while the caution banner states the feature is gone. For decision-making, treat the deprecation callout as the operative guidance for Search UI, and expect Google to align surrounding text over time.

June and August 2026: reporting and tooling, not just pixels

Losing the SERP feature is what marketers notice first, but June 2026 is the engineering inflection point for measurement. When Google removes FAQ search appearance and the rich result report slice tied to FAQ, dashboards that track “FAQ impressions” will go quiet—not because your site changed overnight, but because the metric category is retired.

The Rich Results Test dropping FAQ support means developers lose a first-party button to validate FAQ markup as a rich-result carrier in that tool’s UI. The August 2026 Search Console API removal extends the same cleanup to scripts that pull structured-data summaries into internal systems. If you operate monitoring bots, add a ticket now rather than debugging empty API fields later.

Should you delete FAQ structured data?

Google’s long-standing guidance—reiterated since the 2023 era—is that you do not have to rip out structured data simply because a given rich result stops rendering; unused markup is not inherently a “search penalty” switch. The more nuanced question is maintenance cost: if FAQ JSON-LD was only there for SERP decoration, its ROI collapses once the feature is gone.

A sensible policy is: keep accurate, user-visible FAQ content for usability and clarity; keep markup if it still helps your stack document Q&A pairs consistently; remove or narrow markup if it creates compliance risk (hidden text, mismatched Q&A, promotional “fake FAQs”) or noisy validation workflows. Always ensure questions and answers are actually visible on the page—Google’s content rules have consistently treated invisible FAQ spam as out of bounds.

How this fits Google’s broader “simpler Search” direction

FAQ retirement sits in the same family of moves as other feature removals and reporting simplifications Google has discussed when retiring lesser-used surfaces. The through-line is product discipline: fewer rarely used widgets, faster rendering, and less maintenance burden across Search Console tooling.

For publishers, the strategic implication is familiar: build for the user on the page, not for a specific snippet type that can be deprecated. Q&A formatting still helps readers, supports internal site search, and can be ingested by other systems; it just should not be mistaken for a durable SERP entitlement.

Bottom line

Google’s FAQ rich result is no longer shown in Search from May 7, 2026, with Search Console and Rich Results Test FAQ support ending in June 2026 and API support removed in August 2026, per the caution notice on Google’s FAQPage documentation. That finishes a long arc that began with the August 2023 restriction to authoritative government and health sites.

Treat this as a visibility and analytics change, not a reason to panic-delete real FAQ content. Do treat it as a deadline to update monitoring, retrain teams who still ask for “FAQ schema for SERP expansion,” and refocus on durable technical SEO: crawlability, clear headings, helpful answers, and structured data types that still map to active features you can measure.