Blog / Technical SEO /
Redirect chains: finding and fixing them
One redirect is fine. Three in a row is a game of pass-the-parcel: the old URL sends you to another URL, which sends you somewhere else, and so on until someone drops it. Chains add delay, make troubleshooting a headache and can end somewhere broken. They usually build up over several rounds of site changes, because nobody went back to update the first redirect.
The fix is simple. Crawl the site, look at the hops, and point internal links at the final destination. Keep the redirect map tidy, test each change, and don’t swap a useful redirect for a route that no longer matches the original page.
What a redirect chain looks like
Suppose /old-guide/ redirects to /guide/, which later redirects to /updated-guide/. A visitor and crawler need to request each URL before reaching the final page. A chain can contain several hops, and a loop can send the browser round and round until it gives up.
Chains happen when a URL changes more than once and the old rule is left in place. They can also result from changing HTTP to HTTPS, adding or removing www, migrating a CMS, or moving content between folders without updating earlier redirects.
A single permanent redirect is often the right way to preserve a changed URL. The aim isn’t to remove every redirect. It’s to send old URLs straight to the most relevant final page, with internal links already pointing there.
Find the chains
Start by crawling important site URLs with a crawler that reports status codes and redirect destinations. Include XML sitemap URLs, internal links and known legacy URLs. Export the results and look for any source URL whose destination also redirects.
I always check the final URL by hand, in a browser and with a header checker. Confirm that it loads, returns an appropriate status and contains the expected content. A redirect to a homepage may technically work but still be irrelevant to someone following an old product or article link.
Review the redirect configuration in the platform, CMS, hosting panel, CDN or plugin. A chain can be assembled across more than one layer: a server redirect to a Shopify URL, followed by an app redirect, for example. Identify all places rules may be configured before editing them.
For a smaller site, use Search Console’s indexing reports and analytics landing pages as clues to old URLs, but do not rely on them as a complete redirect inventory. External links, bookmarks and old marketing materials may still point to URLs that no longer appear in current navigation.
Prioritise what matters
Fix chains on important URLs first: pages with external links, organic visits, internal links or ongoing business value. Also address chains that add multiple hops, end in errors or create loops. A chain between two low-value retired pages may be less urgent than a broken redirect for a product customers still need.
Check links in menus, content, product feeds and sitemaps. Update internal links to point directly to the final canonical URL. Leaving internal links aimed at an old address forces every visitor through a redirect and makes future auditing harder.
Don’t delete a redirect just because it shows up in a report. The old URL may still have backlinks or bookmarks. Preserve the redirect while changing its destination to the correct final URL. If there is no relevant replacement, return an appropriate not-found status rather than sending users to an unrelated page.
Fix chains safely
Create a mapping: source URL, current redirect path, intended final destination and reason for the change. Update the first redirect in the chain so it points directly to the final page. Check for conflicts with other rules and test after saving.
If you are changing server or CDN rules, keep a copy of the previous configuration and use a staging or test environment where possible. Make a small batch of changes, then crawl the affected URLs again. Confirm there are no loops, unexpected query-string changes or redirect rules that capture unrelated pages.
In WordPress, redirects may come from a plugin, server configuration or hosting provider. In Shopify, redirects are managed through the store or apps, but domain settings and external layers can also affect requests. Find the active layer first. I’d never add a second rule that fights the first.
Use permanent redirects for permanent moves and temporary redirects only when a move is genuinely temporary. Avoid chains created by mixing redirect types without a reason. The status code should match the intention, but neither a 301 nor 302 is a substitute for a relevant destination.
Test and monitor
After updating rules, test representative old URLs and crawl the final destinations. Check the browser address bar, status code, canonical tag, page content and internal links. Test both slash and non-slash versions or other URL variants where the site handles them.
Watch server logs or crawl reports for repeated requests to old paths. Keep the redirects in place while those paths remain in use. Monitor important landing pages and Search Console after a migration, but do not expect a redirect cleanup to cause a specific ranking improvement.
Document who owns the rules and when they were changed. A simple redirect log can prevent the same chain from returning during the next redesign.
Related reading
- The HTTP status codes every site owner should recognise
- Domain names and SEO: does the name still matter?
- What to do when Google ignores your canonical tag
Take one redirect chain from your crawl and map every hop. Can you point it straight at the page a visitor actually needs?