The short answer
Breadcrumbs are worth having when a site has more than two levels: they tell visitors which section they are in and give every page a link to its parent. Since 23 January 2025 Google shows the breadcrumb trail in place of the URL only on desktop, while mobile results show just the domain. So the main benefit has moved inside the site, and BreadcrumbList markup mostly serves to keep the desktop snippet and the Search Console report in line with your real structure.
On 16 November 2026 I opened three breadcrumb guides that search returned first for "breadcrumbs SEO" in Russian. None of them mentions this change, and two still promise a navigational snippet without noting that mobile no longer shows it.
Where Google shows breadcrumbs after January 2025
Google Search Central published a post on 23 January 2025: on mobile devices the visible URL in a result is simplified to the domain only. Google's reasoning was that breadcrumbs got truncated on narrow screens and told users little. On desktop they stayed, site owners with breadcrumb markup have nothing to change, and the breadcrumb rich result report in Search Console continues.
The markup documentation now says the same in other words: the feature is available on desktop in all regions and languages where Google Search is available. It does not mention mobile at all.
In practice: if you added breadcrumbs so that the mobile result shows "Home › Services › Waste removal" instead of site.com/services/waste-removal/sofa, that effect is gone. If you added them for navigation and internal linking, everything still works.
What breadcrumbs do for a site beyond the snippet
Every step of the trail except the last is an ordinary <a href> link. The "Waste removal" section therefore gets a link from each of its sub-services, and "Services" gets links from every page below it. In a catalogue of 400 product pages the parent category collects 400 internal links with a meaningful anchor without a single manual edit. It is the same internal linking, just sitewide and pointing up the tree.
Breadcrumbs do not work downwards. A product page sitting 7 clicks from the homepage does not get any closer, because breadcrumbs lead away from it, not to it. Click depth is reduced by menus, links from categories and pagination. Breadcrumbs help with something else: a visitor who landed on a product page straight from search reaches the category in one click instead of going back to the results.
The third benefit is less obvious. The trail records the hierarchy you designed. If it shows "Piano moving" under "Office moving", the mistake is in the structure itself, and it is cheaper to fix while the site structure is built from keyword research than after launch.
BreadcrumbList markup: what is required
| Property | Where | Required by Google | What matters |
|---|---|---|---|
itemListElement | BreadcrumbList | yes | Ordered array of steps, at least two ListItem entries |
position | ListItem | yes | Integer, 1 marks the start of the trail |
name | ListItem | yes | The step label users see |
item | ListItem | yes, except the last step | Absolute page URL. The last step may omit it, and Google then takes the current page URL |
A minimal working example for a sub-service page:
{
"@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": "Waste removal", "item": "https://example.com/services/waste-removal/" },
{ "@type": "ListItem", "position": 4, "name": "Sofa removal" }
]
}
You do not have to include the homepage in the trail; Google says so directly. I include it, as in the example above: the visible trail almost always starts with "Home", and the markup should match what is on the page. Other markup types, and what large sites actually use, are covered in my article on schema markup.
What I found on 15 sites
On 16 November 2026 I took 15 sites I work on: my own and clients', service sites, online shops, financial directories. From each sitemap I picked the page with the deepest URL and checked three things: whether the trail is visible on the page, whether BreadcrumbList is in the source HTML, and whether the URLs in the markup return 200 without a redirect.
Ten sites get it right: the trail is visible and the markup is in the HTML, 8 of them use JSON-LD and 2 use microdata. JSON-LD turned up in the source HTML on 9 sites (eight from this group and one from the next), and on all nine every item URL returned 200 without a redirect. Trails run from 2 to 4 steps. The remaining five cases are more interesting.
- A service site outputs a three-step
BreadcrumbList, but the page itself shows no trail. Google's general structured data guidelines are blunt about it: don't mark up content that is not visible to readers of the page. - A financial directory on Next.js renders breadcrumbs on the page, yet the
application/ld+jsontags in the source HTML hold onlyOrganizationandWebSite.BreadcrumbListandFAQPageappear in the DOM only after JavaScript runs; I confirmed this in a browser. - A WordPress site has visible breadcrumbs and no markup at all.
- Two sites have neither. On one it is a second-level page where breadcrumbs are not needed anyway. On the other it is a third-level page whose parent section exists and returns 200, but the page has no trail leading to it.
One good example is worth noting. On a driving school site the course URL looks like /en/courses/<course>/, while the trail has two steps: home and the course. The "Courses" step is skipped, and rightly so, because /en/courses/ returns 404. Breadcrumbs follow real pages, not URL segments.
When breadcrumbs do harm
Breadcrumbs hurt when they misrepresent the structure: in the check above that is the case on 4 sites out of 15. In audits I run into four patterns.
- A step points to a section that does not exist. The trail is built from URL segments, but there is no
/services/page. Every product page then links to a 404, and the crawler finds that broken link on a thousand pages at once. - Markup and the visible trail disagree. The page says "Home › Services › Waste removal" while the markup has a different order or different names, because the theme and the SEO plugin each build breadcrumbs by their own rules.
- The trail changes depending on where the visitor came from. Googlebot has no browsing history, so it sees only one version, and the same product "belongs" to different categories on different crawls. If a product legitimately sits in two categories, Google allows two trails as separate
BreadcrumbListblocks, but I prefer one primary category. - The last step repeats a long H1. On a tyre shop in my check, the last markup element holds a full product name of more than 100 characters, with tyre size and rim parameters. That is not an error, but on desktop such a trail gets truncated anyway. A short model name reads better.
Who does not need breadcrumbs: one-page sites, landing pages and sites where every page is one click from the homepage. There a Home → Contact trail just takes up a line above the heading.
How to check your breadcrumbs in 10 minutes
- Take one deepest page per template: product, category, sub-service, blog post.
- Open the page source (Ctrl+U, not the inspector) and search for
BreadcrumbList. Not in the source but present in the inspector means the markup is rendered by a script. - Compare the names and order of steps in the markup with the visible trail. A mismatch in even one step counts as an error.
- Check the response code of every
itemURL: you want 200 with no redirect. A redirected URL in breadcrumbs repeats on every page of the template, and redirect chains multiply across the whole catalogue at once. - Run the page through the Rich Results Test by URL and look at the Breadcrumbs report in Search Console.
If the breadcrumb template needs rebuilding, that is a developer's job, not an SEO plugin's: one fix, consequences on every page at once. I handle template fixes like this as part of web development and ship them only after checking on a staging environment.
