GOTO URL / NEWS & EVIDENCE
The Google search-data timeline
The history extends beyond the introduction of /goto. Access challenges, result depth, destination resolution and result quality changed at different times.
2025
- Documented access change
January 2025: JavaScript requirements disrupt search-data collection
Google's JavaScript requirements affected how automated clients accessed search results. This was an access-layer disruption before the later depth and /goto changes.
Interpretation: Check whether the result page was obtained before reasoning about the rankings or links it contains.
Original evidence: Ryan Schafer, SerpApi: Google now requires JavaScript ↗
Read this update and our viewpoint → - Provider-observed depth change
September 2025: num=100 stops providing dependable top-100 results
The loss of a dependable 100-results request increased pagination work. This predates the wider /goto discussion and concerns result depth, not destination decoding.
Interpretation: Always record the depth actually collected. An absent keyword beyond that depth is not an observed ranking loss.
Original evidence: Bartek Marmolowski: restricting results per page ↗ · DataForSEO: revised pricing effective 19 September 2025 ↗
Read this update and our viewpoint →
2026
- Limited public observations
June–July 2026: the first public GoTo URL reports
Alex Greenland and Brodie Clark documented the redirect pattern before the wider rollout was confirmed. Derek Perkins said Nozzle had already encountered similar pages.
Interpretation: A first public sighting is not necessarily the launch date. Keep observation, reporting and confirmation dates separate.
Original evidence: Barry Schwartz: Google tests google.com/goto tracking URLs ↗
Read this update and our viewpoint → - Google-confirmed rollout
26 August 2026: Google confirms the GoTo URL rollout
Google confirmed technical measures as /goto redirects spread more widely. Destination extraction became a distinct step for tools reading affected results.
Interpretation: The confirmed change concerns how result links are delivered. It does not establish an algorithmic ranking loss.
Original evidence: Barry Schwartz: Google confirms deploying goto URL redirects ↗ · ScrapingBee: handling Google /goto redirects ↗
Read this update and our viewpoint → - Dated provider resolution claims
August–September 2026: providers publish GoTo URL fixes
DataForSEO and SerpApi describe restoring direct destination URLs. Those notices record adaptation at a point in time, rather than a permanent end to redirect problems.
Interpretation: Read a resolution notice against its date and affected result types. An old fix is not a guarantee about a new variation.
Original evidence: DataForSEO: rollout and resolution update ↗ · Hilman Ramadhan: resolution in progress ↗
Read this update and our viewpoint → - Provider-observed data-quality problem
September 2026: divergent search results complicate rank tracking
SISTRIX and Nozzle describe result sets that differ from expected searches. This is a data-quality issue beyond merely recovering a URL.
Interpretation: A resolved URL can still belong to an unrepresentative result set. Validate the observation as well as the address.
Original evidence: Johannes Beus, SISTRIX: collection changes ↗ · Derek Perkins / Nozzle: Poisoned Google SERPs ↗
Read this update and our viewpoint → - Dated provider incidents
October 2026: search-data quality and pagination incidents remain separate issues
SerpApi's public notices document irrelevant results, empty paginated responses and valid searches returning no results. These should not all be described as /goto failures.
Interpretation: Record why a check is unusable. A wrong result, a missing page and an unresolved destination need different remedies.
Original evidence: SerpApi: irrelevant/poisoned results incident ↗ · SerpApi: empty paginated results incident ↗
Read this update and our viewpoint → - Provider-observed change
Google GoTo URL delays: what changed for rank trackers on 30 October
Providers report new verification delays when resolving Google's /goto redirects. The evidence supports a fresh collection problem, but does not establish a universal rate limit or a ranking update.
Interpretation: A successful search-data request is only useful if it identifies the right results and their destinations. Ask for completion, freshness and destination quality together.
Original evidence: SERP Lens update, visible on Brodie Clark’s LinkedIn profile ↗ · SerpApi: unresolved /goto links incident ↗
Read this update and our viewpoint → - Unconfirmed limited observation
Has Google brought back num=100? A limited sighting, not a confirmed reversal
Brodie Clark reported a search with 99 organic results. That does not establish a general return of the old 100-results parameter.
Interpretation: Do not redesign collection or revise depth costs on the strength of a single observed results page.
Original evidence: Brodie Clark’s original LinkedIn observation ↗ · Barry Schwartz: Google Search may be bringing back num=100 ↗
Read this update and our viewpoint →
What this history does and does not establish
These are the major developments documented in the sources reviewed for this subject, not every Google search experiment or ranking update. The first public /goto report in this record is dated 23 June 2026; broader confirmation followed on 26 August. Earlier observations may exist.
Provider fixes, incidents and studies are retained as dated evidence. A resolution claim is not a new Google launch. Similarly, an incident notice date does not always identify the first affected request. The possible return of num=100 is explicitly unconfirmed.
Four questions for any apparent ranking change
- Access: did the collector obtain a usable result page?
- Depth: how many results were actually checked?
- Destination: was the final publisher page identified?
- Quality: was the result set representative of the intended query and conditions?
GoTo URL’s commentary interprets these sources. It does not claim an independent accuracy test or Google confirmation of every proposed anti-scraping mechanism.
Read the evidence in context
