Introduction
If you added FAQ schema to your website over the past few years to earn those expandable question-and-answer boxes in Google's search results, we have news you have probably already heard rumblings about: those boxes are gone. In 2026, Google officially ended FAQ rich results across the web. The search feature that rewarded your markup with extra real estate on the results page no longer exists.
That change has set off a predictable wave of questions from business owners. The loudest one — the one we keep hearing from clients here in Northeast Indiana — is blunt: “Do I need to rip all that FAQ schema out of my site?”
The short answer is no. And the reason why is more interesting than the change itself. This is not the story of a feature dying. It is the story of a signal quietly changing jobs — from decorating blue links to feeding the answer engines that now sit between your customers and your website. We walked through the mechanics of that shift when the sunset first began earlier this year; this piece is the updated, decision-focused version: what finally changed, and exactly what to do about it now.
Key Takeaways
- FAQ rich results stopped appearing in Google Search on May 7, 2026, and the change was formalized through documentation, not a new algorithm.
- Google is dropping the FAQ report and Rich Results Test support in June 2026, with Search Console API support ending in August 2026.
- Most sites were already ineligible: since 2023, FAQ rich results were limited to authoritative government and health websites.
- Both Neil Patel and Search Engine Journal advise the same thing: keep valid FAQ schema in place — removing it will not restore rich results or improve rankings.
FAQPageis still a valid Schema.org type that machines can parse, which keeps it useful for answer engine optimization (AEO) even without the SERP feature.- The practical move is to audit your FAQ markup for accuracy, keep what reflects real page content, and stop treating it as a rich-results play.
What Exactly Did Google Change in 2026?
The end of FAQ rich results was not a single dramatic announcement. It was the last step in a phase-out that had been running quietly for nearly three years.
Back in 2023, Google narrowed FAQ rich results so they would only appear for “well-known, authoritative government and health websites,” according to Search Engine Journal's reporting. For the vast majority of businesses — your local dental practice, your HVAC company, your law firm — the visible FAQ boxes had already disappeared at that point. Many owners kept the markup anyway, hoping the feature might return or that it still helped in some invisible way.
In 2026, Google closed the door. Here is the timeline both sources lay out:
| Date | What changed |
|---|---|
| 2023 | FAQ rich results restricted to authoritative government and health sites only |
| May 7, 2026 | FAQ rich results stopped appearing in Google Search entirely |
| June 2026 | Google drops the FAQ search-appearance filter, the rich result report, and Rich Results Test support |
| August 2026 | Support for FAQ rich results in the Search Console API ends |
Google's own wording, as Search Engine Journal quotes it, was matter-of-fact: “FAQ rich results are no longer appearing in Google Search. We will be dropping the FAQ search appearance, rich result report, and support in the Rich results test in June 2026.”
The change was formalized the way Google usually formalizes these things: through a quiet edit to its developer documentation. The Google Search Central FAQPage documentation now carries the deprecation notice directly, which is what turned this from “the boxes seem to be gone” into an official, dated end of support. If you want the primary source rather than the commentary around it, that page is it.
One detail worth sitting with: Google offered no public rationale for the move. As Search Engine Journal puts it, Google “did not publish a blog post or explain the reasons behind the removal” — though the timing lines up with the industry's broader pivot toward AI-driven search. In our experience, that silence is itself a signal — Google treated this as housekeeping on a feature most sites could no longer use, not as a policy shift you need to react to in a panic.
It is worth being precise about what did not change, too. The FAQPage type in the Schema.org vocabulary is untouched. Your JSON-LD still validates. Other structured-data types you may rely on — such as Article, LocalBusiness, Product, or Breadcrumb markup — are entirely unaffected by this. This deprecation is narrow: it retires one specific search appearance tied to one specific schema type. Everything else in your structured-data setup keeps working exactly as before, which is why a blanket “clean out our schema” reaction would do far more harm than good.
Should You Remove Your FAQ Schema?
This is the question that actually matters, so let us answer it directly: keep it.
Both of the sources reporting this change land in the same place. Neil Patel's analysis puts it plainly: “If your FAQ markup accurately reflects the content on the page and follows Google's structured data guidelines, leaving it in place is the more practical approach.” He adds that pulling the markup out is not worth the effort — “Removing the markup will not improve rankings, restore lost rich results, or provide meaningful performance gains for most websites.”
Search Engine Journal reaches the same conclusion, noting that “sites with FAQ structured data do not need to rush to remove it” because “unused structured data does not cause problems for Search, and FAQPage is still a valid Schema.org type.”
Here is the decision laid out side by side:
| If you remove FAQ schema | If you keep FAQ schema |
|---|---|
| No ranking improvement | No ranking penalty |
| Rich results stay gone (they are deprecated for everyone) | Rich results stay gone — same outcome |
| You spend developer hours ripping out working markup | Zero effort; it keeps sitting there harmlessly |
| You lose a clean, machine-readable Q&A signal | You retain a signal answer engines can still parse |
The only scenario where removal makes sense is cleanup: if your FAQ schema is inaccurate — describing questions and answers that no longer match what is on the page — then it should be fixed or removed, because misleading structured data is a genuine liability. That is a data-hygiene decision, not a reaction to the deprecation. To be honest about the trade-off: keeping stale, wrong markup is worse than having none. Keeping accurate markup is better than having none.
Why Does FAQ Schema Still Matter for AI Search?
If the SERP feature is dead, why bother? Because the reason to mark up your content with structured data was never only the visual box.
Structured data is machine-readable context. When you wrap a question and its answer in FAQPage markup, you are handing search engines and language models a clean, unambiguous statement: this is a question our customers ask, and this is our answer. That clarity is exactly what answer engines like Google's AI Overviews, ChatGPT, and other generative platforms are built to consume when they assemble responses. We break down how this works in our answer engine optimization guide, and it is the core idea behind treating FAQ schema as an AEO asset rather than a rich-results trick.
Now for the honesty guardrail, because this space is full of overclaiming: Google has not confirmed a direct connection between FAQ schema and AI citations or rankings. Neil Patel's article is careful about this too — “While Google has not confirmed a direct connection, structured data helps organize content in a way that is easier for machines to interpret. That makes it a worthwhile component of a broader content strategy.” We agree with that framing. FAQ schema is not a guaranteed ticket into an AI answer. It is one clean, extractable signal among many, and it costs you nothing to keep.
What we can say with confidence is that the fundamentals answer engines reward — clear questions, direct answers, and unambiguous entity relationships — overlap heavily with what good FAQ markup encodes. If you are serious about being cited, the bigger levers are content clarity and closing your entity gaps, not the FAQ tag by itself. The markup supports that work; it does not replace it.
There is also a simple structural reason FAQ content tends to travel well into AI answers, with or without the schema: it is already shaped like the thing an answer engine is trying to produce. A generative assistant answering “how often should I service my furnace?” is looking for a short, self-contained, authoritative response — which is exactly the format a good FAQ answer takes. The markup makes the relationship between question and answer explicit for a machine, but the underlying content pattern is the real asset. That is a useful way to think about the whole shift: the rich-results box was a reward for a format that happens to be genuinely useful, and the format outlived the reward. Keep writing in it. The businesses that treat their FAQ sections as a serious content surface — accurate, specific, updated when the facts change — are the ones best positioned as more of their customers' questions get answered by AI before anyone clicks through to a website at all.
What Should You Actually Do Now?
Here is a practical, no-drama checklist for the next time you are in your site's back end:
- Do not touch working markup out of fear. If your
FAQPageschema validates and matches your page content, leave it. There is no deadline forcing you to remove anything. - Audit for accuracy, not for the feature. Skim your FAQ blocks. Do the marked-up questions and answers still reflect what is actually on the page and true about your business? Fix anything stale.
- Stop chasing the rich result. Any tool, plugin setting, or agency deliverable still sold on the promise of “FAQ rich snippets in Google” is selling a feature that no longer exists. Reset that expectation.
- Ignore the June/August report changes as a to-do. You will lose the FAQ rich result report in Search Console in June 2026 and the API field in August 2026, but since the results themselves are gone, there is nothing left to monitor there anyway.
- Redirect the energy toward AEO fundamentals. Write answers the way a person actually asks the question, keep them concise and self-contained, and make sure your content reads clearly enough for an answer engine to lift and cite. That is where the return is now.
The through-line: this change asks for almost nothing from you today, and the temptation to over-react is the real risk. The businesses that “fixed” this by tearing out their schema will spend hours to end up exactly where they started — minus a useful signal.
What This Means for Fort Wayne and Northeast Indiana Businesses
For small businesses across Fort Wayne, Allen County, and DeKalb County, this news lands in a specific way. Over the past few years, plenty of local home-services companies, dental offices, law firms, and HVAC contractors added FAQ schema specifically to chase Google's rich snippets. If that was you, the instinct now might be to assume the effort was wasted and clean it out.
Do not. Those same FAQ blocks — “How much does a furnace tune-up cost in Fort Wayne?” or “Do you offer emergency service in Auburn?” — are exactly the kind of local, intent-rich Q&A that AI Overviews, ChatGPT, and AI Mode reach for when a nearby customer asks a question out loud. The SERP box disappeared; the underlying signal did not. If anything, well-structured local FAQs are more valuable now that so many neighbors start their search inside an AI assistant instead of scrolling ten blue links. We dig into the local mechanics of this in our Fort Wayne AEO guide.
The practical takeaway for a Northeast Indiana business is the same as everywhere else, just closer to home: keep your accurate FAQ markup, make sure it answers the questions your actual customers ask, and treat it as part of getting found in AI search — not as a lost rich-result play.
Turning a Deprecated Feature Into an AEO Advantage
The end of FAQ rich results is a small technical footnote with a bigger lesson underneath it: search features come and go, but clear, structured, honestly-answered content keeps paying off no matter which interface your customers use to find you. The businesses that win the next few years will not be the ones who chased every SERP feature — they will be the ones whose content is easy for both people and machines to understand.
If you are not sure whether your FAQ schema is accurate, whether your content is positioned to be cited by AI answer engines, or where to spend your effort now that the rich-results era is over, that is the kind of work we do every day. Our answer engine optimization services are built to help Northeast Indiana businesses stay visible as search shifts from links to answers.
Not Sure If Your FAQ Schema Is Helping or Hurting?
Button Block helps Fort Wayne and Northeast Indiana businesses audit their structured data and position their content to be cited by AI answer engines. We will take an honest look at where you stand — no rip-it-all-out drama, just what actually moves the needle now.
Frequently Asked Questions
- Did Google penalize sites that use FAQ schema?
- No. Google did not penalize FAQ schema, and there is no ranking downside to keeping it. As Search Engine Journal notes, unused structured data does not cause problems for Search, and FAQPage remains a valid Schema.org type. The feature that displayed FAQ rich results was retired; the markup itself is neutral to keep.
- When exactly did FAQ rich results stop appearing?
- FAQ rich results stopped appearing in Google Search on May 7, 2026. Google is dropping the related report and Rich Results Test support in June 2026, and support in the Search Console API ends in August 2026. For most sites, the visible boxes had already been gone since Google restricted the feature to government and health sites in 2023.
- Should I remove FAQ schema from my website?
- In most cases, no. Both Neil Patel and Search Engine Journal advise leaving accurate FAQ markup in place, because removing it will not restore rich results, improve rankings, or provide meaningful gains. The one exception is inaccurate markup — if your schema no longer matches your page content, fix or remove it as a data-hygiene step.
- Should Fort Wayne and Northeast Indiana businesses remove their FAQ schema?
- No. Local home-services, dental, legal, and HVAC companies that added FAQ schema to chase Google rich snippets should keep accurate markup in place. The visible SERP boxes are gone for everyone, but those same question-and-answer blocks still help AI Overviews, ChatGPT, and AI Mode surface your business when a nearby customer asks a question. Removing the markup will not restore rich results or improve rankings — it only discards a clean, machine-readable signal that local answer engines can still use.
- Does FAQ schema still help with AI search or AEO?
- It can help, but it is not a guaranteed boost. Google has not confirmed a direct connection between FAQ schema and AI citations or rankings. What is true is that structured data makes your questions and answers easier for machines to interpret, which is why it remains a worthwhile part of a broader answer engine optimization strategy rather than a standalone tactic.
- Will keeping unused FAQ schema slow down or hurt my site?
- No. Unused structured data does not cause problems for Google Search, and a small block of FAQPage JSON-LD has no meaningful effect on page performance. The only real risk is inaccurate markup that misrepresents your content, which is a reason to correct it — not to strip out schema wholesale.
- What should I do instead of chasing FAQ rich results?
- Focus on answer engine optimization fundamentals: write concise, self-contained answers to the questions your customers actually ask, keep your structured data accurate, and make your content clear enough for an AI answer engine to lift and cite. FAQ markup supports that work, but content clarity and entity accuracy are the bigger levers now.
Sources & Further Reading
- Neil Patel: neilpatel.com/blog/google-ends-faq-rich-results — Google Ends FAQ Rich Results
- Search Engine Journal: searchenginejournal.com/google-drops-faq-rich-results-from-search/574429 — Google Drops FAQ Rich Results From Search
- Google Search Central: developers.google.com/search/docs/appearance/structured-data/faqpage — FAQPage (FAQPage) Structured Data Documentation
- Schema.org: schema.org/FAQPage — FAQPage Schema.org Type