Breadcrumbs and why they help more than they appear to

Aug 29
3 min read

Updated: 4 days ago

Introduction

Somebody arrives on a product page from a search result. They have never seen the site before, they do not know what else it sells, and the only way back to anything broader is the main menu, which tells them nothing about where the current page sits.

Breadcrumbs solve this with one line of small text. They are among the least discussed navigation elements and among the most useful, particularly on sites where most visitors arrive on an interior page rather than the home page — which is to say almost every site.

1. Breadcrumbs and why they help starts with where visitors arrive

Understand the situation they address.

The majority of visits from search land on an interior page. The visitor has no context for where that page sits, and a breadcrumb supplies it in a single line without occupying any meaningful space or requiring them to look for it.

2. They give a route upward, not backward

A distinction worth making.

The browser's back button returns somebody to the search results, which usually means losing them. A breadcrumb offers a step up into the broader category, which keeps them on the site and often leads to a page that suits them better than the one they landed on.

3. They can change how your listing appears

A visible benefit in search results.

With the right markup, search engines may display the breadcrumb path in place of the raw address in a listing. That is easier to read and communicates structure before anybody clicks, which occasionally matters more than the description does.

4. They reinforce your internal linking

A structural benefit that accumulates.

Every breadcrumb is a link from a specific page to its parent categories, applied consistently across the whole site. On a large catalogue this quietly strengthens the category pages, which are usually the ones you most want to perform.

5. They should reflect the hierarchy, not the visit

The most common implementation error.

A breadcrumb showing the path a particular visitor took through the site is a history trail, not a breadcrumb, and it is unpredictable and unhelpful. It should show where the page sits in the structure, identically for everybody.

6. Add the markup so they can be understood

A small technical step with a visible return.

Structured data describing the breadcrumb makes it eligible for display in results. Most platforms and plugins handle this automatically once breadcrumbs are enabled, so it is usually a setting rather than a development task.

7. Keep them short and readable

They are a navigation aid, not a heading.

Small text, clear separators, and the current page shown as plain text rather than a link. A breadcrumb competing visually with the page title has been given more prominence than its purpose warrants.

8. Do not use them on a flat site

They should describe something real.

A site of eight pages with no hierarchy gains nothing from a breadcrumb reading Home followed by the page name. Where there is no structure to communicate, the element is decoration.

9. Check they work on a phone

Where they are most useful and most often broken.

Long paths wrap awkwardly, disappear off the edge, or become unreadably small on narrow screens. Since phone visitors are the ones least likely to explore a menu, this is the case worth getting right rather than the desktop one.

Look at where breadcrumbs actually get clicked in your analytics. On catalogue sites they are used considerably more than most owners expect, and the categories people move up into tell you something useful about what visitors thought they were looking for when they arrived.

Conclusion

Add breadcrumbs because most visitors arrive on interior pages without any sense of where they are.

Understand that they offer a route upward rather than backward, add the markup so the path can appear in your search listings, recognise the internal linking benefit they accumulate across a large site, base them on the site hierarchy rather than on the individual visitor's path, keep them visually small and readable, leave them off a genuinely flat site where they describe nothing, make sure they work on narrow screens, and check in your analytics how often they are actually used.