See every hop from the first URL to the final page, with status codes and timing. Check up to 50 URLs or all 4 versions of your domain, and copy the rule that cuts a chain to one hop.
A redirect chain is when one URL redirects to another, which redirects again, and so on. Each extra hop makes the page slower and makes it harder for Google to follow. Chains often build up over years of site changes, like moving to HTTPS, then to www, then to new URLs. This tool shows the full path and gives you the rule to send visitors straight to the final page in one hop.
| Problem | Why it matters | Fix |
|---|---|---|
| Chain (2+ hops) | Slower pages, harder for Google to follow | Redirect the first URL straight to the final one |
| Loop | The page never loads | Fix the rules that point back to each other |
| Temporary redirect (302, 307) | Google may keep the old URL | Use 301 or 308 for permanent moves |
| HTTPS to HTTP | Visitors lose a secure connection | Keep every hop on HTTPS |
| Ends in an error | The redirect leads to a 404 or 5xx | Point it to a working page |
| Domain versions split | Duplicate versions of your site | Send all 4 versions to one in one hop |
Up to 50 URLs are cleaned, or the 4 versions of your domain are built.
In your browserOur server requests it without following redirects automatically.
Our serverThe Location header is followed hop by hop, recording status code and time.
Our serverChains, loops, temporary redirects, HTTPS downgrades and errors are flagged.
In your browserA rule is built that sends the first URL straight to the final URL in one hop.
In your browserIf http://example.com/old goes to https://example.com/old, then to https://www.example.com/old, then to https://www.example.com/new/, that is 3 hops. The fix is one rule: send /old straight to https://www.example.com/new/ with a 301.
The tool writes the rule for Apache .htaccess, Nginx and the WordPress Redirection plugin.
The tool follows server redirects (3xx). Redirects made by JavaScript or meta refresh in the page are not followed. Timings depend on the distance between our server and yours.
Every step with status and time.
Bulk check after a site move.
http, https, www and non-www in one check.
Catches endless redirect loops.
Flags any hop that drops to HTTP.
Copy rules for Apache, Nginx and WordPress.
Clean up chains after migrations.
Test redirect rules before and after deploys.
Fix chains left by plugins and old moves.
Check where backlinks really point.
First release with full hop paths, bulk mode for 50 URLs, domain version check and one-hop fix rules.
We run the tool against our test cases again and check Google's redirect guidance and HTTP standards for changes.
Tool page last reviewed on .
Tell us what you entered, what happened and what you expected. Our developer checks every report, fixes confirmed bugs as a high priority and tests the fix before it goes live.
This page follows our Editorial Policy and Methodology. If something here is wrong, our Corrections Policy explains how we fix it. Learn more about the SpellMistake team.
No ratings yet. Be the first to rate this tool.
How useful was the Redirect Chain Checker for you?
Ratings come from real visitors. One rating per person. We never add, edit or remove ratings.
A redirect chain is when a URL redirects to another URL that also redirects, so visitors and Google pass through 2 or more hops before the final page.
Yes. It is 100% free, with no sign-up.
They slow pages down and make crawling harder. Google follows up to 10 hops, but one hop is best for speed and clean signals.
301 is a permanent move and passes value to the new URL. 302 is temporary, so Google may keep the old URL in search.
Find the rules that point back to each other, often an HTTPS rule and a www rule, and merge them into one rule.
http, https, www and non-www should all end on one version in one hop. Otherwise you can have duplicate versions of your site.
Up to 50 URLs per check.