Trace every hop in a URL redirect chain. See HTTP status codes, per-hop timing, and compare how desktop and mobile browsers are routed — all in one analysis.
A redirect chain is a sequence of HTTP redirects that occur before the browser reaches the final destination page. For example, a short link might redirect through a tracking server, then to a landing page — that's a two-hop chain.
Every redirect adds latency and is an opportunity for tracking parameters (UTMs, click IDs) to be stripped. Long chains hurt page load speed and can cause mobile/desktop routing discrepancies that lose attribution data.
A 301 is a permanent redirect — browsers and search engines cache it. A 302 is temporary — it should not be cached. For ad tracking, using 302s is often preferred so destination URLs can be updated without browser cache issues.
Best practice is 0–2 redirects. Three or more redirects measurably slow page load and risk dropping mobile visitors before conversion. LinkDecoder's health score penalizes chains with 5+ hops.
Ready to trace your links?
Open LinkDecoder