On this page
Published: September 10, 2026
Breadcrumbs look simple until the page title, navigation label, and URL all describe the same place differently. Settle those differences in the brief instead of asking a developer to guess.
Record every level
For each page, list the breadcrumb label, destination, and position. Say whether the current page is linked. Include rules for filtered listings, paginated archives, campaign pages, and pages with more than one plausible parent.
Use the visitor's hierarchy
A breadcrumb should explain where the page sits in the published site. It should not expose CMS folders or internal department names. Keep labels short, but do not shorten them so far that two destinations become hard to distinguish.
Test the rendered trail
Compare the visible trail with the approved map. Activate every linked level by keyboard, check focus styles, inspect wrapping at narrow widths, and confirm structured breadcrumb data uses the same order and destinations. Record exceptions rather than silently changing the pattern.
Further reading
Related Articles
Keep this decision with the approved page brief and acceptance record.
Ready to plan your next step?
Contact WebsiteDesignOutsource.com
Turn the guidance into a reviewable handoff
Record the owner, input, acceptance condition, evidence, and escalation point before production begins. That small contract makes the work easier to inspect and approve.
Plan a website production handoff