Breadcrumbs: Better Navigation and Search Snippets for Small Business Websites
Breadcrumbs are the small row of links above a page title that reads something like Home > Services > Water Heaters. They take minutes to add, they help visitors who land deep in your site from search, and they give search engines a clear picture of how your pages fit together.
This guide covers when a small business site actually benefits from breadcrumbs, the design rules usability researchers recommend, accessible HTML that works with screen readers, the BreadcrumbList structured data Google reads, and what changed when Google removed breadcrumbs from mobile search results in January 2025.
Key facts
- Jan 2025 — Google removed breadcrumbs from the visible URL in mobile search results
- 3 — Properties Google lists for each ListItem: position, name and item
- 1 — Item per trail that should carry aria-current="page"
- 1 cm — Minimum tap target size NN/g suggests for mobile breadcrumb links
What Breadcrumbs Are (and Aren't)
A breadcrumb trail is a short row of links, usually just above the page title, that shows where the current page sits in your site. On a plumbing company's site it might read Home > Services > Water Heaters > Tankless Installation. The W3C's ARIA Authoring Practices Guide defines it as a list of links to the parent pages of the current page in hierarchical order.
Three things breadcrumbs are not:
- Not your main menu. Nielsen Norman Group's guidelines say breadcrumbs should augment, not replace, your global and local navigation. They are a secondary aid.
- Not a history trail. They show the site's structure, not the pages this visitor happened to click through. A visitor who arrives from Google on a deep page sees the same trail as one who browsed there.
- Not needed everywhere. NN/g notes that sites only one or two levels deep, or linear flows such as a checkout, gain little from breadcrumbs. A five-page brochure site can skip them.
When a Small Business Site Benefits
Breadcrumbs earn their space when your pages naturally nest. Common cases on small business sites:
- Service businesses with several service lines, each with its own sub-pages (for example Services > Roofing > Repairs).
- Online shops with categories and sub-categories, where shoppers land on a product page from search and want to see the rest of the range.
- Blogs and resource libraries organised by topic, where a reader on one guide may want the whole category.
- Multi-location businesses with a page per city or branch under a Locations section.
The common thread is visitors arriving on a deep page from search, an ad or a shared link. Breadcrumbs answer “where am I?” and give them a one-click route up to the broader page instead of the back button.
If your page only lives in one obvious place, that is easy. If a product fits two categories, NN/g recommends showing one canonical path rather than trying to show every route.
Design Rules That Make Breadcrumbs Usable
Most of NN/g's eleven breadcrumb guidelines come down to a few habits:
- Start with Home (or your site name), unless a Home link is already obvious in the main navigation.
- End with the current page, but don't link it. Including the current page confirms where the visitor is; linking it just reloads the same page.
- Use a clear separator. NN/g recommends the “>” character, which suggests moving down a level, though a slash is also acceptable.
- Keep labels short and consistent with your menu and page titles, so “Water Heaters” in the trail matches “Water Heaters” in the menu.
- Keep it small but visible. Breadcrumbs sit above the H1 in a smaller size than the heading; they should not compete with it.
On phones
Long trails are the main mobile problem. NN/g advises against trails that wrap onto several lines and against tiny, crowded links, suggesting tap targets of at least 1 cm by 1 cm. One option it describes is showing only the last level or two on mobile, for example a single “< Water Heaters” link, while desktop always shows the full trail. WCAG 2.2’s target-size criterion points the same way: give each link enough room to tap.
Accessible Breadcrumb Markup
The W3C pattern and MDN agree on simple, standard HTML:
- Wrap the trail in a
navelement witharia-label="Breadcrumb", so screen reader users can find it as a labelled navigation landmark. - Use an ordered list (
ol), because the order means something. - Mark the current page with
aria-current="page". MDN describes thepagevalue as meant for the current page in a set, such as the link to the current document in a breadcrumb. Only one item in the set should be marked current. If the last item is plain text rather than a link, the W3C saysaria-currentis optional. - Add separators with CSS rather than typing them into the HTML, so screen readers don't read out “greater than” between every link. The W3C example does exactly this to avoid redundant, distracting verbosity.
<nav aria-label="Breadcrumb">
<ol class="breadcrumb">
<li><a href="/">Home</a></li>
<li><a href="/services/">Services</a></li>
<li><a href="/services/water-heaters/">Water Heaters</a></li>
<li><a href="/services/water-heaters/tankless/" aria-current="page">Tankless Installation</a></li>
</ol>
</nav>The separator then comes from a rule such as .breadcrumb li + li::before { content: ">"; } in your stylesheet, with a little horizontal padding.
BreadcrumbList Structured Data
Visible breadcrumbs help people. BreadcrumbList structured data tells search engines what the trail is. Schema.org defines a BreadcrumbList as a chain of linked web pages, typically ending with the current page, and says the position property, not the order of your markup, sets the order.
Google's documentation lists what it needs:
itemListElement: the breadcrumbs, in order.- For each
ListItem:position(starting at 1),nameanditem(the page URL). For the last breadcrumb, the current page,itemis not required.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{"@type": "ListItem", "position": 1, "name": "Services", "item": "https://example.com/services/"},
{"@type": "ListItem", "position": 2, "name": "Water Heaters", "item": "https://example.com/services/water-heaters/"},
{"@type": "ListItem", "position": 3, "name": "Tankless Installation"}
]
}
</script>Google supports JSON-LD, Microdata and RDFa; JSON-LD is usually the easiest to keep separate from your design. Two points from its guide are worth following:
- Model the typical user path, not the URL. Google recommends breadcrumbs that represent a typical user path to a page instead of mirroring the URL structure. If your URLs are flat (
/tankless-installation/) but your site has a clear section structure, describe the structure. - Match what visitors see. Google's general structured data guidelines expect markup to describe content that is on the page, so generate the visible trail and the JSON-LD from the same data. That way they cannot drift apart.
What Changed in Google Search in 2025
On January 23, 2025, Google announced on the Search Central blog that it was removing breadcrumbs from the visible URL in mobile search results in every language and region. On phones, a result now shows only the domain. On desktop, the visible URL still has two parts, the domain and the breadcrumb, and Google's breadcrumb documentation now describes the feature as available on desktop.
Google said sites did not need to take any action, that it continues to support breadcrumb markup for desktop results, and that the breadcrumb report in Search Console and testing in the Rich Results Test carry on.
So the practical advice is unchanged: keep the markup if you have it, and add it if your site has a real hierarchy. Just don't add breadcrumbs expecting a dramatic change in how you appear on phones. The bigger, steadier win is on your own pages, where breadcrumbs help visitors and give search engines clear internal links between related pages.
A Ten-Minute Breadcrumb Check
- Pick three deep pages: a service or product page, a blog post and a location page if you have one. Does each show a trail that makes sense to a first-time visitor?
- Click every crumb. Each link should go to a real, useful page, not a 404 or an empty category.
- Check the last item. It should be the current page and should not be a link (or should carry
aria-current="page"). - View on a phone. The trail should fit on one line or be shortened, with links big enough to tap.
- Run the Rich Results Test on each page and confirm a valid Breadcrumb item with the names and URLs you expect. Then watch the Breadcrumbs report in Search Console for errors as Google recrawls.
If you use WordPress, many SEO plugins and themes output both the visible trail and the markup; check that only one of them does, so you don't publish two conflicting trails. On a custom site, build the trail once from your page data and print both the HTML and the JSON-LD from it.
Sources
- Google Search Central: Breadcrumb (BreadcrumbList) structured data
- Google Search Central Blog: Simplifying the visible URL element on mobile search results (January 2025)
- W3C WAI-ARIA Authoring Practices Guide: Breadcrumb pattern
- W3C APG: Breadcrumb example
- MDN: aria-current
- Nielsen Norman Group: Breadcrumbs, 11 Design Guidelines for Desktop and Mobile
- Schema.org: BreadcrumbList
Related reading
Frequently asked questions
Do breadcrumbs still matter after Google removed them from mobile results?
Yes. Google still shows breadcrumbs in desktop results and still supports BreadcrumbList markup, and the on-page trail helps visitors find their way around your site on every device.
Should my breadcrumbs match my URLs?
Not necessarily. Google recommends breadcrumbs that represent a typical user path to the page rather than mirroring the URL structure.
Does every website need breadcrumbs?
No. Usability research from Nielsen Norman Group suggests sites only one or two levels deep, or linear flows like checkout, gain little from them.
Want navigation that helps visitors and search engines?
Tell me how your site is organised and I'll send a free, no-obligation quote for clean, accessible breadcrumbs and markup.
Get a free quote