Discussion starter: a publisher and community SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.
- News SEO
Back button hijacking is now a spam policy. Which recirculation or exit-intent patterns have you found crossing that line?
Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.
1 reply
-
adminAdmin
The patterns that cross the line are the ones that change what happens when a user presses the back button, so they do not return to where they came from, usually the search results, and instead land on an ad page, a recirculation page or more of your content. Google added back button hijacking to its spam policies in April 2026. In practice that covers scripts that insert extra entries into the browser history, intercept the back action to show a full-page “before you go” screen, or redirect users on back to other content. Ordinary recirculation, such as related article modules, end-of-article recommendations and exit-intent overlays that close normally without touching navigation, is a different category, although intrusive overlays carry their own user experience risks.
Where the line falls
Pattern Assessment Script adds fake history entries so back leads to a recirculation or ad page Crosses the line Back action intercepted to show a full-page interstitial before leaving Crosses the line Back leads to a redirect to another article or offer Crosses the line Related articles and recommendation widgets within the page Fine Desktop exit-intent overlay that closes normally and does not affect navigation Not back button hijacking; can still harm user experience Infinite scroll that updates the URL as readers move to new articles Review carefully: if one or two back presses no longer return the reader to the search results, reconsider the implementation Where these patterns hide
Publishers rarely write back button hijacking themselves. It usually arrives through third-party scripts: recirculation vendors, ad-tech partners and “engagement” tools that promise more page views. Some vendors have used history manipulation because it produces impressive page-view numbers. A publisher can be exposed to the policy without anyone in the newsroom knowing the behaviour exists.
How to audit your pages
- Test the real journey. Search for one of your articles, click through from the results, and press back. You should return to the results immediately. Repeat on mobile and desktop, and on several templates.
- Count back presses. If it takes more than one press to return, find out why.
- Inspect history activity. In browser developer tools, watch for history entries being added without navigation, and for handlers that react to the back action.
- Test with scripts disabled one by one. Identify which vendor script causes the behaviour.
- Review contracts and configurations for recirculation and ad partners, and ask vendors directly whether their scripts modify browser history.
Hypothetical example:
A lifestyle publisher’s page views per session rose noticeably after it installed a recirculation widget. After the April 2026 policy, the SEO team tests the journey from search results and finds that pressing back on mobile shows a full-screen “You might also like” page instead of returning to Google. The behaviour comes from the widget’s “exit recovery” feature, enabled by default. The team disables it. Page views per session fall back towards their previous level, which also reveals that the earlier gain was mostly readers trying to leave.
Watch for this:
Metrics inflated by back button manipulation mislead the business as well as users. Engagement and page-view figures that rose after installing an engagement script deserve scrutiny; if the increase came from blocking exits, it was never real engagement.
Build the check into governance
Because the behaviour usually comes from vendors, a one-off audit is not enough. Add a back-button test to the checklist for approving any new third-party script, and to release checks for templates that load recirculation, ad or engagement tools. Ask vendors to confirm in writing that their scripts do not modify browser history or intercept navigation, and check that exit-recovery or similar features are disabled by default in your configuration. Re-test after vendor updates, since features can be switched on in new versions. Someone on the product or SEO team should own this check, with the authority to remove a script that fails it.
Why the policy exists
From a searcher’s point of view, being unable to return to the results is one of the most frustrating experiences on the web, and it also distorts the signals publishers use to judge their own performance. Google’s decision to treat it as spam reflects that it harms users directly. Publishers who have relied on these tools for page views should expect lower engagement numbers after removing them, and should treat the new, lower numbers as the honest baseline to improve from.
Better recirculation that stays within the rules
- Relevant related articles placed where readers finish a section, not only at the very end.
- Topic hubs and series navigation that give readers a reason to continue.
- Newsletter sign-ups offered in the page, not as a barrier on exit.
- Clear, fast pages that make readers want to come back, which is what recirculation is supposed to achieve.
Any pattern that stops the back button taking readers back where they came from is now a spam policy risk. Audit the real journey from search results on every template, find the scripts responsible, switch off exit-recovery features, and build recirculation that readers choose rather than cannot escape.
Need help with this on your own site?
Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.
Add a reply Cancel reply
Replies are open to approved members. Log in or apply to join.