We’re tightening our spam policies. Starting now, a tactic called “back button hijacking” is explicitly classified as a malicious practice. If your site uses it, expect spam actions—like removal from search results—to follow.

What is back button hijacking?

It’s when a site manipulates the browser history or user flow so that clicking the “back” button traps the visitor on the page, redirects them to an unwanted ad, or forces a reload instead of letting them leave. For example, a user tries to return to Google but gets stuck on a landing page or an interstitial ad.

This isn’t new, but until now the policy was less specific. The update makes it a clear, enforceable violation in Google’s spam guidelines.

Why it matters for your business

If you run an e‑commerce store, a booking system, or even a simple business website on Cyprus, this affects your SEO directly. Google’s systems now flag hijacking patterns automatically—human reviewers may also check. A spam action can tank your organic traffic overnight. For small and medium businesses depending on local leads, that’s a serious blow.

Common implementations to avoid:

  • Using JavaScript to push fake history entries every few seconds.
  • Intercepting the popstate event to redirect to a different page.
  • Showing a “confirm exit” overlay that doesn’t actually allow exit.
  • Loading a page that immediately forwards again on back-navigation.

Practical implications for Cyprus/EU sites

If you’re developing a new site or updating an existing one, check your front-end code—especially if you use third-party cookie banners, lead capture modals, or video ads. GDPR compliance already requires clear consent and user control; hijacking the back button violates both. Also, if your audience is multi-language (English, Russian, Greek), note that this policy applies uniformly across all languages. No workaround exists.

Our team at 62px reviews client projects for such patterns before launch. The fix is usually straightforward: remove any script that overrides standard navigation, test on mobile and desktop, and ensure the back button behaves as users expect.

Cost to fix? Minimal—often a few hours of developer time, unless the hijacking is deeply integrated into a legacy CRM or booking system. Either way, the cost of ignoring it is far higher.

Stay clean. Your users—and Google—will thank you.