Google has moved the published JSON files that list its crawler IP ranges to a new, central location: developers.google.com/crawling/ipranges/. If your scripts, monitoring tools or firewall rules fetch those files directly, update the URLs now — Google will keep serving the old /search/apis/ipranges/ paths only temporarily and plans to redirect them to the new location within six months of the March 31, 2026 announcement.

What changed and when

The JSON files used to live under /search/apis/ipranges/. Google Search Central announced on March 31, 2026 that it has moved those files to /crawling/ipranges/ and updated its documentation to point there. During a transition period both the old and new paths will be served; Google says it will phase out the old paths and redirect them to the new location within six months.

Who should act — and why

Any system that references Google’s published crawler IP JSON files directly should be treated as a candidate for immediate update. That includes:

  • Firewall and proxy rules that whitelist Google crawler IPs.
  • Automation that fetches and parses the JSON for monitoring, alerting or analytics.
  • Configuration files, deployment manifests or documentation containing hard-coded links to the old path.

Relying on redirects is brittle: redirects can add latency, fail in edge cases, and — after Google removes them — break unattended systems. Moving links and automation to the new path removes that single point of failure.

Practical next steps

  • Inventory: Search codebases, infrastructure-as-code, runbooks and monitoring configurations for any references to /search/apis/ipranges/.
  • Update: Replace hard-coded URLs with /crawling/ipranges/ and commit the change to version control.
  • Test: Verify automated fetches return the expected JSON and that parsing or extraction still behaves correctly.
  • Deploy: Roll updates through your CI/CD or configuration management so all environments use the new path.
  • Monitor: Watch for redirects in logs during the transition and remove dependencies on redirected URLs before the six-month cutoff.

What to watch next

The announcement is terse: it confirms the move and the six-month transition but provides no further technical changes. Check the new developers.google.com/crawling/ipranges/ location for any follow-up notices, and treat this as maintenance work rather than a functional change to crawler behavior.

Operationally, prioritize any unattended systems that could fail silently when redirects are removed: scheduled jobs, containerized services, CI pipelines and edge firewalls. Once you’ve updated and validated references, add a note in your infrastructure documentation so teams don’t revert to the old path later.