Google Removed FAQ Rich Results What Changes Now?

Google’s documentation changelog says the FAQ rich result stopped appearing beginning May 7, 2026 and later records removal of the feature documentation. This completes a longer decline that began with the 2023 restriction to a narrow set of authoritative government and health sites. Teams should stop forecasting FAQ SERP expansion or treating the markup as an active Google enhancement.

The Schema.org vocabulary still exists. A type can remain semantically valid on the open web after one search feature stops using it. The decision to retain markup is therefore about consumers, maintenance, and visible-content accuracy—not about preserving a Google result that is no longer shown.

An FAQ section may still solve real reader tasks, reduce support friction, and clarify conditions that do not fit the main narrative. Evaluate it as visible content. Remove duplicate questions written only to occupy search space, merge answers that repeat the body, and keep concise answers that help a reader make a decision.

Question headings should reflect actual uncertainty, not awkward keyword permutations. Link to deeper procedures when an answer needs nuance. If the page is primarily a list of questions with one accepted answer per question, FAQPage may still describe it for consumers that understand the vocabulary; if the section is incidental, ordinary Article or WebPage markup may be sufficient.

If FAQPage markup remains, it must match visible questions and answers and avoid claims that the page is eligible for a Google FAQ enhancement. Validate syntax and preserve a dated note explaining the consumer or interoperability reason. If no system uses it, removing the markup reduces code, tests, and future drift without sacrificing the visible answers.

Do not replace FAQPage with an unrelated supported schema type merely to recover a rich result. Schema types describe content; they are not interchangeable promotion flags. An Article that contains a Q&A section can use Article markup matching the page, while the questions remain normal semantic headings and paragraphs.

Remove forward-looking targets for FAQ rich-result impressions and appearance filters. Annotate May 7, 2026 on historical charts so the end of the feature is not misdiagnosed as a site regression. Retain historical data where available, but label it as a retired Search appearance rather than combining it with current structured-data performance.

Update tests that require FAQ enhancement eligibility, Rich Results Test support, or Search Console enhancement reports. Replace them with visible-content parity, JSON-LD syntax when retained, and ordinary page SEO checks. A test should not keep a dead product contract alive inside the build.

Track the canonical URL’s total clicks, impressions, click-through rate, position, engagement, and support outcomes. If markup is removed without changing visible content, record that as a technical cleanup. Do not attribute later ranking movement to the removed JSON-LD without a controlled comparison and adequate data.

For future deprecations, maintain a feature registry with status, official source, checked date, affected templates, reporting fields, and owner. That turns product changes into bounded migrations rather than emergency content rewrites. The durable asset is the useful answer and its evidence—not the transient shape of a result treatment.