How to use
- Enter the address to check. To see whether it upgrades to https, start with http, such as
http://example.com. The Switch to http:// and Add / remove www buttons rewrite the input quickly. - Press Check redirects. A server starts at the address, follows each redirect and records the response of every step.
- The summary shows the number of redirects, the final URL, the final status code and the total time.
- The step table shows each step’s status code (permanent or temporary), what changed (https upgrade, www, trailing slash…) and how long it took.
- Read the findings below. Green is fine, blue is a note, yellow is a warning and red is a problem to fix.
301, 302, 307 and 308
| Code | Type | Request method | Typical use |
|---|---|---|---|
| 301 | Permanent | May change to GET | Moved addresses, http to https, www consolidation |
| 302 | Temporary | May change to GET | Sending visitors elsewhere for a while |
| 307 | Temporary | Preserved | Temporary move where POST must stay POST |
| 308 | Permanent | Preserved | Permanent move where POST must stay POST |
“Preserved” means a request that arrived as POST, such as a form submission, is sent to the new address as POST too. 301 and 302 may turn into GET for compatibility with old browser behavior. For ordinary page address cleanup 301 is enough; where the method matters, such as an API, 308 or 307 is safer. 303 means “fetch the result with GET at another address”, usually after a form submit, and this tool counts it as temporary.
The SEO view behind the findings
- Permanent moves should be 301 or 308. For a permanent move search engines treat the new address as canonical and transfer indexing; for a temporary one they may keep the original. A 302 or 307 used for https, www or trailing-slash cleanup is flagged as a warning.
- Do cleanup in one hop. Sending http to https and then to www takes two trips; going straight to the final address is faster. Two or more cleanup hops trigger a suggestion to merge them.
- Long chains cost you. Three hops or more is a warning and five or more is an error. Each hop adds a round trip, and crawlers may stop following before the end.
- Fix loops at once. Meeting the same address again is a loop, which browsers report as “too many redirects”.
- A redirect from https down to http is an error, because the secure connection is dropped.
- Ending in a 4xx or 5xx means the destination is gone, which is shown as an error.
Examples of the findings this tool produces:
| Path | Finding |
|---|---|
| http to https with one 301 | https upgrade OK, final 200 OK |
| http to https www with a 302 | https upgrade, www added, warning that a temporary redirect is used for cleanup |
| http to https with 301, then https to https www with 301 | www added, warning to merge the cleanup hops |
| Five 301 hops in a row on one domain | Error: too many redirects |
What is sent to the server and the limits
- Only the address you type is sent to the server for the lookup, and neither the address nor the result is stored.
- The server follows at most 5 redirects. Visiting the same host 3 times is treated as a loop and stops the lookup, and the path so far is shown. Each request must answer within 8 seconds.
- Private addresses, internal networks and bare IP addresses are not checked, and only default ports (80, 443) are allowed. If a redirect leads to an address that cannot be checked, the trace stops there.
- Rate limits apply: 6 requests per minute per IP and 30 per minute per target host.
- This is not a port scanner or a way to load someone else’s site. It follows a single address with a few requests.
- Redirects done with JavaScript or meta refresh are not detected, and since the requests come from a server, redirects that depend on region, device or cookies may look different.
FAQ
Should I use 301 or 302?
If the address changed for good, use 301 (or 308). If you send people to an event page for a while and will switch back, 302 (or 307) is right. This tool warns when a temporary redirect is used for https or www cleanup.
Should I use the www or the bare domain?
Either works. Pick one and 301 the other to it. This tool checks one address at a time, so enter both example.com and www.example.com and confirm the two paths end at the same final address.
It answers 200 with no redirect. Is that fine?
If that address is your canonical one, yes. But if you entered an http address and it answers over http without moving, the https redirect is missing and the tool warns about it.
It works in my browser but the tool reports a loop.
Sites that redirect based on cookies, login state or language can bounce in a loop for a request without cookies. Your browser has cookies and may look fine, so check the server configuration too.
How many hops are acceptable?
One is best and two is common. Google follows several hops, but longer chains are wasteful, so reducing anything from three up is recommended. To see response headers at every step use the HTTP header viewer. For the meaning of codes see HTTP status codes, and for a page’s meta tags use the meta tag checker.
The address you type is sent to a server for the lookup and is never stored.