The back button: why breaking it frustrates visitors

Key takeaways

The back button is the most used navigation control on the web, and visitors expect it to take them to where they just were. Sites break it with redirects, filters that do not update the URL, pages that reload to the top and pop-ups that trap visitors. Make sure every meaningful view has its own URL and back always means back.

• Visitors rely on the back button to undo a wrong turn.
• Redirect chains and forced pop-ups break it.
• Filters and tabs should update the URL so back works.
• Long lists should keep the visitor's place on return.

Why does the back button matter so much?

The back button is how visitors undo a mistake. It gives them confidence to explore, because they know they can return. Nielsen Norman Group's heuristic of user control and freedom says users need a clearly marked emergency exit. When back fails, visitors feel trapped and often leave the site altogether.

• How clear website navigation improves user experience
• Nielsen's usability heuristics, applied to navigation

What breaks the back button?

Most breakages come from technical shortcuts. Each one turns a simple 'go back' into confusion.

• Redirects that send visitors forward again when they go back.
• Filters, tabs and search that change the page without changing the URL.
• Pages that reset to the top of a long list on return.
• Pop-ups or overlays that do not close with back on phones.
• Links that open new tabs, so back does nothing.

• Should website links open in a new tab?
• Infinite scroll vs pagination for business websites

How do you keep the back button working?

Give each meaningful view its own URL, so filters, search results and tabs can be returned to. Use permanent redirects only for moved pages, not as a way to route visitors. Make sure product and article lists restore the visitor's scroll position. Close full-screen overlays when visitors press back on phones.

Should you add your own back links?

In multi-step flows, such as booking or checkout, a 'Back' link at the top helps visitors return a step without losing their answers. The GOV.UK Design System recommends a back link in transactional journeys but not on ordinary content pages, where the browser button and breadcrumbs do the job.

• Breadcrumb navigation: does your website need it?

How do you test it?

Walk through your key journeys on a phone and a laptop, pressing back after every step: a filtered product list, a search, a booking form and a blog post opened from a list. Note any step where back does not return you to exactly where you were.

What does this look like in practice?

A pattern we see: a shop's category filters change the products without changing the URL. A shopper filters to their size, opens a product, presses back and finds the filters cleared. Writing filters into the URL brings them back to the filtered list.

• See client work
• Website Design & Development for UK businesses

Back button checklist

• Every filter, tab and search updates the URL.
• No redirect chains that bounce visitors forward.
• Lists keep the scroll position on return.
• Overlays close with back on phones.
• Back links in multi-step flows only.

• Product filters and faceted navigation for small shops
• Website dead ends: pages that leave visitors nowhere to go

Next step

Filter a list on your site, open an item and press back. Did you land where you left?