Redirect Chain Checker
Trace every HTTP hop from your URL to its final destination. Detect redirect loops, flag SEO-damaging 302s, and measure per-hop latency — free and instant.
Why Redirect Chains Matter for SEO & Performance
Every redirect in a chain adds a full network round trip — DNS lookup, TCP handshake, server response — before the browser can even begin loading the final page. For SEO, each unnecessary hop dilutes link equity and reduces Googlebot's crawl efficiency.
Common redirect issues we detect:
- 302 instead of 301: Temporary redirects don't pass PageRank. Every 302 on a permanent move is leaking link equity.
- HTTP → HTTPS → WWW chains: Three hops where one should suffice. Configure your server to redirect directly to the canonical HTTPS+WWW (or non-WWW) URL.
- Redirect loops: Cause browser errors and prevent any page in the loop from being indexed or loaded.
- Chains longer than 3 hops: Each additional hop adds latency and risks Googlebot abandoning the crawl.
Reading the hop chain
The tool shows every hop from start URL to final destination, with the status code per hop, the Location header, and cumulative latency. For example, a status 301 with a Location pointing to the HTTPS version is the standard HTTP-to-HTTPS redirect and should resolve in a single hop.
- One hop, 301 to HTTPS: ideal.
- Two hops HTTP → HTTPS → WWW: consolidate at the edge so clients land on the canonical URL in a single 301.
- Final URL differs from canonical tag: indexing confusion; align canonical with the final destination.
Common issues and fixes
- Redirect loop detected: usually a reverse proxy and application both trying to enforce HTTPS — pick one authoritative layer.
- Mixed 301/302 in the same chain: standardize on 301 for permanent moves; 302 loses link equity for SEO.
- POST turned into GET: 302/303 drop the body — use 307 or 308 to preserve method and payload.
- www and apex redirect to each other: classic infinite loop — configure one as canonical and the other as a one-way 301.
- Trailing-slash double redirect:
/page→/page/→ final; rewrite at the edge to collapse into one hop.
What to do next
Aim for a single 301 between entry URL and destination. After fixing, add HSTS with preload so browsers skip the HTTP hop entirely on return visits.
For continuous monitoring, FlashMon.app tracks changes automatically and alerts you the moment something breaks.
Monitor redirects continuously
Get alerted the moment a redirect chain changes, breaks, or a loop appears on your site.
Frequently Asked Questions
A redirect chain occurs when a URL redirects to another URL, which then redirects again, creating a sequence of hops before reaching the final destination. For example: http://example.com → https://example.com → https://www.example.com → final page. Each hop adds latency and forces browsers and search engine crawlers to follow the entire chain. Short chains (1–2 hops) are normal, but longer chains harm both page load time and SEO crawl efficiency.
A 301 (Moved Permanently) redirect tells search engines that the resource has permanently moved to the new URL. The search engine transfers the original page's ranking signals (PageRank, backlinks) to the destination. A 302 (Found/Temporary) redirect tells search engines the move is temporary, so they keep indexing the original URL and do not transfer ranking signals. Using 302s when you mean 301 is a common SEO mistake that causes link equity to be lost.
A redirect loop occurs when URL A redirects to URL B, which redirects back to URL A (or through a longer chain that eventually returns to a previously visited URL). Browsers detect loops after a few hops and display an error like "Too many redirects." Search engine crawlers give up and fail to index any of the pages. Loops are typically caused by misconfigured web server rules, conflicting CDN settings, or CMS permalink mismatches after a migration.
Google recommends keeping redirect chains to a maximum of 3–5 hops. Each hop adds 50–200ms of latency (a DNS lookup, TCP connection, and server round trip). For mobile users on slower networks, a 4-hop chain can add 400–800ms to the first byte time before the page even starts loading. More importantly, Googlebot limits the number of redirects it follows per crawl, so deep chains can prevent pages from being indexed. The ideal is zero unnecessary redirects — go directly from the canonical entry point to the final URL.
Update the source link or DNS entry to point directly to the final destination URL. For example, if you have A → B → C, configure A to redirect directly to C and remove the A → B hop entirely. In practice: update .htaccess rules or nginx server blocks, reconfigure CDN redirect rules, and update any hardcoded links in your CMS or ad campaigns. After fixing, verify with this tool that the chain resolves in a single hop. Also update your sitemap and canonical tags to reference the final URL directly.
Redirect configurations change during deployments, CDN updates, and CMS migrations — and a misconfiguration that introduces a loop or breaks a redirect can cause instant ranking drops or user-facing errors. FlashMon continuously monitors your key URLs and alerts you the moment a redirect chain changes, a loop appears, or a previously working redirect starts returning an error. Catching a broken redirect within minutes instead of days prevents SEO damage and user experience degradation.