Skip to content
Interface language: English
Design / Signal

Breadcrumbs: when they show the way and when they are just crumbs

Plan breadcrumbs around the site hierarchy and test labels, small screens, accessibility, Google data and direct entry.

Article language: English

People on terraces with coloured panels and tables overlooking water and hills.
In this article

A customer arrives from a search engine directly on a detailed service page. The page is elegant, but it is hard to answer a basic question: where am I? Breadcrumbs help people locate themselves in a site and move to a parent category. Their modest name conceals their ability to prevent a fair amount of wandering. They are worth examining on a site with a broad range of services; on a handful of equal-level pages they may simply be unnecessary.

Before adding a row of links above the heading, draw the content hierarchy. Breadcrumbs explain that hierarchy; they cannot repair an unclear division of services. Here is how to decide when to use them, choose labels and check the result on a phone and after a structural change.

A trail shows location, not visit history

The W3C breadcrumb pattern describes an ordered set of links to parent pages. The distinction matters: “Services > Design > Service websites” describes structure, not necessarily one person's sequence of clicks. A customer may have reached the final level directly from a message or search engine.

Do not build this trail from arbitrary browsing history. Someone who previously read an article about photography should not see it as the parent of an implementation service for that reason. The Back button and breadcrumbs have different jobs. In a long article, a table of contents and a way back to the reading position (in Polish) have another role: moving within the material instead of identifying its category. One returns through history; the other helps reach the appropriate content level.

In a hypothetical training company, a course may be reachable from a topic list, a calendar and the instructor's page. Decide which relationship forms the basis of the hierarchy. If more than one trail makes sense, describe the selection rule. Do not let the result depend on an editor's last click during publication.

Start with the information architecture of a B2B website (in Polish). Each breadcrumb level should have content worth opening. An empty category created solely to make the trail look attractive adds a stop without bringing anyone closer to an answer.

Check whether the hierarchy actually helps the task

Take several pages a customer might enter without knowing the site: a service detail, an article, an expert profile and a project description. Ask which broader group each belongs to and why someone would move there. A concrete answer suggests a possible use for breadcrumbs. If every trail points only to the home page, the benefit may be small.

For example, a reader finds a workshop whose date does not suit them and wants other training in the same field. A link to the relevant category helps more than a general return to the company's entire offer. In another case, after reading an article they want other guides on the same subject. Here too the category's meaning matters, not merely the presence of a trail.

Do not confuse a category with a list of tags. Content may concern several subjects, but a row of every label does not create a clear hierarchy. Related materials can appear separately. Breadcrumbs should answer “where am I?”, not provide the entire answer to “what is this associated with?”.

A person looking for a specific term will still benefit from internal search (in Polish). Breadcrumbs support movement through a known structure; search helps find a subject even when customers do not know your labels. The two mechanisms can complement each other rather than compete for space above the content.

Choose labels shorter than titles without losing meaning

A full page title may be too long for a narrow trail. You can prepare a shorter navigation label if it still recognisably identifies the same place. “Website design for service businesses” might become “Service websites” if the surrounding context does not suggest another meaning. “Solutions” on its own usually says too little.

Keep category names consistent with menus and headings. Customers should not have to wonder whether “Advisory”, “Consulting” and “Strategic support” are three departments or three names for the same group. Shortening should help reading, not create a second vocabulary used only above a heading.

The current page can appear as the last element without a link. If it remains a link, its current state should be marked appropriately. W3C also describes placing the trail in a labelled navigation region. Implementation details belong in the build, but acceptance can include checking whether a screen-reader user recognises this section's role.

A separator between labels need not be a separate control or extra information announced every time. Make sure it does not resemble a tiny button beside a large link. Choosing icons and labels (in Polish) discusses related distinctions. Separating levels should organise the trail, not multiply places to click.

On a phone, preserve context over full length

A long trail can take several lines above the title and push the actual content far down. Before shortening it, check whether every level is needed. Excessive length may result from the company's internal organisation being copied onto the site without assessing customer needs.

If the levels are justified, compare wrapping, shorter labels and showing the nearest parent. Each has a cost. An ellipsis can hide the part of a title that distinguishes it from others; hiding the entire middle can make the location harder to understand. Do not choose on an empty mock-up. Insert the longest real labels, including those in other languages.

If part of the trail is hidden, provide an understandable way to reach the remaining levels when needed. Do not make a control whose purpose can only be guessed by hovering. Check touch, keyboard and enlarged text. This section should work with the mobile menu (in Polish), not demand a separate set of gestures.

Assess spacing between links. Breadcrumbs are often styled as small secondary text, yet they remain actionable. A discreet appearance should not make the right level difficult to hit. If the separator is easier to tap than the category name on a phone, the hierarchy has acquired its own game of skill.

Do not reconstruct hierarchy solely from the URL

Parts of a URL are not always useful navigation levels. They may reflect old configuration, a publishing method or a technical content division. Before building breadcrumbs, check whether each proposed parent is a real page, has an understandable name and helps a task. Do not make customers tour folders just because those folders appear in an address.

Aeneia conceptual photography

The reverse can also happen: an article has a short address without a category but belongs to an organised topic collection. As a design recommendation, consider a trail based on that collection if it accurately explains where the content belongs. A short address does not automatically mean a flat information structure.

Try this on three sheets of paper: the name of the content being read, its nearest category and the broader section. Add what a visitor will see after opening each. If the parent description repeats the child or contains only an empty list, question the level. You may need a better category rather than a longer trail.

This distinction helps later technical changes. Moving content to another storage arrangement should not by itself change the message about its place in the offer. Record the relationship in editorial data and agree it with the person responsible for the structure, instead of reconstructing it each time from a link's appearance.

Separate the category from the active filter

On a project list, a customer may select an industry, service type and year. That set need not create three successive hierarchy levels. Filters describe the current selection; breadcrumbs show the list's place in the site. Combine them without explanation and a visitor may think changing one condition moves them to another part of the company.

Show active filters separately and clearly, with a way to remove them. Breadcrumbs can still lead to a broader list, but decide whether that movement keeps or resets the selection. There is no single rule for every catalogue. The effect should be predictable and testable. For a shop, develop this decision in the filter and results-state design (in Polish), keeping category location separate from current selection conditions.

In a test task, ask someone who entered a project detail directly to find work in another industry. Observe whether they understand the difference between returning to a category and restoring a previous set of filters. If the mechanisms do different things, their names and placement should explain that.

Check Google data separately from visible navigation

Google's BreadcrumbList documentation describes structured data explaining page hierarchy. In the documentation checked at the time, the breadcrumb display feature in search results applies to desktop. Visible navigation on the site can still be useful on a phone; these are two different uses of the same idea.

Structured data is a representation for systems reading the page. It does not replace visible links, and valid data does not guarantee a particular search-result appearance or ranking. When commissioning implementation, check both layers separately: use by customers and agreement between the data and actual content and addresses.

Prepare an example with the names and destination URLs for every level. Open them after publication, check the language and compare them with the hierarchy expressed in code. If the data still refers to the previous category, attractive navigation does not complete acceptance. Technical SEO before publication (in Polish) covers this more broadly.

Do not add artificial levels just to fill the structure. “Home > Best services > Premium offer > Contact” does not help if the middle elements are not real, useful places on the site. Data should describe an order, not replace it with a decorative story.

Maintain the trail when publishing and changing URLs

The relationship between parent and child pages must be maintainable in the publishing system. Decide who chooses a category, whether they can change it and what happens to the existing trail after the change. Manually entering every link in each article easily leads to inconsistency.

When the offer changes, check both destination addresses and the meaning of labels. A correct technical redirect does not necessarily provide good context. If “Open training” is replaced by an entirely different service, retaining it in an older item's trail may mislead even if every link opens a working page.

Include breadcrumbs as a source of internal links in a site migration that preserves addresses (in Polish). Test a sample across several levels, not just the home page. An old navigation link can survive a menu change when the two mechanisms draw information from different places.

On a multilingual site, the trail should remain in the current language and lead to the corresponding versions. Translating only the final title while leaving parents in another language is not enough. Combine these tests with acceptance of website language versions (in Polish).

Test entry without prior knowledge of the site

Give a tester a direct link to a deeper page. Ask them to identify its broader category, find a similar service and return to the material they were reading. Do not start them at the home page: the point is to check whether context works without first traversing the whole navigation.

An individual profile on a team page (in Polish) is one example. The visitor should understand whether they are looking at an expert profile, a group of people or a standalone article. A route to the team helps reveal the wider group, but related services can be shown separately. Not every useful relationship needs to become another breadcrumb level.

After moving to the parent, check the opened page's name too. If the trail says “Training” and the destination shows a broad “Work with us” page, a visitor may wonder whether they arrived in the right place. This mismatch does not always mean a broken link, but it needs assessment. The two names should explain their relationship without requiring knowledge of the company's internal divisions.

Record misunderstandings and places where labels do not meet expectations. If nobody understands a category, first improve its name or division. Enlarging the separator will not solve a conceptual problem. When the trail works, retain the test as a reference for the next major site change.

Want to organise the hierarchy and the path to the right service? See Aeneia Design's scope.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear