Must breadcrumb labels reproduce the URL path?

Definition: A breadcrumb is a trail that indicates a page's position in a site's hierarchy. Google recommends representing a typical user path to the page, so breadcrumb labels and URL path segments can differ.

Key facts

• Google recommends breadcrumbs that represent a typical user path instead of mirroring the URL structure. Its guidance also says the top-level path and the page itself do not require a ListItem. Google's Breadcrumb structured data documentation states this directly.
• Google describes a breadcrumb trail as an indicator of a page's position in the site hierarchy. It says a user can move upward one level at a time by starting from the last breadcrumb.
• Google says one page can have multiple breadcrumb trails when there are multiple ways to reach that page.
• Schema.org defines BreadcrumbList as a chain of linked web pages described with their names and usually their URLs, ending with the current page. The Schema.org BreadcrumbList definition describes the type.
• Schema.org uses the position property to reconstruct the order of items in the list.
• Google's URL guidance recommends a simple structure, logical construction and words that are readable to humans. Google's URL structure documentation gives that guidance separately from breadcrumb labeling.

What should the labels describe?

The labels should describe the path a visitor would use to understand the page's place in the site. Google's breadcrumb documentation says that breadcrumb markup categorizes page information in the context of a Google Search query. The same page can therefore have a breadcrumb trail that fits the context in which a visitor reaches it.

The recommendation is explicit: a typical user path takes priority over a visual copy of the URL. A breadcrumb label can use the fuller name that makes the section understandable. Google's example pairs the label Science Fiction with the URL path /books/sciencefiction, which shows that the label does not need to reproduce the path characters.

The two representations still describe related structure. Google's URL structure documentation recommends URLs that are constructed logically and are intelligible to humans. It also recommends readable words rather than long ID numbers. These URL recommendations apply to the address itself, while the breadcrumb recommendation governs the navigation path presented for the page.

How is the trail represented in structured data?

Google's breadcrumb documentation requires a BreadcrumbList containing at least two ListItem objects for breadcrumb display eligibility. In the JSON-LD example, earlier items have an item URL and the current page item has a name without an item URL:

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [{
    "@type": "ListItem",
    "position": 1,
    "name": "Books",
    "item": "https://example.com/books"
  },{
    "@type": "ListItem",
    "position": 2,
    "name": "Science Fiction",
    "item": "https://example.com/books/sciencefiction"
  },{
    "@type": "ListItem",
    "position": 3,
    "name": "Award Winners"
  }]
}

Schema.org's BreadcrumbList definition says that position reconstructs the order of the items. Its convention places lower values first and starts the trail with the top or beginning of the hierarchy, such as a site or section homepage. The itemListElement property carries the ordered breadcrumb items.

What should a site check?

A review can compare the visible trail with the navigation path that the page represents, then compare the structured data with that trail. The check should confirm that each ListItem has the intended name and order, that linked ancestors point to the corresponding pages, and that the current page is represented according to the chosen format. Google's breadcrumb documentation gives JSON-LD, RDFa and Microdata examples and says the code should be validated with the Rich Results Test.

URL review is separate. Google's URL guidance recommends using the audience's language where possible and using hyphens rather than underscores to separate words. Those recommendations inform URL readability; they do not turn URL segments into mandatory breadcrumb labels.

Related terms

• BreadcrumbList structured data
• Structured data
• JSON-LD
• URL parameters

FAQ

Must every breadcrumb label equal its matching URL folder?

No. Google's breadcrumb documentation recommends a typical user path and gives an example where Science Fiction labels the URL path /books/sciencefiction.

Can one page have more than one breadcrumb trail?

Yes. Google says multiple trails can be specified when there are multiple ways to reach the same page.

Should your URL paths still be readable?

Yes. Google's URL documentation recommends simple, logical structures with readable words and audience language where possible.

Sources

1. Google Search Central, "Breadcrumb (BreadcrumbList) structured data", 8 September 2026
2. Schema.org, "BreadcrumbList", undated
3. Google Search Central, "URL structure best practices for Google Search", 10 December 2025

---

Check how a page reads to answer engines. Open the GEO score analyzer