Breadcrumbs feel like a solved problem. Home > Category > Subcategory > Page. Simple enough that most CMS themes ship one out of the box. But the default output from WordPress, Shopify, and most page builders rarely matches the actual information architecture of your site, and that mismatch creates problems that don't show up until you start wondering why certain pages never appear in search results.
The gap between what your breadcrumbs say and what your site structure actually looks like is where the Breadcrumb Depth Audit earns its keep.
Why depth matters more than you think
Google uses BreadcrumbList schema to understand your site's hierarchy. When you claim a page lives at level 3 but your internal linking treats it as level 5, the crawler has to reconcile two conflicting signals. Usually it just picks the one that's easiest to crawl, which may not be the one that gets your page indexed the way you want.
Deeper pages get crawled less frequently. Googlebot allocates crawl budget roughly by perceived depth from the homepage. A page that's genuinely three clicks from home gets visited more often than one that requires six. If your breadcrumbs say "three clicks" but your actual link graph says "six," the breadcrumbs aren't doing the work you think they are.
For users, breadcrumbs that skip levels are confusing. Clicking from "Mens > Running Shoes > Nike Air Max 90" and landing on a generic "Shoes" page instead of "Running Shoes" breaks the mental model. People bounce. Your analytics blame the landing page, but the real culprit is navigation that doesn't match what you told the visitor to expect.
The common depth problems
Flat breadcrumbs on deep sites. E-commerce stores with 10,000+ SKUs sometimes flatten everything to Home > Category > Product. That erases all the subcategory signals that help Google understand your catalog taxonomy. Your "Running Shoes" subcategory page never appears in the breadcrumb trail, so it never gets the internal linking benefit that breadcrumbs provide.
Over-nested breadcrumbs. The opposite problem: breadcrumb trails that are seven or eight levels deep because someone mapped every folder in the CMS to a breadcrumb item. Home > Products > Footwear > Mens > Athletic > Running > Neutral > Nike Air Max 90. Most of those middle layers don't have real landing pages, so the breadcrumb links either 404 or loop back to the parent category.
Schema that doesn't match the visible breadcrumb. This is the sneakiest version. The HTML breadcrumb on the page shows one trail, but the JSON-LD BreadcrumbList in the head tells Google a different story. Sometimes a plugin generates the schema from the URL path while the visible breadcrumb is generated from the category assignment. They diverge silently, and you have no idea until you check.
What to audit
The Breadcrumb Depth Audit scans your pages for both the visible breadcrumb trail and any BreadcrumbList structured data, then checks for mismatches. It flags trails that skip levels, links that don't resolve to real pages, and nesting deeper than five levels (the point where Google's documentation suggests diminishing returns).
Run it alongside the Schema Completeness tool to make sure your BreadcrumbList items have all required properties, and check the Navigation Depth Audit to see whether your actual click depth matches the breadcrumb depth.
If you're building a site from scratch, The $97 Launch covers flat-but-meaningful information architecture that keeps breadcrumbs honest from day one.
Fixing depth issues
For flat breadcrumbs, add the missing intermediate categories. If you have real subcategory pages (and you should), include them in the trail. Home > Mens > Running Shoes > Nike Air Max 90 tells both Google and your visitors exactly where they are.
For over-nested trails, decide which levels actually correspond to pages worth landing on. If "Athletic" and "Neutral" are just filter states rather than real category pages, they don't belong in the breadcrumb.
For schema mismatches, pick one source of truth. Either generate both the visible breadcrumb and the JSON-LD from the same data source, or remove the JSON-LD and let Google infer the hierarchy from the visible trail (it will, and at least it'll match what users see).
Fact-check notes and sources
- Google's BreadcrumbList structured data documentation recommends including every level of the site hierarchy. Source: Google Search Central, "Breadcrumb structured data".
- Crawl budget allocation correlates with perceived page depth. Source: Google Search Central, "Crawl budget management".
- Five-level nesting guideline is a practical recommendation from SEO testing; Google's docs don't set a hard limit but note diminishing value beyond reasonable depth.
Related reading
- Why the Schema Completeness tool exists — making sure your schema has all the fields search engines expect
- Navigation Depth Audit — measuring actual click depth from the homepage
- FAQ Schema Parity — another case where schema and visible content drift apart
- Link Graph Depth — visualizing how deep your internal link structure actually goes
This post is informational, not SEO-consulting advice. No affiliation with any CMS vendor or search engine is implied.
