How a breadcrumb works
A breadcrumb is the short trail of links usually sitting just under the header: home, then the section, then the subsection, ending with the page you are on. Each step is a link except the last one, which is the current page and should be plain text so nobody clicks it expecting to move.
There are two ways to build one, and only one of them is a good idea. A hierarchy breadcrumb reflects where the page actually lives in the site’s structure and is identical for every visitor. A history breadcrumb reflects the route that particular visitor took to arrive. The second sounds helpful but produces a different trail on every visit, cannot be marked up meaningfully and confuses anyone who arrives directly from search — which, for most sites, is nearly everyone.
Adding BreadcrumbList schema alongside the visible trail lets a search engine read the same hierarchy. When it does, Google may show the trail in place of the raw URL in the result.
Why breadcrumbs matter
Most people do not enter through the homepage. They land deep inside the site from a search result or a shared link, with no idea what else is there. A breadcrumb answers the two questions that visitor has immediately: what kind of page is this, and what is the bigger category it belongs to. That second question is where a sale often starts, because the category page is where alternatives live.
It matters more on a phone, where the main navigation is folded behind a menu icon and nothing else on screen explains the site’s shape. A trail is a small, always-visible piece of orientation that costs almost no space. It also feeds internal linking, because every deep page ends up pointing back at its parent category with a descriptive anchor, which strengthens those category pages without anyone hand-building links.
Common mistakes with breadcrumbs
The trail that does not match reality is the worst of them. If the breadcrumb says one parent and the navigation and URL say another, you have taught both visitors and crawlers a contradiction. Pick one structure and let the breadcrumb express it.
Then there is the trail that starts and stops with the homepage, adding a step and no information. There is the one built only in markup and never shown to visitors, which is a structured data breach because the data must match visible content. And there is the version that uses a raw slug as the label — a step reading like a file path rather than a name people recognise helps nobody.
How to act on it
Decide the site’s real hierarchy first, since the breadcrumb only reports it. Keep the trail shallow, label each step in the words a customer would use, leave the current page unlinked, and wrap the whole thing in a navigation landmark with an ordered list so screen readers announce it correctly.
Add the matching markup once the visible trail is settled, not before, and check a sample of pages in the Rich Results Test. If the exercise exposes that pages sit in categories nobody would guess, that is a structure problem worth fixing properly as part of internal linking and on-page work rather than papering over with a trail.
