Analyze HTTP redirects, visualize chains and detect issues
Get notified when new tools launch.
Every redirect costs time. While Googlebot tolerates up to 5 hops, AI crawlers from ChatGPT or Perplexity often have shorter timeouts — long redirect chains can prevent your page from being crawled at all and therefore not cited in AI answers.
The most common problem: redirect chains through HTTP → HTTPS → www → non-www. Instead of 3 hops, one direct redirect to the canonical URL is enough.
A redirect chain occurs when a URL is redirected multiple times before the final content is delivered. Each redirect costs time and can be handled differently by search engines and AI crawlers.
Ideally 0-1 redirects. Google recommends a maximum of 3-5 hops. AI crawlers often have shorter timeouts and abort chains earlier. A clean chain with direct HTTPS access is optimal.
301 Moved Permanently passes the full link value (PageRank) and is permanently cached by search engines. 302 Found is temporary and passes less value. Always use 301 for permanent redirects.
A redirect loop occurs when URL A points to URL B and URL B points back to URL A. Browsers and crawlers abort on a loop. The checker detects loops when more than 10 hops follow each other.
HTTP URLs should always redirect to HTTPS to ensure security. Google prefers HTTPS pages in rankings. The redirect should happen directly (one hop) and not through intermediate steps.