Breadcrumbs show hierarchy, not history
Aliases: hierarchical trail · location breadcrumb
What it is
A breadcrumb draws where the current page sits in a classification tree: the one hierarchical path from the root to this leaf. It answers “which level of this tree am I on”, not “which pages did I just walk through”. Arrive at a product from search and the crumb should still read Store / Furniture / Chairs / this chair, not Home → Search → this chair. The latter is browsing history, and Back owns it.
Why it happens
A classification tree is a shared map. People use breadcrumbs for two jobs: confirming which parent the current node hangs from, and jumping to any ancestor along that parent chain. Both jobs need the path to mean belongs to, not visited. History paths vary by person and by entry: the same product can arrive from an ad, search, a save, or a message. If the crumb follows the visit, the map is no longer shared and people cannot learn that tapping the second-to-last segment lands on that category. Hierarchical paths are stable; history paths are not. Draw the trail instead of the tree and the control fails as a wayfinding device.
Mixing the two on one line also teaches the wrong Back model. Tapping the parent segment is supposed to mean “go to the parent node”. If the system pops history instead, it may land on search rather than the category. After that, people stop trusting the crumb. Search, filters, and recommendations are ramps into the tree, not nodes on it, and should not be spliced into the middle of the crumb.
Studying it
Use a location probe: enter the same leaf from a non-tree entry (search, external link, notification), ask “which category are you under”, and have people jump to the parent via the crumb. Independent variable: whether the crumb draws hierarchy or history. Dependent variables: correct parent naming, whether the tap lands on the parent node, and whether that landing is treated as the same event as Back.
Add a path consistency check: enter the same leaf from three entries and see whether the crumb is still the same string. Inconsistency means the control is drawing a trail, not a map.
Where it stops holding
Products with no stable classification tree (chat, timelines, canvases) should not invent breadcrumbs; place belongs in the title or another structure. Linear wizards are not trees; that is a stepper’s job. Some tools show a “recently visited” strip; it must be visually distinct from breadcrumbs and labelled Recent, not dressed as hierarchy. Multi-parent objects (an article filed in two columns) make a single crumb lie; pick a primary path or also mark “also in”. A one-level site of root and leaf gives the crumb almost no information, and it can be omitted.
Applying it
- Render only the ancestor chain from root to the current node on the classification tree, ignoring how this session arrived.
- Every segment except the current page links to that ancestor node itself, not to a frame on the history stack.
- When search, tags, or recommendations were the entry, say “arrived from search” elsewhere on the page; do not splice it into the crumb.
- How to check: open the same detail from search, from saves, and from an external link. The three screenshots of the crumb should match word for word. Then tap the second-to-last segment; landing must be the parent node, not the previous page in browser history.