Home >Blog

What Is a Redirect Chain? A Clear Guide With Real Examples

Published 2026/08/23Updated 2026/08/23

A redirect chain is a sequence of HTTP redirects that sends a visitor or crawler through two or more URLs before reaching the page that ultimately loads. Instead of going directly from the requested URL to the destination, the browser follows a series of hops. Understanding that path helps you find slow pages, wasted crawl activity, and avoidable SEO issues.

What is a redirect chain?

A redirect chain happens when one redirect points to another redirect instead of pointing straight to the final page. For example, a request for http://example.com might first redirect to the HTTPS version, then to a www version, and finally to a canonical page.

Redirects are useful when a URL changes, a site moves to HTTPS, or content is consolidated. The problem is not normally one redirect. The problem is an unnecessary sequence of redirects that makes the request travel through several intermediate responses.

Single-hop redirect example

A single-hop redirect has one redirect response between the requested URL and the final URL:

https://example.com/old-page
301 → https://example.com/new-page
200 OK

Here, the old page is the source URL, the 301 response is the only hop, and the new page is the final URL. This is usually the cleanest migration path when the old address must remain available.

Multi-hop redirect chain example

A chain has multiple redirect responses before the final 200 response:

http://example.com/old-page
301 → https://example.com/old-page
301 → https://www.example.com/old-page
302 → https://www.example.com/new-page
200 OK

This path contains three redirect hops. Each response adds another network round trip and another opportunity for a rule conflict, redirect loop, or unexpected destination. The preferred result is a direct redirect:

http://example.com/old-page
301 → https://www.example.com/new-page
200 OK

What does hop mean?

A hop is one redirect step in the chain. In an HTTP trace, every 301, 302, 303, 307, or 308 response that sends the request to another URL counts as a hop. A URL that returns 200 OK is the endpoint, not another redirect hop.

For instance, the path A → B → C → D has three hops: A to B, B to C, and C to D. Counting hops makes it easier to compare alternative URL configurations and spot unnecessary steps.

Source URL and final URL

The source URL is the address you initially request. It may be an old URL, an HTTP version, a non-www hostname, or a URL with outdated tracking parameters.

The final URL is the last address in the redirect path that returns the actual page response, commonly 200 OK. It is the page users see after all redirects finish. A redirect checker compares the source and final URLs and records every intermediate response between them.

Why redirect chains matter

Speed: Every extra hop can add connection and server-response time, especially on mobile networks.
Crawling: Search engines spend crawl resources processing redirects instead of fetching useful content.
Signal clarity: Long or mixed redirect paths can make migrations and canonicalization harder to interpret.
Reliability: Multiple rules increase the risk of loops, temporary redirects left in production, or chains that end in an error.

How to check and fix a redirect chain

Enter the original source URL in a redirect checker.
Record each status code, Location target, and response URL in order.
Confirm that the final URL is the intended canonical page and returns a successful status.
Update the redirect rule so the source points directly to the final URL.
Retest HTTP/HTTPS, www/non-www, trailing-slash, case, and legacy paths after deployment.

Use a permanent 301 or 308 redirect for a lasting URL move when appropriate. Reserve temporary redirects such as 302 or 307 for changes that are genuinely temporary, and always verify the behavior with a fresh request rather than relying on a cached browser result.

Quick takeaway

A redirect chain is a route from a source URL to a final URL through multiple redirect hops. One intentional hop is often fine; several avoidable hops are worth removing. A direct, tested redirect makes the site faster, easier to crawl, and simpler to maintain.

What Is a Redirect Chain? A Clear Guide With Real Examples

What is a redirect chain?

Single-hop redirect example

Multi-hop redirect chain example

What does hop mean?

Source URL and final URL

Why redirect chains matter

How to check and fix a redirect chain

Quick takeaway

Table of Contents

Information

Tags

More Posts

301 vs 302 Redirects: When to Use 301, 302, 307, and 308

How to Find the Final URL Behind a Short Link

Too Many Redirects: Causes, Diagnosis, and Fixes

Do Redirect Chains Hurt SEO? What Google Recommends

Redirect Audit Checklist: How to Find Chains, Loops, and Broken Targets

How to Set Up and Test HTTP to HTTPS Redirects Correctly