You migrated a site, renamed a category, or switched from HTTP to HTTPS a while back, and every redirect worked fine at the time. Then months later a crawl report flags dozens of URLs taking three, four, even five hops to load. Nobody added those hops on purpose — they piled up one small fix at a time, and now old redirects are pointing at other redirects instead of at the real page.
That pileup is a redirect chain, and it's one of the most common technical SEO issues that goes unnoticed because nothing about it looks broken. The page still loads. Visitors still get where they're going. The cost shows up somewhere quieter: crawl efficiency, load time, and how cleanly ranking signals travel to the final URL.
A redirect chain happens when a URL redirects to another URL that is itself a redirect, forcing browsers and search engine crawlers to follow multiple hops before reaching the final live page. Each extra hop adds load time, can weaken how link signals pass through, and wastes crawl budget. The fix is to point the original URL directly at the final destination, collapsing the whole chain into a single redirect.
What is a redirect chain?
A redirect chain is a sequence of two or more redirects strung together between a starting URL and its final destination. Instead of A pointing straight to B, A points to B, and B points to C — so anyone requesting A has to be bounced through B before reaching C, the page that actually returns content.
- One redirect is normal. A single 301 from an old URL to a new one is standard practice and causes no issues on its own.
- A chain is stacked redirects. The problem starts the moment an intermediate URL in the sequence is itself a redirect rather than the final page.
- Chains grow silently. Each new migration, rebrand, or URL cleanup tends to add a redirect on top of the last one instead of replacing it, so chains lengthen over time without anyone noticing.
- They're different from redirect loops. A chain eventually terminates at a real page; a loop points back to a URL already in the sequence and never resolves.
The practical issue isn't that redirects exist — it's that nobody went back to update the earlier links once a newer one was added, so traffic and crawlers keep taking the long way around.
Why redirect chains matter for SEO
A chain that resolves in under a second feels harmless to a human visitor. It's a different story for crawlers and for anything measuring speed:
- Crawl budget gets spent on hops, not pages. Every redirect in a chain is a separate request a crawler has to make, which on a large site adds up to real crawl budget spent resolving old URLs instead of discovering new content.
- Page speed takes a direct hit. Each hop adds a full round-trip to the server before the browser can even start loading the destination page, which shows up in Core Web Vitals metrics like Time to First Byte.
- Signal can weaken across hops. While a chain of 301s is designed to pass ranking signal forward, long or mixed chains (301s combined with 302s) make that transfer less clean than a single direct redirect.
- Chains are more failure-prone. The more hops in a sequence, the more places a single broken link, typo, or removed page can turn the whole chain into a dead end.
Step-by-step: finding and fixing redirect chains
- Pull a list of your site's redirects. Export existing redirect rules from your server config, CMS redirect plugin, or CDN settings so you have a full inventory to check.
- Trace each URL hop by hop. Run key URLs, especially old category pages, migrated posts, and legacy links, through a redirect checker that shows every status code and hop in the sequence, not just the final destination.
- Flag any sequence with more than one hop. Anywhere a redirect leads to another redirect before landing on a 200 status page is a chain worth fixing, regardless of how fast it resolves.
- Identify the true final destination. Follow the chain all the way to the live page that actually returns content, since that's the only URL the original redirect should point to.
- Update the first redirect to point directly there. Edit the original rule so it skips every intermediate hop and goes straight from the starting URL to the final destination.
- Remove the now-unused intermediate redirects. Once nothing points to them anymore, delete the redirect rules that used to sit in the middle of the chain to keep the rule set clean.
- Re-check after publishing. Run the same URLs back through a redirect checker to confirm each one now resolves in a single hop.
Common mistakes that create redirect chains
1. Layering a new redirect instead of updating the old one
When a URL changes again, it's faster to add a fresh redirect from the newest URL back to the previous one than to go find and update every rule that already points there — but that shortcut is exactly how chains form.
2. Migrating HTTP to HTTPS without updating internal redirects
A common pattern is HTTP redirecting to HTTPS, which then redirects to a www version, which then redirects to the final URL — three protocol and domain changes stacked into one chain that could be a single hop.
3. Forgetting to update old redirects after a site restructure
Restructuring a category or renaming a folder often means old URLs get redirected to the new structure, but any redirect rules that already pointed to the old URLs are left untouched, chaining onto the new ones.
4. Redirect plugins that stack rules without deduplication
Some CMS redirect tools add a new rule every time a page's URL is edited but never clean up the rule it replaces, so a page renamed several times can accumulate a chain automatically.
Real-world examples
Where redirect chains actually come from in practice, and what fixing them looks like:
In each case, the fix wasn't a new redirect — it was tracing the existing chain back to its true endpoint and pointing the very first URL there directly.
Redirect chain vs. related issues
Redirect chains get confused with a few similar-sounding problems. Here's how they differ.
| Issue | What happens | Does it resolve? | Main impact |
|---|---|---|---|
| Redirect chain | Multiple redirects in sequence before reaching the final page | Yes, eventually | Slower load, wasted crawl budget |
| Redirect loop | A redirect points back to a URL already in the sequence | No, never resolves | Page fails to load entirely |
| Single redirect | One URL redirects directly to its final destination | Yes, immediately | Negligible, standard practice |
| Soft 404 | A URL returns a 200 status but shows "not found" style content | Yes, but misleading | Confuses crawlers about page validity |
Check your site for redirect chains — free
The Rebrixe Redirect Checker traces any URL hop by hop, showing every status code along the way so you can see exactly where a chain forms and where it finally lands. No account, no limits on how many URLs you check.