Breadcrumbs
Breadcrumbs are the navigational trail showing a page's position in a site hierarchy (Home > Category > Subcategory > Page). When marked up with BreadcrumbList schema, Google replaces the raw URL in the SERP with the breadcrumb path — a clearer, more clickable result for users.
Long definition
Breadcrumbs do three jobs. As UI, they orient users on deep pages — "you are here, and here is the path back". As an internal-linking pattern, they distribute link equity from leaf pages back up to category and parent hubs. As structured data, they tell Google how the site is organized so the SERP can show the path instead of the URL.
The structured-data part is where breadcrumbs become a SEO feature, not just UX. Google reads BreadcrumbList JSON-LD and, when valid, replaces the URL display in the SERP with the breadcrumb trail. "example.com › electronics › phones › pixel-9-review" reads better than the bare URL and signals topical context before the click.
Implementation has two halves that must agree:
- Visible breadcrumbs in HTML. A
<nav aria-label="breadcrumb">containing an ordered list of links. Each link goes to a real, indexable page in the hierarchy. BreadcrumbListJSON-LD in the<head>mirroring exactly the visible trail. EachListItemcarriesposition,name, anditem(the URL).
Mismatch between the two — schema declaring a path the user cannot actually navigate — is one of the top reasons rich results disappear or trigger manual actions for "structured data mismatch".
For category-heavy sites (ecommerce, news, large blogs), breadcrumbs are the cheapest single-action improvement to internal linking and SERP appearance. A PLP that has no breadcrumb up to its category sheds equity at every leaf page.
Common misconceptions
- "Breadcrumbs need a separate schema page-by-page." They need page-by-page JSON-LD because the trail differs per page, but the implementation is templated — the CMS generates the trail from the URL or category tree.
- "Breadcrumbs replace the URL on every result." Google chooses when to render the breadcrumb display. Mobile and desktop rendering differs, and Google may fall back to the URL for low-confidence matches or schema errors.
- "Home > breadcrumb is fine on the homepage." Don't render breadcrumbs on the page they would resolve to alone. A homepage breadcrumb of "Home" is structural noise and Google may ignore the markup.
- "BreadcrumbList works without visible breadcrumbs." Google's rich-result policies require the structured data to match what's visible. Schema-only breadcrumbs are flagged as misleading markup.
Continue exploring