What Is a Redirect Chain? Definition and Why It Matters

A redirect chain happens when a URL redirects to another URL that itself redirects, and so on, before finally reaching live content: A points to B, B points to C, and only C actually loads. Chains rarely appear by design — they build up gradually over years of migrations, rebrands and URL restructuring, each change adding one more hop without anyone going back to flatten the path.

Why chains are a problem

• Slower for users, especially on mobile connections, where every hop adds a round trip before the page renders.
• Less efficient crawling — search engines have finite patience for following redirects, and very long chains may simply be abandoned partway through.
• Risk of loops (A redirects to B, which redirects back to A), which breaks the page entirely for both users and crawlers.
• Diluted link value — each additional hop is an opportunity for something to go wrong, and long chains are generally considered less efficient at passing signal than a single direct redirect.

How chains typically form

A common pattern: a site moves from HTTP to HTTPS (hop one), then restructures its URL slugs a year later (hop two), then migrates to a new domain during a rebrand (hop three). Each migration was handled correctly in isolation — old redirects were added — but nobody went back to update the first redirect to point straight at the final URL. The result is a three-hop chain that nobody intended and few people notice until an SEO crawl surfaces it.

How to fix a redirect chain

1. Crawl your site with an SEO crawler to identify every URL that redirects more than once before reaching a 200 status.
2. For each chain, update the very first redirect to point directly at the final live URL, and remove the intermediate hops where possible.
3. Update your own internal links to point straight at the final URL rather than relying on any redirect at all.
4. For backlinks that matter — especially high-authority placements — consider reaching out to the linking site and asking them to update the anchor to the final URL directly.

A worked example

Consider a guest post placed on a publisher’s site years ago, linking to a page that has since moved twice. A visitor clicking that old backlink today might hit two redirects before landing on the current page. Flattening the chain so the original backlink’s target redirects in a single hop directly to the live URL removes the friction for readers and gives crawlers the cleanest possible path to follow the link’s value through to the destination.

Related terms

301 redirects, link equity, crawl budget.

Why chains creep back in even after a cleanup

Flattening chains isn’t a one-time job. Every subsequent site change — a new URL structure, another migration, a plugin update that rewrites paths — risks adding a new hop on top of redirects you already cleaned up. Treat chain-checking as a recurring item in a technical audit rather than a single project, particularly on sites that have been through several redesigns over the years.

Chains and third-party tools

Some link tracking and analytics platforms insert their own redirect layer — a tracked link that itself redirects to your real URL. Stacking one of these on top of an already-imperfect internal redirect can quietly turn a one-hop redirect into a two- or three-hop chain without anyone noticing, since the extra hop happens outside your own site entirely.

A quick mental model for prioritising fixes

Not every chain needs immediate attention. Prioritise flattening chains on URLs that are internally linked often, carry known backlinks, or receive meaningful organic traffic, and treat obscure, low-traffic chains as lower priority cleanup rather than an emergency. This keeps the exercise proportionate rather than turning a routine maintenance task into an open-ended project.

Chains introduced by third-party plugins

Content management system plugins that handle SEO, caching or security sometimes introduce their own redirect logic independently of your manually configured rules, occasionally stacking on top of them without an obvious warning. When auditing chains, check plugin-level redirect settings specifically, not only the rules you remember configuring yourself.

Treat this as part of ordinary site hygiene rather than a special project: whenever you touch redirect rules for any reason, take a moment to check whether the change you’re making introduces a new hop onto an existing one, and correct it at the source rather than layering another rule on top.

Even a single flattened hop, multiplied across thousands of monthly visits following an old link, adds up to a meaningfully faster, more reliable experience than leaving the chain in place indefinitely.

Where to go next

Redirect chains are exactly the kind of issue a technical checklist catches before you spend money on new placements. Once your redirects are flat, look at the marketplace for publishers to build fresh links with.

Browse every term in the link building glossary.

Frequently asked questions