How will Google punish back button hijacking?

Google classifies back button hijacking as spam

Google has moved to treat “back button hijacking” as spam, with enforcement set to begin in June 2026. The practice involves websites abusing the browser History API to trap users when they try to navigate away—so clicking the back button does not behave normally.

The change matters because it targets a specific, user-visible web behavior that frustrates navigation and can increase bounce or engagement in ways that reflect manipulation rather than content value.

What Google will do

Starting in the enforcement window, sites that interfere with users’ ability to use the back button can be demoted in Google Search. In practical terms, that means affected pages may lose ranking visibility, giving site owners an economic incentive to stop using this technique.

Why it matters for browsing

Back button hijacking undermines a core expectation of the web: navigation controls should work consistently. By defining the behavior as spam, Google is aligning user experience harms with its search-quality enforcement.

This also gives developers a clearer compliance bar: any design that “traps” users by overriding expected navigation may now carry SEO consequences.

What to do if you run a site

If a property uses History API tricks to force users through a funnel, it will likely need to be reworked to allow normal back-button navigation.

For users, the immediate impact may be delayed until enforcement starts, but the direction is clear: manipulated navigation behavior is being treated as a ranking issue, not just an accessibility or usability complaint.