HeyMark
Content

Blog

Website breadcrumbs: navigation and a worked example

4 min read

Website breadcrumbs show where a page belongs in a site’s structure. A trail such as “Shop › Mugs › Blue mug” lets someone return to a category without starting again at the homepage. Its value depends on the levels representing understandable relationships.

Showing every page a visitor opened previously creates a history. That history does not necessarily explain where a product belongs, especially for someone arriving directly from search.

Choosing a mug’s trail

In this fictional example, a mug belongs to “Mugs”, appears in a gift selection and can be found using the “Blue” filter. A visitor lands on its product page without opening any of those lists.

The studio chooses “Shop › Mugs › Blue mug” as its main trail because “Mugs” is a stable category containing comparable products. The gift selection remains a contextual link. A filter does not automatically become another level in the hierarchy.

Proposed trail What it describes Decision in this example
Shop › Mugs › Blue mug Category and product Use it as the main trail
Shop › Blue › Blue mug A product attribute Keep color as a filter unless a useful dedicated collection exists
Home › Search › Page 2 › Blue mug Steps in a browsing session Do not use it as the product hierarchy

Do not create empty categories to complete a trail. If “Mugs” is not a useful page, address that navigation first or choose a structure that exists.

A simple HTML representation could look like this:

<nav aria-label="Breadcrumb">
  <ol>
    <li><a href="/shop/">Shop</a></li>
    <li><a href="/shop/mugs/">Mugs</a></li>
    <li aria-current="page">Blue mug</li>
  </ol>
</nav>

The paths are illustrative. Check that both links open real categories and that the current level is identified when reading the navigation. The browser’s back button has a different purpose: it returns through that person’s history, which may begin outside your site.

Google documents BreadcrumbList and its properties as a way to describe trails using structured data. The markup should represent a relevant path with consistent names, positions and destinations. Adding JSON-LD without building visible navigation does not help a visitor return to “Mugs”.

A product can have more than one valid trail; Google’s documentation covers that case. Select trails reflecting the actual organization rather than reproducing every filter combination. For implementation, the introduction to structured data explains what a validation test establishes and what it cannot establish.

What to check before calling it finished

Open the product page directly, bypassing the catalog. Use the breadcrumb to reach “Mugs” and confirm that the item can be found there. Then compare that trail with the structured data and validate the markup.

Google’s documented breadcrumb search feature is available on desktop; do not promise identical presentation on mobile. Valid markup does not guarantee that Google will show it. Navigation on your page still serves visitors even when search presentation changes.

Plan your next post in HeyMark.

Keep the idea, review the draft with your team, and see how it performed in the accounts you connected.