Breadcrumbs: showing where a page sits on your site

Breadcrumbs are the short trail of links, usually near the top of a page, that shows the path from the home page down to the current page, such as Home › Guides › Backpacks. Google says a breadcrumb trail "indicates the page's position in the site hierarchy." They are the on-page signal that makes a site's structure visible.

What breadcrumbs are

Breadcrumbs are a navigation aid: each step is a link to a level above the current page, and the last step is the page itself. A reader who lands deep in a site from a search result can see at once where they are and move up a level without going back to the home page.

Google's documentation for breadcrumb markup, last updated on 2026-09-08 and checked on 2026-10-12, describes the benefit in reader terms: the trail "may help users understand and explore a site effectively. A user can navigate all the way up in the site hierarchy, one level at a time, by starting from the last breadcrumb in the breadcrumb trail."

Visible trail and markup

A breadcrumb has two parts that should match: the trail a reader sees and the structured data that describes it to search engines.

• The visible trail

  is ordinary HTML links, usually in a <nav> element labelled as breadcrumbs. Because they are real links, they are also internal links, and they connect every page to the levels above it; the internal links page covers why that matters.

• The markup

  is BreadcrumbList structured data, a list of the same steps with their names and addresses. It does not create a trail; it describes the one on the page. Like all structured data, it should match what the reader sees, as covered under structured data.

Where Google shows them

Google can show a breadcrumb trail in place of the address in a search result, which tells a searcher where the page sits before they click. Since January 2025, it does so only on desktop. Its documentation updates record, dated 2025-01-22, that breadcrumbs "only appear on desktop search results, not mobile," because "of how breadcrumbs get truncated on smaller screens."

As with every rich result, markup makes the trail possible in results without guaranteeing it; the rich results page explains how Google decides. On the page itself, breadcrumbs help every reader on every device.

Building a good trail

• Follow the site's hierarchy

  The trail shows where the page lives in the structure, not the path a particular visitor took to reach it. A page in Guides › Backpacks shows that trail whether the reader came from search, a newsletter or another section.

• Make every step a link except the last

  The current page is the end of the trail; linking it to itself adds nothing.

• Use the names readers know

  Each step should use the same name as the page or section it links to, so the trail matches the navigation.

• Keep one trail per page

  A page that belongs in two places should pick the main one for its trail; two trails confuse more than they help.

Breadcrumbs on this site

This site shows a breadcrumb trail on every page below the home page, generated from the address, and declares it as BreadcrumbList markup that matches the visible trail. Where a page is missing breadcrumb markup, AI SEO enrichment fills it from the page's path, without touching markup somebody already wrote.

Breadcrumbs in a CMS

Most content systems can produce breadcrumbs from their own page tree or from a theme setting, and many themes include them. Check two things when turning them on. First, that the trail follows the structure you intend: a system that builds it from categories may put a page under a category a reader would not expect. Second, that the markup matches the visible trail, since a theme and a separate plugin can each output their own version and disagree.

Common mistakes

• A trail that repeats the menu

  Breadcrumbs show the path to this page, not every section of the site.

• The home page named twice

  A trail that starts with both the site name and "Home" spends a step on nothing.

• Markup without a visible trail

  Structured data should describe what is on the page; a BreadcrumbList with no trail for readers describes something that is not there.

• Trails that change with the visit

  A trail built from the visitor's history shows a different hierarchy to every reader and to search engines, which defeats its purpose.

Breadcrumbs and the address

A trail and an address often look alike, because many sites build their addresses from the same hierarchy: /guides/backpacks/atlas-40/ and Home › Guides › Backpacks › Atlas 40. They do different jobs. The address names the page; the trail shows readers how to move up from it. Where the two follow the same structure, keep them in step when sections are renamed, so the trail never points to a level the address no longer has.

When a site does not need them

Breadcrumbs earn their place on sites with depth: several levels of sections, or many pages a reader may land on directly. A site of a few pages, all reachable from the main menu, has no hierarchy to show, and a trail of one step adds clutter rather than help.

FAQ