mediumTechnical SEO

Redirect Chains Affecting SEO

URLs redirect through multiple hops before reaching their final destination, diluting link equity and adding crawl and user latency.

By Seoxpert Editorial · Published Jan 1, 2024

Why it matters

Every hop costs. Google has stated it will follow up to 5 redirects in a single pass; longer chains defer to the next crawl round, so a 6-hop chain can take multiple crawl cycles to fully index. Each hop also adds 50–200 ms of round-trip latency for users, and a small fraction of PageRank does not propagate through intermediate 301s.

Impact

Crawl efficiency drops — each extra hop reduces how often Google re-crawls downstream pages. User performance suffers — a 4-hop chain on a slow mobile connection can add over a second to Time to First Byte, directly worsening LCP.

How it's detected

For each crawled URL the scanner follows redirects manually, recording every hop's status code, destination, and timing. Any chain with more than one intermediate hop is flagged.

Common causes

•HTTPS + www canonicalisation applied as separate rules instead of a single combined rule
•Legacy 301s from site migrations stacked over years
•Internal links updated to the old HTTPS origin but not to the final www+trailing-slash destination
•Analytics or marketing tools inserting their own redirect layer on campaign URLs

How to fix it

First, audit the chain end-to-end with the redirect chain checker to see which hops exist. Then: (1) consolidate protocol and www rules into a single redirect that lands on the canonical form directly; (2) update internal links to point at the final URL, not a known-redirect URL; (3) for old-URL chains from migrations, replace the intermediate rules with a direct rule from origin-to-destination.

Code examples

Nginx: collapse a common 3-hop chain into 1

# BEFORE: http://example.com → https://example.com → https://www.example.com → https://www.example.com/
# AFTER: one rule handles all variants
server {
  listen 80;
  listen 443 ssl;
  server_name example.com www.example.com;
  if ($host != "www.example.com") {
    return 301 https://www.example.com$request_uri;
  }
  if ($scheme != "https") {
    return 301 https://www.example.com$request_uri;
  }
}

Apache .htaccess: combined protocol + www rule

# One redirect to the canonical https://www origin
RewriteEngine On
RewriteCond %{HTTPS} !=on [OR]
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule ^ https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

FAQ

How many hops is too many?

Two or more intermediate hops (three total including the origin request and the final destination) is the point where Google and users both start to pay. One hop — the initial http-to-https or non-www-to-www redirect — is fine and unavoidable.

Does each hop lose link equity?

Modern Google largely preserves PageRank through 301 chains, but a small fraction does leak at each hop. The bigger concerns are crawl efficiency and user latency, both of which scale linearly with chain length.

Related Issues

Redirect Chains Detected

Redirect chains occur when a URL redirects through one or more intermediate URLs before reaching its final destination. This process increases page load times a

medium

Redirect Loops Detected

Redirect loops occur when two or more URLs redirect to each other in a cycle, preventing users and search engines from ever reaching the intended destination pa

high

Found this issue on your site?

Run a scan to see if Redirect Chains Affecting SEO affects your pages.

Scan my website →