SEO
6 min read
June 8, 2026

Redirect Chains Are Quietly Killing Your SEO — Here's How to Find and Fix Them

Every extra redirect hop between a link and its destination leaks a little SEO value and adds real load-time delay. Most site owners have no idea how many chains are hiding on their site — until they trace one.

What a Redirect Chain Actually Costs You

A redirect chain happens when URL A redirects to URL B, which redirects to URL C, which finally lands on the real page. Each of those hops:

  • Wastes crawl budget — Googlebot has a limited number of requests it'll spend on your site per visit; chains burn through that budget on hops instead of content
  • Dilutes link equity — some PageRank-style value is lost at every redirect, especially across long chains
  • Slows down real users — every hop is a full round-trip HTTP request before the page even starts loading
  • Risks breaking entirely — Google has confirmed it will stop following a chain after a certain number of hops, effectively turning your "redirect" into a dead end
  • The frustrating part: chains accumulate silently. A URL gets redirected during a migration, then redirected again during a redesign two years later, and now you've got a three-hop chain nobody remembers creating.

    How to Trace Any URL's Full Redirect Path

    Our Redirect Chain Checker does exactly what Ahrefs' redirect tracer does — paste any URL and it follows every 301/302/307/308 hop live, in real time, showing you:

  • Every hop in the chain, with its HTTP status code
  • The final destination URL and its status
  • A Crawl-Efficiency Score out of 100 — a clean, direct URL scores 100; each additional hop drags the score down
  • Specific flags for redirect loops (URL A → B → A), oversized chains (4+ hops), and broken endpoints (chains that terminate in a 4xx/5xx)
  • It's computed live and deterministically — no cached database, no stale data. You see exactly what a crawler sees right now.

    The 3 Most Common Chain Patterns to Look For

    1. The "migration leftover" chain — old-domain.com → www.new-domain.com → new-domain.com/page. Each migration adds a layer if nobody updates the original links.

    2. The "trailing slash" loop — /page → /page/ → /page (a classic misconfiguration that can also create infinite loops if caught wrong).

    3. The "HTTP to HTTPS to www" stack — http://site.com → https://site.com → https://www.site.com. This one is everywhere, and it's almost always fixable by pointing the original link directly at the final HTTPS+www version.

    How to Fix What You Find

    Once the Redirect Chain Checker shows you a chain, the fix is almost always the same: update the source link or server rule to point directly at the final destination, collapsing the chain to a single hop (or zero, if you can update the link itself rather than redirecting).

    For internal links specifically, run the page through our Internal Linking Suggester afterward — it's a good moment to also review whether your internal links are pointing at the current canonical URLs, not legacy ones that need a redirect at all.

    Make It a Routine Check

    Redirect chains aren't a one-time fix — they reappear every time you migrate, restructure, or rebrand. Pair the Redirect Chain Checker with our Broken Link Checker and Canonical & Indexability Checker for a complete technical health pass: one finds chains, one finds dead links, and one confirms the pages at the end of your links are actually indexable.

    The Bottom Line

    A single redirect hop is normal and harmless. A chain of three or four is a slow leak — in crawl budget, in link equity, and in page speed. Tracing your most important URLs (homepage, top landing pages, anything you've migrated) takes thirty seconds with the Redirect Chain Checker, and the fix is usually a one-line update once you know exactly where the chain breaks down.

    Written by the GMC Tools team