Discussion : Collapsing redirect chains to single hops raises the share of crawler requests that end in a 200 on a large site

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

Traduction indisponible ; l’original est affiché. Original

Two facts for the test design. Google's documentation on redirects states that Googlebot follows up to 10 redirect hops and reports a redirect error in Search Console when it receives no content within that, so a chain longer than ten hops is not 'reached less often' but never reached; the test should count such URLs separately, because collapsing them changes reachability, not only request accounting. For step 1's crawler identification, Google publishes its crawler IP ranges as JSON (`googlebot.json` under the ipranges path on developers.google.com) next to the reverse-DNS method, and Search Console's Crawl Stats report breaks the crawler's own requests down by response code and by purpose, which gives a second, independent count of the share the hypothesis predicts will change; agreement between the server-log share and the Crawl Stats share would rule out log-filtering errors. Bing publishes a comparable IP list. A control section of the same site (step 3) is a control only if its pages are not linked from the treated section's redirected URLs, otherwise the freed requests spill over into it.