FAQ Rich Results Are Officially Dead: What to Do Before August 2026

Google quietly killed one of the most popular schema features on the web. On May 7, FAQ rich results stopped appearing in Google Search. Two days later, on May 9, Google added a deprecation notice to its FAQ structured data documentation that confirms the feature is being retired in stages. If your team has spent the last few years stuffing FAQ schema into landing pages to win extra SERP real estate, that playbook is officially over.

The change is small in code and big in strategy. Removing FAQ rich results closes a tactic many SEO teams used to grab more pixels on the page. It also reopens the question of which structured data still earns clicks in 2026 and which has quietly become decoration. Here is what changed with FAQ rich results, what is not changing, and what to do this week.

What Just Happened With FAQ Rich Results

Google posted a notice on its FAQ structured data page that reads, in part, that FAQ rich results are no longer appearing in Google Search and that the FAQ search appearance, rich result report, and Rich Results Test support will be dropped in June 2026. Search Console API support for FAQ rich results will be removed in August 2026. Search Engine Journal flagged the documentation update on May 9 in a piece by Matt G. Southern, who reported the visual change took effect on May 7. Search Engine Land’s coverage of the FAQ rich result retirement confirms the same three-phase rollout.

The deprecation has three dates worth pinning to your calendar. May 7 is when FAQ rich results disappeared from the SERP. June 2026 is when Google removes the FAQ search appearance filter, the rich result report, and Rich Results Test support. August 2026 is when the Search Console API stops returning FAQ data. After that, any pipeline that pulls FAQ impressions or click data through the API will return nothing.

Google did not publish a blog post or explain the reasoning. It simply added the notice to its developer documentation. That alone tells you how routine this kind of feature retirement has become.

Why Google Killed FAQ Rich Results

FAQ rich results have been on a slow march to the exit since 2023. That August, Google announced it was reducing visibility of FAQ rich results to only well-known, authoritative government and health sites. Every other site got cut off from the feature in one stroke. The new May 2026 deprecation closes the door for those last eligible sites too.

Google has not stated a reason, but the pattern fits a broader trend. Google has been thinning out SERP features that did not pull their weight on user satisfaction. FAQ rich results often pushed organic listings further down the page, and FAQ rich results rewarded sites that loaded their pages with low-effort question-and-answer markup. The signal-to-noise ratio dropped over time. Pair that with the rise of AI Overviews, which now answer common questions inline, and FAQ rich results lost both their differentiation and their reason to exist.

The same forces are reshaping how SEOs think about visibility in general. We covered the bigger shift in our piece on AI search visibility as the new SEO metric for 2026. FAQ rich results are one more proof point that ranking positions and SERP features are losing weight as recognition and citation share gain it.

What Stays the Same After the FAQ Rich Results Deprecation

This is not a schema purge. Several things stay exactly the same after FAQ rich results go away.

FAQPage structured data is still a valid Schema.org type. Per Google Search Central guidance on structured data general principles, unused structured data does not cause problems for Search, so you do not need to rip the markup out of every page in panic. The markup will sit there, run through your validator without errors, and produce no visible result on Google. That is the same trade you have made for years on schema types Google never picked up.

Other rich results are not affected by this change. Product, Review, Recipe, Article, Event, Organization, LocalBusiness, How-To on desktop, Video, and Breadcrumb rich results all continue. If you ranked for a recipe SERP feature yesterday, you still rank today. The deprecation is narrow.

Existing pages that once won FAQ rich results will not lose ranking position from this change alone. Rich results were a visual upgrade, not a ranking factor. Your ranking page is still the same ranking page. What you lose is the extra pixel real estate FAQ markup used to give you, and any click-through bump that came with it. Our SEO for bloggers guide covers the on-page fundamentals that matter more than ever now.

What to Do About FAQ Rich Results This Week

Most teams do not need to take dramatic action. They do need to take a few specific ones in the next 30 days.

Step one. Audit which of your pages currently use FAQPage schema. Pull a list from your CMS, your schema plugin, or a crawl with Screaming Frog or Sitebulb. Document the count. You want a baseline so you can compare impressions and clicks before and after the SERP change. The Google developer documentation on FAQPage structured data is now the canonical source on what Google will and will not do with it.

Step two. Pull a 30-day Search Console report filtered by FAQ search appearance. Save the impressions, clicks, and average position numbers before that filter disappears in June. You will need this baseline if your boss asks how the deprecation hit organic performance. Without a snapshot now, the data is gone. The Search Console performance report documentation explains exactly how to export the search appearance filter before it goes away.

Step three. Decide whether to keep the FAQ rich results markup. There are two reasonable answers. Keep it if the FAQ content is genuinely useful for visitors, since AI search systems may still parse the structured data when they build answers. Remove it if your FAQ blocks were always cosmetic and bloated the HTML. Either choice is defensible. Just make a decision instead of letting the markup sit unmaintained.

Step four. Update any Search Console API pipelines before August. If a dashboard, BI tool, or internal report pulls FAQ-specific impressions or clicks, the API will stop returning that data after the deprecation completes. Patch your queries now while you still have time to test.

Step five. Move FAQ content to better real estate on the page. The questions and answers themselves are still useful. Promote them out of a collapsed accordion and into proper H2 or H3 sections. Visible, well-structured content is what AI systems and human readers both reward. Our piece on mastering crawlability covers how to make sure those upgrades get indexed quickly.

What to Do Instead of FAQ Rich Results

The deprecation is a forcing function. The teams that win the next year of organic traffic will spend the schema budget they used to put on FAQ rich results somewhere more durable.

Put the schema budget on Article and Product markup instead. Both still feed rich results that show up across the SERP, Google Discover, and Search Console reports, and neither has the FAQ rich results problem of cosmetic abuse. Make sure author, publish date, and image fields are filled in correctly. These elements also feed AI systems that summarize content in answer engines.

Invest in topical depth, not surface breadth. AI systems decide who is authoritative on a topic by watching consistency over time. Three deep guides on a single theme outperform 30 thin FAQ pages. Our SEO quick wins playbook outlines the simplest path from a thin page to a useful one, and our note on seasonal SEO explains how to time those efforts around your business cycle.

Tighten conversion paths on the pages that still rank. FAQ rich results gave some pages a click-through rate boost that other pages did not need. Now that the boost is gone, weak pages will see a quieter slide in clicks. Use the freed-up time to fix weak product page copy, slow load times, and unclear calls to action. The brand-foundation work in our what your brand says about you piece pairs well with these conversion-side fixes.

Connect the dots to attribution. If FAQ traffic was secretly driving assisted conversions you never tracked, you will not see the lost lift in your last-click reports. Our piece on how AI Mode is killing last-click attribution explains why this matters more than ever.

The Bigger Picture Behind FAQ Rich Results

Losing FAQ rich results is not the end of organic traffic. It is one more nudge toward the kind of SEO that has always worked. Build content people actually need. Earn citations from credible sources. Stay consistent on a tight set of topics. The shortcuts keep getting closed off, and the durable work keeps paying out.

The teams that treat this deprecation as a wake-up call will use it to clean up their schema strategy, sharpen their content roadmap, and stop chasing the next pixel. The teams that ignore it will find another shortcut next quarter and lose another month chasing it. Choose the boring path.

Your Next Move on FAQ Rich Results

Take 30 minutes this week to run the audit. Pull your FAQ-tagged pages, pull the Search Console snapshot, and decide what stays and what goes. Then redirect the time you used to spend tweaking FAQ markup into one piece of citation-worthy content. The gap between schema theater and real authority will only widen from here.

If you want a second set of eyes on whether your schema strategy is actually moving organic revenue, our team can walk through your account in a 30-minute call. Book a free consultation and we will tell you which pages still earn the schema budget and which ones are wasting it. Let’s Grow!