FAQPage schema is the Schema.org structured data type that labels a page's question-and-answer content so search engines and AI platforms can read each Q&A pair directly. It is one specific type within the broader schema markup vocabulary. Schema is not required to appear in AI features (per Google), but third-party research associates FAQPage schema with higher citation rates because each Q&A pair becomes a self-contained, extractable unit.
What is FAQPage schema?
FAQPage schema is a structured data type from the Schema.org vocabulary that marks up a page built around a list of questions and answers. Where schema markup broadly is the practice of labeling page content so machines can understand it, FAQPage is the specific type for one content shape: the FAQ. A page using it declares that it is a FAQPage, then labels each entry as a Question with an acceptedAnswer.
The type has been part of Schema.org since 2016 and saw wide adoption after Google introduced FAQ rich results in 2019 - the expandable Q&A dropdowns that once appeared under search listings. Its role has since shifted, but the markup itself is unchanged and more useful than ever for answer engine optimization.
How FAQPage schema works
FAQPage schema is almost always written as JSON-LD. A script block declares "@type": "FAQPage" with a mainEntity array. Each item in that array is a Question with two required properties: name holds the question text, and acceptedAnswer is itself an Answer object whose text property holds the answer.
The structure is deliberately flat: one FAQPage, many Questions, one acceptedAnswer each. Answer text can carry limited HTML such as links and lists, but the cleaner and more self-contained each answer is, the more reliably an AI engine can lift it as a direct answer.
Two rules govern valid FAQPage markup. First, the questions and answers must be visible on the page; schema that describes content a reader cannot see is a guidelines violation. Second, FAQPage is for content where the site itself provides the answer. It is not for forums or pages where users submit competing answers, which is what QAPage is for.
FAQPage vs QAPage vs HowTo
Three Schema.org types describe question-shaped content, and they are routinely confused. Choosing the wrong one is one of the most common FAQPage mistakes.
The fork that catches most marketers is FAQPage vs QAPage. If your team wrote the answers, it is a FAQPage. If your users did, it is a QAPage. Search engines treat the two differently, so the distinction is not cosmetic.
Why FAQPage schema matters for AI search
The FAQ is the content format AI answer engines were practically built to consume. A user query is a question; a FAQPage entry is a question with an answer already attached. There is almost no transformation between what the page provides and what the engine needs to cite.
The reported result: third-party research associates FAQPage schema with higher Gemini citation rates, the most-cited single-schema-type signal in published research. The broader schema signal shows up too - Ziptie.dev reports a 47% versus 28% Top-3 citation rate on Perplexity. Google notes schema is not required for AI features, so treat these as correlations - but FAQPage is the standout because it pre-packages content into the exact unit an engine retrieves: a self-contained question-answer pair. It is the same mechanism behind content chunking, except FAQPage does the chunking explicitly instead of leaving the engine to infer it.
How to implement FAQPage schema
- Write the FAQ as visible content first. The schema describes the page; it cannot stand in for a Q&A section a reader cannot see.
- Generate the JSON-LD. One
FAQPage, each Q&A as aQuestion/acceptedAnswerpair. Most content platforms have plugins for this, and hand-coding it is straightforward. - Validate with both tools. Run Google's Rich Results Test and the Schema Markup Validator before shipping.
- Confirm it is earning citations, not just validating. Schema that passes validation but sits on a page nothing cites is not doing its job. Use the AI Visibility Checker or the Quick Audit to see whether tagged pages are being pulled into AI answers.
A thorough AEO audit treats FAQPage coverage as one of its content-layer checks, alongside direct-answer placement and heading structure. Schema is one lever in that layer, not the whole layer.
Common misconceptions
FAQPage schema is dead because Google restricted FAQ rich results
The most damaging myth. In 2023 Google limited the visible FAQ rich result, the expandable dropdown in search listings, to well-known government and health sites. For a typical B2B site, FAQPage schema no longer produces that SERP dropdown. But the rich result was never the main value. The markup is still parsed by Google and, more importantly, by AI engines, and the higher-citation correlation third-party research reports for FAQPage comes from the post-restriction AI-search era. The value moved; it did not disappear.
Any list of questions can be marked up as FAQPage
Only content where the site itself provides the answers qualifies. User-generated Q&A is QAPage. Marketing copy disguised as questions ("Why is our product the best?") is a guidelines risk, not a FAQ. FAQPage is for genuine, useful answers a reader actually wants.
FAQPage schema replaces good FAQ content
Schema labels content; it does not improve it. A FAQ of thin, evasive answers marked up perfectly will still not get cited. The markup is a multiplier on answer quality, not a substitute for it. Write the answer a buyer needs first, then label it.
Frequently asked questions
#What is FAQPage schema in simple terms?
FAQPage schema is a snippet of code that labels the question-and-answer content on a page so search engines and AI platforms know exactly which text is a question and which is its answer. It is one specific type within the larger schema markup vocabulary, written in JSON-LD, and it is the format AI answer engines find easiest to cite because each entry is already a self-contained question and answer.
#Does FAQPage schema still work now that Google restricted FAQ rich results?
Yes. In 2023 Google limited the visible FAQ dropdown in search results to well-known government and health sites, so most sites no longer get that SERP feature. But FAQPage schema is still read by Google and by AI engines like Gemini, ChatGPT, and Perplexity. Third-party research associates FAQPage schema with higher AI citation rates in this current AI-search era (Google notes schema is not required to appear in AI features). The value shifted from SERP decoration to AI extraction; it did not disappear.
#What is the difference between FAQPage and QAPage schema?
FAQPage is for question-and-answer content where the site provides the answers, such as product FAQs, support pages, and glossaries. QAPage is for pages where users submit a question and the community supplies competing answers, like a forum thread. Search engines handle them differently, and tagging a normal FAQ as QAPage (or a forum as FAQPage) is a common and avoidable mistake.
#Where should I add FAQPage schema?
On any page with a genuine question-and-answer section: product and pricing FAQs, support and help articles, glossary entries, and the FAQ block at the bottom of blog posts and landing pages. The only requirement is that the questions and answers are visible to readers on the page, because schema cannot describe hidden content. Most pages have some FAQ content that qualifies even when the page is primarily something else.
#How do I validate FAQPage schema?
Use two free tools. Google's Rich Results Test (search.google.com/test/rich-results) checks whether the markup is valid for Google's FAQ handling, and the Schema Markup Validator (validator.schema.org) checks general Schema.org compliance. Run both before shipping. Validation only confirms the markup is correct, so also track whether the tagged pages are actually being cited in AI answers to know it is working.
