schema.org/BreadcrumbListRich result eligible
BreadcrumbList schema
The path from the site root to the current page.
Where to use it
Every page below the root.
A complete example
Valid as written, with every required property and the recommended ones that carry real information.
breadcrumb-list.json
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"@id": "https://www.seoforsolos.com/#breadcrumblist",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "First",
"item": "https://www.seoforsolos.com/first"
},
{
"@type": "ListItem",
"position": 2,
"name": "Second"
}
]
}Properties
| Property | Status |
|---|---|
itemListElement | Required |
The three mistakes this type attracts
- 01Giving the last item an item URL. It is the current page and must not carry one.
- 02Emitting breadcrumbs in schema with no matching visible navigation.
- 03Starting positions at 0 rather than 1.
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 BreadcrumbList schema type for?
The path from the site root to the current page. Use it on: every page below the root.
Which BreadcrumbList properties are required?
BreadcrumbList requires one property: itemListElement. It also recommends 0: .
Does BreadcrumbList produce a rich result?
BreadcrumbList 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 BreadcrumbList mistake?
The most common BreadcrumbList mistake is: Giving the last item an item URL. It is the current page and must not carry one.