BREADCRUMBSTrails, markup and mobileBreadcrumbs are the short trail of links near the top of a page, such as Home > Services > Payroll. They show a visitor who lands deep in a site where they are. Built well, the same trail tells Google where the page belongs. Built badly, it adds clutter and gives Google markup that doesn't match the page.
Does every website need breadcrumbs?
No. W3C describes a breadcrumb trail as links to the parent pages of the current page, in hierarchical order, so breadcrumbs help where pages have parents worth returning to:
- Online shops, where products sit in categories and subcategories.
- Documentation and help centres, with sections, subsections and articles.
- Multi-service and multi-location sites with a Services or Locations hub.
- Blogs with categories that readers browse.
They add nothing on a flat five-page site where every page is already in the main menu, or on the home page, which is the top of every trail. Google's breadcrumb markup needs at least two items, so a lone Home link isn't a trail.
Should the trail follow your site structure or the visitor's clicks?
Your site structure. Google describes a breadcrumb as showing a page's position in the site hierarchy, so a visitor can move up one level at a time. A history trail of the pages one visitor clicked through is different: it changes on every visit, repeats the Back button and can't be described by markup that is the same for everyone.
Structure doesn't have to mean URL folders. Google recommends breadcrumbs that represent a typical user path to a page rather than mirroring the URL structure, so a product at /p/4471 can still show Home > Women > Running shoes.
How should the visible trail be built?
As a labelled navigation landmark holding an ordered list of links, which is the breadcrumb pattern in the W3C WAI-ARIA Authoring Practices. In practice:
- Wrap the trail in a
navelement witharia-label="Breadcrumb", so screen reader users can find it as a landmark. - Use an
ol, because the order of the steps carries meaning. - Put
aria-current="page"on the link to the current page, and on nothing else. If the current page is plain text rather than a link, W3C treats the attribute as optional. - Draw the separators with CSS, as the W3C example does with a skewed border, rather than typing slashes into the HTML, so screen readers don't announce them.
<nav aria-label="Breadcrumb">
<ol>
<li><a href="https://example.com/">Home</a></li>
<li><a href="https://example.com/services/">Services</a></li>
<li><a href="https://example.com/services/payroll/" aria-current="page">Payroll</a></li>
</ol>
</nav>We place the trail above the H1, directly under the main menu.
What does Google need in the BreadcrumbList markup?
A BreadcrumbList whose itemListElement holds at least two ListItem entries, each with a position, a name and an item. Position 1 is the start of the trail, name is the label shown and item is the step's URL. The last entry may leave out item, and Google then uses the page's own URL. Google's examples cover JSON-LD, Microdata and RDFa; we use JSON-LD because it sits in one block.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/" },
{ "@type": "ListItem", "position": 2, "name": "Services", "item": "https://example.com/services/" },
{ "@type": "ListItem", "position": 3, "name": "Payroll" }
]
}
</script>Keep the markup and the visible trail identical: same steps, same order, same labels. Google's guidelines say structured data must be a true representation of the page and must not describe content readers can't see.
Generate the trail and the JSON-LD from one CMS field, such as the page's parent or category, so renaming a section changes both.
How should breadcrumbs work on phones?
On the page they matter as much as on desktop, but Google no longer shows them in mobile results. Since January 2025 the visible URL in mobile results is the domain only, because breadcrumbs were cut off on small screens. Desktop results still show the breadcrumb, and Google said sites using the markup need not change anything.
Keep the trail and its markup in mobile templates: Google's mobile-first indexing guide asks for the same structured data on mobile and desktop, naming Breadcrumb first among types to prioritise. Then design for a thumb:
- Let a long trail wrap onto a second line rather than run off the screen.
- Use short labels, even when the page's H1 is longer.
- Make every link easy to tap. WCAG 2.2 asks for targets of at least 24 by 24 CSS pixels, or enough space around smaller ones; its stricter enhanced criterion uses 44 by 44.
- If a deep trail needs shortening, collapse the middle steps behind a button that reveals them, rather than deleting them from the mobile HTML.
How do you check breadcrumbs are working?
Test one page per template in Google's Rich Results Test, then watch the Breadcrumbs report in Search Console. The test shows whether a page's markup is valid; URL Inspection shows how Google sees the live page. The report sits under Enhancements and splits items into valid and invalid; an invalid item has a critical issue that stops it appearing as a rich result.
Valid markup makes a page eligible, nothing more: Google doesn't guarantee structured data will show in results. Check the visible trail by hand too, on a phone and with the Tab key.
Where to start
Pick one deep page per template (a product, a help article, a service page) and compare its visible trail with the markup in the Rich Results Test. Where they differ, fix the template, not the page. Our SEO and AI search service covers breadcrumbs with the rest of technical SEO, and schema markup that matters for service businesses covers the other structured data worth adding.
FAQ
Frequently asked questions
Do breadcrumbs improve rankings?
Google doesn't present them as a ranking factor. Its breadcrumb documentation is about categorising a page's information in results and showing the trail on desktop. We add breadcrumbs because they make deep sites easier to move around and give Google a clear path for each page, not as a ranking tactic.
Should Home be the first step in the breadcrumb?
On the page, usually yes, because it gives every visitor a way back to the top. In the markup, Google doesn't require a ListItem for your domain or for the current page, so leaving either out is valid. We include both so the markup matches the visible trail step for step.
What if a product sits in more than one category?
Choose one primary category for the trail, usually the one most shoppers browse through, and use it in both the trail and the markup. Google does accept several breadcrumb trails for a page that can be reached in different ways, but any trail you mark up should also appear on the page.
Do we need breadcrumb markup if our URLs are already readable?
Yes, if you want a say in the path Google shows. Google says you can specify the trail in a result with breadcrumb structured data, and recommends a typical user path rather than a copy of your URL folders. Readable URLs still help people, but they are not the same as a trail you control.
Do breadcrumbs replace the main menu?
No. The main menu takes visitors across the site's top sections from any page, while a breadcrumb shows where one page sits and how to step back up from it. On a deep site the two work together. On a shallow site the menu alone is usually enough, and a trail only repeats it.
Should blog posts show a category or a date in the breadcrumb?
A category. A breadcrumb shows where a post sits in the site, such as Home > Insights > SEO, so a reader can browse more on the same subject. A date says when, not where. If a post belongs to several categories, pick one primary category for the trail and keep it consistent across the blog.

