Redirect Checker
Follow redirect chains for any URL. See every hop, status code, and the final destination. Identify redirect chains that hurt your SEO.
This tool checks one URL at a time. Rate limited to 10 requests per minute.
Frequently Asked Questions
Why do redirect chains matter for SEO?+
Each redirect in a chain adds latency, wastes crawl budget, and can dilute link equity (PageRank). Google recommends keeping redirect chains as short as possible — ideally a single redirect from the old URL to the final destination.
What's the difference between 301 and 302 redirects?+
A 301 is a permanent redirect — it tells search engines the page has moved permanently and to transfer link equity to the new URL. A 302 is temporary — search engines keep the old URL indexed. Use 301 for permanent moves and 302 only for genuinely temporary situations.
How many redirects are too many?+
Google will follow up to 10 redirect hops, but best practice is to have at most one redirect between the original and final URL. More than 2 hops is considered a chain that should be cleaned up.
What are 307 and 308 redirects?+
307 is the HTTP/1.1 version of 302 (temporary redirect) and 308 is the HTTP/1.1 version of 301 (permanent redirect). The key difference is that 307/308 preserve the request method (POST stays POST), while 301/302 may change POST to GET.
How do redirect chains affect page speed?+
Each redirect requires an additional HTTP round-trip (DNS lookup + connection + response). A chain of 3 redirects can add 300-1000ms to page load time depending on server locations. This directly impacts Core Web Vitals and user experience.