A breadcrumb trail sits at the top of almost every page I audit.
Home, then category, then the page itself, in small gray text above the headline.
Visitors barely notice it. Most owners never think about it twice.
What matters is the version underneath it. The code most sites never write.
What the Trail Actually Shows
A visible breadcrumb and the structured version behind it do two different jobs. The visible trail helps a person click back a level on a phone or a laptop. The structured version, written once into a page's code, states the same path so Google or an AI tool like ChatGPT does not have to guess at it.
One is for a person. The other is for everything else reading the page.
Get it wrong and nothing breaks for a visitor. The page still works. The trail still shows. It is the quiet layer underneath that goes missing.
Why Hierarchy Matters at All
A site with no clear structure reads like a stack of pages with no relationship to each other. Which page is the main service. Which pages are supporting detail. Which page is a city variant of another.
The code behind a breadcrumb answers that question directly. Service page under category, category under home. That nesting is one more way an AI tool or a search engine figures out what a page is actually about, especially when a URL alone does not make it obvious.
A page can state its place in a business before anything reads a single sentence of the content on it.
The Boilerplate Breadcrumb Problem
Most site builders generate a visible breadcrumb automatically. Far fewer get the code behind it right. Three patterns turn up on almost every audit I run.
- The trail shows on the page and the code behind it is missing entirely.
- The code exists but only goes one level deep, home and page, skipping the category in between.
- The code was copied from a template and points at the wrong structure for half the pages on the site.
None of these look wrong to a visitor.
All three hand a confusing map to anything trying to read the site by its structure instead of its words.
What Multi City Sites Get Wrong
A business serving more than one Arizona city multiplies this problem. Phoenix, Scottsdale, and Tempe service pages should nest the same way the site's real navigation works.
I have seen the breadcrumb code put a city page directly under the homepage, skipping the service category that actually organizes the site. The visible trail on the page looked fine. The code behind it told a different story entirely.
The fix is not a new page. It is matching the code to the structure that already exists.
A city page that competes with its own category page for the same spot in an AI answer is not a new problem for this blog. It is the same structural confusion that shows up when a sitemap lists everything at equal weight, or when a canonical tag points at the wrong version of a page. The symptom changes. The cause is almost always the same one: a site that nobody mapped before building it.
How to Actually Check It
Checking this does not take special tools. Open the page source and search for the word BreadcrumbList. If nothing comes up, the visible trail is decoration and nothing more.
When it does show up, read the path it states. Compare that path against where the page actually lives in the real navigation on the site. A mismatch usually means a template was built once, copied everywhere, and never checked again.
I run this on every page type during an audit, not just the homepage. An error on one service page almost always repeats across every other service page built from the same template, so finding it once usually means finding it a dozen times over.
Where This Fits With the Rest
A breadcrumb trail is not a fix on its own. It sits next to canonical tags, a clean sitemap, and the links between pages, all doing a version of the same job. Our post on internal linking covers how links between pages signal importance. This is the vertical version of that idea, where a page sits beneath the ones above it.
Fixing it takes an afternoon on most sites once someone actually maps the real hierarchy.
It will not get a page cited on its own. It is one more piece of structure that makes the rest of the work easier to trust, and checking it is part of every SEO / AEO / GEO Foundation engagement.