Design breadcrumbs for articles in several topic hubs
Choose a useful breadcrumb hierarchy for articles in several collections, preserve one article URL and verify visible navigation against structured trails.

A topic relationship is not a second article copy
A measurement article can help readers in both an analytics hub and a paid-acquisition hub. That does not require publishing two copies of the article. Keep one intended address and decide how the real collections lead readers to it.
Google’s breadcrumb documentation supports multiple trails where there are multiple navigation paths to a page. Use that option to describe actual useful hierarchies, not to insert every target keyword as an invented parent. [Google Search Central: Breadcrumb structured data]
One article, two meaningful routes
This original example uses reserved illustration paths. The article remains /guides/refund-revenue in both cases. The two collections have different reader tasks, but each can lead naturally to the same method.
| Route | Reader context | Final article |
|---|---|---|
| Home → Analytics → Revenue measurement | Reconcile reported revenue | /guides/refund-revenue |
| Home → Paid acquisition → Campaign economics | Evaluate net revenue against ad spend | /guides/refund-revenue |
Choose a stable visible breadcrumb for the page’s primary context, or provide clearly understandable alternatives if that improves navigation. Contextual hub links can expose the other relationship without changing the article URL according to the visitor’s previous page.
Avoid making the same article’s canonical depend on which hub sent the visitor. A parameter such as ?hub=analytics may be useful for interface state, but it should not accidentally create another promoted copy of an unchanged article.
Check names, destinations and positions
- List the real navigation levels and verify every destination.
- Confirm that the visible hierarchy makes sense without the visitor’s browsing history.
- Generate one or more structured trails from the approved hierarchy.
- Check ListItem names, absolute destination URLs and sequential positions.
- Inspect the final page for duplicate or contradictory breadcrumb emitters.
- Follow the visible links on desktop and mobile.
The breadcrumb should not point at a missing category page merely because that category exists in a database. If the collection is not a useful public destination, use an actual parent that is. Keep the article’s final label consistent with its visible identity.
If the site layout already emits BreadcrumbList, a page-level renderer should not add an unrelated second version. Multiple deliberate trails are different from accidental duplication. A reviewer should be able to explain why each exists.
Sources
AI-assisted writing and an AI-generated editorial cover. Source links and checked dates are listed below; illustrative examples are labeled in the text.
- Google Search Central: Breadcrumb structured data — checked 2026-10-18