Redirect Checker
Test redirect chains, detect loops, and validate your mapping before you go live.
Test Live URLs
Make real HTTP requests and see exactly where each URL redirects: every hop, status code, and response time.
Paste up to 100 URLs, one per line. For paths such as /old-page, fill in the site to test below.
Password-protected site (basic auth)
For staging sites behind HTTP Basic authentication. The user name and password are sent only to the scheme, host and port of each URL you enter, never to another site a redirect leads to. They are not stored.
What is a redirect checker?
A redirect checker follows the path a URL takes from the original address to the final destination. When a browser or search engine requests a URL, the server may respond with a redirect, sending the request to a different address. This can happen once or multiple times, forming a redirect chain. This tool traces that entire chain, showing every hop with its HTTP status code and response time. You can run the check with common bot identities (Googlebot, Bingbot) or as a desktop browser, and we also offer our branded RedirectaBot if you want the request to identify itself in the target's server logs.
Why check redirects?
Site migrations
After a domain move, CMS change, or URL restructure, redirect rules need to be verified. Broken redirects lead to 404 errors, lost link equity, and dropped rankings. Bulk checking lets you validate hundreds of URLs at once instead of testing them one by one.
Launch day: check against your redirect map
A redirect that works is not always a redirect that is right. Choose "Against expected destinations", paste or upload your source and destination pairs, and every source is checked live against the URL your map says it should reach. Rows that land elsewhere, do not redirect, go through a chain, use a temporary redirect or end on a page that does not load are flagged, and the results export as CSV. For a staging site behind a password, open the basic auth fields. Building that map from your old and new URL lists is what Redirecta does.
Redirect chains and loops
A redirect chain is when URL A redirects to B, which redirects to C, and so on. Each additional hop adds latency and dilutes link equity. A redirect loop is when two or more URLs redirect to each other, creating an infinite cycle that results in an error. Both are common after migrations and should be resolved.
Mixed HTTP and HTTPS redirects
HTTPS migrations often leave behind redirect rules that send traffic through unnecessary hops, such as http://example.com to http://www.example.com to https://www.example.com. These extra steps slow down page loads and can cause indexing issues.
Common HTTP status codes
The request succeeded. The page loaded normally with no redirect.
The URL has permanently moved to a new address. Search engines transfer link equity to the new URL.
The URL temporarily redirects to another address. Search engines may keep indexing the original URL.
Similar to 302, but guarantees the request method (GET, POST) is not changed during the redirect.
Similar to 301, but guarantees the request method is preserved. Used when method consistency matters.
The page does not exist. A missing redirect after a migration will result in this status.
The page has been permanently removed. Unlike 404, this tells search engines to stop trying to index it.
The server encountered an error. Often caused by misconfigured redirect rules in .htaccess or server config.
The server is temporarily down, usually for maintenance. Search engines will retry later.
View all 62 HTTP status codes in our complete reference guide.
Need to Map Your Redirects?
Checking individual URLs is just the start. Our AI-powered mapping engine matches thousands of source URLs to their best destinations automatically using 6-signal scoring. Upload a CSV and get results in minutes.