Redirect Chain Checker

Report an Issue

Help us improve by telling us what went wrong.

Embed this Tool

Customize and copy the embed code for your website.

When a URL redirects to another URL, which then redirects to yet another, you have a redirect chain. These chains are more common than most website owners realise, and they create real problems for both search engine optimisation and user experience. The Redirect Chain Checker traces the full path a URL takes from start to finish, showing every hop along the way, so you can identify and fix chains before they hurt your site.

How Redirect Chains Form

Redirect chains rarely happen on purpose. They accumulate over time as websites evolve. A page gets moved from /old-page to /new-page with a 301 redirect. A year later, /new-page gets reorganised to /category/new-page with another 301. Now any link pointing to /old-page passes through two redirects before reaching the final destination. Add a protocol change from HTTP to HTTPS and a www-to-non-www normalisation, and suddenly a single URL might hop through four redirects before resolving.

Each hop in the chain adds latency - typically 50 to 300 milliseconds depending on server response time and geographic distance. A four-hop chain can add over a second to page load time, which directly impacts user experience, bounce rates, and Core Web Vitals scores.

Why Redirect Chains Hurt SEO

Google has stated that PageRank passes through redirects, but there is ongoing debate in the SEO community about whether some link equity is lost at each hop. Even if the equity loss is minimal per hop, chains create other issues:

Crawl budget waste - Googlebot has a finite budget for crawling your site. Every redirect hop consumes part of that budget without discovering new content. Sites with thousands of chained redirects can see significant crawl efficiency problems.

Indexation confusion - When search engines encounter multiple redirects, there is a risk that intermediate URLs get indexed instead of the final destination, especially if some hops use 302 (temporary) redirects rather than 301 (permanent).

Slower page speed - Page load time is a confirmed ranking factor. Redirect chains add unnecessary latency that directly affects your speed metrics.

What This Tool Shows You

Enter a URL and the checker follows every redirect, displaying the complete chain from the initial URL to the final resolved destination. For each hop, you see:

The HTTP status code - 301 (permanent), 302 (temporary/found), 307 (temporary redirect), or 308 (permanent redirect). The distinction matters because search engines treat 301 and 308 as permanent signals to transfer ranking authority, while 302 and 307 are treated as temporary, meaning the original URL may retain its indexation.

The target URL - Where each redirect points. This lets you see exactly where the chain branches and identify which hops are unnecessary.

Response time per hop - How many milliseconds each redirect takes to resolve, helping you quantify the total latency the chain introduces.

Fixing Redirect Chains

The fix is conceptually simple: update the first redirect to point directly to the final destination, bypassing all intermediate hops. In practice, this means editing your server configuration (Apache .htaccess, Nginx config, or your CMS's redirect manager) to replace chained 301s with a single direct redirect.

For large sites with hundreds of chains, prioritise fixing the chains that affect your most-linked and highest-traffic pages first. Those are where the performance and SEO impact is greatest.

When to Run This Check

Use the redirect chain checker after any site migration, URL restructuring, domain change, or protocol switch. These events are the most common triggers for new chain creation. Also run it periodically - quarterly is a reasonable cadence - as part of your technical SEO maintenance routine. Chains have a way of accumulating silently, and catching them early prevents compounding problems down the road.