Trace HTTP redirect chains, inspect each hop's status code and headers, and verify your redirects work correctly
Redirect Status Codes and Their SEO Impact
What each 3xx means (RFC 9110)
301 (permanent): search engines transfer ranking signals to the new URL. Use for domain moves and URL restructures.
302/307 (temporary): the original URL stays indexed. Use only for genuinely temporary moves or A/B tests β a 302 on a permanent move delays signal transfer.
308: like 301 but preserves the HTTP method (POST stays POST).
Problems worth checking
Chains: AβBβC slows pages and dilutes signals. Point A directly to C.
Loops: AβBβA produces ERR_TOO_MANY_REDIRECTS.
Protocol/host variants: verify all four combinations (http/https Γ www/non-www) 301 to a single canonical destination β the most common baseline audit.
Frequently Asked Questions
A redirect checker is a tool that follows the entire HTTP redirect chain for a URL. It shows you each hop (301, 302, 307, 308), the destination URL, response headers, and timing β helping you verify that your redirects are set up correctly.
A 301 redirect is permanent β it tells search engines that the page has moved permanently and to transfer SEO value. A 302 redirect is temporary β it indicates the move is temporary and search engines should keep the original URL indexed.
307 (Temporary Redirect) and 308 (Permanent Redirect) are modern HTTP redirect codes that preserve the original request method. Unlike 301/302 which may change POST to GET, 307/308 guarantee the method stays the same.
Google recommends keeping redirect chains to 3 hops or fewer. More than 5 redirects can slow page loading, hurt SEO, and some browsers may stop following after a certain number. This tool supports tracing up to 10 hops.
Yes. 301 redirects pass most SEO value (link equity) to the destination URL. Redirect chains reduce the amount of equity passed. Redirect loops and excessive chains can prevent search engines from crawling your pages effectively.
A redirect loop occurs when URL A redirects to URL B, which redirects back to URL A (or through a longer chain back to the start). This creates an infinite loop that browsers and crawlers cannot resolve. Our tool detects loops by limiting chain length to 10 hops.
Yes! Switch to Bulk Check mode to enter up to 20 URLs at once. The tool will trace the redirect chain for each URL and show a summary with the final destination and number of hops.
Response headers reveal important details like cache-control settings, server type, security headers (HSTS, CSP), and cookies set during redirects. Click 'Headers' on any hop to inspect the full response headers.
No, this tool follows server-side HTTP redirects only (301, 302, 303, 307, 308). JavaScript-based redirects (meta refresh, window.location) require a full browser environment and are not detected by this tool.
Yes, to ensure fair usage, the tool allows up to 10 requests per minute per user. For bulk checks, each URL in the batch counts as a separate request.