Glossary · Glossary

Breadcrumb

A breadcrumb is a navigation trail that shows where a page sits within a site's hierarchy.

Updated Oct 26, 2026 Reviewed Oct 26, 2026 en

A breadcrumb is a navigation trail that shows where a page sits inside a site’s hierarchy. It can help users move upward through a section, and it can help search systems understand page context.

Breadcrumbs can be visible on the page and can also be described with structured data using breadcrumb markup.

Why it matters

Breadcrumbs make site structure easier to scan. A glossary term should feel connected to a glossary, a guide should feel connected to its section, and a comparison should feel connected to the wider buying-guide layer.

For search appearance, breadcrumb context can also help distinguish a clean content route from a vague or deeply nested URL.

For AI answer visibility, the hierarchy a breadcrumb states is a context claim. When a definition page names its section and the section names its scope, a retrieval system that reads the page gets an unambiguous answer to “what kind of page is this and next to what.” That clarity costs little and removes one form of ambiguity. It does not, by itself, make an engine cite the page.

How it differs

A breadcrumb is a navigation and hierarchy signal. URL structure is the address pattern of the page. Internal linking is the broader network of links between pages. A site menu is a global navigation device; the breadcrumb is a per-page position statement that stays correct even when a user arrives from search instead of the menu.

A sitemap helps discovery, but it does not replace visible navigation or page hierarchy.

Example

Visible breadcrumb navigation:

<nav aria-label="Breadcrumb">
  <a href="/">Home</a>
  <a href="/glossary/">Glossary</a>
  <span>Canonical URL</span>
</nav>

Breadcrumb structured data:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Glossary",
      "item": "https://www.geolyze.org/glossary/"
    }
  ]
}
</script>

How teams use it

Teams review breadcrumbs when adding new sections, reorganizing topic clusters, or checking whether users can move from detail pages back to section hubs. A practical review asks:

Check	Question
Steps	Does each crumb level name a real, reachable page?
Match	Do the visible trail, the URL, and the structured data tell the same story?
Consistency	Do sibling pages in one section share the same trail shape?
Maintenance	When a page moves, does its trail get updated with the route?

Counterexample

A product page whose visible trail reads Home / Catalog / Item, while its BreadcrumbList markup lists Home / Blog / Item. The machine-readable trail and the visible trail disagree, so any system reading either one inherits a different idea of where the page sits. The fix is one source of truth for the hierarchy, not a second trail.

Common misunderstanding

Breadcrumbs are not the same as URL text. A page can have a readable URL and still need clearer navigational context. The breadcrumb should describe the user’s place in the site, not merely repeat every URL segment.