Google has made something very clear this month.

If your website interferes with the browser back button, even indirectly, it is no longer just a bad user experience. It is now a spam issue in Google’s eyes. On 13 April 2026, Google announced a new spam policy covering back button hijacking, with enforcement beginning on 15 June 2026. Pages using this behaviour may face manual spam actions or automated demotions in Google Search.

That might sound like a niche problem that only affects sketchy websites running obvious tricks. It is not. This is exactly the kind of update that can catch normal businesses off guard, especially if their site is held together with pop-up tools, third-party scripts, ad code, or bloated plugins that nobody has properly audited in months. Google has explicitly warned that some sites may be doing this unintentionally through third-party code, which is what makes this worth paying attention to.

What is back button hijacking?

Back button hijacking is when a page messes with normal browser history so the user cannot leave the site in the way they expect. Instead of returning to the previous page, they get pushed into another screen, another ad, another redirect, or a fake step in the journey that keeps them trapped longer than they intended. Google says this creates a frustrating and deceptive experience, which is why it has now added the tactic to its spam policies under malicious practices.

In plain English, if someone clicks onto your website and then tries to hit Back, Google expects that button to work properly. That should not be controversial, but plenty of websites have spent years trying to squeeze extra pageviews, ad impressions, or conversions out of users by making that journey harder. Google has now decided that enough is enough.

Why this matters more than it first appears

The obvious version of this problem is a spammy site running manipulative code on purpose. The less obvious version is a real business website using a cocktail of tools that create the same effect accidentally. That could be a badly configured pop-up plugin. It could be ad tech. It could be a redirect layer. It could be a script that inserts extra history states into the browser without the site owner ever realising what it is doing. Google’s own announcement makes that point directly. Some affected pages may not be trying to deceive users in a deliberate, coordinated way. They may just be technically messy.

That is why this update is more important than it looks. It is not just about obvious spam. It is about Google becoming less tolerant of behaviour that feels manipulative, even when the cause is lazy implementation rather than outright intent. SEO has been moving this way for a while. Search is no longer just about whether you can rank. It is increasingly about whether your site behaves in a way Google is prepared to trust.

What can actually happen if you ignore it?

Google has given sites a short grace period. Enforcement starts on 15 June 2026, and from that point, pages using back button hijacking can be hit with either a manual spam action or an automated demotion. In real terms, that means affected pages or even broader parts of a site may rank worse in Google Search.

That is the bit most businesses need to focus on. This is not a polite recommendation. It is a policy update with a date attached to it. Google is telling site owners to remove or disable this behaviour before enforcement begins.

If you rely on organic traffic, the smart move is not to debate whether your setup is “probably fine”. The smart move is to check it.

How does this kind of problem happen on normal websites?

A lot of business owners hear the word “spam” and assume the issue must be elsewhere. Usually, on a dodgy affiliate site, a hacked domain, or some terrible ad-filled publisher, they would never want to resemble. That is the comforting version of the story. It is not always the accurate one.

Normal websites end up with risky behaviour all the time. A conversion plugin gets installed because somebody wants more leads. A marketing tool adds an aggressive exit flow. A third-party script creates browser-history weirdness. A developer patches something quickly, and no one tests what happens when a user tries to leave the page. Months later, the site still “works” on the surface, but the experience underneath is clumsy, over-engineered, and harder for users to escape than it should be.

That is exactly why this policy matters. It targets a behaviour, not a website category. If your pages create the same deceptive outcome, Google is unlikely to care whether the code got there through deliberate trickery or thoughtless implementation.

What should you check right now?

Start with the obvious. Open your most important pages on desktop and mobile and test the back button properly. Not once. Repeatedly. Click into the page from Search or another site, interact with pop-ups, close overlays, move through forms, and then try to go back out. If the journey feels strange, sticky, or harder than expected, that is your first warning sign.

Then go a level deeper. Review third-party scripts, ad tags, pop-up tools, redirect logic, and any plugin that changes navigation behaviour. Pages that look clean visually can still create ugly browser-history behaviour underneath. This is one of those moments where technical SEO, UX, CRO, and development hygiene all overlap.

If you run a large site, do not assume the issue will be visible everywhere. It may only affect particular templates, campaign landing pages, ad-driven content, or pages carrying extra scripts.

Our modern ux-focused SEO Agency can help you understand all aspects of this update.

The bigger SEO story behind this update

This is not just a one-off spam story. It is part of a broader shift in how Google is defining search quality. The company is becoming more comfortable treating poor or manipulative experiences as trust problems, not just optimisation flaws. That means the line between “annoying UX” and “search risk” is getting thinner.

For years, parts of the industry operated on the assumption that if something improved conversions, it was probably worth testing until Google explicitly said otherwise. Google has now said otherwise. Back button hijacking is one more sign that the old separation between growth tactics and search quality is collapsing. If a tactic helps you squeeze more from the user by making the experience worse, there is a growing chance Google will eventually classify it as something more serious than bad taste.

This shift toward agentic search, where Google acts more like a task manager than a list of links, means it is becoming far more protective of the user’s journey.