Redirect tracing
Trace the full HTTP redirect chain for any URL. Detect 301s, 302s, redirect loops, and final destination URLs.
The redirect tracing tool follows every redirect hop from the initial URL to the final destination. Use it to audit redirect chains, find unnecessary hops, detect redirect loops, and verify that old URLs land where they should.
What it shows
For each hop in the redirect chain:
| Detail | Description |
|---|---|
| URL | The URL at this hop |
| Status code | HTTP status code (301, 302, 307, 308, etc.) |
| Redirect type | Permanent (301/308) or temporary (302/307) |
| Final URL | Where the chain ultimately resolves |
Redirect types
| Code | Type | SEO impact |
|---|---|---|
| 301 | Permanent redirect | Passes link equity to the destination |
| 302 | Temporary redirect | May not pass full link equity |
| 307 | Temporary (HTTP/1.1) | Preserves request method, similar to 302 |
| 308 | Permanent (HTTP/1.1) | Preserves request method, similar to 301 |
Common issues to look for
- Long redirect chains — each hop adds latency. Chains longer than 2–3 hops should be shortened.
- Redirect loops — URL A redirects to B, which redirects back to A. SERP Lens detects and flags these.
- 302s used as permanent redirects — if the move is permanent, use 301 to ensure link equity transfers.
- HTTPS redirect missing — HTTP should redirect to HTTPS. If it doesn't, search engines may index the HTTP version.
- www/non-www inconsistency — pick one canonical version and redirect the other.