What counts as a chain
For a planned URL move, use the migration redirect map and QA worksheet to choose destinations before investigating the live hops.
A chain is any URL that passes through more than one redirect before landing. The common versions: A to B to C (two hops, the classic accumulated-history chain); http to https to www to the final URL (a host-canonicalisation gauntlet); and the sitemap special, where the sitemap lists a URL that redirects instead of the final address. Every crawler pays a hop on your most important URLs, because those are the ones you told it about.
| Pattern | Verdict |
|---|---|
| 0 redirects | Ideal: link and list final URLs directly |
| 1 redirect | Acceptable and sometimes unavoidable (http to https, retired URLs) |
| 2+ in sequence | A chain: flatten to a single hop |
| Redirect to a 404 | Worse than none: the link was maintained and still fails |
What chains actually cost
Google follows up to a handful of hops and then gives up, so a long chain eventually reads as "page not found" regardless of intent. Each hop is a separate fetch: crawls get slower, crawl budget burns faster, and on a 50k-product store the multiplication matters. Signal dilution is the contested part: a single redirect passes most of a link's value and more than one hop historically passed less. What is not contested: mobile browsers and link previews resolve chains slower, and a chain that ends on a 404 (someone redirected to a URL that later died) is a dead end every visitor discovers one hop late.
A chain anywhere is a small tax. A redirect on a sitemap URL is a chain on every crawl: sitemap entries should point at final URLs only. It is the first thing to check and the cheapest to fix.
Finding them without a full crawl
The check re-requests your key URLs with redirects turned off (the crawler's trick) and inspects what comes back. A direct 200 is clean. A single well-formed redirect to the same path on the canonical host is correct. Anything further along the chain is reported: which URL it hops to, and whether the hop count is already too long. The free redirect check does exactly this on a set of your pages, from outside your network, in seconds.
Flattening them safely
- Point every redirect at the final destination. Rewrite the source redirect to target the live URL, not the intermediate one.
- Update the sources of the old URLs: internal links, sitemap entries, menu items should all name the final URL directly.
- Do not stack a new redirect on an old chain. When a URL moves again, replace the old mapping rather than adding another layer.
- Re-check after the fix. The check follows every hop, so a flattened chain shows as a single hop or a clean 200, and the watch tells you when a new one appears.
Related: broken internal links · orphan pages · soft 404s and redirects on Shopify
Shipwork requests your key pages with redirects disabled, follows the hops manually, and reports every chain: which URL hops where, how many times, and where the sequence ends. Free, no account, no signup. Paste your store address.
Check my redirectsQuestions
How many redirects in a chain is too many?
Do redirect chains hurt SEO?
Is http to https a bad chain?
Should sitemap URLs ever redirect?
Keep reading