BUY WEBSITES
BUY DOMAINS
LOGIN
SIGNUP
301 Redirect Chains: How Redirect Hops Leak a Domain’s Link Equity, and How to Collapse Them Back to One
A 301 redirect chain is what you get when one redirect points at another redirect instead of at the final page. URL A sends the browser to B, B sends it to C, and only C answers with real content. Every extra hop is a tax: a slice of latency, a slice of crawl budget, and, by the heuristic the industry has used for years, a slice of the link equity the redirect was built to carry.
The honest read is the one competitor guides skip. Done right, a 301 is a near-lossless pipe that hands the destination its predecessor’s authority as a canonical signal. Done wrong, stacked into a three or four hop chain that nobody cleaned up after a migration, that same pipe starts to leak, and the authority you paid for at the start of the chain reaches the end thinner than it left.
This guide covers what a chain is, how it leaks, what Google has said about hops and equity, how to find every chain on a property, and how to collapse each one back to a single hop. It also draws the line the field never connects: a redirect only pays off if the domain feeding it carries real, clean authority in the first place. SEO Domains operates the curated marketplace where that raw material is screened before it is priced.
What is a 301 redirect chain, and how it differs from a loop
A 301 redirect chain is a sequence where one URL redirects to a second URL that itself redirects to a third, so the browser and Googlebot pass through two or more hops before reaching live content. A loop is the broken cousin: the chain bends back on itself, so no hop ever resolves, and the browser returns a redirect-loop error.
The textbook chain reads A goes to B, B goes to C, C answers. The clean version of the same intent is A goes straight to C. Both deliver the visitor to the right page, but the chain makes everyone, human and crawler, walk through an extra doorway that adds nothing.
How chains get created in the first place
Nobody sets out to build a chain. They accumulate. A site restructures its blog categories in 2024, so the old post URL gets a 301 to the new category path. A year later the site migrates to HTTPS, and that new path gets a second 301. The original link on the open web still points at the 2024 URL, so a reader following it now travels two hops to land on one article. Stack a domain change on top and the chain reaches three.
Chain versus loop versus a single hop
The three cases behave differently, and naming them precisely is the first step in any audit.
Single hop (the goal)
A redirects directly to the final live URL. One round trip, the canonical signal passes cleanly, and nothing is wasted. This is the state every fix in this guide aims for.
Chain (the tax)
A goes to B goes to C. The page resolves, but through two or more hops that add latency, burn crawl budget, and put the inherited equity at risk the longer the chain runs.
Loop (the break)
A goes to B goes back to A. Nothing ever resolves. Browsers return a redirect-loop error, the page is unreachable, and the equity behind it is stranded until the loop is broken.
A loop is the louder problem because it breaks the page outright, and the server error makes it obvious. A chain is the quieter one. The destination loads, the tools that only check whether a redirect works report a green light, and the slow leak goes unnoticed until a crawl report or a ranking dip surfaces it.
How a redirect chain leaks link equity, hop by hop
The leak has two readings, and the honest answer holds both. Google’s stated position is that a 301 passes ranking signals and that 3xx redirects no longer lose PageRank. The working heuristic the SEO field has used for years assumes a small loss at each hop, on the order of 5 percent, which compounds across a chain. The reality sits between them: the bigger, measurable cost is crawl and latency, with equity dilution as a secondary risk that grows with chain length and irrelevance.
What Google says: 301s pass the signal
Google’s own documentation frames a permanent redirect as a canonical instruction. In the Search Central redirects guide, a 301 or 308 means the indexing pipeline “uses the redirect as a signal that the redirect target is the canonical one,” while a temporary 302 or 307 does not pass that signal. Back in 2016, Gary Illyes of Google stated publicly that 30x redirects no longer lose PageRank, and John Mueller has repeatedly described a 301 as acting like a canonical signal, not a leaky pipe. Taken at face value, a clean single 301 is close to lossless.
The field’s heuristic: a few percent per hop
Practitioners have long planned against a more cautious assumption. The widely repeated working figure, cited in guides such as Conductor’s redirect-chains academy entry, is a loss of around 5 percent of link equity per redirect. Applied to a three-redirect chain, that heuristic implies the target receives roughly 85.7 percent of the equity that entered the first hop. Treat that number for what it is: an industry rule of thumb, not a measured Google constant, and not a figure Google has ever confirmed.
Where the two readings agree
Both camps land in the same place on the practice. Whether the per-hop equity loss is a measured 5 percent or a rounding error, every authority agrees a chain belongs collapsed to one hop. Google advises the direct redirect. The cautious heuristic rewards it. Nobody, on either side of the equity question, argues for keeping the extra hops. That rare consensus is why the fix in this guide is unambiguous even where the theory is contested.
| Chain length | Field heuristic (~5% per hop) | Google’s stated position | What is not contested |
|---|---|---|---|
| 1 hop (direct) | ~100% retained | Canonical signal passes | The correct state for every redirect |
| 2 hops | ~95% retained | Signal still passes, follow cost added | Collapse to 1 where the source link is live |
| 3 hops | ~85.7% retained | Within Google’s “no more than 3” band | Acceptable ceiling, not a target |
| 5 hops | ~77% retained (heuristic) | Past the recommended ceiling | Danger zone, fix on sight |
| 10+ hops | Equity treated as stranded | Beyond the 10-hop follow limit | Page effectively orphaned from the link |
What Google actually says: the 10-hop limit and the no-more-than-five rule
Google publishes two numbers that bound the question. Googlebot follows up to 10 hops in a chain before it stops, and Google’s own guidance recommends redirecting to the final destination directly, keeping any necessary chain to no more than three and fewer than five. Those are the hard ceiling and the soft target, and they come straight from Search Central, not from a third-party estimate.
The verbatim guidance
Google’s Site moves with URL changes documentation states that “Googlebot can follow up to 10 hops in a chain of multiple redirects.” The same source adds the recommendation in plain language: “we advise redirecting to the final destination directly. If this is not possible, keep the number of redirects in the chain low, ideally no more than 3 and fewer than 5.” It closes with the user-side reason: “chaining redirects adds latency for users, and not all user agents and browsers support long redirect chains.”
Why the ceiling and the target are different numbers
The 10-hop limit describes Googlebot’s tolerance, not a safe operating range. A chain at eight hops is still inside the technical limit and is still a problem, because the crawl cost, the latency, and the equity risk all rise long before the crawler quits. Reading the 10 as permission to run long chains inverts the guidance. The number that matters for planning is the recommended ceiling of three, and the target underneath it is one.
The target. A direct redirect from the live URL to the final destination. Source: Google advises redirecting to the final destination directly.
The recommended ceiling. Google’s guidance is no more than three redirects in a chain where a direct redirect is not possible. Treat this as the line you do not cross, not a goal.
The danger zone. Past Google’s “fewer than five” wording. Standard auditing workflows flag four-plus hops as equally poor for crawl and user experience.
The hard cliff. Googlebot follows up to ten hops, then stops. Anything beyond is unreachable to the crawler and the link is effectively orphaned. Source: Google Search Central, site-move documentation.
The crawl-budget and Core Web Vitals tax of every extra hop
Before any equity argument, a chain charges a measurable tax that nobody disputes. Each hop is an additional HTTP round trip, which adds latency for the visitor and consumes crawl budget for the bot. On large properties that crawl tax delays indexing, and on the user side the extra round trips push Time to First Byte and Largest Contentful Paint in the wrong direction.
The crawl-budget cost
A crawler that hits a three-hop chain spends three requests to reach one page. On a property with thousands of redirected URLs, that arithmetic compounds. Crawl budget that goes to walking chains is crawl budget that did not go to discovering and refreshing real content, which is how chains delay indexing on a site move without ever throwing a single error. The bigger the site, the sharper the penalty.
The Core Web Vitals cost
Each redirect adds a round trip before the browser sees a single byte of the destination. That delay lands directly on Time to First Byte, and a slower TTFB drags Largest Contentful Paint with it, because the largest element cannot paint until the response arrives. A chain is one of the few SEO problems that is also a literal page-speed problem, which means it shows up in both a crawl audit and a Core Web Vitals report.
The relevance failure: when a hop drops equity to zero
The chain that leaks 5 percent per hop is the optimistic case. The destructive case is a hop that points somewhere irrelevant. When a redirect sends a URL to an unrelated page or to the homepage, Google can treat it as a soft 404 and transfer nothing at all. Relevance, not hop count, is the variable that turns a small leak into a total loss.
How a redirect becomes a soft 404
A soft 404 is a page that returns a success status but behaves like a missing page. When an old product URL redirects to the generic homepage instead of a like-for-like replacement, Google reads the mismatch and can decline to pass the historical signal, because the destination is not a true continuation of the source. The redirect technically works. The equity behind it does not arrive. StellarSEO’s 2026 engineering analysis frames this as a threshold: below a certain semantic match between source and destination, effective transferred equity falls toward zero.
Why this compounds inside a chain
A chain multiplies the chances of a relevance break. Each hop is another opportunity for an intermediate URL to point at a redesigned, merged, or deprecated page that no longer matches the original context. A two-hop chain where the middle stop is an old category that has since been gutted can leak more than its length suggests, because the relevance thread snaps in the middle. This is why the relevance requirement runs through the whole hub, covered in depth in Relevance requirement for 301 (Koray’s rule) and in the failure-mode breakdown at 301 redirect risks and penalties.
How to find redirect chains and loops, step by step
Finding chains is a repeatable audit, not a guess. Crawl the property with a redirect-aware tool, export the redirect chains report, sort by hop count, cross-check the high-value URLs against the live links that point at them, and confirm no path loops back into a redirect-loop error. The sequence below is the audit, with the mistake that wastes each step called out beside it.
-
Crawl with a redirect-aware tool
Run the site through Screaming Frog in list mode, or a comparable crawler, with “always follow redirects” enabled so the tool walks every hop to the end. Site Audit in Ahrefs or Semrush surfaces the same chains at scale, and the browser’s network panel or a Redirect Path extension checks a single URL on demand.
The mistake: using an online checker that reports only whether the redirect resolves. A green “redirect works” hides a three-hop chain behind it, because the tool stops at the destination instead of counting the hops.
-
Export the redirect chains report and sort by hop count
Pull the dedicated redirect chains export, which lists each starting URL alongside the full path and the number of hops. Sort descending so the longest chains rise to the top, and flag everything at four hops or more for immediate attention.
The mistake: reviewing the redirect list unsorted. The two-hop chains drown the four-hop ones, and the genuinely damaging paths stay buried in a thousand-row spreadsheet.
-
Cross-check the high-equity URLs against their inbound links
A chain only matters where a real link or a crawled internal path enters it. Match the chain starts against the URLs that carry inbound authority, using the backlink report in your toolset, so the fix effort goes to the chains that sit under earned links, not to orphaned redirects nobody follows.
The mistake: treating every chain as equal. A four-hop chain with no inbound links is housekeeping. A two-hop chain under a strong external link is leaking the authority you care about.
-
Confirm there are no loops
Scan the same report for any path that never resolves, or load suspect URLs in a browser and watch for the redirect-loop error a runaway cycle throws. A loop is a page that is offline to users and crawlers alike, so it ranks above chains in urgency.
The mistake: missing the loop because the crawler quietly skipped the URL. A page absent from the crawl is not always a clean page. It can be one the crawler abandoned mid-loop.
-
Verify status codes and redirect type
Confirm each hop returns a genuine 301 or 308, not a 302, a meta-refresh, or a JavaScript redirect. Permanent codes pass the canonical signal. The temporary and client-side variants do not carry the same weight, and a chain that mixes types leaks more than its length implies. The mechanics are detailed in 301 vs 302 for SEO.
The mistake: assuming every hop is a 301. A 302 buried mid-chain breaks the canonical signal, and a JavaScript redirect can be missed entirely by tools that do not render.
How to fix and prevent chains: collapse to one hop
The fix is always the same shape. Point the first redirect straight at the final live URL, delete the intermediate hops, and update internal links so they never enter a redirect at all. Prevention is a discipline: every time a URL changes, repoint the redirects that targeted the old URL to the new one in the same change, so a second hop never forms. The consolidated table below is the mistakes-and-fixes reference.
The collapse, in practice
For a chain that runs A to B to C to D, the repair is to rewrite the A redirect so it sends traffic directly to D, then retire the B and C redirects once nothing else depends on them. The destination does not change. The path to it shrinks from three hops to one. Where the chain crosses protocols or domains, the same rule holds: the earliest hop that a live link can reach lands on the final destination in a single step.
Update the internal links, not just the redirects
A redirect is a safety net for links you cannot edit, such as external backlinks. Internal links you control belong pointed at the final URL directly, so they never trigger a redirect in the first place. Cleaning the redirect chain while leaving internal links aimed at the old URL means the crawler still walks the hop on every internal pass. Fix both, and the chain disappears from internal navigation entirely.
| The mistake | Why it costs | The fix (done-right move) |
|---|---|---|
| Redirect pointing at another redirect | Adds a hop of latency, crawl cost, and equity risk for no benefit | Repoint the first redirect straight to the final live URL |
| Internal links aimed at the old URL | Every internal crawl walks the redirect even after the chain is collapsed | Update internal links to point at the final destination directly |
| Stacked redirects after each migration | Category change, then HTTPS, then domain move builds a three-hop chain | Repoint old redirects to the new final URL inside each migration |
| 302 or meta-refresh mid-chain | A temporary or client-side hop breaks the canonical signal a 301 would pass | Make every hop a genuine 301 or 308 permanent redirect |
| Redirecting to the homepage | An irrelevant destination is read as a soft 404 and transfers no equity | Redirect each URL to its closest topical equivalent, never a catch-all |
| A loop that never resolves | The page is offline, returns a too-many-redirects error, and strands its equity | Break the cycle so the chain ends on one live destination |
| Trusting a “redirect works” checker | It confirms the destination loads but hides the hops behind it | Audit with a hop-counting crawler, not a single-status checker |
| Auditing once and never again | New chains form silently at the next restructure or migration | Re-run the chain audit after every URL change as a standing step |
Redirect chains and the aged-domain 301: protecting the authority you paid for
This is the connection the field never draws. When an aged or expired domain is acquired and 301-redirected into a money site, the whole point of the purchase is the inherited authority crossing that hop. A chain on top of that redirect leaks the exact asset you paid for. And a chain on top of a junk domain leaks nothing worth keeping, because there was no real authority in the source to begin with. The domain quality and the clean single hop are two halves of the same decision.
The chain trap after an acquisition redirect
An expired-domain 301 starts as a single, deliberate hop: the bought domain to the target page. The trap forms later. The target page moves during a redesign, and the redirect is not repointed, so the inherited authority now crosses the acquisition hop and a second hop to the page’s new home. The careful single 301 has quietly become a chain, and the equity the purchase was meant to deliver is being taxed on every crawl. Auditing acquisition redirects is the same discipline as auditing any chain, with higher stakes, because a paid-for authority signal is what leaks.
The asset has to be real before the hop matters
A redirect is a pipe, and a pipe only delivers what enters it. A clean, earned-authority domain pushes a real signal through a single 301. A junk or spam-flagged drop pushes a liability, and collapsing its chain to one perfect hop changes nothing, because the source never carried authority worth transferring. This is the neutral, honest read of redirect strategy: done right, a 301 from a genuinely strong domain is among the cleanest authority moves in SEO. Done wrong, on a junk domain or through a sloppy chain, it moves nothing or moves risk. The timing of when to deploy that redirect is its own decision, covered in When to Deploy a 301 After Acquisition.
Source the authority that survives a single clean hop
Every fix in this guide assumes the source domain carries something worth protecting. The signals that separate a clean, earned profile from an inflated one are the same ones that decide whether a 301 is worth running at all: real referring domains, a balanced Trust Flow to Citation Flow ratio from Majestic, a clean Moz Spam Score, link age, and verifiable history through ICANN-era registration records and RDAP, which replaced the public WHOIS lookup as the ICANN standard on 28 January 2025. A domain that passes those screens is the raw material a redirect can genuinely deliver. SEO Domains operates the curated marketplace where aged and expired domains are screened across that profile before they are listed and priced.
301 redirect chain frequently asked questions
The five questions site owners and SEOs raise about redirect chains, answered against Google’s published guidance and the equity-and-relevance reality this guide draws.
Q1How long can a redirect chain be before it is a problem?
One hop is the target, and Google’s guidance is no more than three where a direct redirect is not possible. Googlebot follows up to ten hops before it stops, but ten is the technical cliff, not a safe range. Four or more hops is the point standard auditing workflows flag for an immediate fix.
Q2Do redirect chains lose link equity, or not?
It depends which source you trust. Google states that 301s pass ranking signals and that 3xx redirects no longer lose PageRank. The long-standing industry heuristic assumes roughly 5 percent loss per hop, which would leave a three-hop chain at about 85.7 percent. Both readings agree the chain belongs collapsed to one hop, and both agree the larger, undisputed cost is crawl budget and latency.
Q3What is the difference between a redirect chain and a redirect loop?
A chain resolves to a live page after two or more hops, so it works but taxes everyone who walks it. A loop bends back on itself and never resolves, returning a redirect-loop error that takes the page offline. A loop is the more urgent failure because the page is unreachable.
Q4How do I find and fix redirect chains?
Crawl the site with a redirect-aware tool such as Screaming Frog, Ahrefs Site Audit, or Semrush, export the redirect chains report, and sort by hop count. Repoint the first redirect straight to the final URL, retire the intermediate hops, and update internal links so they point at the destination directly. Re-run the audit after every migration.
Q5Does a redirect chain hurt an expired-domain 301?
Yes, and it hurts more than a routine chain, because the whole purpose of an expired-domain redirect is the inherited authority crossing the hop. If the target page moves and the redirect is not repointed, the bought authority starts crossing two or three hops and leaks on every crawl. The fix is to keep the acquisition redirect a single direct hop, and to start from a domain whose authority was real to begin with.
The bottom line: one clean hop from a domain worth redirecting
A redirect chain is a self-inflicted tax. It adds latency, burns crawl budget, risks the inherited equity, and on an irrelevant hop it can lose that equity entirely. The repair is unambiguous across every source: collapse each chain to a single direct hop, make every hop a permanent 301, point each redirect at a relevant destination, and update internal links to the final URL. None of it pays off, though, unless the domain at the start of the redirect carried real authority in the first place.
Why the source domain is the variable that decides it
Everything in this guide converges on one point. A flawless single 301 from a junk domain transfers a flawless nothing. A chain on a genuinely strong, clean aged domain leaks an asset that was worth protecting. The redirect mechanics and the domain quality are not separate concerns. They are the two halves of whether a 301 strategy works, and the domain is the half that has to be right before the hop count even matters.
Start the redirect with an asset, not a liability
The legitimate demand behind every redirect-chain search is the same: protect the authority a 301 is meant to carry. That authority is a real asset when it sits on a clean, earned-history domain, and it is a liability when it sits on an unvetted drop. SEO Domains operates the curated marketplace where aged and expired domains are screened across their backlink profile, authority metrics, and registration history before they are listed, so the domain feeding your redirect is the asset, not the risk. Browse screened inventory on the SEO Domains marketplace, and keep the hop that carries it down to one.
