schema.org/AnswerNo rich result
Answer schema
An answer to a Question, carrying the answer text exactly as the page renders it.
Where to use it
Nested inside Question.
A complete example
Valid as written, with every required property and the recommended ones that carry real information.
answer.json
{
"@context": "https://schema.org",
"@type": "Answer",
"text": "A self-contained answer that restates its own subject.",
"url": "https://www.seoforsolos.com/example",
"upvoteCount": 12,
"author": {
"@type": "Person",
"name": "A Real Person",
"url": "https://www.seoforsolos.com/about"
}
}Properties
| Property | Status |
|---|---|
text | Required |
url | Recommended |
upvoteCount | Recommended |
author | Recommended |
The three mistakes this type attracts
- 01Truncating the answer in schema while showing the full text on the page.
- 02Omitting text in favour of a URL alone.
- 03Marking a paraphrase rather than the answer as rendered.
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 Answer schema type for?
An answer to a Question, carrying the answer text exactly as the page renders it. Use it on: nested inside Question.
Which Answer properties are required?
Answer requires one property: text. It also recommends 3: url, upvoteCount, author.
Does Answer produce a rich result?
Answer does not produce a Google rich result. It is still worth shipping, because its value is entity resolution and answer extraction rather than search result presentation.
What is the most common Answer mistake?
The most common Answer mistake is: Truncating the answer in schema while showing the full text on the page.