
Google Officially Ends FAQ Rich Results, If you’ve managed a website for more than a few years, you’ve probably added FAQ schema at some point — maybe to snag that expandable question dropdown in Google search results, maybe just to organize your page better. As of May 7, 2026, that dropdown is gone for good. Google quietly added a notice to its FAQ structured data documentation confirming that FAQ rich results no longer appear in Search or Google Officially Ends FAQ Rich Results
I’ve been working as an SEO specialist for three years, and I use FAQ schema for more than just chasing rich results — I use it to help AI tools pull clean answers from a page and to keep content organized for readers. So when this news broke, I didn’t touch a single site right away. I wanted to actually understand what changed before reacting. Here’s what I found, and where I’ve landed.
What Actually Changed
Google’s rollout isn’t a single event — it’s happening in three stages:
| Date | What Happens |
| May 7, 2026 | FAQ rich results stop appearing in Google Search |
| June 2026 | The FAQ search appearance filter, FAQ rich result report, and FAQ support in the Rich Results Test are removed |
| August 2026 | Search Console API support for FAQ rich result data is removed |
Importantly, FAQPage is still a valid schema.org type. Your markup won’t throw validation errors, won’t trigger a manual action, and won’t hurt your rankings if you leave it in place. What’s gone is the visible payoff in the search results page — not the underlying structured data itself.
Wait, Didn’t This Already Happen?
Sort of. Google narrowed or Google Officially Ends FAQ Rich Results: Should You Remove FAQ Schema FAQ rich result eligibility back in August 2023, restricting the visible dropdown mostly to well-known government and health sites. For the vast majority of commercial sites, agencies, and publishers, the rich result had already stopped showing up years before this official announcement. May 2026 is really Google closing the loop on a rollback that started long ago — not a sudden reversal.
That context matters. If Google Officially Ends FAQ Rich Results: Should You Remove FAQ Schema your FAQ schema stopped producing visible results back in 2023 and you didn’t notice a traffic cliff, this update shouldn’t cause one either.
Why I’m Not Rushing to Remove Anything
Here is my honest take on this. I have been watching how this plays out with the sites I manage. None of my clients are worried about Google Officially Ends FAQ Rich Results. None of them have asked me to remove FAQ schema from their pages. I have not made any changes myself yet. I wanted to take some time to really look into Google Officially Ends FAQ Rich Results. I do not see any reason to rush.
Let us think about Google Officially Ends FAQ Rich Results for a moment. Google Officially Ends FAQ Rich Results. Nothing bad is happening to any site I manage. There is a difference between what people’re saying and what is actually happening with Google Officially Ends FAQ Rich Results. I think a lot of people are overreacting to Google Officially Ends FAQ Rich Results news.
My plan is to leave FAQ schema where it’s wait to see what happens with Google Officially Ends FAQ Rich Results. I will watch what happens in June and August. I will keep an eye on Search Console. If something changes I will adjust my plan regarding Google Officially Ends FAQ Rich Results. This is a way to do things than to make big changes now regarding Google Officially Ends FAQ Rich Results.
There are reasons why I’m okay with waiting. FAQ schema is still good. FAQ schema will not cause any problems. FAQ schema will not hurt rankings. FAQ schema will not cause any errors.
- FAQ schema is still markup
- FAQ schema will not throw errors
- FAQ schema will not trigger an action
- FAQ schema will not hurt rankings
The real change already happened. Google changed the rules for FAQ results in 2023. Most of my clients sites had not seen the dropdown in years. Google Officially Ends FAQ Rich Results is just Google updating its documentation. Google Officially Ends FAQ Rich Results is not a change.
Making changes quickly is not always the idea. Removing schema from a site takes time. It can cause problems. Making changes, in a hurry is not an idea.
If you are managing client sites and you are feeling pressure to make changes because of Google Officially Ends FAQ Rich Results I say wait. Watch what happens in June and August. Make your decision based on what happens with Google Officially Ends FAQ Rich Results. Do not make changes because of the Google Officially Ends FAQ Rich Results news.
So to be clear Google Officially Ends FAQ Rich Results does not change what I do today. Google Officially Ends FAQ Rich Results changes what I will watch between now and August. I will keep an eye on Google Officially Ends FAQ Rich Results and see what happens with Google Officially Ends FAQ Rich Results.
Should You Remove FAQ Schema? My Take
For most sites, no — leave it. Here’s my reasoning:
• It’s not causing harm. Unused or non-visible structured data doesn’t create ranking problems.
• It still serves a comprehension role. AI-driven search features and tools like AI Overviews, ChatGPT, and Perplexity often pull from clearly structured Q&A content, even without a formal rich result tied to it.
• Removal has a cost too. Stripping schema from live pages takes dev time and carries its own risk of breaking something else. Unless it’s actively causing a problem, that effort is better spent elsewhere.
Where I’d actually take action:
1. Stop selling it as a rich-result tactic. If FAQ schema is still listed in your (or your agency’s) deliverables as a way to “win” the FAQ dropdown, update that language now. Position it as a content and comprehension tool instead.
2. Update your QA process. If you were using the Rich Results Test to check whether FAQ schema would trigger the dropdown, that check is obsolete. Swap it for general structured-data validation.
3. Check your reporting pipelines. If you have dashboards or scripts pulling FAQ rich result data from the Search Console API, they’ll break in August 2026. Update those before the deadline, not after.
Common Mistakes I’m Seeing Right Now
The biggest one is treating this as a binary — either rip out all FAQ schema, or declare it more important than ever. Both reactions skip the more useful question: is your FAQ content actually helping the reader? If yes, keep it, schema or not. If your FAQs exist only because a checklist told you to add them, that’s the real problem — and it predates this update.
FAQs
Q: Does removing FAQ rich results affect my rankings?
No. This change only affects a visual search feature, not ranking signals.
Q: Should I remove FAQPage schema from my site?
Not unless it’s causing a real issue. It remains valid and harmless to leave in place.
Q: Will Search Console still show FAQ data?
The FAQ rich result report and filter are being removed in June 2026, and API support ends in August 2026.