Breadcrumbs (Navigation)
Breadcrumbs (Navigation) is the secondary navigation aid that shows visitors where the current page sits in a site’s hierarchy - usually as a horizontal trail near the top: Home > Category > Subcategory > Current Page. Named after the Hansel & Gretel trail; serves the same purpose: knowing how you got here and how to back out.
What breadcrumbs actually do
Three jobs at once:
Orientation. The visitor knows where they are in the site’s structure. Especially valuable on deep e-commerce or knowledge-base sites where someone landed via search 4 levels deep.
Lateral navigation. Easy one-click jump back up the hierarchy. Reduces back-button reliance, increases session depth.
SEO. Properly marked-up breadcrumbs (with structured data via schema.org BreadcrumbList) get displayed in Google search results in place of the bare URL - clearer SERP appearance, often higher CTR.
When you need them and when you don’t
Breadcrumbs earn their slot on three site types:
E-commerce with category hierarchies (Clothing > Men > Outerwear > Jackets).
Knowledge bases / documentation with topic trees.
Large content sites with editorial structure (publication > section > topic > article).
They don’t earn their slot on:
Flat marketing sites with 5-15 pages and a single nav level. Adding breadcrumbs here is visual clutter pretending to be UX work.
Single-page apps where the URL doesn’t reflect a real hierarchy.
Blogs with one or two category levels - the standard nav already handles this.
The most common implementation mistake
Breadcrumbs that don’t reflect the actual user journey. The visitor came in from a Google search to a deep article. The breadcrumbs show “Home > Resources > Articles > Title” - a perfect logical hierarchy that has nothing to do with how the visitor got here. They’re orienting against a structure they never traversed.
Two patterns work better. Either keep the breadcrumbs strictly hierarchical (and let the visitor figure out their own way around if they want) or use a “where you came from” version that traces the actual session path. Don’t pretend a hierarchical breadcrumb is journey-aware when it’s not.
An example
I worked with a 200-page e-commerce site that had no breadcrumbs at all. Category pages were getting decent traffic from Google but session pages-per-visit sat at 1.6 - visitors landed on a product, didn’t navigate elsewhere, left.
The fix: implement breadcrumbs on every product and category page, marked up with schema.org BreadcrumbList. Two-week project including QA.
Three months later: pages-per-session up to 2.4, category-page click-through from product pages up substantially, and the SERP appearance for product results showed the breadcrumb trail instead of the bare URL - anecdotally, click-through from search lifted by something visible in Search Console.
Small intervention. Real compounding lift across multiple metrics.
We built Penfriend to produce content that slots cleanly into breadcrumb-aware site structures. Every piece generates with clear parent-category placement, which is what breadcrumbs depend on. Orphaned content breaks breadcrumb logic silently.
Related terms
- XML Sitemap - the technical SEO neighbour breadcrumbs sit alongside in site-structure work
- User Experience (UX) - the broader discipline breadcrumbs are a small but useful piece of
- Search Engine Optimization (SEO) - the channel breadcrumbs benefit via structured-data SERP display
- Featured Snippet - another SERP-display element worth understanding alongside breadcrumb display
- Hyperlink - the underlying mechanism breadcrumbs are built from