Redirect Checker
See every hop a URL takes before it lands. This free redirect checker follows the full redirect chain step by step and shows the real HTTP status code at each stage — 301, 302, 307, 404 or 200 — so you can spot redirect chains, loops, and broken links that quietly cost you rankings and speed.
💡 We follow up to 10 hops and stop there, so a redirect loop is reported instead of hanging. Redirects created by JavaScript or by a meta refresh tag inside the page cannot be seen from the server — only real HTTP redirects appear here.
How the redirect checker works
One hop at a time, so nothing is hidden from you.
Paste the URL
An old page, a short link, a campaign link — anything public.
We follow each hop
Our server requests each step without auto-following, so every code is captured.
Read the chain
Every URL, its status code, and how long that hop took.
301 vs 302 — and why the difference matters
A 301 says "this page has moved permanently". Search engines pass the old page's ranking signals to the new URL and eventually replace it in the index. A 302 (and 307) says "this is temporary — keep the old URL". Using a 302 for a permanent move is one of the most common and most expensive mistakes in a website migration: the new page never fully inherits the old one's authority, and you wonder why traffic dropped after the redesign.
Chains are the other problem. If old-page → new-page → newer-page → final-page, every visitor waits through four requests, and each hop is a chance for something to break. Point the first URL straight at the final one instead. A quick HTTP status code check after any redesign or domain change catches both issues in seconds.
When you should check your redirects
After a redesign, after moving from HTTP to HTTPS, after changing your permalink structure, and always after a WordPress migration or a move to a new host. Also check any shortened link before you spend money on it: if a redirect drops the query string, your campaign tags are lost, which is why we suggest testing links built with our UTM builder before the ad goes live.
Redirect problems rarely travel alone. Dead links usually show up at the same time, so pair this with our broken link checker, confirm your certificate is valid with the SSL checker, and measure what the extra hops cost you in load time with the website speed test. If you would rather someone else untangle it, that work sits inside our website maintenance and WordPress support plans.
Redirect checker — FAQs
How many redirects are too many?
One is ideal. Two is tolerable. Three or more slows the page noticeably and risks search engines giving up before they reach the destination — flatten the chain so the first URL points straight at the last.
Which redirect should I use for a moved page?
A 301 (or 308) for anything permanent, so ranking signals transfer. Keep 302 and 307 for genuinely temporary situations like a sale page or maintenance notice.
Why does my URL show a 404 at the end?
The redirect points somewhere that no longer exists. Fix the redirect target, or restore the page. This is the single most common cause of lost traffic after a redesign.
Can this see JavaScript or meta-refresh redirects?
No — those happen inside the browser after the page loads. This tool reports real HTTP redirects only, which is what search engines follow and what matters most for SEO.
Can you fix my redirects after a site move?
Yes. Mapping old URLs to new ones is a standard part of our migration service and our ongoing maintenance plans.
Moving your site? Don't lose your rankings.
We map and test every redirect so the traffic you built follows you to the new URLs.
Plan My Migration →