Google’s back-button hijacking policy is now enforceable. Google announced the policy on April 13, 2026, and said enforcement would begin on June 15, 2026. For small business websites, this is less about obscure SEO theory and more about basic website trust. If your site, ad tools, or third-party scripts interfere with the browser back button, Google says that can lead to manual spam actions or automated demotions.

What Google means by back-button hijacking

According to Google Search Central, back-button hijacking happens when a site interferes with browser history so a visitor cannot immediately return to the page they came from. Instead, people might be pushed into pages they never visited, shown unwanted recommendations or ads, or otherwise blocked from normal browsing.

Why this matters for small business websites

Most small businesses are not intentionally building deceptive navigation. The risk is that the behavior can come from old scripts, ad tools, popups, or third-party code that nobody has reviewed in a while. Google explicitly says some cases may come from included libraries or advertising platforms.

• A bad script can damage trust before a visitor ever calls you.
• Search visibility can suffer if Google treats the behavior as spam.
• The problem can sit quietly inside plugins, theme code, or ad configurations.

What website owners should check now

1. Test your main pages on desktop and mobile, then use the browser back button after opening a page from search or another site.
2. Review popup, ad, affiliate, recommendation, and redirect tools that modify browser history.
3. Look at any scripts added by third-party vendors, especially older lead-generation or monetization tools.
4. Remove or disable anything that inserts deceptive pages into browser history or blocks a clean return path.

Where problems often hide

In practice, this kind of issue is often buried in legacy JavaScript, aggressive ad settings, tracking layers, or a plugin that tries too hard to keep people on-site. If the website has gone years without a technical cleanup, this is a good reason to inspect it now.

FAQ

Can a plugin or ad platform cause this?

Yes. Google explicitly says some instances may come from included libraries or advertising platforms, which is why site owners need to review third-party code as well as their own pages.

Can this affect search rankings even without a manual action?

Yes. Google says pages engaging in this behavior may face manual spam actions or automated demotions, so the risk is not limited to one type of enforcement.

What to do if your traffic drops or you get a warning

Google says sites engaging in back-button hijacking may receive manual spam actions or automated demotions. If you fix a manual-action issue, Google says you can submit a reconsideration request in Search Console. That is one more reason to keep Search Console active and reviewed instead of treating it like a set-and-forget tool.

Where CodeForce would focus first

We would start with the pages that matter most for leads: the homepage, service pages, booking flow, and any page using heavy scripts or ads. If the site has old plugins, extra redirect code, or odd mobile behavior, a practical website review or WordPress cleanup is a better move than guessing.

Bottom line

Google’s back-button hijacking policy is not a warning for honest websites to panic. It is a reminder to test the real user experience, especially on pages shaped by third-party tools. If the back button feels broken, manipulative, or confusing, fix that now before Google does it for you.

Source: Google Search Central: Introducing a new spam policy for "back button hijacking"