In May 2026, Google removed FAQ rich results from search.
Not restricted them. Not limited them to a subset of sites. Removed them entirely.
If you implemented FAQ schema markup based on advice from the last five years, you now have markup that does nothing in the search results. Your schema sits there, valid and functional, producing zero visibility. And most content teams haven’t noticed yet — which is the real story here.
This wasn’t a surprise move. Google has been signaling this for three years. In 2023, they restricted FAQ rich results to “well-known, authoritative government and health websites.” In 2026, they finished the job. But the timeline tells you something important: the companies that built FAQ strategies around rich results weren’t paying attention.
The deprecation matters, but not because of the lost rich result. It matters because of what it reveals about how you should actually think about schema markup — and why most of your organization is probably thinking about it wrong.
WHAT HAPPENED
Let me be specific about the timeline, because it’s the evidence of how this decision got made.
May 2023: Google reduced FAQ rich result visibility for most sites. Only government and health sites could still earn the rich result. Everyone else’s FAQ markup stopped producing visible results. That was three years ago.
May 2026: Google deprecated FAQ entirely. Even government and health sites lost the rich result. The Rich Results Test is gone or going. The Search Console report goes away in June. The API support vanishes in August.
For three years — three years — sites have been implementing FAQ schema based on best practices from a feature Google was actively dismantling. And not quietly. Google published a blog post about the 2023 restriction. It was covered in industry publications. The signal was there.
Here’s what that means: You probably still have clients (or a site of your own) with FAQ markup that’s been producing zero rich results since 2023. And you’re just now finding out.
WHY GOOGLE DID THIS (AND WHY THEY DIDN’T TELL YOU)
Google never published an explanation. No blog post. No developer guidance beyond a one-sentence notice added to the FAQ documentation. That silence is the most honest thing they could have done—because the real reason is organizational, not technical.
FAQ rich results became a liability. Here’s why:
One: They opened the door to gaming.
FAQ sections became a place where every site with five questions could stuff queries and answers, hoping for a rich result. The SERPs filled up with low-quality FAQ blocks. Google had to keep restricting eligibility because the feature couldn’t scale honestly.
Two: They didn’t solve a real search problem.
Rich snippets work when they genuinely answer what the searcher typed. But FAQ sections are author-defined Q&A pairs. The questions the site owner thought people would ask aren’t always the questions people are actually typing into Google. The rich result format became window dressing that didn’t serve the search intent.
Three: AI systems don’t need the rich result format to parse FAQ content.
If anything, FAQ markup makes content harder for LLMs to use—it’s constrained and structured in a way that doesn’t map to how conversational AI actually works. This one Google won’t say out loud, but it’s true: the deprecation isn’t separate from the AI search shift. It’s connected to it.
But Google didn’t explain any of this. They just removed the feature and moved on. Which tells practitioners something important:
Google is done explaining why it deprecates things. You’re expected to keep up.
THE REAL PROBLEM: HOW YOU’RE THINKING ABOUT SCHEMA
This isn’t really a post about FAQ rich results. It’s a post about why your organization is probably making schema decisions for the wrong reasons.
Most content teams treat schema markup as a visibility hack. You implement FAQ markup because it might earn you a rich result. You add HowTo because Google previously said it helps. You build schema because somewhere, at some time, Google said it could lift your ranking or CTR.
That’s not a strategy. That’s hope layered on top of technical work.
The practitioners who built FAQ strategies purely because of rich result potential just lost that entire premise. And they’re shocked. They shouldn’t be. The deprecation has been coming for three years.
Here’s how you should actually think about schema:
Schema is infrastructure for clarity. Not for Google. For your reader, for your search presence, for AI systems that parse your content, for the next algorithm shift you can’t predict. Schema markup is an editorial decision, not a technical one — and that means you build it based on what’s true about your content, not based on what might earn you a snippet today.
FAQ markup makes sense for certain content. If your piece actually answers frequently asked questions — and if the questions you’re answering are the questions your audience actually types — then FAQ schema helps clarify that structure. The markup stays. The rich result was always the bonus.
But if you implemented FAQ because someone said it was a ranking factor, or because you wanted the visual real estate in Google, or because you heard it helped with AI, then the deprecation is telling you something: you built on sand.
WHAT THIS MEANS FOR YOUR SCHEMA STRATEGY
You don’t need to remove FAQ markup from your pages. Google said so explicitly — unused schema doesn’t hurt you. But you do need to stop treating rich results as the ROI justification for schema work.
If you’re currently auditing your schema, here’s what matters:
Schema that clarifies content structure matters.
That’s breadcrumbs, it’s article metadata (author, publication date, entity mentions), it’s organization and product information if you’re an e-commerce or service site. These serve a structural purpose independent of whether Google shows a rich result.
Schema that was built entirely for rich results is sunk cost.
FAQ, HowTo (which Google also restricted), and other rich-result-only markup: if your justification was “earn a snippet,” then the ROI disappeared. You can keep the markup, but don’t build new FAQ sections based on the expectation that they’ll earn visibility.
Schema for AI readability might matter more than schema for Google visibility.
This is the emerging principle nobody’s saying out loud yet. As answer engines and AI overviews become your actual competition, schema that helps AI systems understand your content structure becomes more valuable than schema that earns you a Google snippet. But that’s a different structure conversation than the one you’ve been having.
The shift from “will this earn a rich result?” to “does this help search systems understand my content?” is the shift from tactics to strategy. Google killed FAQ rich results to force you to make that shift.
WHAT YOU SHOULD DO INSTEAD
Stop adding FAQ markup based on rich result potential. Period.
If you have existing FAQ schema, leave it. It’s not hurting you. But don’t build new FAQ sections to earn visibility. That’s not a valid strategy anymore.
Instead, invest in:
- Core entity markup. If your brand isn’t a search entity yet, you don’t have the infrastructure to earn rich results anyway. Entity clarity matters more than rich result formats.
- Byline and author clarity. The byline is back as an E-E-A-T signal. Your author schema, your author pages, your author credibility markup—that’s where your visibility gains are. Not in answer format optimization.
- Information gain and originality. The effort you were spending on FAQ formatting should go into making sure your content actually answers questions better than what’s already ranking. Schema structure doesn’t matter if the content inside it isn’t worth citing.
This is the hard part. Schema implementation is something you can outsource or automate. Actually having something to say that matters—that’s the work nobody can shortcut.
THE LARGER PRINCIPLE
Google deprecates features it built. It happens regularly. HowTo, FAQ, rich snippets for certain content types—these get restricted or removed because Google’s priorities shift, algorithms change, and what worked as a ranking factor last year doesn’t work the same way this year.
The companies that suffer aren’t the ones who implemented schema; it’s the ones who built their entire strategy on the assumption that Google’s current reward structure is permanent.
Your content strategy should not depend on a rich result format. It should depend on clarity, specificity, and saying something worth saying. Schema is infrastructure in service of that. Not the other way around.
If you lost visibility because your FAQ rich results disappeared, that’s actually good feedback. It means your visibility was fragile. You built on a feature Google owned, not on content quality you own.
Fix that. Everything else follows.
This post is part of the Clifton Creative guide to SEO for content teams.