QAPage schema

Where to use it

Community question pages, single-question support pages.

A complete example

Valid as written, with every required property and the recommended ones that carry real information.

{
  "@context": "https://schema.org",
  "@type": "QAPage",
  "mainEntity": {
    "@type": "Question",
    "name": "How do I declare a canonical URL?",
    "answerCount": 1,
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Add a link rel=canonical element whose href is the authoritative URL for the page."
    }
  }
}

Generate a QAPage node with your own values in the schema generator, and lint what your page actually ships with the schema validator.

Properties

The three mistakes this type attracts

1. 01Using QAPage where FAQPage is correct: QAPage is for one question with user answers.
2. 02Marking up a page with no accepted or suggested answer.
3. 03Applying it to a FAQ block inside a larger page.

Related types

• Question
• Answer
• FAQPage
• CollectionPage
• SiteNavigationElement
• Article

Where this appears in the playbook

• Structured data: what each type is for and which ones earned their place.
• The schema graph: composing types into one graph with stable identifiers.
• One JSON-LD script per page, holding one @graph
• Stable @id anchors that cross-reference rather than duplicate
• Optional fields are omitted, never emitted as empty strings
• Does schema markup work? What 42 types on one site actually did: which of these types measurably did anything in production.