FAQ content and schema after Google retired FAQ rich results
Review useful visible questions separately from structured markup and Google Search features, using the current May 2026 retirement notice.
Use the current feature status
As checked on October 18, 2026, Google’s Search documentation changelog says the FAQ rich result feature stopped appearing in Search from May 7, 2026. It also records removal of the feature documentation. The old FAQ documentation URL now redirects to the updates page. [Google Search Central: Documentation updates]
That makes the older government/health-site eligibility advice an outdated answer to this current question. Do not use a historical eligibility rule to promise that a newly marked-up FAQ can obtain the retired result. A technically valid schema object and an available search presentation are separate matters.
This article concerns Google Search’s feature status. Other consumers may interpret structured vocabulary differently, and their behavior needs its own verified documentation. Do not transfer a Google retirement statement into a claim that all machines ignore questions.
Keep a question only when it helps the reader
| Candidate question | Editorial decision | Reason |
|---|---|---|
| Does the worksheet require an account? | Keep if the access rule is real and otherwise unclear | Resolves a practical blocker |
| How are partial refunds handled? | Answer near the calculation or as a focused question | Clarifies a meaningful method boundary |
| What is the entire subject of this article? | Usually improve the main answer instead | Avoids repeating the introduction |
| Why is this the best service? | Remove unsupported superiority framing | Does not provide verified useful evidence |
| Can this guarantee better rankings? | Do not imply a guarantee | Publication and indexing outcomes need evidence |
Use support questions, observed search queries or explicit editorial reasoning as the basis. If a question was not measured in Search Console or another source, label its demand basis as editorial in the working brief. A plausible wording is not proof of search volume.
A short article may need no FAQ at all. A calculation with a genuine exception may benefit from one focused answer. Choose the form after the body is clear rather than reserving five mandatory questions for every page.
Keep structured data tied to the visible answer
If a system emits FAQ vocabulary for a legitimate downstream purpose, ensure the same nonempty questions and answers are actually visible, current and accurate. Do not generate hidden promotional answers, empty question objects or a second contradictory FAQ from another plugin.
Treat JSON validity as a technical check. It does not verify the factual answer, the availability of a rich result or the page’s authority. Escape serialized content so editorial text cannot terminate a script element, and inspect the final rendered page after the CMS or framework has combined its components.
Article and breadcrumb markup can also be duplicated when a page-specific component repeats what the site layout already emits. Inventory the actual output before adding more schema. The objective is a truthful description of the page, not the largest number of structured objects.
Remove the promise, preserve the useful content
- Check the current official documentation for the target search feature.
- Read each visible question against an unresolved reader task.
- Verify claims and remove repeated or promotional filler.
- Inspect actual structured output for empty or duplicate objects.
- Test the visible page and keep any search-outcome claim separate.
I would update a page that promises FAQ rich-result eligibility before adding another FAQ block. Preserve a useful answer where it belongs, correct the feature claim and record the date of the primary-source check. That is a concrete content improvement without inventing a ranking benefit.
Sources
AI-assisted writing and an AI-generated editorial cover. Source links and checked dates are listed below; illustrative examples are labeled in the text.
- Google Search Central: Documentation updates — checked 2026-10-18