Google adds a new spam policy targeting back button hijacking
Google has announced a new spam policy that explicitly treats back button hijacking as a violation of its malicious practices rules. The announcement was published on the Google Search Blog, with enforcement scheduled to begin on 15 June 2026. You can read the original announcement here: https://developers.google.com/search/blog/2026/04/back-button-hijacking.
The key point is straightforward: if a site interferes with a user’s ability to navigate back to the previous page using the browser’s back button, Google may apply manual spam actions or algorithmic demotions that reduce visibility in Search.
What Google means by “back button hijacking”
How the behaviour works in practice
Back button hijacking happens when a page manipulates browser history so that pressing the back button does not return the user to the page they just came from. Instead, the user may be redirected to a different page they did not choose, such as an advertisement, an interstitial, a “recommended” page, or another step in a funnel.
Why Google classifies it as a malicious practice
This pattern creates a mismatch between a user’s intent and the result they receive. Users expect the back button to be reliable. When it is not, people feel trapped, misled, or pushed towards actions they did not choose. Google is treating this as a deceptive tactic rather than a mere usability flaw, which is why it is being placed under spam policy enforcement rather than general quality guidance.
Enforcement dates and what to expect
When enforcement begins
Google has stated enforcement will start on 15 June 2026, and the policy has been published ahead of time to give site owners space to identify and fix issues. That lead time is a signal that Google expects this to be relatively common, including on sites where the behaviour is introduced unintentionally through third-party scripts.
How penalties may appear in Search
Google has indicated that violations can trigger manual actions or automated demotions. Practically, that can mean a sudden loss of rankings for affected pages, reduced ability to appear for competitive queries, or suppressed visibility until the behaviour is removed and, where relevant, reconsideration steps are completed. If the hijacking is present on templates, the impact can spread across large sections of a site.
What this means for SEO teams and site owners
User experience is now directly tied to spam enforcement
Technical SEO has always cared about smooth navigation, but this policy raises the stakes. Back button reliability is now a compliance issue as well as a usability concern. Sites that previously “got away” with aggressive retention tricks may find that the cost outweighs any conversion uplift they believed it delivered.
Rankings risk can come from third-party tags, not just your own code
Many instances of back button hijacking are introduced by ad networks, pop-up providers, recommendation widgets, affiliate toolbars, A/B testing tools, or poorly configured analytics events. Even if a marketing tag is the source, the site hosting it is still responsible for the resulting behaviour.
Engagement metrics cannot justify deceptive navigation
Some teams attempt to improve pageviews per session by forcing extra steps, loading new pages on back navigation, or inserting “one more page” into the journey. This update makes it clear that any gains achieved by interfering with expected browser behaviour are not sustainable and can lead to visibility loss.
Common technical patterns that can trigger back button hijacking
History API misuse
Single-page applications and JavaScript-heavy sites often use the History API. When implemented incorrectly, scripts may repeatedly push new states or override popstate handling so that the back button either loops or routes users to content they did not request.
Forced interstitials and redirect chains
Some pages insert an interstitial or an alternative destination when the user tries to leave. If this occurs specifically when users attempt to go back, it can resemble a trap rather than a normal redirect.
Exit-intent overlays that tamper with navigation
Exit-intent tools should not change history entries to keep users on-site. If an overlay triggers a state push that alters the back-stack, users can be forced through additional steps when attempting to leave.
How to audit your site before 15 June 2026
Test real user journeys, not just isolated pages
Start from Google traffic-like entry points such as landing pages, category pages, and popular articles. Click through to a second page, then use the back button. Repeat on mobile browsers as well as desktop. If the back button does anything other than return to the exact prior page, treat it as a priority issue.
Check for template-level scripts and tag manager changes
Review recent deployments and tag container updates. Back button hijacking often arrives through “small” tag changes that were not part of a code release. Pay close attention to scripts that run on every page, including header bidding, affiliate tracking, remarketing tags, and content recommendation widgets.
Investigate anomalies in navigation and session paths
If analytics shows unusual loops, repeated hits to the same URL during back navigation, or spikes in sessions that include an unexpected page between two normal steps, that can be an indicator that history is being manipulated.
Fix approaches that preserve conversions without breaking trust
Use standard UX patterns instead of trapping behaviour
If the goal is to keep users engaged, focus on visible, user-controlled options such as related links, “continue reading” modules, and clear next-step calls to action. These encourage deeper browsing while leaving the browser controls intact.
Make overlays dismissible without altering history
Promotional overlays can still exist if they are not forced through navigation changes. Ensure closing an overlay returns users to the same page state, and pressing the back button returns them to the previous page rather than triggering a new, unrequested destination.
For JavaScript frameworks, validate history and routing behaviour
For SPAs, confirm that each navigation action corresponds to a meaningful history state and that back/forward works predictably. Avoid excessive state pushes and ensure popstate handlers do not rewrite routes in a way that sends users elsewhere when they attempt to go back.
Questions and answers for SEO and engineering teams
Does this affect single-page applications more than traditional sites?
SPAs can be at higher risk because they rely on client-side routing, but traditional sites can violate the policy just as easily through ads, interstitials, and third-party scripts. The deciding factor is the user outcome when pressing back, not the technology stack.
What if the behaviour is caused by an advertising partner?
You should still treat it as your issue to resolve. Remove or disable the script, adjust configuration, or change providers. If a partner cannot guarantee normal back-button behaviour, that partner becomes an SEO liability.
Could a harmless redirect be mistaken for hijacking?
Normal redirects for canonicalisation, protocol changes, or moved content are common and expected. Hijacking is characterised by manipulation that prevents returning to the prior page or redirects users to pages they did not choose when they attempt to go back.
How quickly can rankings recover after a fix?
Recovery depends on whether the site receives a manual action, the scale of the issue, and how quickly Google reprocesses changes. The safest approach is to fix issues well before enforcement begins and to verify behaviour repeatedly after deployments.
Practical examples of compliant alternatives
Replacing a back-button trap with an on-page retention offer
If a page currently pushes a “recommended article” into the back history, replace that with a visible section near the end of the content that suggests related reading. Users can choose it, and the back button continues to work normally.
Replacing forced ad redirects with respectful monetisation
If an ad script redirects users when they try to leave, remove that behaviour and use placements that do not interfere with navigation, such as in-content units, sticky but dismissible banners, or standard display ads that do not manipulate browser history.
What to do next
Create a pre-enforcement checklist and ownership
Assign responsibility across SEO, engineering, and advertising operations to test key templates and top landing pages, identify any back button interference, and remove or replace the offending code. Treat this as a release-blocking issue until resolved, because the downside is a direct loss of search visibility once enforcement begins.
