FAQPage is a Schema.org type for a page with questions and publisher-provided answers. Google retired FAQ rich results on 7 May 2026. Useful FAQs can still help readers, but adding FAQPage markup does not bring that search feature back or guarantee an AI citation.
What changed?
Older guides describe expandable FAQ results beneath a Google listing, sometimes limited to health and government sites. That advice is now out of date. Google’s documentation update log records the retirement. If a proposal promises these results as a new benefit, ask for its source and review the scope.
Keep the questions that help your visitors
Use actual enquiries, support conversations and page-specific research to decide what belongs in an FAQ. On a charity website package page, visitors may need to know whether donation integration is included and who pays platform fees. On a clinician page, booking locations and referral requirements may be useful. Have the responsible owner review the answers.
- Answer a distinct question rather than repeating the main sales copy.
- Put crucial information in the main page when every visitor needs it.
- Use a native disclosure control that works with a keyboard.
- Write as much as the answer needs; there is no required FAQ word count.
- Remove answers when they become inaccurate or no longer help.
If you retain structured data
Keep it consistent with the visible questions and answers. Validate the JSON and the vocabulary being used. Syntax validation is different from eligibility for a search feature. Do not label ordinary headings such as “Direct answer” as questions or add invented questions solely to increase the amount of markup.
How to review an existing implementation
- Find the page’s visible FAQ and its JSON-LD.
- Compare the questions and answers, including prices and scope.
- Check that closed answers remain available through accessible controls.
- Remove claims of a current Google FAQ enhancement from service copy and reports.
- Record the correction date without replacing the original publication date.
Treat the result as a usability and accuracy improvement. If you want to know whether the page attracts more suitable enquiries, use your search and conversion measurements. Do not infer a traffic uplift simply because markup validates.