You know that thing on news sites where pressing Back hijacks you to some pointless "recommended article" page? Finally classified as spam!!

In April 2026, Google announced that interfering with the browser's Back button — a practice known as "back button hijacking" — will be treated as a clear violation of its search spam policy. Enforcement begins on June 15, 2026, and sites with offending implementations may face ranking demotions or manual actions in search. Good riddance — never come back!

What Is Back Button Hijacking?

Back button hijacking refers to techniques that prevent users from returning to the previously viewed page when they press the browser's Back button.

According to Google: "When users click the Back button, they have a clear expectation that they will be returned to the previous page. Back button hijacking betrays this fundamental expectation." Couldn't agree more.

Common patterns include:

  • Forcibly redirecting the user to a page they never visited
  • Inserting "recommended content" such as related articles or ads in between
  • Forcing users to press Back multiple times to leave the site
  • Injecting fake history states into the browser history

Many readers have probably experienced this on news sites and certain media outlets — finishing an article from search results, hitting Back, and being shown a list of "recommended articles" instead of the previous page.

Google points out that such implementations interfere with browser functionality and disrupt the user's expected actions.

Added to the "Malicious Practices" Category

With this update, Google explicitly classifies back button hijacking as a violation under the existing spam policy's "malicious practices" category. (Yes!)

This category already covers behaviors such as malware distribution and the installation of unwanted software, and back button hijacking is now treated alongside them.

In its official blog, Google emphasized prioritizing user experience and explained that back button hijacking interferes with browser functionality and frustrates users.

The company also noted that when users feel they are being manipulated, they tend to become more reluctant to visit unfamiliar sites. Notably, this revision does not introduce a new category but instead extends the existing policy.

Source: Google Search Central Blog, "Introducing a new spam policy for 'back button hijacking'" — https://developers.google.com/search/blog/2026/04/back-button-hijacking

Enforcement Starts June 15, 2026

Google is providing roughly a two-month grace period after the policy announcement, with formal enforcement beginning on June 15, 2026. During this window, site owners are expected to remove or disable any problematic scripts or implementations.

Pages judged to be in violation may be subject to measures such as algorithmic automated demotions.

Google has already begun sending warning emails to affected site owners through Search Console. The emails include sample URLs where issues were detected, along with a link to the blog post explaining the new policy, urging recipients to address the problem before the June 15 enforcement date.

If a site is fixed before enforcement begins, Google states that it will reassess the site and make a fresh determination.

Third-Party Scripts Are Also the Site's Responsibility

One important point: Google has made it clear that even when back button hijacking originates from external libraries or ad platforms, the responsibility lies with the site itself.

Site owners are required to review the technical implementations they have deployed and remove or disable the relevant code, imports, and settings.

Sites that use ad-serving scripts, content recommendation widgets, or third-party engagement tools should audit each integration before the June 15 enforcement date.

Even sites built as Single Page Applications (SPAs) using frameworks such as React, Vue, or Angular may unintentionally fall into back button hijacking territory depending on how they handle the History API.

Conclusion

Manipulating the browser's Back button has long been one of the most disliked "dark patterns" among web users. Google's new stance puts a clear stop to UX-damaging implementations by tying them to a tangible search penalty.