About the Redirect Checker
The Redirect Checker follows a URL exactly like a browser does and shows every stop along the way: server-side 301, 302, 303, 307 and 308 redirects, meta refresh tags and JavaScript redirects. Each hop is listed with its status code, response time, HTTPS state and server signature — so you can spot chains, loops and mixed-content downgrades at a glance.
Typical use cases: verifying a domain migration, testing .htaccess rules after deployment (pair it with the .htaccess Generator), auditing affiliate link cloakers, and making sure every legacy URL reaches its new home in a single 301 hop.
A redirect chain is the sequence of URLs a browser passes through before reaching the final page — for example http → https → www → final URL. Every extra hop costs loading time and dilutes link equity, so SEOs aim for at most one redirect.
A 301 is permanent: search engines transfer rankings and link signals to the new URL. A 302 is temporary: the original URL keeps its signals. For permanent moves always use 301 (or 308), otherwise you can lose rankings.
Yes. Besides server-side 3xx redirects it scans the returned HTML for meta refresh tags and common JavaScript patterns like window.location and location.replace(), and follows them just like a browser would.
Google follows up to 10 hops, but best practice is a single redirect. Chains of 3+ hops slow down crawling and page load. Use this checker after every migration or .htaccess change to confirm each old URL reaches its destination in one hop.