About Redirect Checker
A redirect checker earns its keep after a move to HTTPS, a domain change or a new URL structure. Enter an address and we follow each redirect by hand, up to 15 hops, listing the URL, status code, time, Location target and Server header of every step. You see whether the chain ends on a page that answers 200, loops back on itself or takes too many hops. Type a bare domain like example.com and the check starts from http://, the way a visitor typing it would. For a whole list of old URLs, the HTTP Status Code Checker tests them in one go.
Temporary 302, 303 and 307 redirects are flagged where a permanent 301 or 308 belongs, so search engines pass the ranking to the new address. The final page is also read for meta refresh and JavaScript redirects. With Also test http/https and www versions ticked, the four versions of the home address are opened too, and you learn whether they all end on the same page. Pick a user agent to see what Googlebot or Baiduspider gets, and write the fix with the 301 Redirect Generator.
How to use Redirect Checker
- 1Enter a URL or domain
Type a full address, or just example.com to start from http:// like a visitor would.
- 2Set the options
Pick who visits under Visit as, and keep the http/https and www versions test ticked.
- 3Click Check
Our server follows every hop by hand, up to 15.
- 4Fix what's flagged
Read the checks for loops, temporary redirects or a bad final status, then the Redirect chain table for details.
Why use Cubfile for this
- Every hop listed
URL, status code, time, Location and Server header for each step, up to 15 hops.
- Loops and long chains
Redirect loops, chains of three or more hops and chains that end in an error are flagged.
- 301 or 302
Temporary redirects are called out where a permanent move belongs.
- Four versions compared
http, https, www and non-www are checked to confirm they end on one address.