A redirect chain is a sequence of HTTP redirects where an initial request is forwarded from one URL to another, and from that to a third, and so on, until it reaches the final destination. Each intermediate step is a hop that the browser or client must follow before getting the requested resource. When the chain is too long or forms a loop, the browser stops navigation and shows a message like “too many redirects” (ERR_TOO_MANY_REDIRECTS).
In SEO, a redirect chain is considered a bad practice because it slows down page loading and consumes crawl resources. Google has stated that redirects do not cause PageRank loss, but each hop adds a request and a delay, and Googlebot follows at most 10 hops. That’s why it’s recommended to shorten chains by pointing directly to the final URL with a single permanent redirect.
When redirects add up in sequence
A redirect chain occurs when URL A redirects to URL B, which in turn redirects to URL C, and so on. The phenomenon often arises unintentionally: a site is restructured multiple times, a domain changes ownership, a page is moved and then moved again. If each change adds a new redirect without updating the previous ones, the chain grows progressively longer.
The most common redirects are 301 (permanent move) and 302 (temporary move). A chain can mix both types, but generally you try to keep the first type to preserve SEO value. The longest chains are those resulting from multiple migrations or configuration errors on web servers like Apache or Nginx.
The most frequent causes
The most frequent causes are three: domain migrations, URL structure changes, and uncoordinated manual fixes. In a migration, for example, you create a redirect from the old domain to the new one, but if the new domain already has its own internal redirects, the chain gets longer. The same happens when a URL is updated multiple times without removing the old redirects.
Typical configuration errors
A common mistake is redirecting the www version to the non-www version, and then redirecting the non-www version again to a specific page. Another mistake is keeping an old redirect active that points to an outdated URL, which in turn redirects elsewhere. Redirect management plugins can also create chains if they are not checked periodically.
Chain vs. single redirect: what’s the difference
A single redirect is a direct relationship between two URLs: A points to B and navigation ends. A chain is an indirect relationship: A points to B, B points to C, C points to D. The practical difference is the number of HTTP requests needed to reach the final destination, which in a chain is always greater than one.
What a redirect chain means for SEO
From an SEO perspective, each additional hop means a loss of time for the user and the crawler. Google follows chains (up to 10 hops) and states that redirects do not cause PageRank loss; however, long chains can slow down crawling, especially on large sites.
Another effect is the impact on experience: slower loading can cause users to abandon the page. That’s why it’s best to keep chains as short as possible, ideally a single hop, and update redirects when the final destination changes.
How much value passes from one hop to the next
Google has stated that redirects do not cause PageRank loss, regardless of the 3xx code used. The cost is not in value but in time: more hops, more requests, and more delay. That’s why it’s recommended to point directly to the final URL, avoiding intermediate steps.
Crawling and indexing: the effects
Search engine crawlers follow redirects, but each hop consumes a portion of the crawl budget assigned to the site. If the budget is limited, a long chain can delay the discovery of new pages. Moreover, if the chain contains a broken link, the crawler does not reach the destination and the page may drop out of the index.
Redirect types and their behavior
The following table summarizes the main differences between the most used redirects and their behavior in a chain.
| Type | HTTP code | Signal for Google | Typical use |
|---|---|---|---|
| Permanent | 301 | Strong for choosing the new URL as canonical | Domain change or definitive URL |
| Permanent with method preserved | 308 | Same as 301 | Migrations requiring POST |
| Temporary | 302 | Weaker; if long-lasting may be treated as permanent | Maintenance or testing |
| Temporary with method preserved | 307 | Same as 302 | Testing forms and APIs |
| Meta refresh | None (HTML) | Followed by Google, but less reliable | Non-server-side solutions |
The procedure to fix a chain
To fix a redirect chain, you first need to identify it, then simplify it by pointing directly to the final URL. The following procedure summarizes the recommended operational steps.
- List all URLs that generate redirects on the site, using scanning tools or server logs.
- Identify chains with more than one hop and note the starting URL and the final destination.
- Check the status code of each hop, distinguishing between 301, 302, and other types.
- Replace each chain with a single redirect from the starting URL to the final URL.
- Update internal links so they point directly to the final destination, without going through redirects.
- Check that no broken links or non-existent destinations remain.
- Monitor redirects periodically to prevent new chains from forming after updates or migrations.
- Document changes to facilitate future maintenance and handovers.
Frequently asked questions about redirect chains
How many hops can a redirect chain contain?
There is no universal limit: browsers stop navigation after a variable number of hops (often around twenty) and Googlebot follows up to 10. In practice, it’s best not to exceed one hop, or two in exceptional cases.
Does a redirect chain cause ranking drops on Google?
Rarely due to link value, which Google states is not lost. However, a chain can slow down crawling and the appearance of the new URL in results. The best way to avoid problems is to use a single permanent redirect.
What is the difference between a redirect chain and a redirect loop?
In a chain, navigation proceeds toward a final destination. In a loop, the redirect returns to the starting URL, creating an infinite cycle that the browser interrupts with an error.
How do you identify a redirect chain?
You can use an HTTP header check, which shows the sequence of status codes, or site scanning tools that highlight URLs with more than one hop.
Do 301 and 302 redirects behave the same way in a chain?
For Google, a 301 is a strong signal for choosing the new URL as canonical and a 302 is a weaker signal; both transmit PageRank. In a chain, Google follows all hops to the final destination.
Does a redirect chain affect site speed?
Yes, because each hop adds an HTTP request and a waiting time. Reducing hops improves loading times perceived by users and crawlers.
From glossary to projectNeed to change domain or platform without losing visibility?SEO migration prepares the transition (redirects, structure, checks before and after) to reduce the risk of losing rankings on Google.Discover SEO migration
Related entries:
Redirect Redirecting Value chain Value chain of porter