Most of what a crawler knows about your site hierarchy, it infers. It guesses from URL segments, from which pages link to which, from menu position. Breadcrumbs are the one place where a site states its hierarchy outright — this page lives here, under this, under this — and that statement is read by users, by search engines, and by any tool building an information architecture document from your site.
For the effort involved, nothing else in IA pays back as well.
Three audiences, one component
Users get orientation. Someone arriving from search on a deep product page has no idea where they are; a breadcrumb answers that in one line and offers an immediate way up a level. Users who arrive from search rarely use the global navigation first — they use the breadcrumb.
Search engines get an explicit hierarchy signal, and with BreadcrumbList markup they will frequently replace the raw URL in the search result with the breadcrumb path. example.com › Dresses › Silk reads better than example.com/collections/dresses/silk-2024-ss.
Crawlers and analysis tools get ground truth. When our own DeepAnalyzer builds an IA sheet, a page with breadcrumbs is classified with high confidence from the site's own labels; a page without them has to be inferred from URL shape and navigation position — which works, but is a reconstruction rather than a reading.
What a good breadcrumb looks like
Home › Solutions › Thermal Systems › Heat Pump Modules
Rules that matter in practice:
- Show the full path from the root. A truncated breadcrumb starting at the current section is much less useful.
- Every ancestor is a link; the current page is not. The last item is plain text.
- Labels match the destination page. If the breadcrumb says "Solutions" and the page's H1 says "Our Technologies", you have two names for one node, which confuses users and analysis tools alike.
- Reflect hierarchy, not history. A breadcrumb is not a back button. Showing the path the user happened to take produces a different breadcrumb for the same page on every visit, which destroys the signal.
- Place it above the H1, left-aligned, below the global navigation. This is where people look.
- Keep it on mobile. Truncate the middle with an ellipsis if space is tight, but never drop it — mobile is where orientation matters most.
Markup
Semantic HTML first:
<nav aria-label="Breadcrumb">
<ol>
<li><a href="/">Home</a></li>
<li><a href="/solutions">Solutions</a></li>
<li><a href="/solutions/thermal">Thermal Systems</a></li>
<li><span aria-current="page">Heat Pump Modules</span></li>
</ol>
</nav>
Then the structured data:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/" },
{ "@type": "ListItem", "position": 2, "name": "Solutions", "item": "https://example.com/solutions" },
{ "@type": "ListItem", "position": 3, "name": "Thermal Systems", "item": "https://example.com/solutions/thermal" },
{ "@type": "ListItem", "position": 4, "name": "Heat Pump Modules", "item": "https://example.com/solutions/thermal/heat-pump-modules" }
]
}
</script>
Two things to get right: position starts at 1 and increments without gaps, and the visible breadcrumb must match the markup. Structured data that describes a hierarchy the page does not display is a mismatch, and it is the kind of mismatch that gets rich results suppressed.
The final item may include item or omit it; including the current URL is the safer, more consistent choice. See the structured data guide for how this fits with the rest of your schema graph.
Hard cases
A page with several parents. A product in three categories is the classic problem. Options:
- Assign one primary category per product and always show that path. Simplest, most consistent, and what we recommend by default.
- Show the path matching the referrer's category. Better UX, but the breadcrumb becomes variable, which weakens it as a structural signal — and if you do this, the structured data should still describe the canonical path.
Faceted results. Dresses › Black › Under ₩100,000 is a filter state, not a hierarchy node. Keep the breadcrumb at the category level and let the filter UI show the active filters separately.
Flat sites. With two levels, a breadcrumb adds little. Add it when you have three or more levels, or when you have deep content arriving from search.
Locale segments. /ko/solutions/thermal should show 홈 › 솔루션 › 열관리 시스템, not a "KO" node. The locale is a dimension of the site, not a level of the hierarchy.
Using breadcrumbs as an IA audit
Because a breadcrumb is a declared hierarchy, crawling them across a site gives you the site's structure as the site understands it. That is useful in two ways.
First, as a consistency check: crawl every page and compare the breadcrumb path against the URL path and the navigation position. Where those three disagree, you have an IA defect — a page filed in one place, addressed in another, and linked from a third. Users feel that as "I can never find this again."
Second, as a starting point for the IA document. Depth 1 / Depth 2 / Depth 3 columns in an IA sheet map directly onto breadcrumb levels, and screen IDs follow from the depth grouping (screen ID conventions covers the naming side). A site with complete breadcrumbs can produce a first-draft IA sheet automatically; a site without them requires interpretation at every row.
Before you add them
A breadcrumb exposes your hierarchy. If the hierarchy is bad, the breadcrumb makes that visible rather than fixing it — a path like Home › Products › Products2 › New Folder is an honest reflection of a structural problem. Fix the structure first, then declare it. Analysing your information architecture is the step before this one.
FAQ
Do breadcrumbs affect rankings?
Not as a direct ranking factor. They improve internal linking and crawl paths, they can replace the URL in search results with a more readable path, and they reduce bounce from deep landings. The measurable effects are indirect but real.
Should the breadcrumb include the current page?
Yes, as the final, non-linked item. It confirms to the user where they are. Include it in the structured data too.
What if my URLs don't match my breadcrumb?
That is a signal worth investigating, not something to paper over. URL structure and breadcrumb should normally describe the same hierarchy. Where they cannot — a flat product URL under a category breadcrumb, for example — make sure the breadcrumb reflects the conceptual structure, because that is what users and search results see.
Can I use breadcrumbs instead of a sitemap?
No. They serve different purposes: breadcrumbs declare hierarchy for a page, a sitemap enumerates URLs for discovery. Use both.
How many levels is too many?
More than four or five usually indicates the hierarchy is too deep. Deep paths mean more clicks from the homepage and weaker crawl priority, as covered in crawl budget optimization.