URL Redirect Checker
Follow a URL hop by hop and see every redirect's status code, destination, server and timing — plus clear advice on chains, loops and SEO-safe redirect types.
Checked live from our server — no signup Free, no limits
How to use the Redirect Checker
- Enter a URL or domain (https:// is added if you leave it out), or switch to Bulk and paste up to 10 URLs, one per line.
- Pick the user agent to test with — a normal browser, Googlebot, or our bot.
- Click Trace redirects.
- Read the chain from top to bottom and fix anything flagged: extra hops, temporary redirects or loops.
Frequently asked questions
What is the difference between a 301 and a 302 redirect?
A 301 (and 308) says the move is permanent, so search engines transfer ranking signals to the new URL and index it instead. A 302 (and 307) says the move is temporary, so Google keeps the old URL indexed. Use 301/308 for permanent moves like http→https or a changed slug.
When should I use 307 or 308 instead of 302 or 301?
307 and 308 guarantee the browser repeats the same method and body (a POST stays a POST). 302 and 301 allow browsers to switch to GET. For normal page moves 301 is fine; 308 is the strict modern equivalent.
Why are redirect chains bad?
Each extra hop adds a full round trip, so users wait longer, and crawlers may stop following after several hops (Googlebot follows up to 10). Point every old URL straight at the final destination in a single redirect.
What causes a redirect loop?
Two rules that send traffic back and forth — for example the server forcing https while a CDN or plugin forces http, or www and non-www rules that contradict each other. Browsers show ERR_TOO_MANY_REDIRECTS.
Do you follow meta refresh and JavaScript redirects?
We detect them on the final page and show where they point, but don't follow them, because they only happen after a browser loads the page. Search engines treat them as weaker signals than a server-side 301.
Why does the result differ from what I see in my browser?
Some sites redirect differently by user agent, country, language or cookies. Try switching the user agent, and remember your browser may have cached an old 301.