For years, pressing the back button in your mobile browser after clicking a Google Search result has felt subtly broken. You tap back, expecting to return to your search results. Instead, you land on a strange intermediate page — a Google redirect that flickers for a moment before bouncing you to the results you actually wanted. It’s not a bug. It’s by design.
And now, after a complaint filed with European regulators and growing scrutiny from developers and privacy advocates, the practice is getting the attention it deserves.
Android Authority published a detailed investigation into how Google Search on mobile browsers inserts extra entries into the browser’s navigation history — effectively hijacking the back button to keep users within Google’s orbit for just a little longer. The mechanism is technical but the effect is simple: when you click a search result, Google doesn’t just send you to that website. It routes you through a redirect URL first. That redirect creates an additional history entry. So when you hit back, you don’t land on the search results page. You land on the redirect, which then pushes you forward again to the page you just left — or, in some cases, back to Google’s results after a second tap.
Two taps instead of one. A fraction of a second of extra Google face time. Multiply that by billions of searches per day, and the implications become enormous.
The Mechanics of a Redirect That Shouldn’t Exist
The technical underpinnings are straightforward. When a user performs a Google search on a mobile browser — Chrome, Firefox, Safari, it doesn’t matter — and taps on an organic result, the click is intercepted by JavaScript. Rather than navigating directly to the destination URL, Google’s code sends the user through an intermediary redirect, typically a URL beginning with google.com/url?. This redirect logs the click, then forwards the user to the intended site.
The problem is what this does to the browser’s history stack. The redirect page gets pushed as a separate entry. So the history now reads: search results → redirect → destination site. When the user presses back, the browser dutifully goes to the redirect. The redirect, still functional, immediately sends the user forward again to the destination. The user is stuck. They press back again. This time, they might reach the search results — or they might not, depending on timing and browser behavior.
This isn’t hypothetical. Developers have documented the behavior for years in forums and bug trackers. A report covered by Android Authority noted that the complaint has now been formally raised with regulators under the European Union’s Digital Markets Act, which designates Google as a gatekeeper and imposes specific obligations around fair dealing and user choice.
The DMA, which took full effect in March 2024, prohibits gatekeepers from engaging in practices that degrade the user experience to benefit their own services. A back button that doesn’t work as expected — because Google inserted a tracking redirect — could fall squarely within that prohibition.
Google, for its part, has not issued a detailed public response to the specific back-button hijacking allegations. The company has historically described its redirect URLs as necessary for security, spam prevention, and click measurement. Those are legitimate functions. But the question regulators and critics are asking is whether those functions require breaking standard browser navigation behavior — or whether less intrusive methods exist.
They do exist. The History API, available in every modern browser, allows websites to replace history entries rather than add new ones. Google could use history.replaceState() to record the redirect without creating a new back-button stop. It chooses not to.
Why This Matters Beyond a Minor Annoyance
On the surface, an extra back-button press seems trivial. It’s not.
For publishers and independent websites, every friction point between a user and the back button is a friction point against leaving Google. If pressing back doesn’t cleanly return users to search results — or worse, bounces them back to the site they were trying to leave — it subtly discourages exploration. Users learn, unconsciously, that tapping a search result is a commitment. They become less likely to click on organic results from smaller, unfamiliar sites. They stay on Google longer. They click on ads instead.
This dynamic has been a simmering concern among web publishers for over a decade. Google’s search results pages have steadily absorbed more of the information users once had to visit other websites to find — featured snippets, knowledge panels, AI-generated overviews. The back-button redirect is a quieter version of the same strategy: keeping the user tethered to Google.
The financial stakes are real. Google’s search advertising business generated over $175 billion in revenue in 2023, according to Alphabet’s public filings. Even marginal increases in time-on-site or return-visit rates translate into billions of dollars in additional ad impressions. A redirect that adds one extra second of Google engagement per search session, across five billion daily searches, is not a rounding error. It’s a revenue engine.
And the behavior isn’t limited to mobile browsers. Desktop users have reported similar redirect-based history manipulation, though the effect is less pronounced because desktop back-button behavior tends to be faster and more predictable.
The European Commission has been actively investigating Google’s compliance with the DMA across several fronts. In late 2024 and into 2025, regulators opened proceedings related to Google’s self-preferencing in search results and its treatment of rival services. The back-button complaint adds another vector of scrutiny. If the Commission determines that the redirect behavior constitutes an unfair practice under Article 6 of the DMA, Google could face fines of up to 10% of its global annual revenue — a figure that would run into the tens of billions of dollars.
But enforcement is slow. And Google’s lobbying apparatus in Brussels is formidable.
Meanwhile, browser vendors have done little to address the issue from their end. Chrome, which Google controls, has no built-in mitigation for redirect-based history manipulation. Firefox and Safari could theoretically detect and collapse redirect entries in the history stack, but doing so would require making assumptions about which redirects are legitimate and which are manipulative — a gray area that browser makers have been reluctant to enter.
Some browser extensions attempt to solve the problem. But extensions don’t work on most mobile browsers, which is precisely where the back-button hijacking is most disruptive.
The broader pattern here is one of incremental encroachment. No single change Google makes to its search experience is dramatic enough to provoke widespread outrage. A redirect here. A featured snippet there. An AI overview that answers the query without requiring a click. Each change is small. Defensible in isolation. But the cumulative effect is a web that increasingly begins and ends with Google.
Privacy advocates have raised a parallel concern: the redirect URLs don’t just manipulate browser history. They also serve as a tracking mechanism. When a user clicks through google.com/url?, Google can log the exact result that was clicked, the time of the click, and the user’s identity (if signed in). Direct navigation to the destination URL — without the redirect — would deny Google that data point. So the redirect serves dual purposes: tracking and tethering.
This is not a new observation. Security researchers flagged Google’s outbound click tracking via redirect URLs as far back as 2012. What’s new is the regulatory framework that might finally force a change. The DMA gives European regulators tools that didn’t exist a few years ago. Whether they’ll use those tools aggressively enough to alter Google’s behavior remains an open question.
For now, users who want to avoid the back-button trap have limited options. On desktop, right-clicking the back button reveals the full history stack, allowing users to skip the redirect entry manually. On mobile, long-pressing the back button sometimes works, depending on the browser. Neither solution is intuitive. Neither should be necessary.
The web was built on a simple promise: click a link, visit a page, press back, return to where you were. Google’s redirect breaks that promise. Not dramatically. Not obviously. Just enough to keep you a little closer to Google, a little longer, every single time.
And that, at the scale Google operates, is worth more than most people realize.
WebProNews is an iEntry Publication