Redirect Chain

A redirect chain is a sequence of two or more redirects that a browser or crawler must follow in succession before arriving at the final destination URL. Instead of one URL pointing directly to its final target, the first URL points to a second, the second points to a third, and so on until the real page is reached. Each hop is a separate instruction to go somewhere else, and the chain is the full path the request travels through before content is finally served.

Mechanically, a redirect chain forms when redirects accumulate over time without being consolidated. A page might be moved once, creating a redirect from the old URL to a new one. Later the site restructures again, and the new URL is itself redirected somewhere else. Rather than update the original redirect to point straight at the current location, a new link is added to the chain. The same happens with protocol and format changes: a request for an old address might redirect from HTTP to HTTPS, then from a non-www to a www version, then from a trailing-slash to a non-trailing-slash form, stacking several hops onto what should be a single destination. Each redirect carries an HTTP status code, most often a 301 for permanent moves, and each hop adds a round trip between the client and the server.

The term combines redirect with chain. Redirect comes from the Latin prefix re, meaning again, and directus, meaning to guide or make straight, so to redirect is to guide a request elsewhere. Chain describes the way several redirects link one to the next, each one leading to another, like links in a physical chain. The name captures the structure precisely: redirects joined end to end.

For a business, redirect chains matter because they impose real costs on performance and SEO. Every hop adds latency, slowing the page load that users experience and contributing to worse speed metrics, which are especially punishing on mobile connections. For search engines, each additional redirect consumes crawl budget and can dilute the ranking signals passed along the way; while a single well-implemented redirect passes authority effectively, long chains risk gradual loss of that value and slower recognition of the final destination. Chains also make sites harder to maintain and debug, since the true target of a URL becomes obscured behind several layers.

The nuances and mistakes center on prevention and cleanup. The core fix is to flatten chains so that every old URL points directly to the final live destination in a single hop, updating the earliest redirect rather than piling on new ones. A related and worse problem is the redirect loop, where the chain circles back on itself and never resolves, leaving the page permanently inaccessible. Mixing redirect types, such as temporary redirects where permanent ones belong, sends inconsistent signals to search engines. Internal links compound the issue when they point at outdated URLs that then redirect, so updating internal links to their final targets removes unnecessary hops. Audited regularly and kept flat, redirects remain a clean tool for preserving value through change, while unmanaged chains quietly erode speed and search performance.