Follow the full redirect chain of any URL. See every hop, HTTP status code, and the final destination.
OneStepToRank members get continuous redirect chain monitoring, broken redirect alerts, and link equity tracking across their entire site -- all automated.
Unlock Redirect Intelligence →Track redirect chains, detect broken redirects, and protect your link equity across your entire website. Get alerts before problems happen.
Get StartedRedirects are an essential part of website management, but when they chain together they can silently damage your search rankings. Every hop in a redirect chain adds latency, typically 50 to 300 milliseconds per redirect, which compounds into a noticeable slowdown for users and crawlers alike. More critically, each hop dilutes the link equity (PageRank) flowing through the chain, meaning the final destination page receives less ranking power than it would from a direct link.
Google's John Mueller has confirmed that while Googlebot will follow redirect chains, there is a practical limit. After approximately 10 hops, the crawler will stop following and the destination page may not receive the full benefit of links pointing to the original URL. For most websites, keeping redirect chains to a single hop is the gold standard.
Common scenarios that create redirect chains include HTTP-to-HTTPS migration (http://example.com redirecting to https://example.com), www-to-non-www canonicalization, trailing slash normalization, URL restructuring during site redesigns, and domain migrations. Each of these individually is fine, but when they stack on top of each other -- HTTP to HTTPS, then www to non-www, then old path to new path -- you end up with a three-hop chain that should be a single redirect.
The fix is straightforward: update the original redirect to point directly to the final destination. If URL A redirects to B, which redirects to C, update A's redirect to go straight to C. This eliminates the intermediate hop, speeds up page load, and preserves maximum link equity. Use this tool to identify chains across your site, then update your .htaccess file, nginx configuration, or CMS redirect settings to consolidate each chain into a single hop.
Pay special attention to redirect loops, where URL A redirects to B and B redirects back to A. These create an infinite cycle that results in an ERR_TOO_MANY_REDIRECTS error for visitors and complete crawl failure for search engines. Our tool detects these loops automatically so you can fix them before they impact your users.
A redirect chain occurs when a URL redirects to another URL, which then redirects again, creating multiple hops before reaching the final destination. Each hop dilutes link equity and adds load time. Google recommends keeping redirect chains to a single hop to preserve ranking power and ensure fast page loads.
A 301 redirect is permanent, telling search engines the page has moved forever and to transfer link equity to the new URL. A 302 redirect is temporary, meaning the original URL will return. Using a 302 when you intend a permanent move can prevent link equity from transferring, hurting your rankings at the new URL.
Ideally zero or one. Google will follow up to 10 hops, but best practice is a single redirect from origin to destination. Each additional hop adds 50-300ms of latency and dilutes PageRank. If you find chains with 3 or more hops, consolidate them into a single redirect to the final URL.
A redirect loop is when URL A redirects to URL B, which redirects back to URL A, creating an infinite cycle. This causes ERR_TOO_MANY_REDIRECTS errors. Common causes include conflicting .htaccess rules, HTTPS settings, or CDN configurations. Review your redirect rules in order and eliminate circular references to fix the loop.