schema.org/QAPageRich result eligible
QAPage schema
A page built around one question and its answers.
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.
qa-page.json
{
"@context": "https://schema.org",
"@type": "QAPage",
"mainEntity": {
"@type": "Person",
"name": "A Real Person",
"url": "https://www.seoforsolos.com/about"
}
}Properties
| Property | Status |
|---|---|
mainEntity | Required |
The three mistakes this type attracts
- 01Using QAPage where FAQPage is correct: QAPage is for one question with user answers.
- 02Marking up a page with no accepted or suggested answer.
- 03Applying it to a FAQ block inside a larger page.
Related types
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
Questions
What is the QAPage schema type for?
A page built around one question and its answers. Use it on: community question pages, single-question support pages.
Which QAPage properties are required?
QAPage requires one property: mainEntity. It also recommends 0: .
Does QAPage produce a rich result?
QAPage is eligible for a Google rich result when its required properties are present and valid. A validation error therefore has a visible cost in the search result itself.
What is the most common QAPage mistake?
The most common QAPage mistake is: Using QAPage where FAQPage is correct: QAPage is for one question with user answers.