What you need to know
Use BreadcrumbList with itemListElement containing ordered ListItem nodes. Each ListItem needs position and name; item is normally the canonical URL for that level. Build the trail from the logical site hierarchy, not raw filesystem or routing folders, and avoid a one-item breadcrumb that contains only Home.
BreadcrumbList models page hierarchy. itemListElement is an ordered list of ListItem. position starts at 1. name is the visible label. item is the canonical URL for that hierarchy level. Visible breadcrumbs and JSON-LD should describe the same path.
Key properties
The table below summarizes the fields that most often determine whether the entity is clear and internally consistent. Only provide values supported by the page.
| Property | Importance | How to use it |
|---|---|---|
itemListElement | Required | Ordered breadcrumb ListItem nodes. |
position | Required | Order starting at 1. |
name | Required | Human-readable level label. |
item | Recommended | Canonical URL for the level. |
What BreadcrumbList communicates
Breadcrumbs describe hierarchy, not merely URL syntax. A short URL can still sit under Home → Guides → Product Schema.
Build from information architecture
Do not automatically split every URL segment. Hidden technical folders, route internals and tracking parameters are not meaningful navigation.
ListItem order
Each level is a ListItem. position should start at 1 and increase consistently. name should match a meaningful visible navigation label.
The final item
The last item normally represents the current page. A trail containing only Home communicates almost no hierarchy.
Multiple paths
Some pages genuinely belong to multiple hierarchies. Google documents multiple breadcrumb trails, but only use them when they are meaningful to users.
Visible breadcrumbs
Structured breadcrumbs should correspond to a path users can understand. Search engines may still choose a different presentation.
Maintenance
When a section moves, update visible breadcrumbs, canonical URLs and BreadcrumbList together.
JSON-LD examples
Three-level BreadcrumbList
A guide inside a Guides section.
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://example.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Guides",
"item": "https://example.com/guides/"
},
{
"@type": "ListItem",
"position": 3,
"name": "Product Schema",
"item": "https://example.com/guides/product-schema/"
}
]
}Google, Bing and Yandex
Google documents BreadcrumbList for search-result breadcrumb presentation and page-context categorization.
Bing supports Schema.org JSON-LD and can use hierarchy annotations to understand page context.
Schema.org support varies by feature; breadcrumb markup should still represent real navigation rather than an artificial SEO path.
Important: valid structured data does not guarantee a rich result. Each search engine decides whether to use the data and how to present it.
Common mistakes
- warningBuilding breadcrumbs from filesystem folders.
- warningUsing only Home.
- warningDuplicate position values.
- warningRaw slugs instead of readable labels.
- warningBroken intermediate item URLs.
Frequently asked questions
Should breadcrumbs match the URL path?
Not necessarily. They should match logical site hierarchy.
Can I have multiple breadcrumb trails?
Yes, when the page genuinely belongs to multiple useful hierarchies.
Do breadcrumbs directly improve rankings?
No. They communicate hierarchy and can affect presentation, but are not a direct ranking shortcut.