Redirect chain

What Redirect chain means

Each hop adds failure and latency opportunities, while clients impose different maximums.

How CrawlCheck measures Redirect chain

One finding code measures it. Its share of all scans is computed from the live corpus when this page is served, not typed into it.

Every code, its rule and its current rate: the dataset page. Scan a site to see which apply to it.

Where Redirect chain comes up on this site

• XML sitemap audit: check the file and every URL in itVerify the actual response, then tell it apart from a wall Fetch the headers and the body separately and read both: curl -sS -D /tmp/sitemap.headers -o /tmp/sitemap.xml https://example.com/sitemap.xml cat /tmp/sitemap.headers head -c 500 /tmp/sitemap.xml…
• HTTP status codes for crawlers: what a 200 can hideMost firewall rules match the crawler's name, so GPTBot is enough for a first pass; use the full string from the crawler's documentation to be thorough, and repeat with the names of the other crawlers you care about, such as Googlebot . # Browser vs named…
• HSTS check: missing header, bad preload, removed entriesStart with a short max-age such as 300 seconds while you confirm every subdomain and redirect chain works over HTTPS, then raise it.
• Google's /goto redirect: why referrer data can't show itUnder the origin policy, only the origin is sent, with a trailing slash ( W3C Referrer Policy ). redirectCount is 0 when any hop in a redirect chain is cross-origin, and google.com to your site always is ( w3c/navigation-timing issue 158 ).

Related terms in HTTP, edge and rendering

The delivery layer between an origin and a client: proxies, caches, redirects, status codes and the headers that decide what a crawler actually received.

Content-Language header · HTTP/3 · Alt-Svc · HTTPS DNS record · Link header · content negotiation · Markdown negotiation · Retry-After · Server-Timing · WWW-Authenticate · Allow header · Content-Digest · Origin server · Reverse proxy · CDN · Edge node · WAF · Bot score · TLS handshake · DNS resolution · DNS timeout · Connection timeout · Read timeout · Redirect loop · 301 redirect · 302 redirect · 307 redirect · 308 redirect · 304 response · 404 response · 410 response · 429 response · 500 response · 502 response · 503 response · 504 response · HEAD request · GET request · Content type · MIME sniffing · Content encoding · Compression · Brotli · ETag · Last-Modified · If-None-Match · Cache hit · Cache miss · Cache key · Vary header · Stale response · Stale-while-revalidate · Edge redirect · Origin bypass · Response parity · Header parity · hreflang · canonical URL · HSTS · HSTS preload list · Content-Security-Policy · CSP nonce · edge cache · cache split · cache-buster · Cache-Control · Age header · render-blocking resource · payload text share · lazy loading · 404 and 410 status codes

Questions about Redirect chain

What is Redirect chain?

Two or more redirects before a final response.

How does CrawlCheck measure Redirect chain?

Through the finding code REDIRECT_CHAIN, each with a stated rule, evidence bytes and a live share of scans on the dataset page.

Which area of the glossary does Redirect chain belong to?

HTTP, edge and rendering: The delivery layer between an origin and a client: proxies, caches, redirects, status codes and the headers that decide what a crawler actually received.

← Read timeout  ·  Redirect loop →

See it in the full glossary · 772 terms across 19 areas.