What is a redirect?
A redirect sends visitors and search engines from one URL to another. Redirects are normal and useful: when you move to HTTPS, change a page address or merge two pages, a redirect keeps old links and bookmarks working. But redirects set up the wrong way can slow pages down and waste SEO value.
This redirect checker follows a URL step by step, the same way a browser does, and shows:
- every hop in the chain, in order
- the status code of each hop (301, 302, 307, 308 or the final 200)
- the response time of each step
- the final URL and whether HTTP correctly upgrades to HTTPS
How to check redirects
- Paste one or more URLs, one per line. You can check up to 20 at a time.
- Click Check redirects.
- Read each result card. Green notes are good, orange notes are worth fixing.
A quick test many site owners forget: check http://yourdomain.com and http://www.yourdomain.com. Both should end on your one preferred https address in a single hop.
301 vs 302: which should you use?
- 301 Moved Permanently and 308 Permanent Redirect tell search engines the move is permanent. Google transfers ranking signals to the new URL. Use these for changed URLs, HTTPS moves and domain changes.
- 302 Found and 307 Temporary Redirect say the move is temporary. Use them for short-term cases such as a seasonal page or A/B test.
Google's guide to redirects and Google Search explains how each type is treated.
Why redirect chains are a problem
A redirect chain happens when URL A redirects to B, which redirects to C. Each hop adds delay, and long chains may not be followed to the end by crawlers. The fix is simple: point the first URL straight at the final destination, and update internal links to use the final URL directly.
A redirect loop, where pages keep sending visitors back and forth, breaks the page completely. The checker stops after 10 hops and reports it.
Check the headers of the final page with the HTTP Header Checker, confirm your certificate with the SSL Checker and find dead links with the Broken Link Checker.
Every redirect status code explained
| Code | Name | When to use it |
|---|---|---|
| 301 | Moved Permanently | A page has moved for good. Passes ranking signals to the new URL. |
| 302 | Found | A temporary move, for example during maintenance or a short campaign. |
| 303 | See Other | Mostly used after a form submission. Rare in SEO. |
| 307 | Temporary Redirect | Like 302, but the browser must keep the same request method. |
| 308 | Permanent Redirect | Like 301, but keeps the request method. Treated like a 301 by Google. |
For normal page moves, use 301 or 308. Google's documentation on redirects and Google Search confirms that permanent redirects are a strong signal that the target should be shown in search.
Redirects you should check after a migration
Moving a site is when redirect mistakes cause the most damage. After any migration, test these URLs:
http://example.comshould go straight tohttps://example.com(or the www version you chose).http://www.example.comandhttps://www.example.comshould end at the same final URL.- Your top 20 old URLs (from Google Search Console or analytics) should each redirect to the matching new page, not the homepage.
- Old URLs with and without a trailing slash should both end at one version.
Each of these should be one hop. If you see two or three hops, update the rules so the old URL points directly at the final destination.
Redirect loops and how to fix them
A redirect loop happens when URL A sends visitors to B and B sends them back to A. Browsers show an error like "This page isn't working - redirected you too many times". Common causes are:
- A plugin forcing HTTPS while the server forces HTTP.
- Conflicting rules in
.htaccessand in the CMS settings. - A CDN or proxy set to "flexible" SSL while the server redirects to HTTPS.
The checker stops when it detects a loop and shows you every hop, which makes it much easier to find the rule causing it.
Redirects and page speed
Each redirect adds a full round trip before the page can start loading. On a slow mobile connection, that can add several hundred milliseconds. Internal links in your menu and content should point to the final URL, not to an address that redirects. Use the Broken Link Checker to review links on a page and the HTTP Header Checker to see the exact Location header a server sends.
Example: checking a site after moving to HTTPS
You have just installed an SSL certificate and want to confirm everything redirects correctly. Check these four addresses one by one:
http://example.comhttp://www.example.comhttps://example.comhttps://www.example.com
All four should end on the same final URL with status 200, and none should take more than one redirect to get there. If http://www first goes to https://www and then to https://example.com, that is two hops; update your server or CMS settings so it goes straight to the final address. Then check a few inner pages, such as your contact page and a popular blog post, in the same way.
Frequently Asked Questions
Does a 301 redirect lose SEO value?
Google has said that 301 and 308 redirects pass ranking signals. Long chains and slow hops are still worth avoiding.
Can it detect JavaScript or meta refresh redirects?
No. It follows server redirects (HTTP 3xx), which are the type search engines prefer.
How many URLs can I check?
Up to 20 per run.
Is the tool free?
Yes, with no sign-up.
How long should I keep a 301 redirect?
Keep it for at least a year, and ideally permanently. Old links on other websites may keep sending visitors for many years.
Does the order of www and https matter?
Pick one final version, such as https://www.example.com, and make every other version redirect to it in a single step.
Why does my browser still go to the old page?
Browsers cache 301 redirects. Test in a private window, or use this tool, which always makes a fresh request.
Last updated: October 25, 2026