Breadcrumb structured data
Breadcrumb structured data uses schema.org BreadcrumbList to describe the trail of pages leading to the current page, helping Google show a breadcrumb path in search results instead of a plain URL. This page covers the ItemList structure, the position and item properties Google requires, multiple-trail handling, and validation.
What this means
BreadcrumbList markup describes the sequence of pages from a top level down to the current page. Google can use it to render a breadcrumb trail in the search result, which clarifies where the page sits and can improve click context.
The markup is an ordered list of ListItem entries, each pointing to a page in the path with its position. It should mirror the breadcrumb a user sees on the page.
Required structure
Use schema.org BreadcrumbList with an itemListElement array of ListItem objects. Each ListItem needs a position (1-based, in order) and an item with a name and the URL (often via @id or item.@id). The last item is the current page.
Positions must be sequential starting at 1, and the trail should reflect a real navigational path. The breadcrumb names and order should match the visible breadcrumb on the page for consistency.
- Type: BreadcrumbList with itemListElement of ListItem
- Each ListItem: position (1-based) + item (name + URL)
- Positions sequential, last item is the current page
- Match the visible on-page breadcrumb
Multiple trails and validation
A page reachable by more than one path can have multiple BreadcrumbList objects, one per trail; Google may choose which to display. Keep each trail internally consistent.
Validate with the Rich Results Test and the Schema Markup Validator, and check Search Console's Breadcrumbs enhancement report for errors. Common problems are non-sequential positions, missing names or URLs, and trails that do not match the page. Fix the JSON-LD and re-test.
How it appears in analytics and logs
Breadcrumb markup tells Google the hierarchical path to a page. When valid and consistent with on-page breadcrumbs, Google may show a breadcrumb trail in the result. Invalid ordering or broken item references are reported as structured-data errors and can suppress the breadcrumb display.
Diagnostic use case
Add and validate BreadcrumbList markup so search results display your site hierarchy, improving result clarity and reflecting site structure.
What WebmasterID can help detect
WebmasterID confirms which crawlers fetched the page and the response. The breadcrumb trail also mirrors internal-link structure, so reachable, well-linked breadcrumb targets align with the crawl-discovery picture WebmasterID surfaces.
Common mistakes
- Using non-sequential or zero-based position values in the breadcrumb list.
- Omitting the name or URL on a ListItem's item.
- Markup breadcrumbs that do not match the visible on-page trail.
- Expecting a breadcrumb display even when the markup has validation errors.
Privacy and accuracy notes
Breadcrumb structured data describes site hierarchy, not visitors. WebmasterID records crawler fetches of the page as bot events only and stores no user data.
Frequently asked questions
- Can a page have more than one breadcrumb trail?
- Yes. If a page is reachable via multiple paths, you can include multiple BreadcrumbList objects, one per trail. Google may choose which trail to display in the result.
- Do breadcrumb positions have to start at 1?
- Yes. ListItem positions must be sequential and 1-based, in order from the top level down to the current page, which is the last item.
Related pages
- Diagnosing structured data errors
Structured data (schema.org markup, usually as JSON-LD) lets search engines understand a page and can make it eligible for rich results. Errors — missing required properties, invalid types or values, markup that does not match visible content, or policy violations — can make a page ineligible for those features. Diagnosis uses validators and Search Console's rich-result reports.
- Internal linking for crawl discovery
Internal links are how crawlers discover and reach pages within a site. Google primarily finds new URLs by following links, so pages with no incoming internal links become orphans that are hard to discover. This page explains crawl depth, link equity flow, and practical patterns — hub pages, breadcrumbs, related links, and crawlable HTML anchors — that keep important pages within easy reach of a crawl.
- Article structured data
Article structured data (Article, NewsArticle, BlogPosting from schema.org) marks up news, blog, and editorial pages so Google can better understand and present them, including in features like Top stories. This page covers the type choice, the properties Google recommends (headline, image, dates, author), and how to validate the markup with the Rich Results Test and Search Console.
- Website observability
Confirm crawlers reach the pages in your breadcrumb trails with a 200.
Sources and verification notes
- Google Search Central — Breadcrumb (BreadcrumbList) structured dataRequired properties and position ordering.
- schema.org — BreadcrumbList
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.