Detect redirect chains and loops. Get optimized direct rules for Netlify, Cloudflare, Apache, and Nginx.
One rule per line: /from /to [status]
Enter redirect mappings on the left to detect chains, loops, and optimization opportunities.
💡 Chains add latency and dilute PageRank — collapse to direct redirects.
💡 Loops cause browser ERR_TOO_MANY_REDIRECTS.
A redirect chain occurs when URL A redirects to B, which redirects to C. Each extra hop adds ~100–300ms latency and slowly bleeds PageRank. This tool analyzes your entire redirect map, identifies chains and circular loops, and generates optimized direct redirect rules for Netlify, Cloudflare, Apache, and Nginx.
Each hop passes slightly less link equity. A 3-hop chain may deliver only ~97% of the original PageRank. More impactfully, chains slow page loads — a Core Web Vitals factor.
Loops (A→B→C→A) are usually caused by conflicting rules in different config files. Browsers show an "ERR_TOO_MANY_REDIRECTS" error and users can't reach the page at all.
Google recommends under 3 hops. Browsers typically stop following chains after 20 hops. Any chain of 5+ hops is a strong sign your redirect infrastructure needs auditing.
For highly-linked pages, yes. The bigger win is page speed and crawl efficiency — Googlebot won't waste crawl budget following long chains across thousands of URLs on large sites.