Google Killed FAQ Rich Results. Here's What That Actually Means for Your SEO

Last Wednesday I got three separate Slack messages from clients asking the same thing: "Did Google just break our FAQ schema? Our Search Console is showing zero FAQ impressions."

No, Google didn't break anything. Google deprecated it — deliberately, officially, and honestly with about three years of warning that most people chose to ignore. On May 7, 2026, Google removed FAQ rich results from all of Google Search. Those expandable question-and-answer dropdowns that used to appear below your organic listing? Gone. For everyone. For good.

The SEO internet is, predictably, losing its mind. I've already seen advice ranging from "immediately strip all FAQ schema from your site" to "your rankings are going to tank." Both of those takes are wrong, and I want to walk through what's actually happening — and what you should actually do about it.

What Google Actually Changed on May 7

Here's the precise thing that changed: Google stopped rendering FAQ rich results in the SERP. That's it. The expandable Q&A blocks that used to make your organic listing taller and more clickable — those no longer appear for any website on Earth, including the government and healthcare sites that retained the feature after 2023.

What did not change: FAQPage structured data as a schema type is still completely valid. Google explicitly stated in their deprecation notice that they will continue to use FAQ structured data to better understand pages, even though the rich result display is gone. I'll come back to why that one sentence is the most important part of this whole announcement.

This is a three-phase retirement, not a single overnight switch. If you haven't exported your historical FAQ rich result data from Search Console yet, do it this week — that data disappears in June and there's no getting it back.

This Wasn't Surprising (It Was Basically Inevitable)

If you've been paying attention, this deprecation has been telegraphed since August 2023 when Google restricted FAQ rich results to government and health websites only. At the time, the official reason was vague — something about "search appearance improvements" — but anyone working in SEO knew exactly what happened: FAQ schema had been catastrophically abused.

Between 2019 and 2023, adding FAQ schema to pages became as standard as adding alt text to images. Except people were doing it wrong — attaching FAQ sections to product pages, service pages, even blog posts where the "questions" were marketing copy dressed up as user queries. The game was simple: more SERP real estate = more clicks. So everyone played it, the SERP got cluttered, and Google eventually said enough.

The 2023 restriction didn't fix the problem — it just shifted who was doing it. By the time Google's March 2026 core update cut FAQ rich result impressions by roughly half even for the still-eligible sites, the feature was barely generating measurable traffic for anyone. May 7 just made the death official.

The Critical Distinction: Display vs. Data

This is where most of the bad advice circulating right now falls apart. People are treating "FAQ rich results are gone" as if it means "FAQ schema is dead." Those are two completely different things, and conflating them will cause you to make a dumb decision.

Think of it this way: a rich result is Google choosing to show a visual feature in the SERP using structured data it found on your page. The structured data itself — the machine-readable JSON-LD you embedded — is a separate thing. It's a signal, not a display format.

Google can stop rendering the visual feature while continuing to use the underlying signal. That's exactly what they said they're doing with FAQ markup. The FAQ schema you implement tells Google: "This page contains authoritative answers to these specific questions, in this specific format." That signal is still being read, still being processed, still informing how Google understands your page's relationship to user queries.

This isn't just theoretical. AI search systems — Google AI Overviews, Perplexity, ChatGPT Search, Gemini — actively parse FAQPage structured data when generating answers. Pages with proper FAQ markup get cited at measurably higher rates in AI-generated responses than pages with the same Q&A content presented as unstructured prose. The markup works. Just not in the place you used to see it.

FAQ Schema as an AI Citation Signal

Here's the reframe that makes the current situation make sense: structured data has always been about machine readability. The FAQ dropdowns in Google Search were a nice side effect — Google rewarding you with a visual feature for making your content machine-readable. Remove the reward, and the underlying reason for the markup still holds.

AI answer engines need to extract specific answers to specific questions from huge amounts of web content. FAQPage JSON-LD gives them a shortcut. Instead of parsing your full page and inferring which parts are questions and which are answers, the schema tells them directly: here's question one, here's its answer. Here's question two, here's its answer. That's genuinely useful for the AI extraction pipeline, and the platforms building these systems know it.

So the practical calculus is this: if your page has genuine question-and-answer content, adding FAQ schema now costs you 10 minutes and potentially earns you AI search citations for the next several years. That's a pretty good trade.

Your Actual Action Plan

Let me skip the hedging and tell you exactly what to do, in order.

This Is a Pattern, Not an Anomaly

If you've been doing SEO for more than a few years, the FAQ deprecation shouldn't feel particularly shocking. Google removed HowTo rich results in 2023 under almost identical circumstances — they were widely abused, the SERP feature was killing user experience by making everything look like a listicle, and Google pulled the plug while keeping the schema functional as a comprehension signal.

The pattern here is deliberate. When structured data types get adopted at scale as SERP manipulation tools rather than genuine content signals, Google removes the visual reward while keeping the underlying data. Product schema, Review schema, Video schema — all of these have had their rich result displays tightened or deprecated for specific use cases over the years. The schema types themselves live on.

What this means for your structured data strategy going forward: stop thinking of schema markup as a SERP decoration tool. It's a page comprehension tool. The visual payoff from any given schema type can disappear at any time. The comprehension signal tends to persist.

What "Good" FAQ Schema Looks Like in 2026

Since the visual incentive is gone, your FAQ content quality standard just got harder to justify — which is actually a good thing. Here's what FAQ schema should look like if you want it to work as an AI citation signal rather than just inert markup:

• The questions are real — things actual users search for, not marketing angles dressed up as queries
• The answers are specific and complete enough to stand alone — an AI system should be able to cite the answer without needing the surrounding page context
• The FAQ content is visible on the page — Google's guidelines require that the schema markup reflects visible on-page content, not hidden or schema-only text
• The questions are written by you, not user-submitted — user-generated content doesn't qualify per Google's guidelines
• The answers aren't promotional — if your FAQ answer is "Our product is the best because X," that's not a real answer
• The Q&A pairs are genuinely relevant to the page topic — a product page FAQ should address product-specific questions, not general industry questions you shoehorned in
• JSON-LD implementation is clean and validated — malformed schema is worse than no schema

If your existing FAQ markup meets these criteria, you have nothing to do except update your dashboards and move on. If it doesn't, this deprecation is a useful forcing function to clean it up.

The Bottom Line

Google removing FAQ rich results is genuinely fine news if you've been running clean FAQ schema on real Q&A content. The SERP feature is gone. The underlying signal isn't. The traffic boost from the dropdown is over. The AI citation potential is just starting.

The people who should be worried are the ones who were running garbage FAQ sections stuffed onto pages where they didn't belong. For them, this deprecation removes a SERP advantage that was costing Google result quality. Good riddance.

For everyone else: export your Search Console data before June, leave your schema alone, write better FAQs going forward, and tell your dev team about the August API change. That's the whole checklist. Don't let the noise convince you this is more complicated than it is.