Updated April 2026

Redirect Chains: How They Hurt SEO and How to Fix Them

Find redirect issues in your sitemapAnalyze My Site

A redirect chain happens when a URL redirects to another URL, which redirects to yet another URL, creating a sequence of hops before reaching the final destination. For example: /old-page redirects to /temp-page which redirects to /new-page. Each hop adds latency, consumes crawl budget, and leaks a small amount of PageRank. Google recommends keeping redirects to a single hop wherever possible.

Why Redirect Chains Are a Problem

Each redirect in a chain adds around 100-300ms of load time. For users on mobile or slow connections, a 3-hop chain can add nearly a second to page load. More critically for SEO: Google has historically reduced the PageRank passed through each redirect hop, meaning a long chain dilutes the link equity from external links. Google also stops following redirect chains that exceed about 5 hops - anything beyond that may not get indexed. Googlebot spends extra crawl budget following each redirect, leaving less for your actual content.

Common Causes

Redirect chains usually accumulate over time. You migrate from HTTP to HTTPS - that is one redirect. Later you add www to non-www standardization - that is another. Later you restructure URLs - another hop added on top. The result is HTTP/old-url redirects to HTTPS/old-url redirects to HTTPS/new-url. Each migration adds a layer without anyone cleaning up the previous ones. CMS platforms can also create chains: a WordPress category rename creates a redirect, and if you had previous redirects to that category, you now have a chain.

How to Find Redirect Chains

The fastest method is Screaming Frog - run a crawl and filter by redirect chains in the Response Codes tab. You can also use curl to follow redirects manually: curl -L -s -o /dev/null -w "%url_effective\n%num_redirects" yoursite.com/old-url. If you get a num_redirects value greater than 1, you have a chain. In Google Search Console, the Pages report under "Page with redirect" shows URLs in your sitemap that redirect, which is a signal to check for chains.

How to Fix Redirect Chains

The fix is to update every redirect in the chain to point directly to the final destination. Instead of A to B to C, make A go directly to C. Update your redirect rules in your .htaccess file, nginx config, or CDN redirect rules. Also update any internal links still pointing to intermediate URLs - link directly to the final URL. Check your sitemap: if any URLs in your sitemap redirect, update the sitemap to use the final destination URL directly. Sitemaps should never contain redirecting URLs.

Redirect Loops

A redirect loop is when URL A redirects to URL B which redirects back to URL A. Browsers show an error like “The page is not redirecting properly.” Loops usually happen due to misconfigured HTTPS redirects — for example, when both HTTP and HTTPS versions of the same URL redirect to each other. Fix by checking your SSL configuration and ensuring only the non-secure version redirects to the secure version, never the other way around.

Redirect Chains After Site Migrations

Site migrations are the most common source of long redirect chains. A migration from HTTP to HTTPS creates one layer. A later rebrand with a new domain adds another. A URL restructuring sprint adds a third. Without active cleanup after each migration, chains accumulate silently — the redirect still works for users, so nobody notices, but each additional hop leaks PageRank and increases the latency Googlebot experiences when crawling. Always audit your redirects after every migration using a tool that follows the full chain and reports the number of hops per URL.

After identifying chains, update your redirect rules to point each intermediate URL directly to the final destination. For Apache servers, edit your .htaccess file and replace chained redirects with a single Redirect 301 /old-url /final-url. For Nginx, update your server block location rules. For Next.js, update next.config.js redirects array. Test each URL with curl -L -s -o /dev/null -w "%{http_code} %{url_effective} %{num_redirects}" to confirm it resolves in exactly one hop.

Redirect Chains in Your Sitemap

Your XML sitemap should only contain final destination URLs — ones that return 200 OK with no redirects. If any URL in your sitemap returns a 301 or 302, it will show up in Google Search Console as “Page with redirect” under the Pages report, and Google will count it as an inefficiency rather than a valid sitemap entry. A sitemap with 20% redirecting URLs is telling Google that your housekeeping is poor — it reduces trust in the sitemap as a reliable index of your site's canonical content.

Run SitemapFixer or Screaming Frog against your sitemap file specifically (not a full site crawl) and filter for non-200 status codes. Any URL returning 3xx should be updated in your sitemap to the final destination URL. After updating the sitemap, resubmit it in Google Search Console so Google processes the corrected version promptly.

Check your sitemap for redirect issues

Free - finds chains and loops in 60 seconds

Analyze My Site Free