Redirect Checker
URL to trace
Every hop is requested in turn, so each status, target and timing is real.
Traced from
-
Redirect Chain
Each hop in order, from the URL you entered to the final response.
Summary
The values pulled out of the chain.
Notes
Anything unusual about this chain.
Nothing traced yet
Enter a domain or URL above to see every redirect it passes through before the final page.
How redirect chains form
A redirect chain appears when one rule sends a request to a second URL that redirects again. A common example is HTTP to HTTPS, then the apex domain to www, then a trailing slash normalisation. Three hops means three round trips before a browser even starts downloading the page.
Every hop costs a request. On a slow mobile connection that can add a second to first paint, and search engines spend crawl budget following them. Collapse the chain so the original URL redirects straight to the final destination in one step.
Which status code to use
| Code | Meaning | Use it when |
|---|---|---|
| 301 | Moved permanently | A URL will never come back. Search engines pass ranking signals. |
| 302 | Found, temporary | Short campaigns or A/B tests. Signals are not consolidated. |
| 307 | Temporary, method preserved | A POST must stay a POST on the new URL. |
| 308 | Permanent, method preserved | A permanent move where the method must not change. |
A 302 left in place for years is a common mistake. It tells search engines the move is temporary, so the old URL keeps its signals and the new one competes with it.
Loops, mixed protocols and other failures
A redirect loop happens when two rules point at each other, often because a canonical redirect and a trailing slash rule disagree. Browsers stop after a limit and show an error, and crawlers abandon the URL entirely.
An HTTPS to HTTP hop is worth flagging on its own. It downgrades the connection mid-flight, so anything sent after that point travels in the clear. If a CDN terminates TLS and forwards to a plain HTTP origin, the browser URL still shows HTTPS while the link between edge and origin does not.
Redirecting to a different hostname is fine when it is intentional, such as consolidating several old domains onto one. It becomes a problem when the destination does not match the certificate, and every hop here is timed so you can see which step is slow.
Frequently asked questions
How many redirects is too many?
More than one for a given URL. A single permanent redirect to the final destination is ideal. Three hops is common and wasteful, and most browsers abandon a chain after twenty.
Why does my redirect loop?
Two rules usually disagree, for example a force-HTTPS rule combined with an HTTP-only canonical rule, or a trailing slash rule that strips and re-adds the slash.
Does a 302 lose ranking?
It does not damage the target, but it tells search engines the move is temporary, so the original URL keeps its signals. Make it a 301 once the move is settled.
What is the difference between 301 and 308?
A 301 may change a POST into a GET. A 308 guarantees the method and body are replayed unchanged. Use 308 for API endpoints and form submissions.
Should www and non-www both resolve?
Both may resolve, but one should redirect to the other with a 301 so search engines see a single canonical host.