FAQPage vs QAPage schema: what each type is for

FAQPage and QAPage are Schema.org types for describing question-and-answer content. They can make page meaning more explicit to machines, but Google stopped showing FAQ rich results in May 2026 and there is no controlled evidence that FAQPage markup itself increases AI citation. Here is when each type is appropriate and how to implement it accurately.

Key takeaway: Use FAQPage only where the visible page genuinely contains multiple FAQs. Use QAPage for a page centred on one question with answers from users or experts. FAQPage remains valid Schema.org vocabulary, but Google stopped showing FAQ rich results in May 2026 and the markup should not be sold as a direct AI-citation tactic.

What is FAQ schema, and what does it actually do?

FAQ schema is structured data, commonly published as JSON-LD, that describes question-and-answer content using Schema.org vocabulary. It gives compatible parsers an explicit representation of the questions and answers already visible on the page.

The important distinction is between machine-readable semantics and a ranking or citation effect. Structured data can help systems interpret page meaning, but that does not prove a direct increase in AI citations. Google deprecated FAQ rich results on 7 May 2026 and removed its FAQ rich-result documentation in June, so FAQPage should no longer be implemented for the promise of expandable Google FAQ panels.

FAQPage remains a valid Schema.org type even though Google no longer offers the FAQ rich-result feature. Use it when it accurately describes visible FAQ content and when a consumer of Schema.org data may benefit from the explicit structure. Do not claim that ChatGPT, Gemini, Claude or Perplexity prioritise pages because FAQPage markup is present unless provider documentation or controlled evidence establishes that effect.

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.

QAPage and FAQPage describe different content models. QAPage is for a page focused on one question where users can submit answers; FAQPage is for a list of questions and answers supplied by the site. The markup should match the visible page rather than being chosen for a hoped-for search feature.

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 the Schema.org markup. Use Schema.org Validator to check the JSON-LD structure, then verify that every marked-up question and answer is actually visible on the page. Google’s Rich Results Test no longer provides an FAQ rich-result target because Google retired that feature in 2026.

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 Schema.org structured data that describes question-and-answer content already visible on a webpage. It can make the content easier for compatible parsers to interpret, but it does not guarantee rankings, rich results or AI citations.",
        "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": "There is no controlled evidence that FAQPage markup by itself increases AI citations. Its defensible benefit is semantic clarity for systems that consume Schema.org data; the visible answer quality, crawlability and source authority still matter independently.",
        "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.

What FAQ schema can and cannot do for AI search

FAQPage makes the relationship between a question and its answer explicit in a standard machine-readable format. That can reduce ambiguity for systems that parse Schema.org data, which is a legitimate implementation benefit.

What we should not infer is a direct citation advantage. Answer engines use different retrieval systems and do not publish a universal rule that FAQPage markup increases selection. Clear visible answers, crawlability, relevance and source credibility should be treated separately from the presence of schema.

The safest reason to use FAQPage is therefore accuracy and semantic clarity: when the page genuinely contains FAQs, mark them up faithfully. Do not add FAQ schema to manufacture an AI-search signal or to mark up content users cannot see.

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.

Do not expect an FAQ rich-result report in Google Search Console: Google retired the feature in 2026. Validate the markup itself, monitor the page normally in Search Console, and review the schema whenever the visible FAQ content changes.

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 only questions that are genuinely relevant and visibly answered on the page. Schema.org does not impose a Google FAQ-panel limit because Google no longer shows that rich-result feature. Keep the markup aligned with the content rather than adding questions to hit a target count.

Does FAQ schema work for local business pages?

Yes, if the page visibly contains genuine FAQs. FAQPage can sit alongside LocalBusiness schema when both accurately describe the content, but there is no basis for promising a ranking or AI-citation boost from that combination.

What happens if my FAQ schema fails validation?

A validation failure means the structured data is malformed or does not conform to the vocabulary you intended to use. It does not create an FAQ rich-result issue because Google no longer offers that feature. Use Schema.org Validator, correct the markup, and make sure it matches the visible content.

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.

Continue Reading

Part of Content Method - see all guides in this series →