What it is
FAQPage is a schema.org type, usually written in JSON-LD, that wraps a list of Question items, each with an acceptedAnswer containing the answer text. It describes a page where the publisher asks and answers the questions, not one where users post answers.
For years it was mainly used to earn expandable FAQ results in Google. That reason no longer exists, which changes what the markup is for and when it is worth adding.
Why it matters
Google first limited FAQ rich results to authoritative government and health sites, then stopped showing them in Search altogether and removed the documentation. Any advice that says FAQ schema will win you extra space in Google results is out of date.
The questions themselves still matter. A page built as clear question-and-answer pairs is easy for people to scan and easy for any system to lift an answer from, and the markup is a precise description of that structure. The case for adding it is accuracy about your content, not a promised search feature.
- Google's documentation updates for September 14, 2023 record that the FAQ feature became "only shown for well-known, authoritative government and health websites".Google Search Central, Documentation updates, 15 Sept 2026
- Google's May 8, 2026 entry, "Deprecating the FAQ rich result feature", says "This feature will no longer appear in Google Search starting May 7, 2026", and its June 15, 2026 entry records "Removed documentation for the FAQ rich result feature".Google Search Central, Documentation updates, 15 Sept 2026
- Google's QAPage guidance says "Don't use QAPage markup for FAQ pages or pages where there are multiple questions per page."Google Search Central, Q&A (QAPage) structured data, 15 Sept 2026
How to do it
- 1
Use FAQPage only where the visible page is genuinely a set of questions the site answers, and mark up exactly the questions and answers a reader can see.
- 2
Write each answer to stand alone: lead with the direct answer in the first sentence, then the detail, so it still makes sense when quoted on its own.
- 3
Use QAPage instead for a single question with answers submitted by users, such as a forum thread or a support community page.
- 4
Remove any expectation of a Google rich result from reporting and briefs, and judge FAQ sections by whether they answer real buyer questions.
- 5
Validate the JSON-LD against schema.org whenever the questions change, so the markup never describes text that is no longer on the page.
Run this check on your own site
Free, no sign-up.
Common mistakes
- Adding FAQ markup to win expandable results in Google, a feature Google stopped showing in Search.
- Marking up questions that do not appear on the page, or hiding them, so the structured data describes content readers cannot see.
- Using FAQPage for community Q&A where users submit answers, which is what QAPage exists for.
An example
What the markup looks like
A pricing page with a visible "Questions" section carries one JSON-LD block of type FAQPage whose mainEntity is a list of Question items. Each Question has a name holding the exact question text and an acceptedAnswer of type Answer whose text matches the answer shown on the page.
Not to be confused with
- QAPage
- FAQPage is for questions the site answers itself. QAPage is for a single question where users can submit answers, and Google says not to use it for FAQ pages.
- Schema markup
- Schema markup is the whole vocabulary of structured data types. FAQPage is one type within it, for one page format.
Sources
- 1Google Search Central, Documentation updates read 15 Sept 2026
- 2Google Search Central, Q&A (QAPage) structured data read 15 Sept 2026