FAQ structured data
FAQ structured data uses schema.org FAQPage to mark up a list of questions and their answers. Note that Google narrowed FAQ rich-result eligibility in 2023 to well-known authoritative government and health sites, so most sites no longer get the visual rich result. This page explains correct FAQPage markup, the eligibility change, and how to validate it.
What this means
FAQPage structured data marks up a page that contains a list of questions, each with a single answer, using schema.org FAQPage with Question and Answer (acceptedAnswer) items. It is meant for content where the site provides both the questions and the answers.
Google reads the markup to understand the Q&A content. Historically it could produce an expandable FAQ rich result in Search, but eligibility was substantially narrowed in 2023.
The 2023 eligibility change
In August 2023, Google announced that the FAQ rich result would be limited to well-known, authoritative government and health websites. For all other sites, valid FAQPage markup generally no longer produces the visual FAQ rich result.
You can still include accurate FAQPage markup for clarity and potential future use, but set expectations accordingly: most sites will not see the rich result, so do not add FAQ markup expecting guaranteed visual enhancement.
- FAQ rich result narrowed to authoritative gov/health sites (Aug 2023)
- Most sites no longer get the visual FAQ rich result
- Markup can still be valid and accurate
- Do not expect guaranteed visual enhancement
Correct markup and validation
Each Question must have exactly one acceptedAnswer, and the questions/answers must be visible on the page and authored by the site (not user-submitted Q&A, which uses QAPage instead). Do not use FAQPage for advertising or to mark up content that is not a genuine FAQ.
Validate with the Rich Results Test and the Schema Markup Validator, and watch Search Console for structured-data errors. Because the rich result is restricted, treat validation as confirming correctness rather than unlocking a guaranteed feature.
How it appears in analytics and logs
FAQPage markup describes a question-and-answer set. Since Google's 2023 change, the FAQ rich result generally shows only for authoritative government and health sites, so most sites should not expect the visual treatment even with valid markup. Misusing FAQ markup for non-FAQ content violates the guidelines.
Diagnostic use case
Mark up genuine FAQ content correctly and understand the limited FAQ rich-result eligibility so you set realistic expectations and avoid policy violations.
What WebmasterID can help detect
WebmasterID confirms which crawlers fetch the FAQ page and the response. Validating the FAQPage JSON-LD is done with Google's tools; WebmasterID complements that by confirming the page is crawlable.
Common mistakes
- Expecting an FAQ rich result on a non-authoritative site after the 2023 restriction.
- Using FAQPage for user-submitted Q&A instead of QAPage.
- Marking up questions/answers that are not visible on the page.
- Stuffing promotional content into FAQ markup, violating the guidelines.
Privacy and accuracy notes
FAQ structured data describes published Q&A content, not visitors. WebmasterID records crawler fetches of the page as bot events and collects no user data.
Frequently asked questions
- Will FAQ markup give me a rich result?
- Usually not anymore. Since August 2023, Google limits the FAQ rich result to well-known authoritative government and health sites. Most other sites no longer get the visual FAQ enhancement even with valid markup.
- When should I use QAPage instead of FAQPage?
- Use QAPage for pages where users submit and answer questions (like a forum thread). FAQPage is for question-and-answer content authored by the site itself.
Related pages
- Diagnosing structured data errors
Structured data (schema.org markup, usually as JSON-LD) lets search engines understand a page and can make it eligible for rich results. Errors — missing required properties, invalid types or values, markup that does not match visible content, or policy violations — can make a page ineligible for those features. Diagnosis uses validators and Search Console's rich-result reports.
- Article structured data
Article structured data (Article, NewsArticle, BlogPosting from schema.org) marks up news, blog, and editorial pages so Google can better understand and present them, including in features like Top stories. This page covers the type choice, the properties Google recommends (headline, image, dates, author), and how to validate the markup with the Rich Results Test and Search Console.
- Breadcrumb structured data
Breadcrumb structured data uses schema.org BreadcrumbList to describe the trail of pages leading to the current page, helping Google show a breadcrumb path in search results instead of a plain URL. This page covers the ItemList structure, the position and item properties Google requires, multiple-trail handling, and validation.
- WebmasterID docs
Reference for how WebmasterID records crawler activity on your pages.
Sources and verification notes
- Google Search Central — FAQ (FAQPage) structured dataMarkup requirements and restricted eligibility.
- Google Search Central Blog — Changes to FAQ and HowTo rich results (Aug 2023)
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.