Redirect Checker

What Is a Redirect Chain?

A redirect chain is a sequence of HTTP redirects between an original URL and its final destination. Instead of URL A pointing directly to URL C, it goes A to B to C, with each step adding a separate HTTP request. Each hop costs time and, depending on the redirect type, can erode the SEO value passing from the source to the destination.

Redirect chains most commonly appear after domain migrations where old redirects are not cleaned up, after switching from HTTP to HTTPS through an intermediary URL, and when marketing landing pages or shortened URLs point to other short URLs before reaching the real page. The longer the chain, the worse the impact on both crawlers and real users.

How Redirects Affect SEO and PageRank

Since Google's Penguin 4.0 update in 2016, a single 301 (permanent) redirect passes close to 100% of PageRank to the destination. This corrected the older behavior where each hop caused a measurable loss of link equity. However, chained redirects still cause cumulative dilution at each step. A chain of three hops through 301s loses a meaningful percentage of the original link equity, so any backlinks pointing to the start of the chain pass less value to your actual page.

Google also enforces a hard limit of 10 redirect hops before abandoning the crawl. If your URL chain exceeds this, the final page will not be indexed at all. Most real-world chains stay under 10, but they do consume crawl budget: every hop is a separate Googlebot request against your server. For large sites with thousands of redirected URLs, this can meaningfully reduce how many pages Google crawls each day.

301 vs 302 vs 307 vs 308

Common Redirect Problems for Indie Makers

• www to non-www (or reverse)If your domain redirects www to non-www but your CDN also redirects at the origin, you get two hops. Consolidate at the DNS level or in your hosting config.
• HTTP to HTTPS via an intermediateSome setups redirect HTTP to a http://www. URL first, then to https://. This creates a chain. Your HTTP URL should redirect directly to your final HTTPS URL in a single hop.
• Old redirects stacking after migrationsWhen you migrate a domain, you create a new set of redirects. If the old domain already had redirects, they chain with the new ones. Audit all redirects after any migration and update old ones to point directly to the final URL.
• Redirect loopsURL A redirects to URL B and URL B redirects back to URL A. Browsers and crawlers detect this and return a 'too many redirects' error. The page becomes completely inaccessible.
• 302 used where 301 was intendedUsing a temporary redirect for a permanent move prevents Google from transferring PageRank and may cause the original URL to stay indexed indefinitely while the destination ranks for nothing.

How to Fix Redirect Chains in Next.js and Vercel

In Next.js, define all redirects in next.config.js. Each entry maps a source pattern directly to its final destination. To eliminate a chain, make sure no source URL points to another URL that also has a redirect entry:

// next.config.js
module.exports = {
  async redirects() {
    return [
      // Good: single hop, permanent
      {
        source: '/old-page',
        destination: '/new-page',
        permanent: true, // generates 301
      },
      // Avoid: chaining — /very-old -> /old-page -> /new-page
      // Instead, point very-old directly to new-page
      {
        source: '/very-old-page',
        destination: '/new-page',
        permanent: true,
      },
    ]
  },
}

On Vercel, you can also configure redirects in vercel.json. The same rule applies: always point directly to the final destination, never through an intermediate URL that itself redirects.

Redirects and AI Crawler Indexing

AI crawlers like GPTBot (OpenAI), ClaudeBot (Anthropic), and PerplexityBot follow redirects the same way Googlebot does. A page buried behind a long redirect chain may not get crawled at all if the chain causes a timeout or exceeds the crawler's hop limit. For AI citation purposes, the canonical URL that gets attributed in answers is the final destination — so if your most important content pages are behind chains, they are less likely to be discovered, indexed, and cited in AI-generated responses. Clean, direct URLs with no redirects are the safest baseline for both search and AI visibility.

Frequently Asked Questions