Breadcrumbs and multiple paths
A breadcrumb trail states a page's position in the site hierarchy, and the engine uses its markup to categorise the page's information in the results. One page may declare several trails, which answers the case of pages reachable by more than one route. The feature is described as available on desktop.
A display, and a declaration of hierarchy
A breadcrumb trail indicates a page's position in the site hierarchy and may help readers understand and explore a site; starting from the last breadcrumb, a user can navigate all the way up, one level at a time.
officialSource : Google Search Central, “Breadcrumb (BreadcrumbList) structured data”
The definition insists on one precise gesture: going up one level at a time. That is what separates a breadcrumb trail from a plain back link, and what makes it a navigation element rather than an ornament at the top of a page.
The engine uses breadcrumb markup in the body of a web page to categorise the information from that page in search results.
officialSource : Google Search Central, “Breadcrumb (BreadcrumbList) structured data”
The verb used is worth noting: categorise the page’s information. This is not a positional signal but a way of situating content, just as the site name situates its source. The two labels are read in the same part of a result, as it happens.
The case this markup really settles
A single page may declare several breadcrumb trails, the documentation giving the example of a page reachable by two distinct routes and supplying the corresponding markup as a list.
officialSource : Google Search Central, “Breadcrumb (BreadcrumbList) structured data”
This is the most useful part of the document, and the most overlooked. Many sites agonise over where to file content that legitimately belongs in two places: an award-winning book that is both science fiction and a prize winner, a service that belongs to two trades, a guide that fits two sections.
The published answer is that no choice is needed: both routes are declared. What looked like an architecture decision becomes a declaration with two entries.
In the published examples, the last item in the trail — the current page — carries a name but no address, unlike the levels before it.
officialSource : Google Search Central, “Breadcrumb (BreadcrumbList) structured data”
Add marked-up breadcrumbs to every page: it is a structural signal that mechanically improves the ranking of your deep pages.
What stops a trail working
The markup only counts if the page stays accessible to the engine: not blocked by robots.txt, not marked for non-indexing, and not behind a login requirement.
officialSource : Google Search Central, “Breadcrumb (BreadcrumbList) structured data”
Nothing specific to breadcrumbs, and that is exactly the point: the three obstacles listed are those of all structured data. Impeccable markup on an inaccessible page produces nothing, and the first check concerns access rather than syntax.
The feature is described as available on desktop, in all regions and languages where Search is available.
officialSource : Google Search Central, “Breadcrumb (BreadcrumbList) structured data”
A declared trail matching no real route through the site describes a hierarchy that does not exist: markup should follow the navigation, never the other way round.
hypothesis
The status is that of a reading. The documentation does not put the requirement in those terms; it describes a trail as the reflection of a navigable hierarchy, from which we conclude that a trail with no matching route describes an imaginary structure. It is an inference, and it is displayed as one.
Declaring a page's real routes, including when there is more than one
hypothesis
- Effort
- moderate
- Time to effect
- weeks
- Risk
- none
- Durability
- structural
The effort lies in the template and in checking that the displayed trail matches the declared one. The delay follows the next crawl. The risk is nil. Durability is good: a site hierarchy rarely changes, and the markup follows it with no extra work once the template is in place.
What does not work, or no longer works
Marking up a trail the page does not display. Reader and engine must receive the same information, and the documentation describes a navigation element, not an abstract declaration.
Then choosing arbitrarily between two legitimate classifications. The markup accepts several trails for one page, and the complete example sits in the documentation.
Finally, expecting a ranking effect. No published source presents this markup as a signal; what it produces is a display and a better reading of the site’s structure.
Sources
- Breadcrumb (BreadcrumbList) structured data — Google Search Centralaccessed on
- Provide a site name to Google Search — Google Search Centralaccessed on
Block revalidated on
Frequently asked questions
- Do breadcrumbs improve ranking?
- No published source says so. What the documentation writes is that the engine uses this markup to categorise the page's information in the results, which is a matter of presentation and of understanding the site. The certain benefit lies elsewhere: a reader who knows where they are.
- Can a page carry several trails?
- Yes, and the documentation supplies the complete example. A page reachable by two routes may declare both, as a list. That is the proper answer for catalogues and reference sites, where one piece of content legitimately belongs to two classifications.
- Should the last item carry an address?
- The published examples do not give it one: the last item, standing for the current page, carries a name without an address. The levels before it carry both. It is an implementation detail, but the one validation tools flag most often.
- Why is my trail not displayed?
- Three causes appear in the documentation, and none of them is the markup itself: a page blocked by robots.txt, a non-indexing rule, or a login requirement. The feature is also described as available on desktop.
- Should you mark up a trail the page does not show?
- No. A declared trail must match a real route through the site, otherwise it describes a hierarchy the reader cannot follow. Markup follows navigation, never the reverse, and a hierarchy invented for display contradicts itself on the first click.