Redirect Chain
Also known as: Redirect Hops, Multi-Hop Redirect
A redirect chain occurs when a URL redirects to a second URL that redirects again to a third or more before reaching the final destination. Each hop adds latency and consumes crawler resources, and long chains can prevent engines from following through to the target.
Key Takeaways
- A redirect chain is two or more redirects linked together before a request reaches its final destination URL.
- Each extra hop adds latency for users and consumes crawler resources that could be spent on other pages.
- Long chains can cause engines to stop following before reaching the target, leaving the destination undiscovered.
- The fix is to update every redirect to point directly at the final URL instead of chaining through old targets.
- Chains commonly form when HTTPS moves, migrations, and trailing-slash changes stack on top of each other.
How It Works
A redirect chain happens when the first URL returns a redirect to a second URL, which itself redirects to a third, and so on until the request finally lands on the real page. Each hop is a separate round trip, so the browser and any crawler must follow every link in sequence before content loads.
The cost shows up in two places. For users, the extra round trips slow page delivery and hurt Core Web Vitals. For search engines, following long chains wastes Crawl Budget, so pages deeper in the site may go uncrawled. Signal consolidation can also weaken across hops, meaning the ranking authority you expect at the final URL may not fully arrive.
To find and flatten chains, use Log File Analysis or a crawler to spot URLs with multiple 301 or 302 responses, then rewrite each rule to target the final address directly. Pair the cleanup with a correct Canonical Tag on the destination so engines consolidate signals on one authoritative URL.
Why It Matters
Chains slow page loads for users and waste crawl capacity, and signal consolidation can weaken across multiple hops. Collapsing chains to a single redirect preserves speed and ensures ranking signals reach the intended final URL.
Example
An ecommerce store moves from http to https, then later drops trailing slashes, then rebrands a category. An old product link now hops http, to https with slash, to https without slash, to the new category URL: four requests before the page loads. Collapsing all three rules so the original link points straight to the final URL removes the delay and preserves ranking signals.
Common Mistake
Letting chains accumulate after site migrations, HTTP-to-HTTPS moves, and trailing-slash changes stack on top of each other. Each should be updated to point directly at the final URL rather than chaining through previous redirect targets.
Frequently Asked Questions
How many redirects is too many?
Ideally zero chains: one redirect from old URL to final URL. Two hops is tolerable but worth fixing. Three or more meaningfully slows users and risks crawlers abandoning the path before reaching the destination.
Do redirect chains hurt SEO?
Yes. They waste crawl budget, slow page loads, and can weaken signal consolidation across hops. Long chains may prevent engines from reaching the final URL at all, so the destination never gets fully credited or indexed.
How do I find redirect chains on my site?
Run a site crawler or use log file analysis to flag URLs returning multiple sequential 301 or 302 responses. Both surface the full hop path so you can rewrite each rule to point directly at the final URL.