Google Ended FAQ Rich Results: Should You Remove FAQ Schema?

If a web vendor ever bolted FAQ schema onto your site to chase that tidy drop-down list of questions under your Google result, here’s the news: that drop-down is gone. On May 7, 2026, Google stopped showing FAQ rich results in Search for every website — including the government and health sites that were the last ones allowed to keep them.¹ Now Fort Wayne owners are asking the obvious question: do I rip the FAQ markup out?

Short answer, and the one you probably won’t hear from whoever wants to bill you for the cleanup: don’t panic-strip it. The visual feature is retired, but the underlying markup is not forbidden, and in a lot of cases the right move is to audit — keep, rewrite, or remove each block on its own merits — rather than tear everything out in an afternoon. This is a technical-SEO decision, and like most of them, it rewards a calm read over a rushed reaction. It also fits a bigger shift we’ve written about in the Fort Wayne small business guide to AI: the payoff for good, structured content moved from pretty search features to getting quoted by AI.

Key takeaways:

• FAQ rich results (the drop-down under your listing) stopped appearing in Google Search on May 7, 2026 — for all sites, not just some.¹
• The FAQPage markup type is not dead. It’s still a valid Schema.org type, Google still reads it, and other search and AI systems use it.
• Google’s position: you may remove FAQ markup, but you’re not required to, and valid markup left in place won’t cause Search problems.¹
• The real decision is an audit: keep blocks tied to real, visible answers; rewrite thin ones; remove boilerplate that only ever existed for the drop-down.
• Google’s tooling retires in stages — June 2026 for the report and Rich Results Test, August 2026 for the Search Console API.
• The upside of genuinely helpful Q&A didn’t disappear — it moved to AI Overviews, ChatGPT, and other answer engines.

What exactly did Google change?

Google added a deprecation notice to its structured-data documentation and then quietly pulled the FAQ rich result page. The notice is blunt: “As of May 7, 2026, FAQ rich results are no longer appearing in Google Search.”¹ The tooling around the feature is being retired on a schedule, not all at once, which matters if anyone on your team watches a Search Console report or pulls data through the API.

According to Priority Pixels’ breakdown, this is the formal end of a tactic that had been losing ground since 2023 — delivered as a documentation notice rather than a headline announcement.² The longer backstory, as PPC Land recounts, goes back further: FAQ rich results arrived in 2019 and were genuinely useful for grabbing organic real estate, then Google narrowed them in April 2023 and restricted them to well-known government and health sites by August 2023.³ For a typical Fort Wayne HVAC, dental, or restaurant site, in other words, the visible benefit had already been gone for more than two years. May 2026 just made it official for everyone.

Here’s the rollout in one place:

If you or your developer have any dashboards, validation checks, or API calls that reference the FAQ rich result, the practical to-do is to update those before the June and August dates so nothing breaks silently.

Does this mean FAQPage schema is dead?

No — and this is the distinction that saves you from a pointless rebuild. The visual feature is gone. The markup type is still alive. FAQPage remains a current, valid type on Schema.org, defined as a web page that presents one or more frequently asked questions.⁴ Google still reads valid structured data; it simply stopped drawing the drop-down from it.

Other systems haven’t stopped reading it either. Other search engines can still process FAQ markup, and — more importantly for where attention is going — structured, clearly-answered questions are exactly the kind of content that AI answer engines pull from. That’s the thread running through what answer engine optimization actually is: the goal shifted from winning a search feature to becoming the source a machine quotes. If you’ve ever wondered why AI recommends your competitor instead of you, a page that answers real questions in plain language is part of the fix.

So the honest framing isn’t “FAQ schema died.” It’s “the drop-down died, and the reason to keep good Q&A content got better.”

Should you remove your FAQ schema?

Google’s own guidance is permissive: you can remove FAQ structured data if you want, but there’s no requirement to, and valid markup left in place causes no problems for Search.¹ That means the decision is yours — so make it deliberately, block by block, instead of running a site-wide delete.

The quick test: does the FAQ block reflect real questions with helpful answers that are actually visible on the page? If yes, keep it. If the markup was generated purely to earn the drop-down — boilerplate questions copied across dozens of pages, or markup that no longer matches what a visitor reads — that’s the stuff worth rewriting or removing. As Priority Pixels puts it, in a lot of these setups “the questions often followed the template rather than the user.”²

Here’s the decision framework we use when we audit a client’s FAQ markup:

One technical note worth flagging: FAQPage markup is meant for pages where each question has a single, official answer from you. If you run a page where visitors post their own answers, that’s QAPage markup, not FAQPage — a detail Google’s documentation still calls out.¹

Where FAQ content actually pays off now

This is the part we’d rather you spend energy on than the cleanup. The effort you used to pour into FAQ schema for a search feature now pays off somewhere more valuable: the AI answers your customers increasingly see first. When someone asks ChatGPT, Gemini, or Google’s AI Overviews a specific question — “do Fort Wayne HVAC companies charge for after-hours calls?” — the systems assemble an answer from pages that state clear questions and clear, trustworthy answers.

Clear Q&A content is some of the easiest material for those systems to lift and cite. That’s why the work connects directly to getting found in AI search and tracking the leads it sends, and to building local pages AI search will actually trust. It’s also how you earn a mention inside the AI answer itself. The markup is a nice-to-have signal; the visible, genuinely-useful answer is the asset.

A Fort Wayne audit: what to keep and what to cut

Say you run a dental office in Fort Wayne and a past vendor dropped a 12-question FAQ block onto every service page to chase the drop-down. Walk it the way we would. Start on your highest-traffic pages. Where the questions are real ones patients actually ask — “do you take Delta Dental?”, “is there parking off Jefferson?”, “can I be seen same-day for a broken crown?” — and the answers are visible and specific, keep them and keep the markup. Those earn their keep in AI answers now.

Where the block is the same generic list repeated across every page, with vague answers nobody reads, cut it down to the handful that are true for that page and rewrite them in plain Allen County English. Delete duplicate markup if two plugins are both emitting FAQ schema. The time you save not babysitting a dead search feature is better spent making a few answers genuinely helpful — which is exactly what helps an Allen County homeowner, and the AI they’re asking, pick you. This is the same instinct behind everything we do for Northeast Indiana businesses: fix the thing that helps a real customer, skip the thing that only helped a dashboard.

Let’s put your FAQ effort where it pays off

If you’re staring at a site full of inherited FAQ schema and not sure what’s helping and what’s dead weight, that’s a quick, honest audit — not a rebuild. Our answer engine optimization work is built around exactly this shift: turning real customer questions into content that AI systems quote and that still earns you clicks. If the underlying issue is messier technical SEO — duplicate markup, thin pages, tooling that references the retired feature — our SEO services can sort the plumbing first. Either way, tell us what you’re working with and you’ll leave with a clear keep/rewrite/remove list and a plan to point the saved effort at visibility that actually converts.