Redirect Chain

A sequence of multiple redirects between the initial URL and the final destination, where each redirect points to another redirect.

Sep 6, 2026 / About 1 min read

Redirect

A redirect chain occurs when a URL redirects to another URL, which in turn redirects to yet another URL, creating a sequence of multiple hops before reaching the final destination. For example, URL A redirects to URL B, which redirects to URL C, which finally serves the content. Each additional hop means one more network round trip, and one more hop the crawler has to follow before it reaches the final page.

Redirect chains commonly arise during site migrations, URL restructuring, or when multiple URL shortening services are layered. Over time, as URLs are updated without cleaning up old redirects, chains can grow to three, four, or more hops. Each additional hop adds network round-trip time and increases the risk of the chain breaking if any intermediate URL becomes unavailable.

Keeping chains short, ideally a single hop from source to destination, avoids these extra round trips. Google Search Central documentation states that Google's crawlers follow up to 10 redirect hops by default, and that the limit may differ for the crawlers of specific products (as of August 2026). Every additional hop is one more request the crawler makes before it reaches the content that is finally served.

To identify and fix redirect chains, use tools like Screaming Frog, Ahrefs, or browser developer tools to trace the full redirect path. The fix is straightforward: update each redirect in the chain to point directly to the final destination, eliminating intermediate hops.

Was this article helpful?

Related Terms

Redirect Loop

An error condition where two or more URLs redirect to each other in a circular pattern, preventing the browser from reaching any destination.

301 Redirect

A permanent HTTP redirect that tells browsers and search engines the resource has moved permanently to a new URL.

Meta Refresh

An HTML meta tag that instructs the browser to automatically redirect to a different URL after a specified delay.

404 Not Found

An HTTP status code indicating that the server cannot find the requested resource at the specified URL.

Client-Side Redirect

A redirect executed by the browser using HTML meta tags or JavaScript, after the initial page has been partially loaded.

JavaScript Redirect

A client-side redirect implemented using JavaScript code to navigate the browser to a different URL.

301 vs 302 Redirects - Choosing the Right Type for Short URLs

Understand the differences between 301 and 302 HTTP redirects. Learn how each type affects SEO, analytics, and performance for short URLs.

URL Shorteners and SEO - How Short Links Affect Search Rankings and Link Equity

Analyze the impact of short URLs on search engine optimization. Covers 301 redirect link equity, crawl budget effects, and SEO best practices.

Link Rot Prevention - How to Keep Your URLs Working for Years

Learn why links break over time and how to prevent link rot. Covers URL monitoring, redirect strategies, and long-term link preservation techniques.

FAQ

How many redirect hops are acceptable in a chain?

Google Search Central documentation states that Google's crawlers follow up to 10 redirect hops by default (as of August 2026). Even so, the ideal is to reach the final URL in a single redirect, because every extra hop adds a network round trip before the page appears.

How can you detect redirect chains?

Tools like Google Search Console, Screaming Frog, and the curl command can detect them. Using curl -L -v lets you inspect each step in the redirect chain.

Put the terms to work

Shorten a URL for Free