What Is a Redirect Chain?

Q: How do I check if a URL has a redirect chain?

Run curl -sIL or use httpstatus.io 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.

A redirect chain is when one URL redirects to a second, which redirects to a third, before finally serving a page. Google said in 2016 that 30x redirects don't lose PageRank, so chains rarely cost link value directly. They do cost crawl efficiency, speed and reliability, and Google's crawlers follow only 10 hops by default.

What a chain looks like

A chain is any redirect that takes more than one hop to reach a live page. 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.

Redirect chain vs redirect loop

A chain eventually reaches a working page; a loop never does. In a loop, A redirects to B and B redirects back to A (or round a longer circle), so browsers give up with a "too many redirects" error and the page cannot be reached at all.

	Redirect chain	Redirect loop
Reaches a live page?	Yes, after several hops	Never
What users see	A slower load	"Too many redirects" error
Effect on indexing	Usually indexed if under the hop limit	Not indexed
Typical cause	Migrations stacked over the years	Conflicting rules (for example, one forcing www and another removing it)
Fix	Point every rule straight at the final URL	Find and remove the conflicting rule

Loops are the urgent one, because the page is simply gone. Chains are a slow leak you fix on maintenance days.

Does a redirect chain lose link value?

Not by the mechanism most people assume. In July 2016 Google's Gary Illyes posted that "30x redirects don't lose PageRank anymore", as reported by Search Engine Journal. Google's redirect documentation describes a permanent redirect as a signal that the target should be the canonical URL. The older folk rule that each redirect leaks 10 to 15% of link equity dates from an 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 hop limit. Google's documentation on HTTP and network errors says its crawlers follow up to 10 redirect hops by default. A URL that needs more than that never gets its content crawled. 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. 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 begins, which feeds directly into Core Web Vitals.

Fragility. This is the one that actually costs you links. If any hop later breaks (a rule removed during a migration, a plugin reset), everything upstream dies with it, and every backlink pointing at the original URL now points at nothing. Chains are how backlinks silently disappear; see do backlinks expire.

Mixed status codes. A chain with 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 many redirects is too many?

More than one hop is already too many for a URL you control. Google's crawlers stop at 10, but the practical rule is that every old URL should reach its final page in a single redirect.

Worked example: the chain above has four hops (http to https, apex to www, old slug to new slug, new slug to the /resources/ folder). It works, because four is under ten. But every visitor and crawler waits for four round trips, and four separate rules have to keep working forever. Flattened, the same move is one 301 from each old URL straight to https://www.example.com/resources/new-page.

Two hops caused by a protocol-and-host redirect followed by a page redirect is common and not an emergency. Three or more, or any chain on a URL with backlinks, is worth fixing this week.

How to check a redirect chain in 60 seconds

You can see every hop of a single URL with free tools in under a minute; a crawler does the same for a whole site.

Command line: run curl -sIL https://example.com/old-page. Each block of headers is one hop; read the status code and location: line of each.
Browser dev tools: open the Network tab, tick "Preserve log", load the URL, and look for 301, 302, 307 or 308 entries before the final 200.
An online checker: httpstatus.io shows the same hop list without the command line.
A whole site: Screaming Frog has a dedicated Redirect Chains report, and Ahrefs Site Audit and Semrush Site Audit both flag chains as issues.

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 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 broken or run past the hop limit.

How to fix them

The fix is always the same: point every redirect directly at the final destination. Instead of four sequential rules in the earlier example, 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, because external sites and old bookmarks still point at them. Re-target each one instead.
Update your own internal links too. If your site links to /old-page internally, fix the link rather than relying on the redirect.
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 check after deploying; badly ordered server rules can create loops.

Where chains matter most for link building

Any URL that has earned backlinks deserves a one-hop path to its content. A page with 30 referring domains that now resolves through three hops still works, but it carries 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 link: the damage is invisible until you go looking. When you trade links on Backlinkster, each swap is verified by API, and the link you submit has to be a real article URL on your own domain, so it pays to make sure that URL resolves cleanly before you share it.

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 said in 2016 that 30x redirects don't lose PageRank. The older "10 to 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 its crawlers follow up to 10 redirect hops by default. A URL that needs more never has its content crawled. 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, 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 inaccessible.

How do I check if a URL has a redirect chain? Run curl -sIL <url> or use httpstatus.io 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. Check 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.