Redirect Chain Checker

What Is a Redirect Chain?

When a browser or crawler requests a URL, the server can respond with a "redirect" status code (301, 302, 307, or 308) and a Location header pointing to a different URL. The browser then requests that new URL. If the new URL also redirects, you've got a chain.

Redirect chains happen naturally when you move pages, change domains, migrate from HTTP to HTTPS, or reorganize site structure. A single redirect (HTTP → HTTPS, or old URL → new URL) is normal and healthy. But chains accumulate over time — every migration adds hops to old URLs, and some sites end up with 5+ hops between an old link and its final destination.

Each hop costs a full round-trip. On a slow connection, 5 hops can add 2–3 seconds to page load time. Google has publicly stated that chains beyond 1–2 hops are treated as a crawling inefficiency and can impact rankings.

Redirect Status Codes Explained

301 Moved Permanently

The gold standard for permanent moves. Search engines transfer nearly 100% of the page's ranking signals to the destination. Use this when a URL has changed permanently (domain migration, page rename, HTTP → HTTPS).

302 Found (Temporary)

Temporary redirect. Search engines keep the original URL indexed and don't transfer ranking signals. Use this for A/B tests, temporary maintenance, or geo-based redirects. Do not use 302 for permanent moves — it's the most common SEO mistake with redirects.

303 See Other

Forces a GET request after a POST. Rarely used for public-facing pages. Common in form submission flows.

307 Temporary Redirect

Like 302 but preserves the original HTTP method (POST stays POST). Used for API redirects.

308 Permanent Redirect

Like 301 but preserves the HTTP method. The modern equivalent of 301 for POST-heavy flows.

Common Redirect Problems

Redirect Loops

A chain that eventually returns to a URL it already visited creates an infinite loop. Browsers detect this after a few hops and show "This page isn't redirecting properly." Crawlers give up entirely. This is critical — the URL is effectively broken for both users and search engines.

HTTPS → HTTP Downgrades

If a chain moves from https:// to http://, all subsequent traffic is unencrypted. This is a security regression and browsers will show a "Not Secure" warning. Never do this.

www → non-www → www Round Trips

A chain like www.example.com → example.com → www.example.com wastes hops and indicates a canonical inconsistency. Pick one form and redirect all variations to it directly.

Excessive Chain Length

More than 2 hops is inefficient. More than 5 hops is a serious problem. Google reduces crawl budget on long chains, and users on slow connections see noticeable delays.

Cross-Domain Redirects

Redirecting to a different domain is sometimes necessary (company rebrand) but always loses some ranking signal. Make sure it's intentional and use 301 (permanent), not 302.

Redirecting to Non-200 Destinations

A chain that ends at a 404 or 500 is worse than no redirect at all — the visitor and the crawler both end up at a broken page. Always verify the final destination returns 200.

Meta Refresh and JavaScript Redirects

These are client-side redirects implemented in HTML or JS. They work for users but are treated poorly by search engines — Google prefers server-side 301s. If you find these on your final destination page, migrate them to proper HTTP redirects.

How to Fix Redirect Chains

1. Audit your redirects. Run this tool on your most important old URLs to see the actual chain.
2. Consolidate. Change each redirect rule to point directly to the final destination, skipping intermediate hops.
3. Use 301 for permanent moves. If any redirects are 302s but should be permanent, change them.
4. Update internal links. Link directly to the canonical (final) URL everywhere, avoiding redirects entirely for internal navigation.
5. Update your sitemap. Make sure the sitemap contains only final destination URLs, not redirected ones.
6. Monitor. Set up alerts or re-check periodically. New chains accumulate as you add features, change platforms, or move infrastructure.

Why This Matters for SEO

Redirect chains don't cause penalties, but they do cost you:

• Crawl budget. Google crawls each hop separately, wasting resources on obsolete URLs.
• Page load time. Each hop is a full network round-trip — 200–500ms typically.
• Signal dilution. Some PageRank is lost through each hop, especially with 302s.
• User experience. Slow redirect chains feel sluggish and can lose impatient visitors.

For high-traffic pages, cleaning up redirect chains is a straightforward SEO win. Even a small ranking improvement on a page with existing traffic translates to meaningful revenue.