Google Removed FAQ Rich Results. What Now?
Keep useful answers. Stop treating FAQ markup as a search-result feature. Make structured data match the page users can actually see.
Google stopped showing FAQ rich results in May 2026 and removed the related documentation in June. That changes the expected search-result benefit of FAQPage markup. It does not make customer questions useless. The practical response is to keep FAQs where they help a decision and stop adding boilerplate questions merely to create schema.
What Changed
Google’s search documentation update records the removal of the FAQ rich result and the subsequent documentation cleanup. A page should no longer expect the expanded FAQ treatment in Google Search.
Structured data is not a ranking shortcut. It is a machine-readable description of visible content. When Google no longer supports a search feature, the markup should not remain a core deliverable or reporting claim.
Keep FAQs When They Improve the Page
- The question removes a real sales objection.
- The answer clarifies eligibility, geography, pricing approach, timing, or risk.
- The question covers an edge case that does not belong in the main narrative.
- The answer is specific to the service or article rather than copied sitewide.
- The section is readable and useful without structured data.
A useful FAQ section can still earn long-tail visibility because the answer is part of the page’s text. It can also improve conversion by resolving doubt near the next step.
Remove the Markup When It Has No Job
| Situation | Recommended action |
|---|---|
| Visible, useful FAQs with accurate markup | Markup is optional; keep the visible content |
| FAQPage markup with no visible matching questions | Remove it immediately |
| Same FAQ schema copied to many pages | Remove or rewrite the visible content page by page |
| FAQ markup sold as a rich-result tactic | Correct the deliverable and reporting language |
| Article and Breadcrumb markup match the page | Keep and validate them |
What Structured Data Still Deserves Attention
Use Article markup on a genuine article, Breadcrumb markup where the visible path exists, and organization or local-business information that matches public business details. Product, Review, Event, JobPosting, Video, and other supported types should be used only when the page meets the feature’s current requirements.
The most important QA is consistency: canonical URL, Article URL, Open Graph URL, sitemap URL, visible title, dates, author, and main entity should agree. Our structured data work treats accuracy as the deliverable, not the number of schema types installed.
We keep visible FAQs that help the reader, remove obsolete or unsupported search-feature claims, and validate structured data against the canonical page before publication.
Frequently Asked Questions
Should I delete every FAQ section from my website?
No. Keep questions that help customers understand the service or make a decision. The removed feature is the FAQ rich result, not the usefulness of question-and-answer content.
Should I remove FAQPage schema?
It is no longer a Google FAQ rich-result tactic. Remove it when it is unsupported, duplicated, inaccurate, or maintained only for that feature. Keeping accurate but unused markup provides little practical value.
Do FAQs still help SEO?
They can help when they answer genuine searches and improve the page. Repetitive boilerplate questions added only for keywords are unlikely to strengthen the content.
What schema should a blog post use?
A genuine article can use Article or BlogPosting markup, plus accurate Breadcrumb markup where appropriate. The canonical URL, author, dates, title, image, and visible page should agree.
Make Structured Data Match the Site
We will audit canonical URLs, schema, visible content, and search-feature eligibility without selling obsolete markup as a shortcut.
Request a Free Audit →