Wayfinding
Date: 2026-08-17
Knowing where you are, how you got here, and what’s nearby. Borrowed from physical environments, and the useful part is that it treats orientation as a continuous need rather than a navigation feature.
Wayfinding is the set of cues that let someone maintain orientation while moving through a space. In an interface it answers three questions continuously:
WHERE AM I?
HOW DID I GET HERE?
WHERE CAN I GO?
Navigation is what you provide; wayfinding is whether it works. A site can have a complete menu and still leave people lost — Navigation Patterns.
The cues
LANDMARKS recognisable, consistent
elements — the header,
the logo, the basket
→ "I'm still on the same
site"
PATHS breadcrumbs, back, the
trail you took
DISTRICTS visually distinct sections
→ trade vs consumer,
editorial vs shop
SIGNS labels, headings, page
titles
EDGES where one area ends and
another begins
The most-missed cue is the current-location marker. An active state on the navigation is a one-line change and it’s absent on a large share of sites.
Deep entry is the normal case
The assumption that breaks most wayfinding: people do not enter through the front door.
ENTRY POINTS
search results → a product page
an email link → a category
a shared URL → anywhere
an ad → a landing page
Most visitors’ first page is not the home page. They arrive with no context about what else exists, so every page has to orient someone who has never seen the site.
EVERY PAGE NEEDS
what site is this logo, header
what page is this H1, title
where does it sit breadcrumbs
what else is there navigation
what should I do a clear primary
action
Breadcrumbs do the most work here for the least effort — one line providing structure, context and an upward route for someone who landed cold — Information Architecture.
Where orientation is lost
MODALS AND OVERLAYS
the page behind is obscured; escape
routes unclear
INFINITE SCROLL
no sense of extent, position lost
on return
FILTERED VIEWS
"am I still in Skincare, or is this
everything?"
→ show applied filters persistently
— Faceted Filtering
CHECKOUT
navigation stripped for focus, which
also strips orientation
→ keep the logo, show progress
— Checkout Design
SEARCH RESULTS
a flat list with no relationship to
the structure
See: Faceted Filtering · Checkout Design
The back button restoring scroll position is the single most common wayfinding failure in retail, and it’s a technical fix rather than a design one — a visitor who returns from a product to the top of an unrestored category list has lost their place entirely — Category Page Design.
Design consequences
- Keep landmarks fixed. The header in the same place, the logo always linking home
- Mark the current location in navigation, always
- Breadcrumbs on every page below the top level
- Persistent applied-filter chips, individually removable
- Progress indicators in multi-step flows, and honest ones
- Restore state on back — scroll position, filters, sort
- Page titles that describe the page, not the brand.
Sensitive Skin Cleansers | BrandbeatsBrand | Shop
Where it differs on mobile
Less screen means fewer persistent cues, so the ones that remain matter more:
STICKY HEADER even a minimal one
BOTTOM BAR primary destinations
in thumb reach
— Mobile Interaction Patterns
BREADCRUMBS often dropped for space,
and often shouldn't be
FILTER CHIPS essential — the applied
state is otherwise
invisible behind a panel
See: Mobile Interaction Patterns
The test
Open any page cold, with no history, and answer the three questions. If a page can’t tell someone where they are and what else exists, it’s relying on a journey that most visitors didn’t take — which is testable directly in Usability Testing by starting a participant on a deep page rather than the home page.