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.
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": "Person",
"name": "A Real Person",
"url": "https://www.seoforsolos.com/about"
}
}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.
- 03An empty mainEntity array, which is a validation error.
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 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.
Which FAQPage properties are required?
FAQPage requires one property: mainEntity. It also recommends 0: .
Does FAQPage produce a rich result?
FAQPage 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 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.