Skip to main content
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:
DetailDescription
URLThe URL at this hop
Status codeHTTP status code (301, 302, 307, 308, etc.)
Redirect typePermanent (301/308) or temporary (302/307)
Final URLWhere the chain ultimately resolves

Redirect types

CodeTypeSEO impact
301Permanent redirectPasses link equity to the destination
302Temporary redirectMay not pass full link equity
307Temporary (HTTP/1.1)Preserves request method, similar to 302
308Permanent (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.

Next steps