What Is a Redirect Chain?

A redirect chain is when one URL redirects to a second, which redirects to a third, before finally serving a page. Google has said since 2016 that 30x redirects don't lose PageRank, so chains rarely cost you link value directly. What they do cost is crawl efficiency, page speed, and reliability — and past ten hops, Googlebot stops following.

What a chain looks like

A clean redirect is one hop:

/old-page  →  301  →  /new-page  (200 OK)

A chain is several:

http://example.com/old-page
  → 301 → https://example.com/old-page
  → 301 → https://www.example.com/old-page
  → 301 → https://www.example.com/new-page
  → 301 → https://www.example.com/resources/new-page  (200 OK)

Nobody builds that deliberately. It accumulates: an HTTPS migration adds a hop, a www canonicalisation adds another, a slug rename adds a third, a site restructure two years later adds a fourth. Each change was reasonable on its own and nobody flattened the earlier ones.

A redirect loop is the pathological version — A redirects to B, B redirects back to A. Browsers show "too many redirects" and the page is simply unreachable.

Does a redirect chain lose link value?

Not by the mechanism most people assume.

Google's Gary Illyes stated publicly in 2016 that 30x redirects don't lose PageRank. Google's own redirect documentation reflects the same position — permanent and temporary redirects both pass signals to the target. The older folk rule that each redirect leaks 10–15% of link equity dates from a much earlier era and no longer describes how Google behaves.

So a two-hop chain is not quietly draining your backlinks. The real costs are these:

The 10-hop limit. Google's documentation is explicit that Googlebot follows up to 10 redirect hops in a single crawl attempt. If it doesn't reach content within that budget, the URL is treated as an error and the page isn't indexed. Ten sounds like a lot until you inherit a site that has migrated three times.

Crawl budget. Every hop is a request. On a large site with tens of thousands of chained URLs, that's a meaningful share of crawl activity spent on hops instead of pages — which matters most on the sites that can least afford it. See what is crawl budget.

Latency for real users. Each hop is a round trip. Three unnecessary redirects on a mobile connection can add hundreds of milliseconds before rendering even begins, which feeds directly into Core Web Vitals.

Fragility. This is the one that actually costs you links. Every hop is an opportunity for a future breakage. If any link in the chain later 404s — a rule removed during a migration, a plugin reset — everything upstream dies with it, and all the backlinks pointing at the original URL now point at nothing. Chains are how backlinks silently disappear; see do backlinks expire.

Mixed status codes. A chain that includes a 302 in the middle is riskier than one made of 301s, because Google has to judge whether the move is permanent. Keep permanent moves permanent, end to end.

How to find redirect chains

A single URL: httpstatus.io or curl -sIL <url> will show every hop and status code in order. This is the fastest way to check a specific backlink target.

A whole site: Screaming Frog has a dedicated Redirect Chains report (Reports → Redirects → Redirect Chains) that lists every chain with its hop count. Ahrefs Site Audit and Semrush Site Audit both flag them as issues too.

Your backlinks specifically: export your referring pages from Ahrefs or Semrush, extract the target URLs, and run them through a status checker. This is the highest-value pass, because a chain sitting on a URL that 40 sites link to matters far more than one on a page nobody links to. How to check if a backlink is indexed covers the related check.

Search Console: the Pages report surfaces "Page with redirect" and redirect errors, which will catch chains that have exceeded the hop limit.

How to fix them

The fix is always the same: point every redirect directly at the final destination.

Take the earlier example. Instead of four sequential rules, you want:

http://example.com/old-page          → 301 → https://www.example.com/resources/new-page
https://example.com/old-page         → 301 → https://www.example.com/resources/new-page
https://www.example.com/old-page     → 301 → https://www.example.com/resources/new-page
https://www.example.com/new-page     → 301 → https://www.example.com/resources/new-page

Every historical URL resolves in one hop. Practical notes:

Do it after every migration, not before the next one. Flattening is a five-minute job the week you launch and a forensic exercise three years later.
Keep the old rules. Don't delete the intermediate redirects — external sites and old bookmarks still point at them. Just re-target each one.
Update your own internal links too. If your site links to /old-page internally, fix the link rather than relying on the redirect. Internal links should never need redirecting.
Handle protocol and host first. One rule that forces HTTPS and the canonical host in a single hop prevents the most common source of chains.
Recrawl and verify. Re-run the audit after deploying; badly ordered server rules can create loops.

Where chains matter most for link building

If you've ever renamed a URL that had backlinks, check it. A page that earned 30 referring domains and now resolves through three hops is working — but it's carrying three separate points of failure, and any one of them ends 30 links at once.

It's the same category of risk as a partner quietly removing a swapped link: the damage is invisible until you go looking. Backlinkster verifies every exchanged link by code on an ongoing basis, so a placement that stops resolving — whether it was deleted or stranded behind a broken redirect — shows up immediately rather than at your next audit. See the plans — five verified swaps a month on the free tier.

Frequently asked questions

What is a redirect chain? A redirect chain is a sequence where one URL redirects to another, which redirects again, before finally returning a live page. Two or more hops between the requested URL and the final destination is a chain.

Do redirect chains lose link juice? Not directly. Google stated in 2016 that 30x redirects don't lose PageRank, and its current documentation says redirects pass signals to the target. The older "10–15% loss per hop" rule is outdated. The real costs are crawl waste, slower load times and the risk of a hop breaking.

How many redirects will Google follow? Google's documentation says Googlebot follows up to 10 redirect hops in one crawl attempt. Beyond that the URL is treated as an error and won't be indexed. Staying at one hop leaves no room for trouble.

Are redirect chains bad for SEO? They're a maintenance problem rather than a penalty. Each extra hop adds latency for users, consumes crawl budget, and creates another point of failure that can kill every backlink pointing at the original URL. Flatten them, but don't panic about a single two-hop chain.

What's the difference between a redirect chain and a redirect loop? A chain eventually reaches a working page. A loop never does — A points to B and B points back to A, so browsers give up with a "too many redirects" error and the page is completely inaccessible.

How do I check if a URL has a redirect chain? Run it through httpstatus.io or curl -sIL <url> to see every hop and status code. For a whole site, use Screaming Frog's Redirect Chains report or the equivalent issue in Ahrefs or Semrush Site Audit.

The bottom line

Redirect chains don't drain PageRank the way the old rule of thumb claimed, but they waste crawl budget, slow pages down, and stack up failure points on exactly the URLs your backlinks depend on. Audit them after every migration, re-target each rule at the final destination so nothing takes more than one hop, and fix your internal links so they never rely on a redirect at all.