Google Just Killed FAQ Rich Results — Here's What to Do This Week

On May 7, 2026 — just three days ago — Google quietly dropped one of the most widely used SERP features in SEO history. FAQ rich results are gone. Not deprecated-with-a-grace-period gone. Gone gone. If you've been using FAQPage schema to expand your search snippets and pick up extra SERP real estate, that space closed overnight.

I've seen plenty of Google announcements come and go without causing real damage. This one is different. FAQ rich results were genuinely useful — pages with them consistently showed up taller in the SERPs, with expandable Q&A pairs that ate up screen space competitors couldn't touch. For a lot of sites, especially in health, finance, and e-commerce, FAQ snippets were quietly doing serious CTR work. Now they're not showing. At all.

This article covers exactly what changed, why Google made this call, what your existing FAQ schema markup is actually worth right now (hint: it's not completely worthless — just differently valuable), and the specific things you should do this week to make up the lost SERP ground. There's a real playbook here. Let me walk you through it.

What Actually Changed on May 7, 2026

Let me be precise about this because the internet is already full of half-accurate takes. Here is what Google actually confirmed:

FAQ rich results no longer appear in Google Search as of May 7, 2026. The FAQ "search appearance" category has been dropped entirely. If you open Search Console right now and go to your Search Appearance performance filters, the FAQ entry is either already gone or disappearing in the next few days. The Rich Results Test — the tool you'd use to validate FAQ schema — will drop FAQ support in June 2026. And the Search Console API support for FAQ data ends in August 2026.

What this means practically: those nice expandable accordion dropdowns under your search snippet? Gone. The extra 100–200 pixels of SERP real estate your FAQ sections used to occupy? Someone else now fills that space — probably your competitor whose page didn't rely on rich results to look substantial.

Here's the thing a lot of people are missing in the coverage: Google isn't saying FAQPage schema is invalid or harmful. They're saying they won't render it as a visual SERP feature anymore. The schema can still exist in your HTML. It's just invisible in the traditional search results. We'll get into why that distinction matters in a minute.

Why Google Did This (And Why It Matters More Than You Think)

Google doesn't kill popular features for no reason. The official statement was characteristically vague — something about "simplifying the search experience" — but if you read between the lines and follow what's happened across the last six months of Google updates, the real reason is pretty obvious: FAQ rich results were being gamed into the ground.

I've seen this a hundred times. A new SERP feature appears, savvy SEOs use it legitimately to add value, then every content farm and thin-content operation discovers it and hammers it. By late 2025, half the FAQ schemas appearing in search results were on pages where the "frequently asked questions" were clearly written by someone who had never met a customer. They were just question-shaped keyword targets. Google's quality filters struggled to separate genuinely helpful FAQ content from manufactured FAQ fluff, and the easiest fix was to turn off the visual feature entirely.

The timing also lines up with something bigger. Google's entire March 2026 Core Update was built around rewarding real expertise and punishing content that exists to manipulate rankings rather than help people. Killing FAQ rich results is consistent with that direction. If a feature can't be reliably used well, and it's being abused at scale, Google would rather remove it than spend engineering resources playing whack-a-mole with bad actors.

What This Signals About Structured Data's Future

Nobody talks about this but the FAQ deprecation is the third structured data feature Google has scaled back in the past 18 months. HowTo rich results lost their visual appearance for most query types in late 2024. Q&A schema stopped generating visual enhancements earlier this year. Now FAQ is gone. The pattern suggests Google is becoming more selective about which schema types earn visual SERP treatment — not abandoning structured data, but reserving the visual payoff for types it can verify against high-quality signals.

What's still holding strong? Product schema, Article schema, Review schema, Recipe schema, Event schema, and JobPosting schema. These are either transactional (where Google has clear verification signals) or content-type specific (where the schema maps to a defined content format). The Q&A and FAQ types were too easy to manufacture on any page for any purpose, which is why they're gone.

The lesson here isn't "structured data is dying." It's "structured data that can't be verified is dying." That's actually fine if you're building for real users. But it means the SEO playbook around FAQ schema needs a complete rewrite.

The CTR You're Losing Right Now

Let me be honest with you about the damage. If your site had FAQ rich results showing regularly, you've just lost something that was working. Pages in competitive niches were seeing CTR lifts of up to 35% from FAQ snippets, according to Search Engine Journal data. Rotten Tomatoes reported a 25% higher click-through rate on pages with schema versus equivalent pages without. These numbers are real.

The mechanics are simple: FAQ snippets made your result physically larger on the page. On mobile — where more than 60% of searches happen — a result with two or three expanded FAQ rows took up nearly the entire visible screen. Users couldn't miss it. Competing results were below the fold. That visual dominance translated directly into clicks.

Now everyone's result is the same size again. Your title, your URL, your meta description. Same as every other organic result. If your title and meta description aren't doing heavy lifting on their own, you're going to feel this change in your analytics within 30 days.

How to Diagnose Your Exposure

The first thing to do is figure out how reliant you actually are. Pull your Search Console performance data right now — filter by "Search appearance: FAQ rich result" — before that filter disappears. Export the data. Look at which pages were generating FAQ impressions and what their CTR was compared to your non-FAQ pages in the same position range. That gap is your exposure. That's the number you need to make up with other optimizations.

If you don't have Search Console access set up properly, or if your site has technical issues that have been silently suppressing your appearance data, there's never been a more urgent moment to get a proper audit done. You can't fix what you can't measure.

What Your FAQ Schema Is Still Worth in 2026

Here's where most of the coverage is getting it wrong. Just because FAQ rich results are gone from Google's visual search results doesn't mean the schema is worthless. There's a completely separate reason to keep your FAQPage markup — and if you're thinking about AI search at all, this is actually the more important reason.

AI search tools — ChatGPT, Perplexity, Google's own AI Overviews, and the dozen other AI answer engines that have gained serious traction in 2026 — pull structured data when assembling their answers. FAQPage schema is one of the clearest signals you can give an AI system that your content directly answers a specific question. Several studies tracking AI citation rates found that content using FAQPage structured data appeared in AI-generated answers at a significantly higher rate than equivalent unstructured content covering the same topics.

Let me be clear about what this means strategically. The FAQ schema you've spent time implementing isn't dead — its audience has shifted. You're no longer writing FAQ schema to impress Google's visual rendering system. You're writing it for AI citation engines that are increasingly answering questions before users ever click a link. That changes how you write the questions and answers, but it doesn't change whether you should use the schema at all.

The sites that will win over the next 12 months are the ones that understand this duality: traditional SEO for getting into organic results, and structured data optimization for getting cited in AI answers. FAQ schema was built for the second job. It's still very good at it.

Your Replacement Playbook: What to Do This Week

Okay, enough background. Here's what I'd actually do if I woke up this week with a site that had been relying on FAQ rich results for SERP visibility. This isn't theory — it's the checklist I'd run through personally.

The goal isn't to "replace" FAQ rich results with something equivalent. That's the wrong framing. The goal is to identify the specific pages where FAQ snippets were doing CTR work and shore up their organic performance through other means. In some cases that means title tag work. In some cases it means targeting richer schema types. In some cases it means going after the AI citation game more directly.

• Export your FAQ impressions from Search Console before June — That filter is going away. Screenshot or export the data now. You'll need it to know which pages are affected.
• Audit pages that had FAQ rich results for title/meta quality — Your title and meta description are now your only SERP real estate. If they're weak, they need a rewrite immediately. Aim for titles that answer the searcher's intent, not just match the keyword.
• Review your FAQ content quality for AI citation potential — Go through your existing FAQ sections. Are the questions written in natural language the way someone would actually ask them? Are the answers specific and direct? If yes, keep the schema. If they look like keyword placeholders, rewrite them before keeping the markup.
• Upgrade your Article and Product schema — If you have blog posts or product pages that aren't using Article or Product schema, get that in place now. These are the structured data types Google is still rendering visually, and they help with AI citations too.
• Look at People Also Ask (PAA) as your new CTR lever — Google's PAA boxes are still alive and well. They serve almost exactly the same content purpose as FAQ rich results — answering specific questions inline in the SERP. Structuring your content to target PAA triggers is now your primary path to that question-answer visibility in traditional search.
• Check your keyword targeting against question-intent queries — Use a keyword volume tool to find which question-based queries in your niche have meaningful search volume. These are your PAA targets and your AI citation targets simultaneously.

The Keyword Research Angle Most People Are Missing

Here's something practical that's getting overlooked in the discussion: if FAQ rich results were earning you impressions on question-based queries, you now need to understand which of those question queries actually have real search volume and commercial intent worth chasing. Not all question-based traffic is created equal.

There's a meaningful difference between "what is [product]" (awareness-stage, hard to monetize) and "how do I fix [problem with product]" (action-intent, much more likely to convert). Your FAQ sections probably targeted both without distinguishing between them. Now that you're rebuilding your question-content strategy from scratch, you have an opportunity to be more intentional — focus your energy on the question queries that lead somewhere.

Use a keyword volume checker to validate which question-based terms in your niche are worth targeting before you invest time restructuring content around them. It takes 10 minutes and will save you weeks of working on pages that will never drive meaningful traffic regardless of how well they're optimized.

One more thing before the wrap-up: don't panic-delete your FAQ sections from pages just because the rich result is gone. I've already seen a few people in SEO communities suggesting you strip out FAQ content entirely since it "no longer works." That's bad advice. FAQ content written for real users still helps people who land on your page. It still gets picked up for AI citations. And if Google ever reverses course on this feature (it's happened before), you'll be in a much better position than sites that pulled everything.

The move is adapt, not retreat. Update your strategy, keep what works for AI and user experience, replace what was purely display-driven with better title and meta work. That's it.