Google removed FAQ rich results from Search as of May 7, 2026. The dropdowns are gone, and Google says the related Search Console reporting and Rich Results Test support are being removed too.
That sounds like “FAQ schema is dead.”
It is not.
Answer: FAQ schema still matters when it accurately describes visible FAQ content, but it should no longer be treated as a rich-result tactic. Businesses should shift toward structured data that clarifies entities, services, articles, breadcrumbs, reviews, proof, and trust.
The real story is not that schema stopped mattering.
The real story is that Google killed another shortcut.
Jump Ahead
- What Google actually changed
- FAQ rich results and FAQ schema are not the same thing
- Why schema still matters for AI Findability
- What businesses should do now
- What schema should focus on instead
- The bigger lesson
What Google Actually Changed
Google’s FAQ structured data documentation now says FAQ rich results are no longer appearing in Google Search as of May 7, 2026.
Google also says it will remove the FAQ search appearance, FAQ rich result report, and FAQ support in the Rich Results Test in June 2026. FAQ rich result support in the Search Console API is scheduled to go away later too.
Plain English:
The little FAQ dropdowns in search results are gone.
The reporting around those dropdowns is going away.
The testing tool support for that specific rich result is going away.
That is a real change.
But it does not mean “schema is dead.”
That line is going to spread because it is easy to say, but it is the wrong takeaway.
FAQ Rich Results and FAQ Schema Are Not the Same Thing
FAQ rich results were a visual search feature.
FAQ schema is structured data.
Different thing.
A rich result is what Google may choose to show in the search results. A dropdown. A star rating. A product price. A recipe card. A video enhancement.
Structured data is a machine-readable layer that helps describe what exists on the page.
FAQPage schema says:
“This page has visible questions and answers.”
It does not force Google to show a dropdown.
It never did.
For years, a lot of SEOs treated FAQ schema like a cheap way to grab more SERP real estate. Add questions. Add markup. Get bigger search result. Take up more space.
That worked for a while.
But if your schema strategy depended on Google handing you extra pixels in the search results, that was not a strategy.
That was a bonus with an expiration date.
Why Schema Still Matters for AI Findability
Schema is not magic.
It does not guarantee rankings.
It does not guarantee AI Overview placement.
It does not force ChatGPT, Perplexity, Gemini, or Google AI Mode to cite your website.
But it still matters because the web is becoming more machine-read.
AI systems and search engines are trying to understand:
- Who you are
- What your business does
- Which services you offer
- Who authored the content
- Where your company operates
- What your pages are about
- Which claims are supported by visible content
- How your pages connect to each other
- Whether your brand looks consistent across the web
Schema is one piece of that clarity layer.
Not the whole thing.
One piece.
Google’s AI features documentation says there are no additional technical requirements to appear in AI Overviews or AI Mode beyond normal Search indexing and snippet eligibility. That matters. There is no secret “AI schema” button.
But Google also continues to care about pages being understandable, crawlable, indexable, and supported by visible content.
That is the useful frame.
Schema does not replace good content.
Schema translates good content.
What Businesses Should Do Now
Do not panic.
Do not rip out every FAQ section.
Do not delete all FAQPage schema just because the dropdown is gone.
And definitely do not assume structured data stopped mattering.
Here is the sane move:
1. Keep FAQs that answer real buyer questions.
If the questions help prospects understand your service, pricing, process, timing, risk, comparison points, or next steps, keep them.
Those questions still help humans.
They also give search engines and AI systems clearer answer material.
2. Remove thin FAQ sludge.
If the FAQ section only exists because someone wanted a rich result, clean it up.
Bad FAQs look like this:
- “Do you offer quality service?”
- “Are you the best company?”
- “Can I contact you?”
- “Do you care about customers?”
That is not helpful. That is filler.
3. Make sure schema matches visible content.
This is the part people love to skip.
Structured data should describe what is actually on the page. If the FAQ is not visible to users, do not mark it up as visible FAQ content.
If the page does not contain a review, do not invent review schema.
If the page does not clearly describe a service, do not expect Service schema to save it.
Machines are getting better at checking whether your markup and your page actually agree.
Good.
They should.
4. Shift effort toward entity and trust clarity.
For most established businesses, the bigger opportunity is not FAQPage markup anymore.
It is making the whole site easier to understand.
That includes your About page, service pages, case studies, author information, location details, internal links, proof, reviews, and comparison content.
This is where AI Findability starts to become more than SEO cleanup.
It becomes website infrastructure.
What Schema Should Focus on Instead
FAQPage schema can still be useful when the page has real FAQ content.
But it should not be the center of the strategy.
For most business websites, I would rather see clean structured data around:
OrganizationPersonWebSiteWebPageArticle/BlogPostingServiceLocalBusinesswhere appropriateBreadcrumbListReviewwhen reviews are real and visibleProductwhen there is a real productVideoObjectwhen video is part of the pageFAQPageonly when the FAQ is visible and useful
The goal is not to mark up everything because you can.
The goal is to reduce ambiguity.
A good schema strategy should help machines answer basic questions about your business:
- Is this a real company?
- Who is behind it?
- What does it sell?
- Who does it help?
- Where does it operate?
- What proof supports the claims?
- Which page is the authoritative answer for this topic?
That is the real game now.
Not “how do we get the dropdown back?”
The Bigger Lesson
Google killed the FAQ dropdown.
It did not kill schema.
It killed a lazy incentive.
And honestly, that is probably healthy.
The old version of SEO rewarded too many little hacks:
- Add FAQ markup
- Chase snippets
- Stuff questions into the page
- Build content around SERP features instead of buyer needs
- Call it strategy
That playbook keeps getting weaker.
The stronger playbook is harder, but it compounds.
Build pages that clearly explain what you do.
Answer the questions buyers actually ask.
Show proof.
Connect your entities.
Use schema to describe real visible content.
Make your site easier for humans, Google, AI answers, and future buyer agents to understand.
That is AI Findability.
And it is where SEO is going.
Final Takeaway
FAQ rich results are gone.
FAQ schema is not automatically useless.
Schema is still useful when it accurately describes visible, helpful content.
But if your strategy was built around getting extra dropdowns in Google, this is your warning.
Stop chasing markup tricks.
Start building machine-readable trust.
That work is not going away.
Sources
- Google Search Central: FAQPage structured data — confirms FAQ rich results stopped appearing as of May 7, 2026, with related Search Console and Rich Results Test support being removed.
- Google Search Central: AI Features and your website — confirms there are no additional technical requirements for AI Overviews or AI Mode beyond normal Google Search indexing and snippet eligibility.
Suggested CTA
If you want to know whether your website is still readable, trustworthy, and structured for Google and AI search, start with a Findability OS Audit.
We look at the stuff most quick SEO scans miss: entity clarity, service structure, schema, proof, internal links, crawlability, and whether an AI system can actually understand why your business should be recommended.