Status codes
See 301, 302, 303, 307, 308, 404, and 500-level responses in order so you can spot temporary redirects and broken destinations.
A redirect checker follows a URL through each HTTP redirect and shows the status codes, final destination, hop count, and SEO issues that can slow down crawlers or send visitors to the wrong page.
See 301, 302, 303, 307, 308, 404, and 500-level responses in order so you can spot temporary redirects and broken destinations.
Confirm that every old URL lands on the canonical HTTPS page you expect, with no extra campaign parameters or stale paths.
Flag loops, too many hops, temporary redirects in permanent migrations, HTTP destinations, and unhealthy final responses.
A redirect checker follows a URL from the starting address to the final destination and reports each HTTP status code, location header, hop count, and redirect issue it finds.
Long redirect chains slow down users, waste crawl budget, and make migrations harder to audit. Search engines can follow redirects, but shorter permanent chains are easier to crawl and maintain.
Use a 301 redirect when a page has permanently moved and you want browsers and search engines to treat the new URL as the canonical destination.
A 302 redirect is not bad when the move is temporary. For permanent URL changes, use 301 or 308 so the signal is clearer to crawlers and analytics tools.
No. The checker only inspects public http and https URLs. It blocks local and private network addresses for safety.