Yes for the reader, no as a rich-result tactic. Google announced in May 2026 that the FAQ rich result is no longer shown in Search, and removed the FAQ rich result documentation on June 15, 2026. FAQPage markup therefore does not earn a visible FAQ display. Questions still help because they match how people phrase queries and how answer engines extract passages, but Google has published no causal link between FAQ markup and AI citations.
What exactly changed, and when?
Two separate events matter, and they are often merged into one.
First, the feature itself. Google's Search Central changelog states that the FAQ rich result is no longer shown in Google Search results, as announced in a May 2026 entry. The exact date commonly cited for the change is 7 May 2026.
Second, the documentation. In the June 2026 documentation updates, Google recorded that it removed the FAQ rich result documentation, explaining that the feature is no longer shown, as announced in the May 2026 changelog entry (Google Search Central documentation updates).
That second step is the one people misread. Removing a help page is not the same as adding a penalty. It means there is no longer an eligibility path to document, because there is no longer a display to be eligible for.
The old health and government eligibility rules no longer apply
Before the retirement, FAQ rich results were already restricted. Only authoritative government and health websites could typically trigger them, and even then only for a narrow set of question types. Advice that still tells you to "qualify for FAQ rich results by being a health or government site" is describing a rule that no longer exists. There is no current eligibility category to target, for any site type, in any country.
Does FAQPage markup still do anything?
This is where precision matters, because two different claims get confused.
Claim one: FAQPage markup produces a rich result. Not supported. The feature is retired.
Claim two: FAQPage markup improves AI visibility. Not established. Google has not published a mechanism by which FAQPage markup increases the chance of being cited in AI Overviews, AI Mode or any other generative surface. Anyone asserting a causal link is extrapolating.
What can be said with confidence is narrower and more useful: structured data is a machine-readable description of what is already on the page. It does not create content, and it does not substitute for content. If your FAQ answers exist as visible text, the markup is a redundant description of them. If they do not exist as visible text, the markup describes nothing.
A practical way to decide
| Situation | Reasonable action |
|---|---|
| FAQPage markup already deployed, answers visible on page | Leave it. Removing it is busywork with no documented benefit. |
| FAQPage markup deployed, answers hidden or absent | Either publish the answers as visible text or remove the markup. Markup describing invisible content is a maintenance liability. |
| Planning a new FAQ section | Write the questions and answers for readers first. Treat markup as optional. |
| Vendor promises rich results from FAQ schema | Ask for the current documentation page that supports the claim. There is none. |
Why do questions still help if the rich result is gone?
The mechanism is not markup. It is language matching and passage structure.
People type questions. They type them into Google, into AI assistants and into site search. A page that contains the question in a heading and answers it directly in the following paragraph gives a retrieval system a clean unit to work with: a heading that states the topic, and a self-contained passage that resolves it.
That structure helps in at least three places:
- Classic search snippets. A concise answer paragraph is easier to lift than an answer buried in a long narrative.
- Generative answers. Systems that assemble responses from retrieved passages benefit from passages that make sense on their own.
- Human readers. Someone scanning a page for one specific answer finds it faster.
None of this is a guarantee. It is a structural advantage, not a ranking factor with a published weight.
Example (hypothetical)
Imagine a UK bicycle retailer with a page about commuting bikes. The page currently has one long section titled "Everything you need to know". A rewritten version uses headings such as "Can you cycle to work on a bike without mudguards?" and "How much should a commuter bike weigh?", each followed by a two-to-four sentence answer.
This is an illustration, not a measured result. The plausible benefit is that a system retrieving a passage about mudguards gets a coherent answer rather than a fragment of a general paragraph. Whether that changes any given citation is unknown.
How should you write FAQ content now?
Treat the FAQ as editorial structure, not as a technical trick.
- Start from real question phrasing. Use the wording people actually use, including the slightly awkward version. "Is X worth it in 2026" is more useful as a heading than "Value proposition considerations".
- Answer in the first sentence. Put the direct answer first, then the qualification. Readers and retrieval systems both benefit.
- Keep each answer self-contained. Avoid "as mentioned above". A retrieved passage may arrive without its context.
- Do not manufacture questions. Padding a page with questions nobody asks adds length without adding value.
- Do not duplicate one answer across twenty pages. Repeated boilerplate across a site is a maintenance problem and adds nothing for readers.
A verification method you can run yourself
Because Google has not published a rule for how FAQ content affects generative surfaces, the honest approach is measurement rather than assertion.
Pick ten question-shaped queries relevant to your topic. Record, on a fixed date, whether your domain appears in the standard results and in any AI-generated answer for each. Rewrite the FAQ sections on two or three pages. Re-check the same ten queries after a reasonable interval, using the same location and device settings. Log the results in a simple table.
This will not prove causation. It will tell you whether anything moved, and it prevents you from repeating a claim you have not tested.
What about other retired structured data?
FAQ is not an isolated case. Google has been simplifying the results page and phasing out several structured data features. The same documentation update page records the removal of the practice problem structured data type, and earlier entries cover the retirement of other types such as vehicle listing and the cached link feature (Google Search Central documentation updates).
The pattern is consistent: Google documents a feature, later withdraws it, and removes the documentation. Sites that treat structured data as a permanent entitlement rather than a current contract keep getting surprised. The related lesson from VideoObject markup and Google's clarification of creator and interaction statistics is the same: the documentation describes what Google currently supports, not what it will always support.
Does this differ between the UK, the US and France?
The retirement is a global Search change, not a regional one. There is no UK-specific or US-specific FAQ rich result, and no French-language exception. The same applies in France, French-speaking Belgium and Switzerland.
What does vary by region is which other Search features are available. Google added documentation in September 2026 about regional differences in Search experience, covering features such as aggregator units and supplier units that apply in specific markets, including parts of the European Economic Area. That is a separate topic from FAQ, and it should not be mixed into FAQ planning. If you operate in multiple markets, check the regional documentation rather than assuming a feature is universal.
What should you actually do this quarter?
- Confirm whether FAQPage markup exists on your site and whether the corresponding answers are visible to readers.
- Stop treating FAQ markup as a route to a rich result. That route is closed.
- Invest in question-shaped headings and direct, self-contained answers where they serve readers.
- Remove or update any internal guidance that still references health and government eligibility for FAQ rich results.
- If a tool or agency promises FAQ rich results, ask for current documentation. There is none to provide.
The short version: the markup lost its display. The questions did not lose their value.
Follow-up questions
Should I remove FAQPage markup from my site?
There is no documented reason to rush. Google has not said the markup causes harm. If the answers are visible on the page, leaving the markup in place is a low-cost choice. If the markup describes content users cannot see, fix that mismatch first, either by publishing the answers or by removing the markup.
Will FAQ content get me cited in AI Overviews?
No one can promise that, and Google has not published a mechanism connecting FAQ markup to AI citations. What you can do is make answers easy to retrieve: clear question headings, direct opening sentences, self-contained passages. Treat any citation outcome as unproven and test it on your own queries.
Google’s guide to AI search features prioritizes unique, useful content and SEO fundamentals. Question headings can make answers clearer to readers; that does not establish a causal increase in AI citations.