↪️ Redirect Checker
Check where a URL or link redirects: every hop in the redirect chain, with status codes, timing and the final destination
📚 About HTTP Redirects
HTTP redirects are used to send browsers and search engines from one URL to another. Understanding your redirect chain is important for SEO and user experience.
How to Check a URL's Redirects
Enter a URL or a bare domain above. The checker requests it without a browser, follows each Location header in turn, and shows one row per hop:
- Status code: 301, 302, 307 or 308 for a redirect; 200 (or an error code) for the final page
- URL and padlock: the address requested at that hop, and whether it was HTTPS
- Location: where that hop sends you next
- Time: how long that hop took to respond
It flags loops, chains of more than a couple of hops, mixed permanent and temporary redirects, and a final page that isn't HTTPS. It's also a safe way to see where a shortened or unfamiliar link really goes before you open it.
Redirect Test: HTTP→HTTPS and www
Test all four variants of your domain: http://example.com, http://www.example.com, https://example.com and https://www.example.com. Each should reach the same canonical address (for example https://example.com/) in a single 301 or 308 hop, then return 200. Two hops (HTTP→HTTPS, then www→non-www) work, but one is better.
301 vs 302: Which Redirect Should You Use?
| Code | Name | Permanent? | What Google does | Typical use |
|---|---|---|---|---|
| 301 | Moved Permanently | Yes | Indexes the target; a strong canonical signal | Domain moves, HTTP→HTTPS, retired URLs |
| 302 | Found | No | Keeps the original URL indexed at first; a long-lived 302 is eventually treated like a 301 | Short campaigns, A/B tests, geo routing |
| 303 | See Other | No | Same as 302 | After a form POST |
| 307 | Temporary Redirect | No | Same as 302; the HTTP method is preserved | Temporary moves of POST endpoints; browsers also show it for HSTS upgrades |
| 308 | Permanent Redirect | Yes | Same as 301; the HTTP method is preserved | Permanent moves of API and POST endpoints |
All of these pass PageRank. Choose permanent or temporary based on which URL you want in search results. Browsers cache 301 and 308 redirects aggressively, so test a permanent redirect before you ship it.
Redirect Chains and Loops
- Chains: every extra hop adds a round trip for visitors. Point old URLs straight at the final address instead of at another redirect.
- Loops: two rules that send traffic back and forth end in a browser error. The checker stops and flags the loop.
- HTTPS: always redirect HTTP to HTTPS, and pick either www or non-www and redirect the other to it.
Frequently Asked Questions
How do I check where a link redirects?
Paste the link into the checker. It follows each hop without opening the page in your browser and shows the status code, the Location it points to, the response time and the final URL. It's a safe way to see where a shortened or unfamiliar link really goes.
Is a 301 or 302 redirect better for SEO?
Use a 301 (or 308) when the move is permanent, because Google then indexes the new URL. Use a 302 (or 307) when it's temporary and you want the original to stay in search results. Both pass PageRank; the choice is about which URL should rank.
How many redirects is too many?
Aim for one hop. Each extra hop adds a round trip for visitors, and Googlebot follows at most 10 hops. Browsers give up at around 20 with a "too many redirects" error.
What causes ERR_TOO_MANY_REDIRECTS?
Two rules sending traffic back and forth. Classic cases: a CDN connecting to your origin over HTTP while the origin forces HTTPS (Cloudflare's "Flexible" SSL mode), or one rule adding www while another removes it. Run the checker on the URL and look for the repeating hops.
How do I test that HTTP redirects to HTTPS?
Enter http://yourdomain.com. You should see one 301 or 308 to https://yourdomain.com followed by a 200. Check http://www. too, so both variants end at the same canonical host in a single hop. Then confirm the certificate with the SSL Checker.