Loading…
Enter any URL and instantly trace the full redirect chain — every 301, 302, 307, and 308 — with status codes, response times, and final destination. Catch redirect loops and PageRank-diluting chains before they hurt your rankings.
🔗 Try the free Redirect Chain Checker →A redirect chain checker traces the full HTTP redirect path from a source URL to its final destination, recording every intermediate URL, status code, and response time along the way. Redirect chains occur when a URL redirects to another URL that itself redirects — creating a chain of two or more hops before reaching the final page.
For example, old-site.com → http://new-site.com → https://new-site.com → https://www.new-site.com is a three-hop chain. While the end result for users is the same, each additional redirect hop adds latency, reduces the PageRank (link equity) passed through the chain, and increases crawl budget consumption for bots. Google recommends keeping redirect chains to a single hop wherever possible.
Try the free Redirect Chain Checker
No login required. Results in seconds.
Google's PageRank flows through 301 redirects, but some equity is lost at each hop. A single clean 301 passes roughly 99%+ of link equity. A three-hop chain compounds the loss at each step, meaning inbound links pointing to your old URL pass progressively less authority to your canonical page.
Every redirect is an additional HTTP round-trip — typically 50–200ms each. A three-hop chain adds up to 600ms of avoidable latency before the browser receives a single byte of page content. This directly impacts Core Web Vitals, specifically TTFB and LCP.
Googlebot follows redirect chains but uses crawl budget on each hop. For large sites where crawl budget is a constraint, redirect chains mean fewer unique pages get crawled per crawl session. Shortening chains frees up budget for content pages.
A URL that redirects from HTTP → HTTPS as one of its hops (rather than going straight to HTTPS) sends users and crawlers through an unencrypted connection, even briefly. This HTTP leak can affect site trust signals and create mixed-content warnings.
Paste the URL you want to check — typically an old page URL, an internal link, or a URL from your backlink profile that you suspect has a long redirect chain.
The tool follows every redirect (up to 10 hops) and displays each step: the URL at that hop, its status code (301, 302, 307, etc.), the target URL it redirects to, and the response time for that hop.
The checker automatically flags redirect loops (where a URL eventually redirects back to itself), HTTP-to-HTTPS transitions mid-chain, and chains with 3+ hops.
Update your server config, .htaccess, or redirect rules to point the original URL directly to the final destination, eliminating all intermediate hops. Update any backlinks or internal links pointing to old intermediate URLs.
No account needed · Instant results
A 301 (Moved Permanently) redirect tells browsers and search engines that the page has permanently moved. Google transfers most of the original page's link equity to the new URL. A 302 (Found / Moved Temporarily) signals a temporary move — Google may choose to keep indexing the original URL. Use 301 for permanent URL changes; use 302 for temporary redirects like maintenance pages or A/B test variants.
Google recommends keeping redirect chains to a maximum of 5 hops, but ideally just 1. Beyond 5 hops, Googlebot may stop following the chain and fail to index the final destination. For performance, even 2 hops is worth fixing — the most common pattern is updating the redirect so the original URL points directly to the final page.
Yes. If the chain contains a 302 (temporary) redirect before the final 301 (permanent), Google may treat the entire chain as temporary and continue indexing the original URL rather than the final destination. Replace any temporary 302s in a permanent redirect chain with 301s.
Yes. When Google follows a redirect chain, it canonicalizes to the final destination URL — not the source. However, the source URL may also be stored as a known alternate. To make the final destination URL the clear canonical, also ensure it has a self-referencing canonical tag and is included in your sitemap.
No account required. Works on any public URL. Results in seconds.
Open free Redirect Chain Checker →