FAQ Schema After Google Reduced Its Display: What Still Matters

FAQ schema no longer earns a visible rich result in Google Search: Google fully deprecated the feature on May 7, 2026, three years after first restricting it to government and health sites in August 2023. The markup itself still works and won’t hurt anything if you leave it in place. It just doesn’t buy you the expandable accordion snippet in the search results anymore, for any site.

A lot of site owners are asking the wrong question right now: should I rip FAQ schema out entirely? The more useful question is what the schema was ever actually doing for you, separate from the rich result. If you added it purely to chase the SERP snippet, that specific reason is gone. If your FAQ content answers real questions people search for, that value never depended on the schema in the first place.

What exactly changed, and when?

The removal happened in stages over three years, not all at once, and the details matter for anyone still relying on old advice about FAQ schema.

Google didn’t publish a blog post explaining the reasoning. The only official record is a notice added to the FAQPage structured data documentation, stating plainly that the feature is being dropped and giving the phased timeline above.

Should you rip FAQPage schema out of your site?

No, and I’d actively push back on doing it reflexively just because the rich result is gone. Google’s own documentation states that unused structured data doesn’t cause problems for Search, and FAQPage remains a valid, supported Schema.org type outside of Google’s rich result system specifically. Removing working markup for no functional gain is developer time spent on nothing.

The exception: if you’re also deleting or rewriting the FAQ content itself, update the schema to match so it doesn’t describe questions that no longer exist on the page. Stale schema pointing at content that’s gone is a real (if minor) quality signal problem, separate from the rich result question entirely.

What should you actually do with your FAQ content now?

FAQ Schema and Content: The Post-Removal Checklist

• Keep existing FAQPage schema in place. Harmless, still describes your content accurately.
• Stop chasing the rich result. That specific payoff no longer exists for any site.
• Keep writing FAQs that answer real queries. The content value was never only about the wrapper.
• Keep FAQ content visible on the page. Schema mirrors visible content, never replaces it.
• Stop monitoring FAQ rich result reports. Retired from Search Console through June and August 2026.
• Redirect effort into structure and clarity. Still earns attention from readers and AI systems alike.

Does FAQ schema help with AI search or ChatGPT answers?

Google hasn’t tied the rich result removal to AI Overviews or any AI search product specifically, and there’s no confirmed evidence that FAQPage markup alone improves how often an AI system cites your content. Be skeptical of anyone claiming a guaranteed link between the schema type and AI visibility, because that claim currently has no public backing from Google or from any AI search provider.

What does help, independent of schema entirely, is content structured so a question and its direct answer sit next to each other in plain HTML: a clear heading phrased as the question, followed immediately by a self-contained 40 to 60 word answer. That pattern is easy for a crawler, an AI retrieval system, or a human skimming the page to parse. Schema markup around that content is a bonus for machine-readability, not the mechanism doing the actual work.

What about HowTo schema, did it go the same way?

Yes, on a parallel track. The same August 2023 change that restricted FAQ rich results also deprecated HowTo rich results on mobile search. Google grouped the two changes together in its own announcement, which suggests a broader decision about SERP real estate rather than a complaint specific to either schema type. If you’re running HowTo schema expecting a step-by-step rich result on mobile, that expectation needs updating the same way FAQ schema does.

Does losing the rich result mean your rankings will drop?

No, and this is a distinction worth making explicitly because the two things get conflated constantly. FAQ rich results were always a SERP display feature, not a ranking factor. Having the accordion snippet never moved your position in the results; it changed how your existing position looked to a searcher, sometimes taking up more vertical space and improving click-through rate as a side effect. Losing that display feature means you lose whatever click-through advantage the extra SERP real estate gave you. It does not mean Google’s ranking algorithm now scores your page any differently, because FAQPage schema was never an input to that scoring in the first place.

If you do notice a click-through rate dip on pages that previously showed the FAQ snippet, that’s the change to investigate, not a ranking drop. Check Search Console’s performance report for those specific URLs around the May 2026 removal date and you’ll likely see impressions holding steady while clicks soften slightly, which is the rich result’s absence showing up exactly where you’d expect it.

Will FAQ rich results ever come back?

I wouldn’t plan around it. Nothing in Google’s public communication suggests this is a pause rather than a permanent decision, and the pattern itself argues against a reversal: three years of restriction followed by full removal is not how a temporary experiment usually ends. The more likely explanation, unconfirmed by Google but consistent with everything else happening in search right now, is that AI-driven answer experiences reduce Google’s appetite for handing SERP space to publisher-controlled rich results generally. Build your content strategy on the assumption that this stays gone.

What if an SEO plugin still bolts FAQ schema onto every post automatically?

Leave it running. Both Rank Math and Yoast (and most other WordPress SEO plugins) will happily keep generating FAQPage JSON-LD for any FAQ block you add, and there’s no reason to go disable that setting. The plugin isn’t doing anything wrong by continuing to output valid schema for valid content. What changed is entirely on Google’s side of the exchange, not in how the plugin behaves.

The one habit worth breaking: don’t let a plugin’s FAQ block talk you into padding a post with weak, thin questions purely because the block exists and used to earn a rich result. I still see posts with five FAQ entries where two are genuinely useful and three are filler added to hit a schema minimum that was never a real requirement. Cut the filler. A short, sharp FAQ section beats a long, padded one for readers and for AI systems both.

What’s the actual takeaway for anyone auditing their content plan?

Separate the schema decision from the content decision, because conflating them is what’s causing the confusion right now. Keep the markup if it’s already there, since it costs nothing to leave and nothing to gain by removing. Judge your FAQ content on whether it answers real questions clearly, not on whether it earns a SERP feature that no longer exists for anyone. That was always the more durable reason to write good FAQ sections in the first place.

Frequently asked questions

Does FAQ schema still matter after Google removed the rich result?

Not for the reason most sites originally added it. The rich result is gone for every site as of May 7, 2026, so FAQ schema no longer earns the accordion snippet in search results. The underlying FAQ content still matters for answering user questions and for how AI systems read your page, just not through this specific schema type.

Should I remove FAQPage schema from my site?

No, not reflexively. Google has said unused structured data doesn’t cause problems for Search, and FAQPage remains a valid Schema.org type. Removing it accomplishes nothing unless you’re also removing the FAQ content itself, in which case update the schema to match.

Does FAQ schema help with AI search or ChatGPT answers?

Google hasn’t connected the rich result removal to AI search specifically, and there’s no confirmed guarantee that FAQPage markup alone improves AI citation. What helps more reliably is clear, well-labelled question-and-answer content on the visible page, which any system, human or AI, can parse regardless of whether schema wraps it.

What happened to HowTo schema too?

HowTo rich results were deprecated on mobile in the same August 2023 change that restricted FAQ rich results. Both moves came from Google reclaiming SERP space for its own answer experiences rather than a specific complaint about either schema type.

Will FAQ rich results ever come back?

Nothing Google has published suggests that. The three-year path from restricting the feature in 2023 to removing it entirely in 2026 reads as a deliberate decision, not a temporary rollback. Plan your content strategy as if this change is permanent.

Sources

• Google Drops FAQ Rich Results From Search, Search Engine Journal
• FAQPage Structured Data, Google Search Central
• Schema Markup: A Practical Guide With Copy-Paste JSON-LD
• Does Schema Improve Rankings Directly?
• HowTo Schema: Where It Still Earns Results
• Rich Snippets vs Rich Results vs SERP Features