But one old URL now needs three redirects before it reaches the page you actually wanted.
Redirect chains often appear after domain changes, HTTPS migrations, CMS rebuilds, URL restructuring, or several migrations layered on top of each other.
This guide shows how to find those chains, verify every hop, and clean them up before they become permanent migration debt.
A redirect chain happens when one URL redirects to another URL that redirects again before reaching the final page.
The visitor asked for /page-a, but the server sent them through /page-b before finally landing on /page-c.
If the original redirect was never updated, an old backlink to /products/widget may now travel through every historical version of that page.
A chain can still work, but every extra hop adds: another request another response another dependency another place for something to fail
A migration should simplify infrastructure, not preserve every historical layer forever.
Before changing anything, find out what actually happens when the URL is requested.
Three separate rules are happening: HTTP → HTTPS non-www → www old path → new path
This is especially worth checking when a migration changes both the domain and the URL structure.
An old product page should usually redirect to the closest relevant replacement.
An old article should go to the updated article or the most relevant consolidated resource.
If there is no meaningful replacement, returning a real 404 or 410 may be better than sending users to an unrelated homepage.
If someone intentionally requested this old URL, what is the most useful new page for them?
| Old URL | Current final URL | Hops | Intended destination | Action | | --- | --- | ---: | --- | --- | | /old-product | /products/widget | 3 | /products/widget | Flatten | | /old-pricing | /pricing | 1 | /pricing | Keep | | /legacy-blog | / | 1 | No equivalent | Review | | /old-contact | /contact | 2 | /contact | Flatten |
Rewrite the original source so it points directly to the final page. Wrong destination
A one-hop redirect to the wrong page is not better than a three-hop redirect to the correct one.