You click an old link and the page loads. It looks fine. But behind the scenes, the browser may have been bounced three or four times before it got there.
That’s a redirect chain. Nobody sets one up on purpose. They grow quietly, one sensible change at a time, until a single click turns into a relay race.
The good news: chains are easy to find and usually easy to fix. You just have to look.
What is a redirect chain?
A redirect chain is when a URL redirects to another URL that also redirects, and so on, before the visitor reaches a real page. Each step is called a hop.
A typical one looks like this:
http://oldbrand.com/pricingredirects tohttps://oldbrand.com/pricingwhich redirects to
https://www.oldbrand.com/pricingwhich redirects to
https://newbrand.com/pricingwhich redirects to
https://newbrand.com/plans
Four hops, one destination. The clean version is a single redirect from the first URL straight to https://newbrand.com/plans.
A chain is different from a loop. In a chain the hops eventually end on a page. In a redirect loop they point back at each other forever and the browser gives up.
How chains usually form
Chains are almost always the result of history, not a single mistake. Common causes:
Layered fixes. One rule forces HTTPS, another adds
www, a third moves the domain. Each works on its own, but together they stack.Repeated migrations. You moved
/blog/postto/articles/posttwo years ago, then moved/articles/to a new domain. The old rule still points at the middle step.Renamed pages.
/pricingbecame/plans, then/plansbecame/pricing-2026. Each rename added a hop instead of updating the first rule.Several systems at once. A registrar forward, a Cloudflare rule and a CMS redirect can each add a hop, and nobody sees the full picture because each lives in a different dashboard.
Why chains are worth fixing
A chain still “works”, which is why it’s easy to ignore. But each hop has a cost.
Speed. Every hop is another round trip before the page can start loading. Google’s Lighthouse documentation notes that each extra trip can delay loading by hundreds of milliseconds, which is most noticeable on mobile connections.
Crawling. Google’s crawlers follow up to 10 redirect hops by default. Long chains waste crawl budget and past that limit the destination may not be reached at all.
Google’s own advice. In its site move guide, Google recommends redirecting to the final destination directly, and if that’s not possible, keeping chains ideally to no more than 3 hops and fewer than 5.
Fragility. The more hops, the more places something can break. If one domain in the middle expires or one rule is deleted, every URL that passed through it stops working.
Mixed signals. A single
302in the middle of a chain of301s can make an otherwise permanent move look temporary.
How to spot a redirect chain
You can’t see a chain in the browser’s address bar, because it only shows where you end up. You need a tool that follows every hop.
Paste the URL into the free redirect tester. It shows each hop, its status code and the final destination, and tries to name the platform behind each redirect, so you know which dashboard to open.
When you test, check more than one version of the URL:
http://andhttps://with and without
wwwold URLs from backlinks, bookmarks, printed material and email signatures
The tester’s “Both” option runs the chain from http:// and https:// in one go, which catches the most common extra hop.
How to collapse a chain into one rule
The fix is always the same idea: point every old URL straight at the final page.
Write down the chain. List each hop and where its rule lives (registrar, DNS provider, CMS, server config).
Find the final URL. The last address that returns a
200page is your real destination.Update the first rule. Change it so the original URL goes directly to the final URL in one step.
Update the middle rules too. Old links may point at any step in the chain, so each intermediate URL should also go straight to the final page, not to the next hop.
Remove rules that are no longer needed. If a system in the middle only existed to pass traffic along, take it out of the path.
Test again. Run the original URLs through the tester and confirm you see one hop and a
301(or308) for a permanent move.
If you’re handling HTTPS and www in a separate place from the domain move, that split is often the source of the extra hops. Handling all three in one place is usually the simplest way to keep it to a single redirect.
How Redirect Supply handles it
In Redirect Supply, HTTPS and www handling are built into every redirect and always on, so you don’t need separate rules for them. Rules are checked in a fixed order: an exact path match first, then a wildcard prefix match, then the domain’s global catch-all. You can read the details in Creating a redirect.
That means a migration can live in one list: exact rules for important pages, a wildcard like /blog/* for whole sections, and a catch-all for everything else, all pointing at final URLs. If you’re planning a bigger move, the website migration redirect checklist walks through the rest.
A good habit to keep
Whenever you rename or move a page, search your redirects for anything pointing at the old URL and update it to the new one. One minute now saves a chain later.
