In short. QAPage structured data describes a page focused on one question and its answers, with Google eligibility rules for user-submitted responses.

Definition: QAPage structured data is machine-readable markup describing a page focused on one question and its answers. As of 17 October 2026, Google's QAPage documentation covers pages where users can submit answers, including forum threads and product support questions.

Key facts

Google's QAPage documentation requires a single Question nested in the page's mainEntity property.
Schema.org's Question definition distinguishes an acceptedAnswer from a suggestedAnswer and defines answerCount as the number of answers received.
Schema.org's Answer definition allows answers that are opinions or incorrect; the type itself makes no judgment about accuracy.
Google's general structured data guidelines require markup to represent content visible to readers.

Which pages fit Google's QAPage rules?

Google's content guidelines list forum and product support pages where users answer a single question. A business-written FAQ without alternative user answers, a how-to article, and a product page containing multiple questions fall outside this scope. Eligibility applies to individual qualifying pages within a forum.

The same documentation describes a separate education-related case: homework questions submitted by users may have a single answer supplied or selected by in-house experts.

What does the markup look like?

Google's property definitions require name and answerCount on the question and full text on each answer. Rich result eligibility, meaning eligibility for an enhanced search listing, requires at least one accepted or suggested answer.

This reduced JSON-LD example adapts Google's ounces-to-pounds example to a single accepted answer. JSON-LD is the JSON-based structured data format Google recommends in its general guidelines.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "QAPage",
  "mainEntity": {
    "@type": "Question",
    "name": "How many ounces are there in a pound?",
    "answerCount": 1,
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "1 pound (lb) is equal to 16 ounces (oz)."
    }
  }
}
</script>

The general guidelines require the question and answer represented by this markup to appear in the page's visible content.

How are accepted and suggested answers different?

Schema.org's Question vocabulary describes accepted answers as answers selected through a site's acceptance mechanism, which can reflect community opinion or the question author's view. Suggested answers are possible responses, including potentially incorrect ones.

Google's QAPage rules recognize acceptance by the question asker, a moderator, or a voting system. Sorting by recency alone cannot establish acceptance. Clarifications belong in comment with the Comment type. With paginated answers, answerCount records the total across pages.

How is an implementation checked?

Google's general guidelines name the Rich Results Test and URL Inspection tool for technical checks. They require the page to remain accessible to Googlebot and the markup to represent the page's main content. Automated tests catch most technical errors; quality rules also require editorial review, including checking for misleading or hidden content.

FAQ

Can I mark up an unanswered question?

Google's QAPage documentation permits answerCount set to 0. Your unanswered question remains ineligible for a QAPage rich result until it has an answer.

Does an accepted answer certify correctness?

Schema.org's Answer definition includes opinionated or wrong responses. Acceptance records the site's selection process; accuracy still requires a content judgment.

Is passing a technical test sufficient?

Google's general guidelines also require compliance with quality rules that automated tools cannot readily test. Check that your markup accurately represents visible content and follows the QAPage content rules.

Sources

Check how a page reads to answer engines. Open the GEO score analyzer