Learn · How-To

How to Check Whether Your Rank Data Survived the /goto Change

Google confirmed the google.com/goto passthrough link in late August 2026. Your visitors did not notice. Your rank tracking almost certainly did, because the destination address is no longer readable in the results markup and has to be resolved one request at a time. The risk is not that your dashboard breaks loudly — it is that coverage quietly thins and you keep reading the chart as though nothing happened. This audit tells you which it is.

1. 1

   Find the instrumentation boundary in your own charts

   Pull your visibility or average-position trend for the last six months and mark August 2026 on it. Anything that crosses that line is two series, not one. Do this before you look at any numbers, so you are not tempted to explain a step change as performance.

2. 2

   Cross-check visibility against traffic for the same period

   Put your rank-tracking visibility score and your Search Console clicks on the same timeline. If visibility moved sharply and clicks did not, you are looking at a measurement event rather than a ranking event. This is the single fastest way to catch the failure mode, and it costs ten minutes.

3. 3

   Ask your provider the direct question in writing

   Email them: do you resolve google.com/goto links, and what changed in your coverage, sampling frequency or crawl depth after August 2026? Ask for a written answer. Some vendors updated promptly, some reduced refresh rates to control cost, and some have not said. All three are survivable; not knowing which is not.

4. 4

   Test the depth of your data specifically

   Look at how many of your tracked keywords still report positions beyond the top ten, and compare that count against the same month last year. Deep-position data is the most expensive to collect under the new mechanism and therefore the first thing a provider quietly trims.

5. 5

   Re-baseline and write the footnote

   Set a new baseline from September 2026 onward and add a standing note to your reporting template explaining that comparisons across August 2026 are not like-for-like. A report that shows the discontinuity is more credible than one that smooths over it, and it protects you from being asked later why the trend looks odd.

6. 6

   Shift reporting weight onto first-party sources

   Search Console, server logs and your own analytics do not depend on reading Google's results page, so none of them are affected by this change. Move your headline metrics onto them. They are narrower than a visibility index and they will still be true next quarter.

7. 7

   Apply the same test to your AI visibility tooling

   Share-of-answer and citation-tracking tools are built on the same foundation — automated retrieval of a surface the platform does not supply as data. Ask those vendors the same question about coverage and sampling, and treat any AI visibility trend line with the same suspicion until you have an answer.