Avoid Multiple Page Redirects: Flatten Redirect Chains

What this means

A redirect tells the browser that the URL it asked for now lives somewhere else. One redirect is normal and often necessary. A chain is when the browser has to follow two or more redirects in a row before it lands on the real page. For example: http://example.com → https://example.com → https://www.example.com → https://www.example.com/page/.

That is three hops to reach one page. The visitor still arrives, so nothing looks broken, which is why these chains pile up quietly as a site moves to HTTPS, picks a www preference, and migrates URLs. SEO ProCheck flags the page because the round trips are pure overhead.

Why it matters

Each redirect is a separate request and response across the network before the browser even starts fetching the page you actually want. Google's own guidance is blunt: redirects add an extra trip across the network that can delay loading by hundreds of milliseconds, and they are especially costly for resources in the critical rendering path.

• Speed and Core Web Vitals. Every hop adds latency before the document can load, which pushes out Time to First Byte and, in turn, Largest Contentful Paint. Three hops can mean the better part of a second lost before rendering begins.
• Wasted crawl budget. Search crawlers spend requests following each hop instead of fetching real content. On a large site, chains slow how quickly new and updated pages get discovered and indexed.
• Diluted link signals. Long chains pass authority less cleanly than a single direct redirect, and crawlers stop following after a limited number of hops.

How it gets flagged

This is the Lighthouse Avoid multiple page redirects audit, which SEO ProCheck mirrors. A page fails when it is reached through two or more redirects, and the report lists the URLs in the chain so you can see each hop in order. In newer Lighthouse versions the check folds into the broader Document request latency insight, but the rule is the same: the fewer hops, the better, with zero or one as the target.

How to fix it

1. Point your links at the final URL

The cheapest fix is to stop triggering the redirect at all. Update internal links, navigation, sitemaps, canonical tags, and hreflang references so they reference the final destination directly. A link that already points at the resolved URL never enters the chain.

2. Flatten the chain to one hop

Wherever a redirect must exist, rewrite it so the starting URL jumps straight to the final URL in a single step. If A goes to B and B goes to C, change the A rule to send users directly to C, then retire the middle rule. Audit your redirect map and replace every multi-step path with one direct rule. See our deeper guide on redirect chains and loops.

3. Fix stacked protocol and host rules

The most common chain is HTTP to HTTPS, then non-www to www (or the reverse), handled by two or three separate rules that fire one after another. Combine them. A single rewrite rule can move any request to the canonical protocol and host in one hop, for example forcing https://www.example.com directly, rather than chaining one rule per change. Use permanent 301 redirects for canonical moves so signals consolidate; reserve 302 for genuinely temporary cases, as covered in 301 vs 302 redirects.

4. Retire device redirects

If you still redirect mobile visitors to a separate mobile URL, that is an extra hop on top of everything else. Moving to responsive design serves one URL to every device and removes the redirect entirely.

False positives

Not every flag demands action. Watch for these:

• A single necessary redirect. One hop, such as HTTP to HTTPS on a directly typed URL, is expected and fine. The audit targets two or more.
• The chain starts at an external link you do not control. If another site links to an old URL that then redirects twice on your side, fix your own internal hops; you cannot edit their link, but you can still flatten your own rules.
• Login or consent gateways. Intentional auth or region-gate redirects may show as hops. Confirm they are required before removing them, and keep them to one step.

FAQ