Redirect Chain Checker
Trace the full HTTP redirect chain for any URL. See every hop, status code, and the final destination.
Understanding HTTP Redirects
HTTP redirects tell browsers and search engines that a URL has moved to a different location. When a server responds with a 3xx status code and a Location header, the client follows the redirect to the new URL. Redirect chains occur when multiple redirects are chained together -- each hop adds latency and can cause issues for SEO and performance.
301 Moved Permanently
A 301 redirect indicates that the resource has permanently moved to a new URL. Search engines transfer link equity (ranking power) to the new URL and update their index. This is the recommended redirect type for permanent URL changes, domain migrations, and enforcing canonical URLs.
Location: https://www.example.com/new-page
302 Found (Temporary)
A 302 redirect signals that the resource is temporarily located at a different URL. Search engines typically keep the original URL in their index. Use 302 for A/B testing, temporary maintenance pages, or geo-based redirects where the original URL should be preserved.
Location: https://www.example.com/temp-page
307 Temporary Redirect
A 307 redirect is the HTTP/1.1 strict equivalent of 302. The key difference: the client must not change the request method. A POST request redirected with 307 will remain a POST. This is important for form submissions and API endpoints.
Location: https://api.example.com/v2/submit
308 Permanent Redirect
A 308 redirect is the strict permanent equivalent of 301. Like 307, it preserves the HTTP method. A POST redirected with 308 stays a POST. Use this when you need a permanent redirect that must preserve the request method.
Location: https://api.example.com/v2/resource
Redirect Chains & SEO
Redirect chains occur when URL A redirects to B, which redirects to C, and so on. Each hop dilutes link equity and adds latency. Google recommends keeping redirect chains to a minimum -- ideally one hop. Long chains (3+) can cause crawl budget waste, slower page loads, and incomplete link equity transfer. Audit your redirects regularly.
Common Redirect Issues
Redirect loops: A redirects to B and B redirects back to A, causing infinite loops. Mixed protocols: HTTP to HTTPS chains with extra hops. Trailing slashes: Redirects between /path and /path/ adding unnecessary hops. WWW/non-WWW: Not canonicalizing creates duplicate content and extra redirects.