SEO

Redirect chains and broken links: how to find them and which ones matter

A redirect chain sends a visitor or crawler through several URLs before reaching the page, and a broken link points at a page that no longer exists. Both turn up in nearly every crawl. The useful question isn’t how many there are but which ones affect pages you want found, and which are just noise.

What a redirect chain is and why it happens

A redirect chain is a series of redirects in a row, such as URL A to B to C. Each change to a site adds another hop: an http to https rule, a trailing-slash rule, a renamed page, and a later restructure. Nobody plans a chain, they build up when old redirects are left in place.

Google’s crawler documentation says Googlebot follows up to 10 redirect hops by default when crawling general web content [1]. That’s a ceiling, not a target. Google’s site-move guidance recommends redirecting to the final destination directly, and if that isn’t possible, keeping chains short, ideally no more than three and fewer than five [2]. It also notes that chaining adds latency for users and not all browsers and user agents handle long chains [2].

A loop is the worst case. URL A redirects to B and B redirects back to A, so nothing resolves. Browsers show a “too many redirects” error and Search Console reports it as a redirect error.

How to find them

A crawler that follows redirects and records every hop is the quickest tool. Export the list of URLs that redirect, with the number of hops and the final destination. Anything with more than one hop is a chain, and anything that never reaches a 200 is a loop or a dead end.

Search Console adds the view from Google’s side. The Page indexing report includes a status for pages with a redirect and one for redirect errors [3]. Comparing that list with your crawl shows which chains Google has actually met.

Check the type of redirect too. Google’s documentation says a permanent redirect is treated as a signal that the target should be canonical, while a temporary one isn’t [4]. A temporary 302 left on a page that moved for good is a common fault, and it’s cheap to fix.

Finding Usual cause What I’d do
A to B to C An old redirect left in place after a later change Point A directly at C
A to B and B back to A Conflicting rules, often a plugin and a server rule Remove one rule and retest
302 where the move is permanent A default setting Change to 301
Internal links pointing at redirecting URLs Menus and old content never updated Update the links to the final URL
Redirects ending at a 404 A destination page later deleted Redirect to a real equivalent, or accept the 404

A broken link is a link whose target returns an error, usually a 404. Google’s guidance is that 404s on URLs that should no longer exist don’t harm the rest of your site in search [5]. The Search Console help page agrees that you can usually ignore 404s for pages that are meant to be gone [6]. Both are older sources, so I’d treat them as reassurance and not a licence to ignore everything.

What I’d fix is any broken link that sits on a page people or Google actually use. An internal link to a dead page sends visitors to an error, and it wastes the link. A broken link in the main navigation, in a high-traffic post or on a page that earns enquiries is worth fixing quickly. A stray 404 from a mistyped URL on another site probably isn’t.

Soft 404s are the case to watch. A soft 404 is a page that tells the visitor it’s missing but returns a 200 status [7]. Google’s guidance is to return a real 404 or 410 when content is gone with no replacement [7].

Redirecting everything to the homepage

When pages are deleted, the tempting repair is a blanket redirect of every missing URL to the homepage. Google’s guidance lists redirecting unknown URLs to the home page, instead of returning 404s, as a pattern that can confuse how it understands the site [5]. It also tends to look like a soft 404.

A better answer depends on the URL. If there’s a genuinely equivalent page, redirect to that. If not, let it 404 or return 410. For a large set of old URLs, the redirect mapper matches old to new by path and flags the ones that need a human decision. For migration work, the migration checklist covers where this fits.

What I’d do

Fix in this order: loops, chains that include a temporary redirect, internal links to redirecting URLs, then broken internal links on valuable pages. Leave genuine 404s for removed content alone. Re-crawl afterwards to confirm each one resolves in a single step.

If a recent change caused the problem, what goes wrong in a site migration lists the faults that tend to appear after a move. The technical SEO audit includes redirect and link checks across the whole site.

Redirect chains and broken links

FAQ

How many redirects are too many?

Google follows up to 10 hops, but advises redirecting straight to the final destination, and says chains should ideally be no more than three and fewer than five. In practice I’d aim for one hop everywhere I can, because extra hops slow users down.

Do 404 errors hurt SEO?

Not by themselves. Google has said 404s on URLs that should no longer exist don’t harm the rest of your site. They matter when internal links or valuable pages point at them, or when a page that should exist returns an error.

Should I redirect deleted pages to the homepage?

Usually not. A redirect to the homepage rarely matches what the old page offered, and Google lists it as a pattern that can confuse how it reads a site. Redirect to a closely equivalent page, or let the old URL return a 404 or 410.

What is a soft 404?

A page that tells visitors it can’t be found but returns a 200 success status. Google recommends returning a proper 404 or 410 instead, so crawlers understand the page is gone. Search Console reports soft 404s in the Page indexing report.

Sources

  1. Google Search Central, How HTTP status codes affect Google’s crawlers, accessed 2 November 2026.
  2. Google Search Central, Site moves and migrations, accessed 2 November 2026.
  3. Search Console Help, Page indexing report, accessed 2 November 2026.
  4. Google Search Central, Redirects and Google Search, accessed 2 November 2026.
  5. Google Search Central Blog, Do 404 errors hurt my site?, May 2011.
  6. Search Console Help, 404 (Page not found) errors.
  7. Google Search Central, Troubleshoot Google Search crawling errors, accessed 2 November 2026.

Get started

Proof, not promises.

Tell me what's going on and I'll come back with what I'd do first. No obligation, and no report you need a translator for.

Over 925,000 impressions and 13,795 clicks in a year, from people asking one awkward question: what size do I need?condoms.uk, past 12 months

Get in touch WhatsApp

Brands and sites I have worked on

Brands worked on across nearly twenty years, in agency roles and directly.