Trace the redirect chain of any public URL — every hop, exact HTTP status, latency at each step. Catches redirect loops, 302→301 mixups, HTTPS→HTTP downgrades, and unnecessarily long chains. For monitoring your own site continuously, use Site Health → Redirects after signing in.
Enter a URL
We'll follow every redirect up to 20 hops and show you the full chain.
What counts as a "healthy" redirect chain?
• Zero or one hop. Each extra redirect adds latency and bleeds a little link equity on the way.
• Use 301 (permanent). 302/307 are for temporary moves; Google sometimes still honours the old URL's ranking.
• Never downgrade HTTPS → HTTP. It leaks the referrer and breaks mixed-content protections.
• Avoid 302 → 301. Pick one or the other; mixing them confuses search engines.
These tools are free and need no account.
They check one page at a time. RankCause itself does the thing they can’t:
it watches your pages over time and tests whether a change you made
actually moved a ranking.