Free redirect checker
Trace every hop of a URL's redirects with the status code of each: 301 or 302, chains, loops, and whether the insecure http:// address upgrades to https://. No signup.
A bare domain starts at http:// so you see the HTTPS upgrade too. Nothing is stored.
What this checker tests
Redirects are how a website says "this page lives somewhere else now". Done well, visitors and search engines never notice. Done badly, they cost you rankings and speed without any visible sign. This tool requests the address you enter without following redirects automatically, so it can record each hop: the status code, where it points, and what the final page returns.
Reading your result
One 301 redirect, ending in a 200 is the ideal when a page has moved. 302 or 307 redirects are flagged because they tell search engines the move is temporary, so the old address can linger in results. Chains of two or more hops are flagged because each adds a round trip, which is slow on mobile and wastes crawl budget. Loops, dead ends (a redirect to a 404) and HTTPS downgrades are marked as problems to fix now.
When to use it
Before and after a redesign or platform move is the big one: our website migration SEO checklist explains why. It's also the quickest way to check that http:// and www versions of your site all land on one address (see www vs non-www), and to settle which redirect type you actually need.
This is one check. Your site needs dozens.
The full AuditCrow audit runs this alongside speed, SEO, accessibility, trust and AI readiness, then tells you what to fix first, in plain English.
Common questions
Straight answers about what this check does, and doesn't do.
What's the difference between a 301 and a 302 redirect?
A 301 says a page has moved permanently, so search engines move its rankings to the new address. A 302 (or 307) says the move is temporary, so the old address may stay in search results. If a page has moved for good, use a 301 or 308.
What is a redirect chain?
A chain is when one redirect leads to another, for example http to https, then to www, then to a new page. Each hop adds a delay for visitors and wastes crawl budget. The fix is to point the first address straight at the final one.
Why does a bare domain start at http://?
So you can see the whole journey a first-time visitor takes, including whether the insecure http:// address upgrades to https://. Type https:// yourself if you only want to trace from the secure version.
What causes 'too many redirects'?
A loop: two rules that undo each other, such as one sending www to non-www and another sending it back, or a CDN and a server disagreeing about HTTPS. The checker shows the exact hops so you can see which pair is fighting.
From the blog
All posts301 vs 302 Redirects: Which One You Actually Need
A 301 redirect passes ranking signals to the new URL. A 302 doesn't, unless it's left in place so long Google treats it as permanent anyway. Here's how to pick the right one.
Read moreThe Website Migration SEO Checklist (Redesigns, Replatforms, and Domain Moves)
A redesign, a CMS switch, or a domain change can quietly cost a site its rankings if nobody checks what actually happened underneath. Here's what to verify before and after.
Read morewww vs non-www: Why It Doesn't Matter Which You Pick, But It Matters That You Pick
www.example.com and example.com look identical to a visitor and are treated as completely different URLs by search engines. Neither version is better for SEO. Leaving both reachable at once is what actually costs you.
Read moreOther free tools
Quick checks for the things that most often go quietly wrong.