GitHubDownload ZIP
301 chain301 chain
Permanent redirects stacked one after another.
Found by Redirect checker →
302302
A temporary redirect on a page that moved for good.
Found by Redirect checker →
SchemaUpdated

BreadcrumbList Schema: breadcrumb markup

In short

BreadcrumbList is Schema.org markup that describes a page’s navigational path so eligible Google results can show contextual hierarchy rather than only a URL.

BreadcrumbList is structured data for a visible breadcrumb trail: the navigational route that puts the current page in context. It is not a substitute for site architecture, internal links, or a canonical URL. It describes a path that a visitor can also understand and use. Google can use eligible markup to present a contextual hierarchy in a result, but the appearance remains Google’s decision and varies by surface.

Model the trail as an ordered sequence of real navigation choices. A product or article can have more than one meaningful route, and Google’s documentation allows multiple breadcrumb trails for the same page. The useful choice is the path shown to a person for the context in which that page is reached—not a manufactured chain of keyword labels.

Illustrative diagram: a visible hierarchy and its structured-data representation should describe the same path.
Breadcrumb markup can make a page eligible for a breadcrumb presentation; it does not guarantee a rich result or cause a ranking change.

Start with the rendered page, not a spreadsheet of URLs. Record the visible label and destination of every crumb, then decide whether the current page is included as the final ListItem. Use absolute URLs for destinations. Keep positions consecutive from 1 and keep names concise, human-readable, and consistent with the page UI. Do not mark up a hierarchy that does not exist on the page.

json
{\n  "@context": "https://schema.org",\n  "@type": "BreadcrumbList",\n  "itemListElement": [\n    {"@type":"ListItem","position":1,"name":"Home","item":"https://example.com/"},\n    {"@type":"ListItem","position":2,"name":"Guides","item":"https://example.com/guides/"},\n    {"@type":"ListItem","position":3,"name":"Technical SEO","item":"https://example.com/guides/technical-seo/"}\n  ]\n}

Generate this JSON-LD from the same data that renders the breadcrumb component where possible. That avoids the common drift in which a renamed category is updated in the UI but remains stale in markup. A CMS template should emit no BreadcrumbList where the page has no useful trail, such as a shallow homepage.

  1. Inspect the rendered trail on a representative page and confirm every destination resolves to the intended canonical URL.
  2. Compare the DOM, JSON-LD, and information architecture: labels, order, and paths should agree.
  3. Run Google’s Rich Results Test, then use URL Inspection after release to confirm Google can fetch the page without authentication, robots blocking, or noindex.
  4. Check Search Console’s breadcrumb enhancement report after recrawling, and sample templates rather than assuming one valid URL covers every template.

Treat validation as a syntax and accessibility check, not as evidence that the result will show breadcrumbs. Google explicitly recommends deploying a few representative pages, checking how Google sees them, and allowing time for recrawling. A change to a taxonomy needs a repeat pass because it can affect hundreds of trails at once.

Do not claim that BreadcrumbList improves CTR or rankings by itself. Measure any search-performance change against the query set and other simultaneous changes.

For a practical regression check, sample one URL from each breadcrumb template after every navigation or taxonomy release. Compare the rendered labels, JSON-LD sequence, canonical destination, and HTTP response. This small routine catches template drift before it becomes a broad enhancement-report problem.

Keep the record of that check with the release notes: URL sampled, template, result, and the follow-up if any. It makes a later Search Console warning actionable without turning a markup feature into an untestable SEO claim.

FAQ

Only pages with a meaningful visible breadcrumb trail need it. The markup should describe navigation that exists for users, not add an artificial hierarchy to every template.
Yes. Google documents multiple breadcrumb trails for a page when people can reach the content through different useful hierarchies. Each trail must be coherent and accurate.
No. It confirms that Google can understand eligible markup. Google decides whether and how to show a search feature for a particular result.
A final ListItem can identify the current page. Keep the sequence and labels consistent with the visible trail; avoid inventing a self-link merely to satisfy a convention.