Redirect chains: how to find and fix multiple hops
Free redirect chain checker. Find URLs with multiple redirect hops that waste crawl budget and leak PageRank, and learn how to fix them.
What it means
A redirect chain is when a URL doesn't go directly to its final destination but instead passes through two or more intermediate redirects before reaching the 200 response. Google follows up to 10 hops per crawl attempt, so a chain of three or more is flagged as a warning.
Why it matters
Each hop costs a crawl request and adds latency, which wastes crawl budget on sites with many URLs. Redirect chains also dilute the canonical signal — a 301 or 308 passes strong canonical weight to the target, but a chain means the original URL is further from that target. For AI agents and crawlers that parse responses on the first pass, deep chains can delay or obscure the final content.
How to fix it
- Audit the chain: use the URL Inspection tool or a redirect checker to see each hop and its status code.
- Consolidate to a single redirect from the original URL to the final destination.
- Verify the final destination returns a clean 200 with the expected content (not a soft 404).
- Ensure the final URL uses a canonical link tag pointing to itself.
When it's not a problem
A short chain of two or three hops is usually harmless — Google follows them without issue, and the canonical signal still reaches the target. Crawl rate is not a ranking signal, so chains only matter when they consume meaningful crawl budget on a large site with many changing URLs.
How common is it?
1352 audited sites in our corpus currently show this issue. The breakdowns below show which platforms, gatekeepers, verticals and countries are most exposed.
Related guides
Audit your own site — free
157 checks, internal PageRank, render-diff. No signup, results in ~30s.