Google FAQ rich results stopped appearing in Search on 7 May 2026. For most website owners, that means FAQPage structured data no longer produces the expandable question-and-answer treatment that once appeared beneath a search result.
This does not make useful FAQs obsolete. It changes the reason for creating them. FAQs should now be judged by whether they help visitors understand a service, product or process—not by whether they may enlarge a Google listing.
What Google changed
Google added the deprecation to its documentation in May 2026. Its Search documentation updates state that the FAQ rich result feature no longer appears from 7 May 2026.
The change completes a longer reduction in FAQ visibility. In 2023, Google limited regular FAQ rich results largely to authoritative government and health sites. The 2026 change removes the feature rather than merely restricting eligibility.
Do not confuse this with ordinary questions and answers appearing in page copy. Google can still crawl and index useful text. The change is specifically about the enhanced FAQ presentation in Search.
What the change means in practice
Element
Current position
Recommended action
Visible FAQs
Still useful for readers
Keep only questions that resolve real concerns
FAQPage schema
No Google FAQ rich result
Keep only when accurate and operationally useful
Search Console reporting
No FAQ rich-result performance to optimise
Measure page clicks, engagement and conversions
QAPage schema
Reserved for eligible community Q&A pages
Do not use it as a replacement for FAQs
Should you remove FAQ schema?
There is no universal need for an emergency site-wide removal. If the markup is valid, matches visible content and supports another system or internal workflow, keeping it can be reasonable. However, it should not remain solely because a team expects Google FAQ rich results.
Remove or stop generating it when it creates maintenance work, conflicts with visible copy, produces validation problems or encourages thin FAQ sections. Search markup should describe content accurately; it should not become a reason to add repetitive content.
Before changing a WordPress template or SEO plugin, test the decision on a small group of pages. Save a copy of the existing output, clear relevant caches and inspect the rendered source after deployment. This prevents a narrow schema cleanup from accidentally removing Article, Breadcrumb or other markup that still serves a valid purpose.
For a wider markup review, Kayaar’s Article schema and author URL guide explains a more durable way to connect articles with their authors. Use Google’s supported feature documentation as the source of truth for Google-specific behaviour.
Do not replace FAQPage with QAPage
QAPage is not a workaround. Google’s Q&A structured data guidance says it is intended for a page focused on one question where users can submit answers. An editor-written FAQ section containing several questions does not meet that use case.
Changing the schema type without changing the page model can make the markup inaccurate. Keep the vocabulary aligned with what visitors can see and do.
Keep FAQs when they improve the page
A useful FAQ handles genuine objections or clarifies details that would interrupt the main explanation. Good candidates include eligibility, timing, cost factors, limitations, required information and the next step. Avoid rewriting every heading as a question or repeating paragraphs already covered above.
Five concise answers are usually more helpful than twenty generic ones. Make the questions visible, accessible and easy to open on mobile. This supports the clarity-first approach in Kayaar’s Google AI Mode content workflow and the practical quality checks in the August spam update guide.
Measure usefulness after the rich result
Stop using rich-result eligibility as the primary success measure. Review whether visitors open the accordions, continue to a relevant service page, contact the business or complete another useful action. In Search Console, watch ordinary page and query performance rather than waiting for an FAQ appearance filter.
If a page loses traffic, do not assume the schema change caused it. Compare stable periods, check ranking and demand changes, and review the whole result page. Kayaar’s Search Console AI performance guide provides a measured framework for interpreting visibility data.
A practical audit workflow
List templates and pages that output FAQPage markup.
Confirm every marked-up question and answer is visible to visitors.
Remove duplicate, outdated or promotional questions.
Check whether any external system genuinely uses the structured data.
Test important pages after template changes and monitor engagement.
For strategic help deciding which technical changes deserve attention, contact Kayaar for a focused SEO review.
Key takeaway
Google FAQ rich results are gone, but helpful questions and answers still have a place on strong pages. Keep FAQs for people. Keep FAQ schema only when it accurately describes visible content and has a clear purpose beyond chasing a discontinued Google feature.
FAQs
When did Google remove FAQ rich results?
Google says the FAQ rich result feature stopped appearing in Search on 7 May 2026.
Should I delete all FAQPage schema now?
Not automatically. Keep it only when it matches visible FAQs and serves a clear purpose; remove it when it is inaccurate, broken or maintained only for Google’s discontinued rich result.
Do visible FAQs still help SEO?
They can improve page usefulness and clarity when they answer real visitor questions. They are not a guaranteed ranking benefit or rich-result shortcut.
Can QAPage schema replace FAQPage schema?
No. QAPage is intended for eligible pages focused on one question where users can submit answers, not ordinary editor-written FAQ sections.
How should FAQ performance be measured?
Measure engagement, useful onward journeys, enquiries and ordinary Search performance rather than FAQ rich-result appearances.
