From the 2023 restriction to the 2026 removal
The familiar eligibility rule belongs to an earlier stage. In its August 2023 change notice, Google wrote:
Going forward, FAQ (from FAQPage structured data) rich results will only be shown for well-known, authoritative government and health websites.
Google Search Central Blog, August 2023
That was the eligibility restriction announced in 2023, not the current availability of the feature.
Google's documentation update record subsequently stated:
This feature will no longer appear in Google Search starting May 7, 2026.
Google Search documentation updates
Google's official documentation update record says Google removed the FAQ rich-result documentation in June 2026 because the feature was no longer shown. The former FAQPage documentation address now redirects to that update record.
Begin the page review with the questions themselves. Would removing an answer make the page less useful to someone comparing options, checking a requirement or deciding what to do next? If so, preserve the answer in an appropriate location.
Keep questions that resolve a real decision
A useful FAQ handles a question that remains after the main explanation. It might clarify an exception, a required input, an implementation constraint or the meaning of a term that buyers regularly misunderstand. Use actual reader enquiries or a clearly identified gap in the page to choose questions; a keyword list alone does not show what someone needs answered.
Read the body before adding questions. If the main section already explains an issue clearly, another answer at the bottom rarely contributes much. If the missing answer is central to the page's purpose, put it in the main body. Reserve the FAQ for related questions that need a short, separate response.
For example, consider a hypothetical page for a placeholder technical service. Its body describes the service and required documents, but never explains what happens when one document is unavailable. A question about that exception could help the reader. A question asking what the service does would merely repeat the introduction.
Write each retained answer so that its subject, condition and conclusion are understandable together. Avoid answers such as “Yes, as explained above,” which force the reader to search for a missing condition. Where evidence is needed, attach it to the answer rather than leaving an unsupported statement beside a remote reference.
The technical answer evidence brief discusses connecting claims to supporting material. Here, the narrower task is deciding which unanswered questions deserve space on the page.
Drop repetition and sales copy
Remove FAQ entries that simply turn headings into questions. A heading called “Required inputs” followed by “What inputs are required?” often gives the same information twice. Consolidate the answer unless the second location resolves a distinct uncertainty.
Also remove questions created mainly to introduce praise, broad superiority claims or a request to contact the seller. A buyer question should lead to a useful answer, rather than become a device for repeating a sales message.
Apply three editorial checks:
- Distinct information: Does the answer add something the body has not already explained?
- Usable answer: Can the reader understand it without reconstructing its meaning from several sections?
- Relevant scope: Does it help someone complete the decision addressed by this page?
A question that does not meet these criteria may need rewriting, relocation or removal. Adding more entries is not the objective. Leave fewer unresolved questions. A long answer with several conditions may deserve its own section; a short answer duplicating the introduction may deserve no separate entry.
Decide what the markup is meant to accomplish
After editing the visible content, inspect any existing FAQPage markup. Schema.org defines FAQPage as a web page presenting one or more frequently asked questions. That vocabulary definition is separate from whether a search engine offers a corresponding display feature.
If markup remains, compare its questions and answers with what readers can see. Google's general structured-data guidelines say not to mark up content that is invisible to readers or irrelevant to the page. As a practical check, retain the answer's qualifications in both places, and correct markup when the visible answer changes.
For Google's AI Overviews and AI Mode, its documentation says no special schema.org structured data needs to be added. That statement concerns those Google features; it does not establish how other answer engines treat FAQPage.
The cited sources do not establish that other answer engines use or prefer FAQPage markup when selecting sources. Treat that as unresolved. A self-contained answer can be useful to a reader without becoming a confirmed selection signal.
Keep accurate markup when you can identify its purpose and maintain its agreement with the page. Consider removing it when it adds maintenance effort without an identified use. Deleting the markup need not delete the useful visible answers. Neither decision establishes that the page will be cited.
Validate accuracy without expecting a search feature
Use the Schema Markup Validator for the code check. Its documentation describes extracting JSON-LD, RDFa and Microdata, displaying the extracted graph and identifying syntax mistakes. It can fetch a page URL or accept markup directly. These are implementation checks, rather than evidence of search-display eligibility.
Then compare every marked-up question and answer with the rendered page. Check for omitted qualifications, old answers and questions that no longer exist. Review whether the visible answers are accessible and understandable. A syntax tool cannot decide whether an answer resolves the buyer's uncertainty.
Google's general guidelines describe the Rich Results Test and URL Inspection tool as catching most technical errors, while noting that quality guidelines are not easily tested automatically. Those general statements do not establish current FAQ-specific support. Use each tool for the checks it currently exposes; do not expect a FAQ enhancement report or a rich-result preview from valid FAQPage syntax.
Record what was checked: extracted markup, syntax issues and agreement with visible answers. Valid syntax establishes syntax. Agreement with visible content establishes consistency. Neither establishes that Google will show an FAQ rich result or that another engine will cite the answer.
When an AI answer links to the page, compare its wording with the relevant visible answer. The citation guide provides context for that separate observation.
Want to see how AI engines describe your brand today?
Get a free growth audit