Google FAQ Rich Results Are Gone: What to Do Before the August 2026 API Sunset

The FAQ dropdowns that used to expand right inside Google's search results are finished. Google stopped showing FAQ rich results on May 7, 2026, pulled the related Search Console report and Rich Results Test support in June, and will remove FAQ support from the Search Console API in August 2026. If your reporting pipelines still query that data, the clock is running.

Here is the part most panic threads miss: this is a SERP-display change, not a ranking change. FAQ markup was never a ranking factor, so nothing about how you rank moves because of this. What changes is how your listing looks and which data feeds you can still pull. This guide lays out the exact timeline, what actually breaks, and a short checklist to close out the change cleanly.

What changed, and when

Google retired FAQ rich results on a three-phase schedule that mirrors how it sunset HowTo rich results back in 2023. The dates matter because a few of them are automated deadlines, not gentle suggestions.

Date	What happened
May 7, 2026	FAQ rich results stopped appearing in Google Search; a deprecation note was added to the FAQ structured data docs.
June 2026	The FAQ search-appearance filter, the Search Console rich-result report, and Rich Results Test support were removed.
August 2026	Support for the FAQ rich result in the Search Console API is removed. Automated calls for that data start returning empty.

Google's own FAQPage documentation now carries the deprecation note, and the change was confirmed by Search Engine Land and Search Engine Journal. This isn't a rumour or a temporary test — it is a full deprecation.

Why Google is doing this

FAQ rich results launched in 2019 as a way to surface question-and-answer content directly on the results page. Over time they became a magnet for manipulation: sites bolted generic FAQ blocks onto pages purely to grab extra SERP real estate, whether or not the questions were genuinely useful. Google narrowed eligibility to authoritative government and health sites back in August 2023, and the May 2026 move finishes the job.

The wider context is Google's ongoing effort to simplify a cluttered results page. As AI Overviews and other answer surfaces take over the top of the page, decorative rich-result features that added noise without adding trust are being trimmed. FAQ dropdowns were an early casualty of that clean-up.

Does this hurt your rankings or traffic?

Your rankings will not move because FAQPage markup was never a ranking signal. What can shift is click-through rate on the affected pages. Pages that carried a prominent FAQ dropdown occupied more vertical space in the SERP, and that extra footprint sometimes lifted clicks. With the dropdown gone, those listings return to a standard appearance, so a modest CTR dip on a handful of pages is possible — not a ranking penalty.

To see whether you are actually affected, export the FAQ rich-result data and CTR history from Search Console before the reports disappear. If a page never earned the rich result in the first place — likely, given the 2023 eligibility clamp-down — this change costs you nothing at all.

Should you delete your FAQ schema?

No. Removing valid markup is busywork with a small downside. Three reasons to leave clean FAQPage schema in place:

• Google still reads it. Google has confirmed it will continue to use FAQ structured data to better understand a page, even though it no longer renders the rich result.
• AI engines parse it. ChatGPT, Claude, Perplexity and Gemini read structured data when they index pages. Well-formed question-and-answer markup is exactly the kind of self-contained, extractable passage those systems like to cite — a point we cover in our guide to optimizing your content for AI search.
• Other engines and tools use it. Schema.org's FAQPage type remains valid, and plenty of non-Google systems rely on it.

The one exception: if you added FAQ blocks purely to game the rich result — forced, thin, or duplicated questions with no real user value — this is a good moment to prune them. Keep FAQs that genuinely help readers; delete the ones that only ever existed for the SERP.

The checklist: what to do before August

1. Export your FAQ data now

The Search Console FAQ report and Rich Results Test are already gone, and API support ends in August 2026. If you feed FAQ rich-result metrics into dashboards, BigQuery, or any automated monitoring, pull the historical data you want to keep this month. After the API cutoff, those calls return nothing.

2. Audit which pages relied on the feature

List the URLs that previously earned FAQ rich results and note their CTR trend across the change. This is your evidence base if you later see a click dip and need to explain it to stakeholders. A quick pass with your usual reporting stack — see our roundup of website SEO audit tools — makes this a ten-minute job.

3. Keep genuine FAQ content, prune the filler

Retain FAQPage markup on pages with real, useful questions. Rewrite or remove blocks that were obviously manufactured for the rich result. The goal is a leaner, honest FAQ footprint that still helps users and still feeds AI systems clean answers.

4. Update automated reporting and alerts

Anything that queries the FAQ search appearance in the Search Console API needs to be repointed or retired before August, or it will silently break. If you also track social and video performance, note that Google recently added platform properties in Search Console — a good reminder to review what your reporting actually pulls.

5. Redirect the CTR strategy, not the panic

If a page leaned on the FAQ dropdown for visibility, earn that attention elsewhere: a stronger title and meta description, eligibility for other valid rich results (such as Article or Product), and answer-first content that positions you for AI citations. The traffic opportunity didn't vanish — it moved.

What this signals about structured data in 2026

FAQ isn't the only rich result Google has trimmed — HowTo went in 2023, and Practice Problem markup lost Search Console reporting in January 2026. It is tempting to read this as "structured data is dying." It isn't. Google has been explicit that it still uses many schema types to understand pages, and structured data remains central to how both search engines and AI systems interpret content.

The real lesson is narrower: markup that exists only to decorate the SERP is fragile, while markup that genuinely describes your content is durable. Schema you add to help machines understand a page — organization, author, article, product, breadcrumb — keeps earning its place. Schema you add purely to win a visual feature can be switched off at Google's discretion, as FAQ just was. Build your structured-data strategy around understanding, not decoration, and deprecations like this one stop being emergencies.

The takeaway

Google FAQ rich results are gone for good, but the sky is not falling. Rankings are untouched, valid FAQ markup still helps Google and AI engines read your pages, and the only hard deadline is the August 2026 API cutoff for anyone pulling FAQ data programmatically. Export what you need, prune filler questions, keep the genuinely useful ones, fix your reporting pipelines, and move on. Treat structured data as a way to explain your content rather than to dress up your listing, and the next feature deprecation will be a footnote instead of a fire drill.