FAQPage schema
A page of questions and answers, marked up so each question and its accepted answer are machine-readable.
Where to use it
Pages with a genuine FAQ, visible on the page. FAQ page schema and FAQPage are the same type: schema.org spells it as one word.
A complete example
Valid as written, with every required property and the recommended ones that carry real information.
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What does FAQPage markup do?",
"acceptedAnswer": {
"@type": "Answer",
"text": "FAQPage markup makes each visible question and its accepted answer machine-readable."
}
},
{
"@type": "Question",
"name": "Does FAQPage still produce a rich result?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Google has shown FAQ rich results only for authoritative government and health sites since August 2023."
}
}
]
}Generate a FAQPage node with your own values in the schema generator, and lint what your page actually ships with the schema validator.
Properties
| Property | Status |
|---|---|
mainEntity | Required |
The three mistakes this type attracts
- 01Marking up questions that are not visible in the rendered HTML. This is a documented manual action trigger.
- 02Adding a FAQ to every page regardless of relevance.
- 03Question items missing their nested requirements: each Question needs a name and an acceptedAnswer whose Answer carries text.
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
- Does schema markup work? What 42 types on one site actually did: which of these types measurably did anything in production.
Questions
What is the FAQPage schema type for?
A page of questions and answers, marked up so each question and its accepted answer are machine-readable. Use it on: pages with a genuine FAQ, visible on the page. FAQ page schema and FAQPage are the same type: schema.org spells it as one word.
Which FAQPage properties are required?
FAQPage requires one property: mainEntity.
Does FAQPage produce a rich result?
Google has shown FAQ rich results only for authoritative government and health sites since August 2023, so FAQPage markup on a SaaS site earns answer extraction, not a rich result.
What is the most common FAQPage mistake?
The most common FAQPage mistake is: Marking up questions that are not visible in the rendered HTML. This is a documented manual action trigger.
What does each Question inside FAQPage require?
Each Question inside FAQPage requires a name carrying the question text and an acceptedAnswer of type Answer whose text property carries the answer exactly as the page renders it. mainEntity as anything other than an array of Question items fails validation.