FAQ schema for AI citation: FAQPage vs QAPage explained
FAQ schema is one of the most direct ways to communicate structured facts to AI engines. When implemented correctly, it tells ChatGPT, Gemini, Perplexity and Copilot exactly what questions your page answers - and what the answers are. Here is the difference between the two schema types, which one to use, and how to add it to your site in under 10 minutes.
Key takeaway: Use FAQPage schema on any page that answers common questions. Use QAPage only on pages that are genuinely a single question-answer pair. Most websites should use FAQPage - it is simpler, more flexible, and directly supported by Google in search result rich snippets.
What is FAQ schema, and why does it matter for AI citation?
FAQ schema is structured data in JSON-LD format that you add to the <head> of a web page. It describes a set of question-and-answer pairs using schema.org vocabulary. When an AI engine crawls your page, it reads this markup and registers the Q&A content as machine-readable facts rather than prose to be interpreted.
The practical effect is significant. Pages with FAQ schema can appear as rich results in Google Search - those expandable FAQ panels you see beneath some search listings. More importantly for GEO, AI engines that ingest your page treat the schema-marked Q&A as authoritative statements. That makes them far more likely to cite those facts verbatim in response to user queries.
According to Google’s own documentation, FAQ schema is supported for both AMP and standard HTML pages, and Google may show FAQ rich results for any site that has at least one valid FAQ entry. For AI engines beyond Google, FAQ schema signals intent and structure that most large language models are trained to recognise and prioritise.
FAQPage vs QAPage: what is the actual difference?
This is where most people get confused. The two schema types look similar but serve different page structures.
- 1 FAQPage = many Q&As
- 1 QAPage = one Q&A
FAQPage is for pages with multiple questions and multiple answers. A typical FAQ page on a SaaS product site, a service page, or a blog post that addresses several related questions should use FAQPage. The schema contains an array of MainEntity items, each with a question and accepted answer.
QAPage is specifically for pages that consist of a single question and a single answer - think of a dedicated page built around one specific troubleshooting question. QAPage wraps a single Question and its AcceptedAnswer. If your page has more than one Q&A pair, you must not use QAPage - you must use FAQPage instead.
Google’s structured data testing guidelines explicitly state that using QAPage for a page with multiple questions is a validation error and will prevent the page from qualifying for rich results. If in doubt, FAQPage is almost always the correct choice.
Rule of thumb: If your page has an FAQ section with more than one question, use FAQPage. Only use QAPage for a dedicated single-question page with one definitive answer.
How to implement FAQPage schema in 5 steps
You do not need a developer to add FAQ schema. Follow these five steps and you will be done in under 10 minutes.
- Identify the questions your page answers. Look at your H2 headings, your actual FAQ section, and the queries you want to rank for. Each question should map to a distinct user intent.
- Write concise, complete answers. Each answer should fully address the question in 30-90 words. Do not reference the question or use vague language. State the answer directly.
- Generate the JSON-LD. Use the schema below as a template. Replace the questions, answers, and URLs with your own content.
- Add the JSON-LD to your page head. Place the script tag inside the
<head>section, before the closing</head>tag. Do not put it in the body. - Validate with Google’s Rich Results Test. Run your URL through Google’s Rich Results Test and confirm that FAQ is detected. Fix any errors before publishing.
FAQPage schema code example
Here is a complete, valid FAQPage JSON-LD block. Copy this, replace the content, and paste it into your page head.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is FAQ schema?",
"acceptedAnswer": {
"@type": "Answer",
"text": "FAQ schema is structured data in JSON-LD format that tells search engines and AI engines exactly what questions a page answers and what the answers are. It appears in the <head> of a webpage.",
"author": {
"@type": "Organization",
"name": "SearchScore"
}
}
},
{
"@type": "Question",
"name": "What is the difference between FAQPage and QAPage schema?",
"acceptedAnswer": {
"@type": "Answer",
"text": "FAQPage is for pages with multiple Q&A pairs. QAPage is for pages with exactly one question and one answer. Use FAQPage in most cases.",
"author": {
"@type": "Organization",
"name": "SearchScore"
}
}
},
{
"@type": "Question",
"name": "Does FAQ schema help AI engines cite my content?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. AI engines recognise FAQ schema as authoritative, machine-readable facts. Pages with FAQ schema are cited more frequently and more accurately by ChatGPT, Gemini, Perplexity and Copilot.",
"author": {
"@type": "Organization",
"name": "SearchScore"
}
}
}
]
}
</script>
Three common FAQ schema mistakes to avoid
Implementing FAQ schema is straightforward, but certain errors are remarkably common and will reduce or eliminate the benefit.
Mistake 1: Duplicating content across FAQPage and visible page content. Some tools generate FAQ schema that duplicates content already on the page. This is not a problem in itself, but Google may flag you for structured data that does not match visible content. Ensure your schema answers match what users can read on the page.
Mistake 2: Using QAPage when you should use FAQPage. We see this constantly. A page with four FAQ items but QAPage markup will fail validation and may be treated as deceptive markup. Always use FAQPage for multiple questions.
Mistake 3: Marking up promotional content as questions. Your FAQs should be genuine informational questions a user might ask, not marketing statements phrased as questions. AI engines are particularly sensitive to this. The questions should sound like things a person would actually type into a search bar or ask an AI assistant.
Why FAQ schema specifically helps AI citation
AI engines do not read web pages the way humans do. They process tokens - chunks of text that represent meaning. When an AI model encounters FAQ schema, it receives the Q&A pairs in a highly structured format that maps cleanly to its training data patterns. The question-answer pairing is one of the most statistically significant patterns in how large language models represent knowledge.
When an AI engine is formulating a response to a user question, it searches its citation database for pages that have a close question match. A page with FAQ schema explicitly listing that question has a structural advantage over prose that might mention the topic but not frame it as a Q&A. The schema provides a direct signal: this is a question, this is the answer, and this organisation stands behind it.
The citation mechanism also works through entity recognition. Each question in FAQ schema is tagged with an accepted answer that names entities, dates, figures, and processes. These precise factual assertions are more likely to be retrieved as citations because they contain verifiable data points that can be traced back to the source.
Monitoring and maintaining your FAQ schema
FAQ schema is not a one-time setup. As your content evolves, your schema must evolve with it. Review and update your FAQPage entries at least quarterly, or whenever you publish significant new content that changes the questions your page answers.
Use Google Search Console to monitor your FAQ rich result performance. In the Enhancements section, Google reports how many of your pages have valid FAQ structured data and how many impressions the rich results have generated. If you see errors, address them promptly - a validation error on FAQ schema can affect how Google treats your page overall.
Frequently asked questions
Can I use FAQ schema on a page that also has other structured data?
Yes. A page can have multiple schema types simultaneously. Common combinations include Article schema plus FAQPage, or Product schema plus FAQPage. Just ensure each JSON-LD block is complete and valid on its own, and that they do not conflict with each other.
How many questions should I include in FAQPage schema?
Include as many questions as are genuinely relevant to the page topic. There is no upper limit defined by the schema spec, but Google’s rich results guidelines cap the visible FAQ panel at 10 items for regular pages and 30 for HowTo pages. As a practical guide, include the questions that represent the most common user queries for that topic - typically 4 to 10.
Does FAQ schema work for local business pages?
Yes. Local business pages commonly use FAQPage to address questions about opening hours, service areas, booking processes, and parking. Combine FAQPage with LocalBusiness schema for maximum benefit on local intent queries.
What happens if my FAQ schema fails validation?
A validation failure means Google will not show your FAQ rich results, but it does not automatically penalise your page. However, invalid structured data can signal low-quality markup to AI engines, so it is worth fixing. Use Google’s Rich Results Test to identify the specific error and correct it.
Is FAQ schema only for Google?
No. While Google is the most well-documented user of FAQ schema for rich results, the schema is defined by Schema.org and is part of the open structured data ecosystem. AI engines including ChatGPT, Perplexity, and Bing Copilot all have documentation confirming they read and prioritise schema.org structured data when formulating citations.
Part of Content Method — see all guides in this series →