Breadcrumbs and Site Navigation: A Practical Guide for Crawlable Websites

What are breadcrumbs?

Breadcrumbs are a row of links, usually near the top of a page, that shows where the page sits in the site hierarchy. A typical trail reads Home > Blog > Navigation, with each level linking to its parent page. Google describes a breadcrumb trail as an indicator of the page’s position in the hierarchy, and says it may help users understand and explore a site.

What is site navigation?

Site navigation is every route that helps visitors find pages, including the main menu, footer links, sidebars, search, and links inside the content. The main menu is the primary route. Other elements support it. A visitor may use more than one in a single visit, so they should not contradict each other.

How do breadcrumbs support the main menu?

Breadcrumbs support the main menu by giving a second, lighter way to move up the hierarchy without opening the menu or using the back button. They do not replace the menu. A visitor who lands on a deep page from a search result can use the trail to reach the parent category in one click. The menu then remains the primary route for moving across to other sections.

Do breadcrumbs help SEO? What Google says and does not say

Google presents breadcrumbs as a way to help users understand a page’s position and, through markup, to categorise the page in search results, but it does not claim that breadcrumbs raise rankings. Breadcrumb links also add internal links that reinforce your hierarchy, which is a sensible part of website SEO. Some blogs claim large gains in rankings or engagement. I could not verify those claims from Google, so I treat them as unproven. Judge breadcrumbs by usability first.

Hierarchy-based breadcrumbs

Hierarchy-based breadcrumbs show the page’s fixed position in the site structure, from the home page down to the current page. An example is Home > Services > Web Design. This is the most common type and the one most websites need. It works like folders on a computer: each level is broader than the one below it.

Attribute-based breadcrumbs

Attribute-based breadcrumbs show the categories, tags, or product features that describe the current page. They suit sites where one item can belong to several groups. A shop might show Shoes > Running > Waterproof, where the last two steps are attributes the visitor has chosen. For an e-commerce business, this type can help visitors narrow a large catalogue. Be careful with attributes that create many near-duplicate URLs.

Path-based breadcrumbs

Path-based breadcrumbs show the route a visitor took to reach the page, such as a “Back to results” link. The trail changes with each visit, so it does not describe the site hierarchy. It is less common, and it is better suited to search results than to content sites. Do not use it as a replacement for a hierarchy trail.

Which type fits your site?

Choose hierarchy-based breadcrumbs for most blogs, service sites, and corporate sites, and add attribute-based trails only where visitors filter large catalogues. If a page can appear under several parents, pick one main trail and keep it stable. Path-based trails rarely suit a site where visitors read articles or compare services.

[Image Placeholder – Paste Your image here]

Start from your site architecture and topic clusters

Group pages by topic and by the way visitors think about them, and let each group become a level in the hierarchy. A topical map is a useful starting point because it already groups pages into clusters with a clear parent. Each cluster can become a category page, and each article beneath it can show that category in its trail. Keep the number of levels low, and avoid levels that exist only to hold one page.

Match breadcrumb labels to page titles and URLs

Use short labels that match the page’s main name, so the trail, the page heading, and the menu all use the same words. If the menu says “Web Design” and the trail says “Design Services”, visitors have to stop and think. Google’s guidance adds a useful point: it recommends breadcrumbs that represent a typical user path, not a copy of the URL structure. A clean URL still helps, and Google’s URL structure page explains how to write readable ones. The trail does not need to mirror every folder in the address.

What if a page sits in more than one category?

Choose one main trail for the visible breadcrumb, and use the same trail every time a visitor opens that page. Google’s documentation does allow multiple breadcrumb trails in markup when a page can be reached in more than one way. Even so, a visible trail that changes unpredictably confuses visitors. Decide which parent is the primary one, and link to secondary categories from the content instead.

How deep should a breadcrumb trail be?

Keep the trail to the levels that genuinely exist, and aim for three or four steps in most cases. This is a practical guideline, not a rule from Google. If a trail needs six or seven steps, the site structure is probably too deep. Cutting labels will not fix that. Review the structure instead.

Placement, size, and separators

Place the trail at the top of the page content, below the main menu, in smaller text than the menu. Most sites use a greater-than sign or a slash between levels. The exact symbol matters less than consistency. Put the home page first and the current page last, so the trail reads from broad to specific.

Why the current page should not be a link

The last item should show the current page as plain text, because a link to the page the visitor is already on adds nothing. It also invites a pointless click that reloads the page. Keep the text styled differently from the links so visitors can tell which items are clickable.

How should breadcrumbs work on mobile?

On mobile, keep the trail to one line, and show the nearest parent page first if the full trail does not fit. This is practical guidance rather than a Google rule. Make the links large enough to tap comfortably, and avoid wrapping that pushes the page heading far down the screen. Google’s breadcrumb page states that the search feature is available on desktop, so the on-page trail matters most for your visitors, not for the search listing.

Accessibility: nav landmark, label, and current-page marking

Accessible breadcrumbs sit inside a labelled navigation landmark, and the link to the current page carries aria-current=”page”. This follows the W3C breadcrumb pattern, which asks for a navigation landmark with a label. Use an ordered list, because the order carries meaning. Add the separators with CSS so a screen reader does not read each symbol aloud. If the current page is plain text rather than a link, the W3C says aria-current is optional.

Visible breadcrumbs vs. Breadcrumb List markup

Visible breadcrumbs are links on the page for visitors, while Breadcrumb List markup is code that describes the same trail to search engines. They are two separate things. A site can have a visible trail with no markup, or markup with no visible trail. Keep them aligned, because markup that describes something visitors cannot see goes against Google’s structured data guidelines.

A JSON-LD example for one breadcrumb trail

A single trail needs a Breadcrumb List with ordered List Item entries, each with a position, a name, and, except for the last item, a URL. The example below follows Google’s pattern for a page called “Breadcrumb Guide”:

{ “@context”: “https://schema.org”, “@type”: “Breadcrumb List”, “item List Element”: [

{ “@type”: “List Item”, “position”: 1, “name”: “Guides”, “item”: “https://example.com/guides/” },

{ “@type”: “List Item”, “position”: 2, “name”: “Navigation”, “item”: “https://example.com/guides/navigation/” },

{ “@type”: “List Item”, “position”: 3, “name”: “Breadcrumb Guide” } ] }

Google says you do not need a list item for the site’s top level or for the page itself. If the last item has no URL, Google uses the URL of the containing page.

Multiple breadcrumb trails for one page

If a page can be reached through more than one route, Google allows several Breadcrumb List blocks on the same page. Its example shows one trail through Books and Science Fiction, and another through Literature. Use this only when both routes genuinely exist on your site, and keep one visible trail as the main one.

How do you test breadcrumb markup?

Test with Google’s Rich Results Test, then use the URL Inspection tool and the rich result status report in Search Console. Google advises fixing critical errors before release, and it notes that re-crawling can take several days. It also says that structured data does not guarantee a rich result. Page markup that breaks the guidelines can lead to a manual action, so avoid adding breadcrumb code that does not match what visitors see.

Right-to-left sites, such as Arabic

On a right-to-left page, the trail should start at the right with the home page and read leftwards, because it follows the reading direction. Set the page direction with the HTML dir attribute, and make sure the separator symbols face the correct way. A greater-than sign that points the wrong way suggests the trail runs backwards. These are practical points that I recommend testing with native readers, since I have not verified them against a single authoritative source.

Multilingual sites across Europe and Asia

Each language version needs its own labels, its own parent links, and its own markup, so a German page links to German parents and not English ones. Mixed-language trails confuse visitors, and they muddle the hierarchy. If the structure differs between languages, show the trail that matches the page the visitor is reading.

Labels and URLs for each language version

Write breadcrumb labels and URL words in the language of the page, and link each version to its matching alternatives. Google’s URL guidance advises using words in your audience’s language in URLs, and suggests a structure that makes geotargeting easy for multi-regional sites. Google also provides guidance on how to tell it about localized versions of a page. Read that guide before you add language folders.

CMS themes and plugins

Use the theme or plugin that your platform already provides, and then check what it outputs on the page. Google’s documentation notes that when you use a CMS, a plugin integrated into the CMS may be easier than writing markup by hand. Not every plugin outputs the markup in the same way, so test a few pages. Check that the trail matches your hierarchy, that the current page is not a link, and that the markup does not duplicate itself.

A simple custom HTML pattern

A custom breadcrumb is a labelled navigation element containing an ordered list of links, with the last item marking the current page. This is the structure that the W3C pattern describes:

<nav aria-label=”Breadcrumb”>

<ol>

<li><a href=”/guides/”>Guides</a></li>

<li><a href=”/guides/navigation/”>Navigation</a></li>

<li><a href=”/guides/navigation/breadcrumbs/” aria-current=”page”>Breadcrumb Guide</a></li>

</ol>

</nav>

Style the list so the items sit in a row, and add the separators with CSS.

A pre-publish checklist

Answer yes to every item below before a page goes live.

1. Does the trail start at the home page and end with the current page?
2. Does every level link to a real, working page?
3. Is the current page shown as plain text, or marked with aria-current=”page”?
4. Are the labels short and the same as the page names used in the menu?
5. Is the trail no more than three or four steps deep for a typical page?
6. Does the page use one main trail, even if it belongs to several categories?
7. Is the trail inside a labelled navigation landmark and an ordered list?
8. Does the Breadcrumb List markup match the visible trail?
9. Does the trail fit on one line on a phone, with links large enough to tap?
10. On multilingual pages, are labels, links, and direction correct for that language?

How do you audit breadcrumbs with a crawler and Google Search Console?

Crawl the site with a tool such as Screaming Frog to see the breadcrumb links on every page, then check Google Search Console for markup errors. A regular technical SEO and audit routine can include these checks:

• Look for breadcrumb links that return errors or redirect.
• Find pages that have no trail, or a trail that differs from similar pages.
• Open the rich result status report for breadcrumbs in Search Console to see valid and invalid items.
• Use the URL Inspection tool on a sample page to check that Google can read the markup.
• Compare the trail on each page with your planned hierarchy, and note the pages that break the pattern.

Fix template-level problems first, because one change to a template can correct hundreds of pages.