Redirect Chains: How to Detect, Fix, and Prevent Them

A redirect chain occurs when the browser (and Google's crawler) must pass through two or more intermediate redirects to reach a final URL. The result: longer load times, PageRank lost at each hop, and a higher chance that Google abandons crawling before reaching the destination. This guide covers exactly why they form, how to detect them with free tools, and how to eliminate them at the root.

What is a redirect chain?

When you access a URL, the server returns an HTTP status code. A 301 or 302 code indicates that the resource has moved and the browser should follow to another URL. If that second URL also redirects to a third, and that one to a fourth, you have a chain.

Google has no published rule about the maximum number of hops it will follow, but official documentation warns that long chains can prevent crawlers from reaching the final destination. In practice, more than 3–4 hops starts to become problematic for sites with limited crawl budgets.

Why redirect chains hurt SEO

• •PageRank loss at each hop. While Google claims a 301 passes virtually all PageRank, each additional redirect introduces friction and potential signal loss.
• •Increased load time. Each redirect adds 100–300 ms of extra latency. On mobile, with slower connections, the impact on Core Web Vitals (especially TTFB and LCP) can be significant.
• •Wasted crawl budget. Google assigns a crawl budget per site. Following chains consumes that budget without indexing new content.
• •Degraded user experience. Users perceive slowness even if they don't see the redirects. Bounce rate increases when response time exceeds 3 seconds.
• •Wasted external links. If an external site links to a URL that starts a 3-hop chain, some of that link's authority is diluted along the way.

Why chains accumulate over time

Most chains are not created intentionally. They accumulate organically over the life of a website. These are the most common scenarios:

Successive redesigns and migrations

The site migrates from /blog/article-title to /articles/article-title (first redirect). A year later it migrates again to /resources/article-title (second redirect). Instead of updating the first redirect to point directly to the final destination, a new redirect is added on top of the previous one.

Unupdated protocol and domain changes

When migrating from HTTP to HTTPS, all internal links still using http:// generate an automatic first hop. If there is also a redirect from www to non-www (or vice versa), you have two hops before even reaching the content.

Plugins and CMS adding redirects without prior audit

WordPress plugins like Yoast SEO or Redirection make it easy to create redirects. The problem is that multiple editors or administrators can add redirects without checking whether one already exists pointing to that URL from another source.

Tracking URLs and UTM parameters

An email campaign uses the URL /summer-landing?utm_source=email. This URL redirects to /deals/summer. If /deals/summer also redirects to /deals, you already have a two-hop chain before the destination. Multiplied across dozens of campaigns, the problem scales quickly.

How to detect redirect chains

There are several ways to identify chains on your site, from manual methods to automated tools.

Method 1: Online analysis tool (fastest)

With iRankly's Redirect Chain Analyzer you can check up to 50 URLs in a single analysis. The tool shows each hop in the chain, the HTTP code of each redirect, the time in milliseconds per hop, and the total time to the final destination. Ideal for quick audits or post-migration verification.

Method 2: curl command in terminal

# Shows all redirect hops for a URL
curl -sI -L --max-redirs 10 https://example.com/old-url | grep -E "HTTP|Location"

Method 3: Screaming Frog (for full site audits)

In Screaming Frog go to Bulk Export → Response Codes → Redirection (3xx) Inlinks. Export the list and filter by "Redirect Chains" in the "Chain" column. The free version analyzes up to 500 URLs.

How to fix redirect chains

The solution is always the same: make each redirect point directly to the final destination, eliminating intermediate hops. The process varies depending on how you manage redirects on your server.

In Apache (.htaccess)

# BAD: 2-hop chain
Redirect 301 /old-url /intermediate-url
Redirect 301 /intermediate-url /final-url

# GOOD: direct redirect to the final destination
Redirect 301 /old-url /final-url

In Nginx

# GOOD: direct redirect with no intermediate hops
server {
    location /old-url {
        return 301 https://example.com/final-url;
    }
}

In WordPress with the Redirection plugin

Go to Tools → Redirection → Groups. Find the source URL that generates the first hop and modify the destination to point directly to the final URL. Then delete or disable any intermediate redirect that is no longer needed.

How to prevent chains from accumulating again

1. 1.Keep a centralized redirect log. A simple Google Sheet with columns for source URL, destination URL, date, reason, and owner is sufficient for small teams. For large sites, use the redirect plugin's database as the source of truth.
2. 2.Check existing redirects before creating a new one. Always verify whether the source URL already redirects somewhere. If it does, update the destination of the existing redirect instead of adding a new one on top.
3. 3.Audit redirects every 6 months. Include a bi-annual redirect review in your SEO calendar. Remove redirects pointing to non-existent URLs (404s) and fix any chains that have formed.
4. 4.Update internal links after every migration. Creating redirects is not enough — also update internal links to point directly to the final URL. This reduces the number of redirects crawlers have to follow.
5. 5.Set up monitoring alerts. Tools like Google Search Console (crawl errors) or periodic checks with iRankly's Analyzer will alert you when new chains appear.

Frequently asked questions about redirect chains

How many redirects in a chain are acceptable?

Google does not publish an exact number, but the general SEO industry recommendation is not to exceed 3 hops from the source URL to the final destination. In practice, the ideal is always 1 single direct hop.

Does a 301 redirect pass all PageRank?

Google has confirmed that a 301 passes virtually all PageRank. However, in multi-hop chains, the accumulation of small losses at each hop can have an impact. Additionally, the extra processing time can affect how Google prioritizes crawling those URLs.

Do redirect chains affect Core Web Vitals?

Yes, especially TTFB (Time to First Byte). Each redirect adds an additional HTTP request with its own DNS resolution, TCP connection, and server response time. On mobile, with higher latencies, the impact is especially noticeable on LCP.