Redirect Checker

Who this is for

PPC managers tracking campaign UTM parameters through redirects. Migration teams validating 301 chains after site moves. E-commerce operators troubleshooting lost conversion tracking. Anyone who needs to verify that redirects preserve parameters and don't introduce latency that kills conversions.

What problem this solves

Most teams assume "301 = done" — but redirect chains quietly break tracking, add latency, and lose attribution data. UTM parameters get stripped. Campaign tracking disappears. Multiple hops add 200-500ms latency that increases bounce rates. Temporary redirects (302/307) prevent proper crawling and caching.

Standard browser DevTools show you the final destination but hide what happens in between. You need to trace the full chain, measure latency per hop, detect parameter loss, and identify redirect type issues — all of which require CLI tools or advanced crawling infrastructure most teams don't have.

What this checks

• Full redirect chain — every hop from original URL to final destination
• HTTP status codes — detect temporary vs. permanent redirects
• Latency per hop — measure performance impact of each redirect
• Caching headers — identify cacheable vs. non-cacheable hops
• Parameter preservation — verify UTMs and tracking codes survive the chain
• Visual chain map — see the flow and timing in waterfall view

What breaks without this

Lost conversion tracking. Wasted ad spend on campaigns you think work but can't measure. Slow page loads from redirect latency killing mobile conversions. SEO penalties from redirect chains that crawlers can't follow. Revenue attribution that points to "direct" because UTMs got stripped somewhere in the chain.

What it does NOT do

This checks redirects at the HTTP level. It doesn't detect JavaScript redirects, meta refresh redirects, or client-side routing. It's a diagnostic tool for HTTP 3XX redirect chains, not a full-site crawler.