Trace the full redirect chain of any URL hop by hop. See every status code, Location header and response time, and catch loops, chains and insecure hops before Google does.
Trace the full redirect chain of any URL hop by hop. See every status code, Location header and response time, and catch loops, chains and insecure hops before Google does.
All four versions of a domain should end up at the same final URL. If they don't, search engines may treat them as separate pages competing with each other.
Each URL is requested once from this server, following up to ten hops, and results are cached for ten minutes. Redirects performed in JavaScript after the page loads cannot be detected by any server-side tool, including this one, though meta refresh tags are flagged where present.
Found a technical issue?
Our technical SEO team fixes crawl errors, redirects, schema and indexing so Google can rank every page.
A redirect sends visitors and search engines from one URL to another. Redirects are essential after site migrations, URL changes and HTTPS moves, but chains and loops quietly slow pages down and waste ranking value.
This free redirect checker traces any URL hop by hop. You see every status code, Location header and response time, the final destination, and the response headers on the final page. It flags loops, long chains and insecure HTTP hops, and can test all four versions of a domain: http, https, www and non-www.
Copy the chain or download it as CSV to share with your developer.
Enter any URL above to see every redirect between it and the final page. Ideally a URL reaches its destination in one hop with a 301 status, and all four versions of your domain (http, https, www, non-www) end at the same final URL.
Use it on old URLs after a migration, on links from other sites, and on your own domain variations.
Paste any public address, including the http:// or https:// prefix.
Tick the option to check http, https, www and non-www versions together.
Each hop shows its status code, destination and time. Problems are highlighted.
Point old URLs straight to the final page, then run the check again.
The status code tells browsers and search engines whether a move is permanent or temporary.
301 Moved permanently (passes ranking signals)
302 Found, temporary
307 Temporary, keeps request method
308 Permanent, keeps request method
200 OK, final page loadedJavaScript redirects that run after the page loads cannot be detected by any server-side checker. Meta refresh tags are flagged where present.
A business moved to HTTPS and later changed its domain.
Most redirect issues come from layered changes made over several years.
| Problem | Why it matters | Fix |
|---|---|---|
| Redirect chain (2+ hops) | Slower loads, diluted signals, crawl waste | Redirect the first URL straight to the final one |
| Redirect loop | Page never loads for users or Google | Find the conflicting rules in server or plugin settings |
| 302 used for a permanent move | Search engines may keep the old URL | Change to 301 or 308 |
| HTTP hop in the chain | Insecure, can trigger browser warnings | Redirect to HTTPS at the first hop |
| Domain variations disagree | Duplicate versions compete in search | Send all four variations to one final URL |
| Redirect to homepage | Treated like a soft 404 | Redirect to the closest matching page |
Clean redirects keep migrations from costing you traffic.
A 301 is permanent and tells search engines to transfer the old URL's signals to the new one. A 302 is temporary, so search engines may keep the original URL indexed.
Aim for one. Two is acceptable. Google follows up to about ten hops, but every hop slows users down and risks losing signals.
A single 301 to a relevant page is fine. Long chains, loops and redirects to unrelated pages cause problems.
When URL A redirects to B and B redirects back to A, so the page never loads. Browsers show a "too many redirects" error.
Each is technically a different URL. If they do not all end up at the same place, search engines may treat them as separate competing pages.
No server-side tool can, because JavaScript runs in the browser after the page loads. Meta refresh redirects are flagged.
We map every redirect, protect your rankings during the move and monitor Search Console afterwards. Explore our technical SEO services.