FAQ Rich Results Ended: What Publishers Should Remove, Keep and Re-measure
Google ended FAQ rich results. Audit obsolete markup and dependencies, preserve useful reader answers, and annotate the display change before comparing performance.
Published August 9, 2026: Google stopped showing FAQ rich results on May 7, 2026 and removed the feature’s documentation in June.
Publishers should stop treating FAQ markup as a Google Search enhancement. Remove implementation work that exists only to win the retired rich result, preserve genuinely useful answers for readers, and reset the measurement baseline so the expected display loss is not misdiagnosed as a site failure.
The end of the feature does not make every question-and-answer section useless. It changes the reason for keeping one.
What changed
Google’s Search documentation updates state that FAQ rich results stopped appearing on May 7, 2026. Google removed the FAQ structured-data documentation on June 15. The earlier result had already been restricted for most sites, but this update closes the remaining display path.
The documented change concerns Google’s FAQ rich result. It does not mean the visible text must be deleted, that questions can never help a reader, or that another product cannot interpret ordinary page content. It does mean a publisher should no longer promise a Google FAQ enhancement from FAQPage markup.
Remove, keep, and re-measure
| Action | Use it for | Example |
|---|---|---|
| Remove | Markup and tooling maintained only for the retired result | A plugin whose only job is injecting FAQPage JSON-LD |
| Keep | Visible answers that resolve real objections or edge cases | A concise eligibility question beside a tool |
| Rewrite | Repeated mini-FAQs that fragment a coherent article | Move the direct answer under the relevant section heading |
| Re-measure | Search appearance baselines and reports | Annotate May 7 before comparing CTR or pixels occupied |
Audit the implementation
- Inventory FAQ markup. Find templates, blocks, plugins, custom fields, and static JSON-LD that emit FAQPage.
- Separate content from markup. Mark which visible answers serve a reader and which exist only for a search feature.
- Remove dead dependencies. Retire dedicated scripts, styles, or database fields when no other feature needs them.
- Test generated schema. Confirm that removal does not damage Article, BreadcrumbList, Product, or other valid markup.
- Annotate the change. Record the Google retirement date and your deployment date in reporting.
- Watch for stale claims. Update editorial guidance, sales pages, and old posts that still promise FAQ rich results.
Do not delete a plugin or field simply because its name contains “FAQ.” It may also power accessible accordions, internal help, or another page type. Trace the output and dependency before removal.
How to write questions after the rich result
Keep a question when it resolves a distinct reader decision that is not already answered clearly. Put the direct answer first, state the boundary, and link to supporting documentation where the answer can change. If a question requires several paragraphs of reasoning, it probably deserves a normal section rather than a collapsed FAQ item.
Avoid generating dozens of near-duplicate questions to imitate search queries. That creates a repetitive page and makes maintenance harder. The evidence-led publishing guide recommends coherent sections, source proximity, and an original layer that changes what the reader can do.
Reset the baseline
Search-result appearance changed independently of your page. If the old FAQ result occupied more vertical space, click-through behavior may change even when position and content remain stable. Add May 7, 2026 to the reporting timeline, preserve representative before-and-after screenshots where available, and avoid attributing the entire difference to a content edit.
After removing obsolete markup, validate representative templates, inspect Search Console enhancement reports, and monitor crawl errors. Use the technical SEO launch checklist for the release gate.
Ask a question or join the discussion