Craig Campbell SEO Training & Consultancy

Tutorials

Redirect chains SEO: find unnecessary hops and fix the destination

By Craig Campbell · 15 Nov 2026

4 min read

A redirect chain sends a visitor through more than one redirect before reaching the final page. A redirect loop never reaches a usable destination because the URLs send the request back around.

The useful fix is not “remove every redirect”. Keep redirects that protect old links, but send each old address as directly as possible to a relevant working page.

This guide uses Harbour & Hide, a fictional Glasgow outdoor shop. All businesses, URLs and decisions are illustrative only, not a crawl of Craig’s site or measured client results. Sources checked 15 November 2026.

1. Collect the URLs worth checking

Start with old addresses that still matter: navigation links, historic product pages, links from other sites and URLs in a migration map.

  • Export internal URLs with a crawler that records response codes and destinations.
  • Include old HTTP, hostname and path variations where relevant.
  • Review existing redirect rules as well as current pages.
  • Include important retired URLs; a crawl of the current site alone can miss them.

Keep a sheet with source URL, each hop, final response, intended replacement and decision. The migration checklist covers the wider launch process.

2. Separate chains, loops and wrong destinations

  • Chain: old page → intermediate page → final page.
  • Loop: page A → page B → page A.
  • Wrong destination: the request ends successfully, but the content does not replace the old answer.
  • Broken destination: the redirect ends at an error or unavailable page.

Check the complete response path, not just the first status. Google recommends avoiding chains and redirecting directly to the final destination where possible. Extra hops also add requests for visitors; the benefit of removing them depends on the site.

Do not attach a fixed percentage of “lost link value” to every hop. That is not a reliable way to estimate the impact.

3. Choose the replacement before changing rules

A permanently moved page normally needs a permanent server-side redirect, such as 301 or 308. Use a temporary redirect when the move really is temporary. These signals do not guarantee Google’s final indexing choice.

  • Map an old page to its genuinely equivalent replacement.
  • Keep a retired page’s content when it is still useful and appropriate.
  • If there is no suitable replacement, returning a proper 404 or 410 can be better than redirecting everything to the homepage.
  • Review exceptions manually; similar wording in two URLs does not prove matching intent.

Harbour & Hide — fictional UK example; illustrative only

Before: /raincoats → /walking-jackets → /waterproof-jackets.

The final category genuinely replaces both earlier ranges in this invented example.

  • Old source: /raincoats → /waterproof-jackets.
  • Intermediate source: /walking-jackets → /waterproof-jackets.
  • Current links: update menus and guides to point straight to /waterproof-jackets.

Keep both old-source redirects. Removing the intermediate rule entirely would break people arriving at /walking-jackets.

Different decision: an old workshop page has no equivalent. Do not send it to the jackets category simply to avoid a 404.

These paths are example-shop addresses, not links on Craig’s website.

5. Test before and after release

Test changes in a safe environment, then repeat the checks on the actual public addresses.

  • Confirm each source reaches its intended final URL.
  • Check for loops, wrong hosts and accidental query-string changes.
  • Check the final response is 200 and inspect the content.
  • If the destination should appear in search, check indexability and its canonical signal too.
  • Update internal links and sitemaps to preferred final URLs.
  • Recheck representative old links after any later rule changes.

For site moves, Google recommends keeping redirects for at least a year; useful old links may justify keeping them much longer.

Limitations and next step

A clean redirect path does not guarantee rankings or immediate reindexing. Crawlers can miss unlinked historic URLs, and your hosting platform may impose some normalisation hops.

Start with valuable old pages and loops, then tidy internal links. Use Search Console to investigate indexing and the crawl-budget guide to judge whether crawl efficiency is a meaningful priority for your site.

Sources

Sources checked 15 November 2026. The workflow and fictional examples are editorial recommendations, not firsthand testing or client results.

Let's work together.

Whether you need an SEO partner, a consultant, a speaker for your event or training for your team — get in touch and let's chat.

Get in touch
Get in touch