Cookie Banners and the Back Button: Consent That Breaks Navigation
A consent banner that traps the back button leaves the visitor stuck on a page she wanted to leave. The fix is a history entry that should never have been created.
A visitor lands on a product page, declines the cookie banner, and hits the back button to return to the search results. Nothing happens, or the banner reappears, and she has to press back twice, then three times, before the browser finally leaves the page. She will not do that again. Next time she closes the tab.
The cause is a banner that writes a history entry when it opens, or a single-page app that treats the banner as a route. The back button is the most trusted control in the browser, and a consent tool that breaks it has broken the visitor's trust along with it.
How the banner hijacks the back button
Some consent tools open the preferences panel as a modal and push a history state so the back button closes the panel instead of leaving the page. That is a reasonable pattern for a modal, and a terrible one when the panel opens automatically on arrival, because the visitor who never asked for the panel now has to press back twice to leave a page she only just reached.
Single-page stores make it worse. The banner re-renders on every route change, and each render can add a history entry, so the back button walks the visitor through a stack of banner states instead of back to the page she came from. The visitor experiences it as a broken back button. The store experiences it as a bounce.
Why it matters beyond annoyance
A back button that does not work is a navigation failure, and navigation failures cost sales the same way a broken checkout does. The visitor who cannot leave a page cleanly is a visitor who will not come back, and she will not file a bug report. She will close the tab and buy elsewhere.
There is also a consent angle. A visitor who cannot leave without interacting with the banner is being pressured to make a choice in order to navigate, which is not a free choice. The banner should never be the price of leaving a page.
The fix, and the test
The banner should not push a history state when it opens automatically. If the preferences panel needs a back-button close behaviour, add the history entry only when the visitor opens the panel herself, and remove it when the panel closes. On single-page stores, the banner should render once per session, not once per route, and route changes should not re-trigger it.
Test it the way a visitor would. Arrive from a search result, decline the banner, and press back once. You should be back at the search results. If you are not, the banner is intercepting the navigation, and the fix belongs in the consent tool's configuration, not in the theme.
Related reading: Consent Banners on a One Page Checkout: No Second Screen to Fix a Bad Choice, Reject Buttons That Move, Shrink, or Fade: Reading a Banner Like a Regulator, A Practical Audit Checklist for Consent Mode Signals.
Frequently asked questions
Why does the back button stop working after a cookie banner?
Some consent tools push a history entry when the banner opens, so the back button closes the banner instead of leaving the page. On single-page stores the banner can re-render on every route change and stack more entries, so back walks through banner states instead of pages.
Is a broken back button a consent problem?
It can be. A visitor who cannot leave without interacting with the banner is being pressured to make a choice in order to navigate, which is not a free choice. The banner should never be the price of leaving a page.
How do I test back-button behaviour after consent?
Arrive from a search result, decline the banner, and press back once. You should return to the search results. If the banner reappears or nothing happens, the consent tool is intercepting navigation.
Should a consent panel push a history entry?
Only when the visitor opens it herself. If the panel opens automatically on arrival, it should not add a history entry, because the visitor never asked for it and will have to press back twice to leave.