Breadcrumbs And Site Hierarchy

Most service sites are flat. Twenty pages, all one click from the homepage, no relationship between any of them.

Which is fine at twenty pages and falls apart at two hundred, because nothing tells a visitor or a crawler how the pages relate to each other.

What hierarchy actually does

It groups related pages, so authority concentrates around a topic rather than spreading evenly across unrelated ones.

It tells a visitor where they are, which matters most for somebody who landed deep in the site from search rather than arriving at the homepage.

It gives the crawler a map of what sits under what.

It appears in search results, where the breadcrumb path replaces the raw URL and makes the listing more legible.

Designing the structure

Start from how customers think about the work, not from how the business is organised internally.

For a service business that is usually service, then specialisation, then location or project. For a product business it is category, then subcategory, then product.

Three levels is almost always enough. Four is occasionally justified. Five means the structure is wrong and something should be collapsed.

The test is whether somebody could guess the URL of a page from the structure. If they can, the hierarchy is doing its job.

URLs should match it

A hierarchy that exists in the navigation but not in the URLs is half a hierarchy.

So the path reflects the structure, in lowercase, hyphen separated, with no dates, no IDs and no stop words. Short, readable, and stable, because changing it later costs you the redirect work in the audit nobody wants to do.

Breadcrumbs in the markup

Two parts, and both are required.

The visible trail, near the top of the page, with every level a real link except the current page.

The structured data, so the path is machine readable and eligible to appear in the results listing.

The visible trail without the markup gets the user benefit and none of the search benefit. The markup without the visible trail is a mismatch between what the page shows and what it claims, which is a guideline problem.

Internal links carry the structure

Breadcrumbs are one direction. The links that matter most run the other way.

A parent page links to each of its children, in body copy rather than only in a template. Each child links back to the parent and sideways to its siblings where it makes sense. That is what turns a hierarchy into a connected set of pages rather than a diagram.

Template links are weak and body links are strong, which is why a category page with real editorial copy and real links outperforms one that only lists its children.

Navigation is not the hierarchy

The main menu is an editorial choice about what to promote. The hierarchy is the whole structure.

Which means plenty of pages sit inside the hierarchy without appearing in the menu, reached from their parent page, the footer, the sitemap and body links. A menu with forty items in it is not a navigation system, it is a list.

The flat site problem

Two hundred pages all at the root, no grouping, no parents, nothing explaining what relates to what.

The fix is not a redesign. It is choosing the five or six real topics the site covers, writing a proper page for each one, and connecting the existing pages underneath them. The pages already exist; what is missing is the layer that organises them.

That layer is also what gets cited by AI search, because a page that explains a topic and links to the specifics is the page worth quoting.

What this unlocks: a site where authority accumulates around topics instead of being spread thin across unrelated pages.