Definition
A redirect chain is a series of redirects where URL A redirects to B, which redirects to C, and so on, instead of A going straight to the final URL.
Redirect chain explained
Chains build up over years. A page moves once, then its new URL moves again, then the site switches to HTTPS, and each change adds a redirect on top of the old ones. Visitors eventually arrive, but each hop adds time, and search engines follow only a limited number of hops before giving up.
Redirect chains cause several problems:
- Slower page loads, because each hop is a separate request, which also affects Time to First Byte.
- Wasted crawl effort on large sites.
- A higher risk that one broken link in the chain leaves visitors on an error page.
- Messier signals about which URL is canonical.
The fix is to point every old URL directly at the final destination in one hop, and update internal links, canonical tags and sitemaps to use final URLs. Crawl tools can list every chain on a site, which makes this a quick clean-up.
Example
An old campaign URL on your site redirects to an HTTP page, which redirects to HTTPS, which redirects to a renamed product page: three hops. Updating the original redirect to go straight to the final product page removes the chain.
Why it matters
Flattening chains speeds up pages and makes sure old links and rankings reach the right URL reliably.
Related service
301 Redirections
Redirect mapping, chain and loop clean-up so URL changes keep their rankings and links.
301 redirect management servicesPublished by Vidern, founded and led by Malhar Shah. Updated .
Planning a migration or URL change?
Tell us what's changing and we'll reply within 1 business day with how we'd protect your rankings.
Related terms
- 301 redirectA 301 redirect is a permanent redirect: the server tells browsers and search engines that a URL has moved for good and sends them to the new address.
- Redirect loopA redirect loop is when redirects point back to each other, for example A to B and B to A, so the page can never load.
- TTFB (Time to First Byte)TTFB (Time to First Byte) is the time from requesting a page to receiving the first byte of the response; web.dev suggests 0.8 seconds or less.
- Crawl budgetCrawl budget is the number of URLs a search engine can and wants to crawl on a site in a given time, set by crawl capacity and crawl demand.