On May 7, 2026, FAQ rich results stopped appearing in Google Search. The expandable question-and-answer panels that used to sit under search listings are gone — and the supporting tools are following them out the door. But here's the part that matters: you should not rip your FAQPage schema out of your site. Google still parses it, and well-built Q&A content still does real work in an AI-driven SERP. Here's exactly what changed and what to do about it.

What Changed

This is the completion of a phase-out Google started years ago, not a sudden reversal:

  • May 7, 2026: FAQ rich results stopped showing in Google Search results.
  • June 2026: Google removes the FAQ search-appearance report from Search Console and drops FAQ support from the Rich Results Test.
  • August 2026: Search Console API support for FAQ rich results is discontinued.

Back in August 2023, Google had already restricted FAQ rich results to "well-known, authoritative government and health websites," which removed eligibility for nearly every commercial site. The 2026 change removes that last remaining slice too. The display feature is now fully retired.

Why Google Did It

Every time Google retires a SERP feature that handed third-party content extra display real estate, the surface that gains ground is Google's own AI Overviews. Google is reclaiming space at the top of the results page for its own answer experiences and trimming the visual real estate available to third-party rich results. FAQ panels were prime real estate; now that space is Google's.

What This Means for Your FAQ Schema

The critical distinction: Google retired the display feature, not the content strategy.

  • FAQPage structured data is still a valid Schema.org type. Google has confirmed it continues to parse FAQ markup to understand pages.
  • Clear question-and-answer content still helps answer-driven systems like AI Overviews surface and quote your material — even though there's no longer a dedicated rich-result reward for the markup.
  • The reporting you relied on is going away. Update any internal dashboards that pulled FAQ rich-result data from Search Console or its API before June–August.

What To Do About It: Step-by-Step

Step 1: Don't remove FAQPage schema impulsively

If your FAQ markup is accurate and low-maintenance, leave it in place. Google still reads it, and yanking valid structured data out of every page is busywork that can introduce errors. The guidance from practitioners is blunt: don't rip it out, but don't keep it blindly either.

Step 2: Remove or rewrite thin FAQ content

The flip side: FAQ blocks that exist only to win a rich result — vague, templated, or keyword-padded answers — no longer earn anything and may dilute page quality. Either rewrite them to genuinely answer the question or remove them.

Step 3: Audit your schema for errors

Since the Rich Results Test will stop validating FAQ markup, use Schema.org validators and your own QA to confirm the markup is still syntactically correct and matches the visible page content.

Step 4: Update your reporting

Remove FAQ rich-result metrics from client reports and internal dashboards before the Search Console report and API support disappear, so you're not chasing data that no longer exists.

Quick-Win Checklist

  • Do NOT bulk-delete FAQPage schema — Google still parses it.
  • Rewrite or remove thin, templated FAQ answers that add no real value.
  • Validate remaining FAQ markup with a Schema.org validator (the Rich Results Test no longer covers it).
  • Ensure FAQ answers match the visible on-page content.
  • Strip FAQ rich-result metrics out of dashboards before June–August 2026.
  • Focus Q&A content on genuinely useful, direct answers AI systems can quote.

Sources