Google /goto SERP Change: How Ranktracker Fixed It First

Intro

Google has just made one of the biggest changes to how search result URLs are delivered to users and SEO tools in years.

By late August, Google was routing a growing share of organic search results through google.com/goto redirects instead of exposing the destination URL directly.

For rank trackers and SERP data providers, that matters.

A lot.

But for Ranktracker, this wasn't a new problem.

We detected the change on June 11, 2026.

We patched it the same day.

That was 76 days before Google confirmed the wider rollout on August 26 — and weeks before most of the SEO industry had even started talking about it.

Today, more than a week after Google's /goto change reached near-total coverage across several residential IP providers, some of the biggest SEO platforms in the world are still dealing with the fallout.

Ahrefs publicly acknowledged this week that Google's /goto change had caused inconsistencies in its data and said its team was still working to restore the affected results.

That is exactly why detecting SERP changes early matters.

What Google Changed

Until recently, extracting the destination URL from a Google organic result was relatively straightforward.

A result ranking a page like:

example.com/page

would normally expose that destination directly inside the search result.

Google has now started replacing those direct URLs with something closer to:

google.com/goto?...

The /goto URL acts as an intermediate redirect before sending the user to the actual destination.

For a normal Google user, very little appears to change.

You click the result. You arrive at the website.

For software collecting Google rankings at scale, however, the difference is significant.

The real destination URL is no longer simply sitting there waiting to be extracted.

Tools have to correctly resolve the new behaviour while still determining:

• which website is ranking
• the exact ranking URL
• its position
• SERP features
• competitors
• historical ranking changes
• landing-page changes

If that process fails, the rank tracker can end up recording Google's /goto URL instead of the website actually ranking.

And once bad SERP data enters a system, it can affect everything built on top of it.

Ranktracker Detected It on June 11

Our monitoring first detected the new behaviour on June 11, 2026.

It immediately stood out as something that could affect the integrity of our ranking data.

We investigated it.

We patched Ranktracker.

And the fix went live the same day.

Since then, we haven't seen Google's /goto URLs slipping through into our ranking data.

The interesting part is what happened next.

For weeks, almost nobody was talking about it.

The first widely documented public sighting came on June 23.

By July 8, Search Engine Roundtable was reporting that only a handful of people had noticed the behaviour. Barry Schwartz said at the time that he still couldn't reproduce it himself.

The article also showed examples of Ahrefs already beginning to pick up the new URL pattern.

By that point, Ranktracker's fix had already been running for almost a month.

Then Google Turned It Up

For much of June and July, /goto appeared to be something Google was testing across a limited percentage of searches.

That changed dramatically in August.

On August 26, 2026, Google confirmed that it was deploying new technical measures against abuse of its search services.

On the same day, data from Nozzle showed /goto behaviour reaching near-total coverage across several residential IP providers.

At that point, this stopped being an occasional edge case.

It became an infrastructure problem for companies collecting Google SERPs at scale.

A workaround that might be acceptable when /goto appears in a tiny fraction of requests becomes a very different problem when it appears almost everywhere.

That's when early detection starts paying off.

A Week Later, Major SEO Platforms Were Still Recovering

This is probably the most interesting part of the story.

Ahrefs is one of the largest and most technically sophisticated SEO platforms in the industry.

Yet in early September, Ahrefs publicly acknowledged that Google's increased use of /goto redirects had caused a temporary inconsistency in its data.

Its team said it was still working to restore the affected results.

That update came roughly a week after Google's wider rollout was confirmed.

Ranktracker had already been running its fix since June 11.

There's no suggestion here that processing Google SERPs at enormous scale is easy.

It isn't.

Google changes constantly, and changes designed specifically to make automated data collection more difficult create serious engineering challenges for every company operating in this space.

But that's also the point.

A rank tracker is only as useful as the data behind it.

And the size of the company providing that data doesn't automatically mean it will detect every Google change first.

The Real Competition Is Detection Speed

People sometimes think of rank trackers as simple tools that check where a website ranks.

Behind the interface, there is a constant battle to keep up with Google.

Google changes:

• HTML structures
• SERP layouts
• result types
• localisation behaviour
• anti-bot systems
• URL structures
• JavaScript
• AI-generated results
• request behaviour

Sometimes those changes are announced.

Most of the time they aren't.

A SERP data provider doesn't get an email from Google saying:

"We're changing this next Tuesday. Please update your parser."

You find out because something changes in the data.

The challenge is detecting that signal before it turns into a widespread problem.

That's what happened here.

The Timeline Says It All

June 11, 2026 Ranktracker detects Google's new /goto behaviour and deploys a fix the same day.

June 23, 2026 The first widely documented public sighting of Google's new /goto URLs appears.

Early July 2026 More SEOs begin reporting the behaviour, although it remains difficult to reproduce consistently.

August 26, 2026 Google confirms the wider deployment of the new redirect system. Near-total coverage is reported across several residential IP providers.

Early September 2026 Ahrefs publicly confirms that the change has caused inconsistencies in its data and says affected results are still being restored.

Ranktracker's fix had already been live for nearly three months.

This Is What Rank Tracking Is Supposed to Do

There is an obvious response to all of this:

"Isn't detecting changes in Google literally a rank tracker's job?"

Yes.

Absolutely.

That's exactly our point.

Our users pay us to monitor Google.

They shouldn't have to discover a Google change on Twitter, LinkedIn or an SEO news site and then wonder whether their ranking data has been wrong for the last week.

They shouldn't have to wait for a banner telling them that their data has been affected.

Ideally, they shouldn't notice the infrastructure change at all.

We should notice it.

We should fix it.

And their rank tracking should continue working.

On June 11, our monitoring told us something had changed inside Google's SERPs.

We investigated it and shipped the fix that same day.

The wider SEO community started noticing it afterwards.

Google eventually pushed it much more broadly.

And nearly three months later, some of the industry's biggest platforms were still working through the consequences.

That's the difference early detection makes.

Google will keep changing.

Our job is to make sure Ranktracker changes faster.