QAPage

Minimal valid version

The smallest markup that still produces a valid QAPage entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "QAPage",
  "mainEntity": {
    "@type": "Question",
    "name": "Why does XooStructured show a validation error on nested @id references?",
    "answerCount": 3,
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "XooStructured flags circular @id chains. Reference the PostalAddress directly from both blocks instead of chaining through Organization."
    }
  }
}
</script>

Google rich results this unlocks

Markup matching this example makes your page eligible for the following Google Search rich results. The primary target drives the required / recommended property classification in the advanced code block above.

• Q&A rich resultprimary

  Google docs

Common QAPage mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

1. 01

   Using QAPage for editorially controlled FAQ content

   Wrong

   QAPage markup on a company FAQ page where the site owner writes all questions and answers

   Right

   FAQPage for editorial Q&A, QAPage for community/user-generated Q&A

   Google enforces the distinction. QAPage is for pages where users submit questions and other users answer them. FAQPage is for pages where the site owner controls both sides. Using QAPage on a company FAQ may trigger a manual action because the content does not match the expected pattern.

2. 02

   Multiple questions on a QAPage

   Wrong

   QAPage with mainEntity as an array of multiple Question objects

   Right

   QAPage with a single Question as mainEntity; use FAQPage for multiple Q&A pairs

   QAPage represents a single-question thread. One question, one or more answers. If the page has multiple questions (like a FAQ), use FAQPage instead. Putting multiple questions in a QAPage confuses the rich result and Google may ignore the markup.

3. 03

   answerCount that doesn't match reality

   Wrong

   "answerCount": 2 when the page shows 3 answers

   Right

   "answerCount": 3 (matches the actual number of answers on the page)

   Google cross-checks answerCount against the visible page content. A mismatch signals that the structured data does not reflect the page, which can result in the rich result being suppressed. Report the real count.

4. 04

   Omitting upvoteCount on answers

   Wrong

   Answer objects with text and author but no upvoteCount

   Right

   Each Answer with "upvoteCount": 18 (the real community vote score)

   When no acceptedAnswer exists, Google uses upvoteCount to pick the best suggestedAnswer for the rich result snippet. Without vote counts, Google has no ranking signal and may display a random answer or skip the rich result entirely.

5. 05

   acceptedAnswer and suggestedAnswer on the same answer

   Wrong

   The same Answer object listed as both acceptedAnswer and in the suggestedAnswer array

   Right

   The accepted answer appears only in acceptedAnswer; other answers go in suggestedAnswer

   An answer is either accepted or suggested, not both. Duplicating it in both properties creates a confusing signal. If the question has an accepted answer, put it in acceptedAnswer and all other answers in suggestedAnswer.

Schema properties in this example