Breadcrumb schema generator. JSON-LD trail.
Add your breadcrumb sequence (Home → Category → Page). The generator outputs a valid BreadcrumbList with auto-numbered position fields. The most-rendered rich-result for non-restricted sites since 2024.
Add the breadcrumb sequence (top crumb = Home, bottom = current page). The right panel renders BreadcrumbList JSON-LD live with auto-numbered positions. The most-rendered rich result for commercial sites in 2026.
Sources used by this generator
- schema.org/BreadcrumbList · /ListItem
- Google breadcrumb rich-result spec
- The one rich result that survived the 2023 / 2024 restrictions — still rendered for all commercial sites.
Privacy: form runs in-browser only.
The one rich result commercial sites still get.
FAQ rich results restricted in August 2023. HowTo deprecated September 2023. AggregateRating on self-serving Service / Organization schema unrendered since 2019. The list of rich results commercial sites can rely on shrunk dramatically — but BreadcrumbList survived.
Breadcrumb is the one rich result Google still renders reliably for non-restricted domains in 2026. It replaces the URL slug under your title in SERP listings with a clean Home › Category › Page trail. On mobile, where the URL line is hardest to read, the named breadcrumb is the scannable replacement that lifts CTR by 3-7 percentage points on category-deep pages.
Cost-benefit: 200 bytes of JSON-LD per page. Most pages already have a visible breadcrumb in the page header — the schema just makes it machine-readable. Add it to every page that's deeper than two clicks from the homepage.
Position numbers are 1-indexed and sequential. Position 1 is closest to root (Home). Highest position is the current page. Don't skip numbers; don't start at 0. The generator auto-numbers as you add crumbs, so you can't get this wrong.
Six questions users ask.
Why is breadcrumb schema worth shipping?
Breadcrumb is the one rich result Google still renders reliably for commercial sites in 2026. It replaces the URL slug under your title in SERP listings with a clean Home > Category > Page trail, which lifts CTR 3-7 percentage points on category-deep pages.
What positions should I use?
Position numbers are 1-indexed and sequential. Position 1 is the breadcrumb closest to root (usually Home). The deepest level — the current page — is the highest position number. The generator auto-numbers as you add crumbs.
Should the last crumb include a URL?
Best practice: yes, but it's optional. Schema.org accepts ListItem with or without an item URL on the final crumb. We include the URL for consistency since it adds zero risk.
Do I include 'Home' as the first crumb?
Yes. The home page should always be position 1. Use whatever name matches the visible breadcrumb on your page.
How does this affect mobile SERPs?
On mobile, breadcrumbs replace the URL line entirely with the named breadcrumb sequence. Mobile is where the CTR lift comes from.
Does this tool log my breadcrumbs?
No. The form runs entirely in JavaScript on your device. Nothing is sent to Digital Heroes servers.
Three mistakes we see most.
Breadcrumb rich results are the one schema type that still earns visible SERP real estate for commercial sites in 2026, yet roughly half of the BreadcrumbList markup we audit fails Google's Rich Results Test. The failure mode is almost always a mismatch between visible HTML and the schema graph, not a syntax error in the JSON-LD.
Mistake 1, schema name does not match visible breadcrumb text: the schema.org BreadcrumbList spec defines each ListItem with a name that is supposed to mirror the human-readable label the user actually sees. Teams generate breadcrumbs from URL slugs ("running-shoes") in the schema while the visible breadcrumb shows "Running Shoes". Google flags this as a structured-data warning and may suppress the rich result entirely. Always render the same string the user reads, not the slug.
Mistake 2, missing position 1 root: position 1 should be Home (the site root), not the section. Teams skip the root because the visible breadcrumb on category pages reads "Shop > Running > Shoes" with no Home crumb. Google's breadcrumb structured-data docs require the full chain from root. Without position 1 the entire BreadcrumbList may be ignored, costing you the rich result on the page that needed it most.
Mistake 3, using URL paths as the name: some teams populate name with the full URL ("/category/running-shoes/") because their CMS only exposes the slug. Google's docs are explicit: name is a human label, item is the URL. Confusing the two trips a "Field 'name' is invalid" warning. The generator on this page enforces the split automatically, so if you are hand-rolling, use it as a reference.
When to actually use this: generate fresh markup whenever you ship a new template that introduces a new path depth (product variant, sub-category, regional storefront), after any IA restructure, and during quarterly schema audits. Pair with our SEO service if you are running multi-locale or large taxonomy stores where breadcrumb consistency at scale is the work.
Related Digital Heroes services + reading: See our SEO service for production-grade schema architecture, plus our Schema Markup Generator and Article Schema Generator. Sibling tools: Structured Data Validator and FAQ Schema Generator.
Schema cluster.
Published · Last updated .