As of May 7, 2026, Google no longer shows FAQ rich results in Search. No more expandable question-and-answer dropdowns under your blue link. The reporting tools and the Rich Results Test support are going away too.
I want to head off the bad advice that's about to flood your inbox.
This does not mean FAQ content is useless. This does not mean schema is dead. And it definitely does not mean you should go rip the FAQ section off your service pages tonight.
Short answer Google is removing the FAQ search feature, not the value of answering questions clearly. Helpful FAQs, clean page structure, and accurate schema still help Google, AI tools, and the actual humans trying to figure out whether to hire you.
Table of contents
What Google actually changed
Google quietly added a note to the top of its FAQ structured data documentation on May 7, 2026. No blog post, no explanation. Just a line at the top saying the feature is gone.
Here is the rollout, with the actual dates:
- May 7, 2026: FAQ rich results stopped appearing in Google Search.
- June 2026: FAQ support in the Rich Results Test goes away.
- August 2026: Support for FAQ rich results in the Search Console API is removed.
For most of you, none of this is a surprise. Google already restricted FAQ rich results to “well-known, authoritative government and health websites” back in August 2023. That means most business websites lost FAQ dropdowns almost three years ago. May 2026 just closed the door on the few verticals that still qualified.
So if you have not seen FAQ dropdowns under your own search results in ages, now you know why.
FAQ rich results are not the same as FAQ content
This is where the bad advice starts.
Some people will hear “Google is removing FAQ rich results” and read that as “delete your FAQs.” That is the wrong takeaway.
FAQ rich results were a search display feature. They were a bonus. They were never the point.
FAQ content is what answers your customer's real questions before they pick up the phone. Good FAQs still help:
- Visitors decide faster
- Sales teams stop answering the same email for the 400th time
- Service pages handle objections without you in the room
- Google understand what a page is actually about
- AI tools describe your business correctly when someone asks them
- Your website become genuinely useful instead of just pretty
The dropdown in Google is gone. The value of clearly answering questions is not.
Does FAQ schema still matter?
Yes, but not the way it used to.
Schema markup is structured data you add to your page so machines (Google, Bing, ChatGPT, Perplexity, Claude, your customer's voice assistant) can understand what you do, where you do it, and who you do it for. Schema can describe your business, services, location, reviews, articles, videos, products, FAQs, and organization details.
FAQPage schema specifically will not produce a rich result anymore. The Schema.org type is still valid, and Google has confirmed that leaving unused structured data on your pages does not hurt your search performance. So you do not have to scrub it.
But here is the rule going forward: schema should reinforce what is already on the page. It is context for machines, not a magic trick.
If the content is visible to a human and the schema describes what is actually there, you are doing it right.
If the schema only exists to chase a search feature that may or may not show up, you are doing busy work.
WebsiteHQ has its own schema markup generator. If you want a free tool to write clean, valid schema for your business, services, or articles, use the WebsiteHQ Schema Markup Generator. We built it for exactly this. No login. No upsell.
What this means for your website
Here is the lesson I keep trying to drive home with our Website HQ clients: do not build your SEO around features Google might take away tomorrow.
They do this constantly. Featured snippets shift, knowledge panels change, sitelinks rearrange, and now FAQ dropdowns are gone. Anyone who built their content strategy around any one of those is now scrambling.
The better play is to make your website easier for everyone to understand. Humans. Google. Bing. ChatGPT. Perplexity. Voice assistants. The buying agents your customers will be using next year.
That means your site should answer the basics, clearly:
- Who you are
- What you do
- Who you help
- Where you serve
- Why you are trustworthy
- What questions customers ask before buying
- What makes you different
- What someone should do next
Get that right and a single rich result feature disappearing is barely a footnote.
Should you remove your FAQ sections?
Almost certainly no.
Keep your FAQs if they answer real questions your customers ask. Keep them if they make the page more useful. Keep them if your sales team would otherwise field the same five emails every week.
The only FAQ sections worth cleaning up are the ones that were padded with filler questions because someone heard FAQ schema might earn a Google dropdown. If that describes a section on your site, trim it back to the questions that actually help a buyer.
A strong FAQ section answers things like:
- How does your process work?
- What does the service include?
- How much does it usually cost?
- Who is this service right for?
- What happens after I contact you?
- What do customers usually get wrong about this?
- What makes you different from the cheaper option I just found?
That content still matters. Not because of a fancy search result. Because it helps people make a decision.
What about AI search?
This is the part I care about most.
Search has changed. People are not only googling the old way. They are asking ChatGPT to compare three companies. They are asking Perplexity to summarize a service. They are asking Claude to recommend a provider. Voice assistants and AI agents are doing the same thing, just behind the scenes.
For your business to show up in those answers, your website has to be legible to machines and humans at the same time. That means:
- Clean page structure
- Specific service descriptions (not “innovative solutions”)
- Helpful FAQs (yes, still)
- Accurate business info on every property
- Strong internal linking between related pages
- Real proof: testimonials, case studies, photos of actual work
- Crawlable text (not text trapped in images)
- Consistent name, address, services across the web
- Schema that matches what is visible on the page
Notice how almost none of that is a trick. It is the same disciplined work Website HQ has been doing for decades. Get found in Google. Get cited in AI answers. Same work, done a little smarter.
The bigger SEO lesson
Google removing FAQ rich results is not the death of schema. It is the death of one more lazy SEO shortcut.
For years, some sites jammed in FAQ schema because it helped them take up more real estate in search results. That was useful while it lasted. It was never a strategy.
A real strategy is built on clarity, trust, and usefulness. Your website should help visitors understand what you do. It should help Google understand what you do. And increasingly, it should help AI tools understand what you do.
That is where search is headed.
What to do next
Here is the practical move. Do not panic. Do not delete your FAQs. Do not abandon schema. Pull up your site and ask:
- Are our FAQs actually useful, or are they padding?
- Is our schema accurate, and does it match the visible page?
- Are our services clearly explained, or do they read like a template?
- Could Google, ChatGPT, and Perplexity all describe what we do correctly?
- Is this site built for long-term clarity, or for the next SEO feature?
If your website depends on outdated tricks, this update is a quiet warning. If your website is built around clear, helpful, trustworthy content, this change is a non-event.
The takeaway
Google is removing FAQ rich results. FAQs are not useless. Schema is not dead. The visible reward in search is gone. The real work has not changed.
Build a website that people, search engines, and AI tools can all understand. That is what keeps your business findable.
Frequently Asked Questions about FAQ Schema
No. Google removed the FAQ rich result, which is the visual dropdown that used to appear under your search listing. FAQPage schema is still a valid Schema.org type, and Google has confirmed it will keep using FAQ structured data to understand pages. The display feature is gone. The markup still does work behind the scenes.
Almost never. If the schema accurately describes visible question-and-answer content on the page, leave it alone. Google has stated that unused structured data does not hurt your search performance. The only time to clean it up is when the FAQ section itself was filler that you only added to chase the rich result.
For most websites, no. Google restricted FAQ rich results to authoritative government and health sites back in August 2023, so commercial sites lost the dropdown almost three years ago. If your traffic survived that change, the May 2026 update is a non-event.
Yes. Helpful FAQ content still helps Google understand the topic of a page and still feeds AI Overviews, ChatGPT, Perplexity, and the People Also Ask box. The shift is that FAQ content now earns visibility through AI answers and topical clarity instead of a Google dropdown.
You do not have to replace it. FAQPage is still valid for genuine FAQ pages. For most business websites, the higher-leverage schema types are Organization, LocalBusiness, Service, Product, Review, and Article. If you want a free tool to generate clean schema for any of those, use the WebsiteHQ Schema Markup Generator.
The official cutoff was May 7, 2026. FAQ support in the Rich Results Test goes away in June 2026, and FAQ rich result support in the Search Console API is removed in August 2026.
Not by this specific change. Google did already drop HowTo rich results in 2023. If your site relied on either FAQ or HowTo rich results, the same lesson applies: build for clarity, not for one search feature.
Not sure if your site is still structured for how people actually search now? Website HQ]] reviews your content, schema, and page structure and tells you what is helping, what is outdated, and what needs to be cleaned up. Get in touch.