How many redirect hops is too many?

One is ideal, two is unremarkable, three starts costing users measurable time. Engines will generally follow several but there is no benefit to testing the limit, and the user-facing latency argument settles it before the ranking argument needs to.

Do redirects lose link equity?

A permanent redirect passes signals, and the long-standing guidance is that no meaningful loss occurs. The practical risks are chains that get abandoned partway, redirects to irrelevant pages, and redirects that end in errors, not a percentage lost per hop.

Should I redirect a deleted page or let it 404?

If a genuinely equivalent page exists, redirect to it. If not, let it 404 or 410. Redirecting everything to the homepage is treated as a soft 404, gains nothing, and makes your own reporting harder to read.

Redirect chains: the cost, and when it is worth fixing

You have redirects stacked on redirects and want to know whether it is hurting you enough to be worth an afternoon.

Short answer

A redirect chain is two or more hops between the requested URL and the final page. Each hop is a separate round trip, so chains cost real time for users and real requests for crawlers. Modern engines follow several hops and pass signals through them, so a two-hop chain is a performance problem more than a ranking one. Long chains and loops are a genuine ranking problem because they can end in nothing being indexed.

What a chain actually costs

Every hop is a full request: DNS, connection, response, then start again. On a slow mobile connection three hops can add most of a second before the page even begins to load. That cost lands on the user first and on your crawl second, which is why this is worth fixing even where the ranking effect is negligible.

How chains accumulate

Nobody builds one deliberately. They grow: a page moves, then the site moves to https, then the URL structure changes, then www is enforced. Each change adds a rule that fires on top of the last, and because every individual change was tested and worked, nobody notices the stack.

The ones that matter most

Redirects on your highest-traffic entry points, because that is where the latency lands on the most people. Redirects in your sitemap, because you are explicitly telling crawlers to fetch a URL that is not the destination. And redirects on URLs that carry external links, because that is where the signal has furthest to travel.

Loops and soft failures

A loop is fatal: the browser gives up and the page is unreachable. Subtler is the chain that ends in a 404 or a login, which happens when an old URL redirects to a section that itself has since been removed. Those look fine in a redirect map and deliver nothing.

Temporary versus permanent

A 302 says the move is temporary and the original should be kept. A 301 says it is permanent. Using 302 for a permanent move is common, usually accidental, and it means engines may keep returning to the old URL indefinitely. If the move is permanent, say so.

How to find yours

Take your top pages and your sitemap URLs, request each one, and record every hop. Anything above one hop is a candidate. Fix by pointing the first rule directly at the final destination rather than adding another rule to the pile.

The honest scale of the problem

On a small site with clean URLs this is a tidy-up, not an emergency. It becomes urgent after a migration, when hundreds of URLs can acquire multiple hops at once and the cumulative crawl cost is real. Sequence it accordingly rather than treating it as an always-critical item.

Questions

How many redirect hops is too many?: One is ideal, two is unremarkable, three starts costing users measurable time. Engines will generally follow several but there is no benefit to testing the limit, and the user-facing latency argument settles it before the ranking argument needs to.
Do redirects lose link equity?: A permanent redirect passes signals, and the long-standing guidance is that no meaningful loss occurs. The practical risks are chains that get abandoned partway, redirects to irrelevant pages, and redirects that end in errors, not a percentage lost per hop.
Should I redirect a deleted page or let it 404?: If a genuinely equivalent page exists, redirect to it. If not, let it 404 or 410. Redirecting everything to the homepage is treated as a soft 404, gains nothing, and makes your own reporting harder to read.

Measured, not asserted

The audit that fetches a URL for ihatepdf.cv records the full redirect chain and time to first byte, because those two are unanswerable from HTML alone. On a site that reached 100,542 users, the chains that mattered were the ones on the five pages carrying 75.4% of all clicks, not the long tail.

Free tool for this: SERP Audit. No account, nothing uploaded.

Where this goes deeper

Every number on this page comes from one complete dataset: one product taken from zero to 100K+ users on search alone, with nothing spent on advertising. The full argument is Chapter 10 and Chapter 11 of the book. Five chapters are free to read.