How to Fix Redirect Chains and Collapse Them to One 301
A redirect chain happens when a URL redirects to another URL that redirects again before reaching the final page, such as http → https → www → trailing slash. This guide shows you how to find every URL that takes two or more hops, rewrite your rules so each old URL reaches its destination in a single 301, and update your own links so most visitors skip redirects entirely.

Why it matters
Each extra hop adds a full network round trip, often 100–300 ms on mobile, before the browser can request the page. Googlebot follows up to 10 hops, but every hop uses crawl budget and is one more place for a misconfigured rule to break. AI crawlers and link-preview bots are usually less patient and may stop after one or two redirects, so your content never gets fetched.
Chains also tend to hide mixed 301/302 hops, which send weaker signals about which URL is canonical. A single 301 avoids all of this.
What you need
Step-by-step fix
Export every URL that takes 2+ redirects
Start from the audit's list of URLs that pass through two or more redirects before resolving. If you need the full picture, crawl the site in Screaming Frog with Configuration > Spider > Advanced > Always Follow Redirects turned on, then open Reports > Redirects > Redirect Chains. Put the results in a spreadsheet with these columns: source URL, each hop, final URL and status codes.
Trace each chain to see where the hops come from
Run curl against a few flagged URLs to see every hop and its status code. Use the Server and CF-Ray headers to tell which layer issues each redirect: your CDN, your web server or your CMS. Stacked chains usually happen when two layers each do part of the job.
For example, Cloudflare forces HTTPS and then WordPress adds www.
curl -sIL http://example.com/pricing | grep -iE '^(HTTP/|location:|server:|cf-ray:)'
Merge protocol, host and slash rules into one hop
Pick a single canonical form: protocol, host and trailing-slash style. Then write one rule that sends every non-canonical variant straight to it. Remove the overlapping rules in other layers.
If you keep HTTPS forcing in your CDN, turn off the duplicate redirect in your CMS or server. The Nginx example below catches http and non-www requests in one server block. htaccess:
- RewriteEngine On
- RewriteCond %{HTTPS} off [OR]
- RewriteCond %{HTTP_HOST} !^www\. [NC]
- RewriteRule ^ https://www.example.com%{REQUEST_URI} [L,R=301]
server {
listen 80;
listen 443 ssl;
server_name example.com;
# ssl_certificate lines here for the 443 listener
return 301 https://www.example.com$request_uri;
}
server {
listen 80;
server_name www.example.com;
return 301 https://www.example.com$request_uri;
}Flatten old redirect-map entries
Chains also build up over time. You redirected /old to /new last year, then /new to /newer this year. In your redirect list, change every entry so its target is the final URL.
If A→B and B→C both exist, change A→B to A→C and keep B→C. In a spreadsheet, a VLOOKUP of each target against the source column shows which targets are themselves redirected.
# Before /summer-sale /sale 301 /sale /offers/ 301 # After /summer-sale /offers/ 301 /sale /offers/ 301
Point internal links, sitemap and canonicals at final URLs
Redirects are a safety net for outside links. Your own links should not rely on them. In Screaming Frog, use Bulk Export > Response Codes > Internal > Redirection (3xx) Inlinks to see which pages link to redirecting URLs, then update those links in menus, templates and content.
Also check these places:
- XML sitemap: only final 200 URLs
- rel=canonical and hreflang tags
- Open Graph og:url
- Links in email templates and ads you control
<!-- Before --> <a href="http://example.com/pricing">Pricing</a> <!-- After --> <a href="https://www.example.com/pricing/">Pricing</a>
Purge caches and confirm one hop per URL
Clear your CDN cache and any page or redirect cache in your CMS, because old 301s are often cached. Re-run curl on the URLs you traced earlier. Each should now show exactly one 3xx line followed by a 200.
Then re-crawl the site or re-run the audit and check that the count of URLs with 2+ redirects is zero.
for u in http://example.com/pricing http://www.example.com/pricing https://example.com/pricing; do echo "$u"; curl -sIL "$u" | grep -E '^HTTP/'; echo; done
Platform-specific notes
WordPress
Chains usually come from the WordPress Address and Site Address settings in Settings > General disagreeing with a host or CDN HTTPS redirect, or from plugin redirects stacking on top of each other. Make sure both addresses use the final https://www form. Then edit targets in Tools > Redirection, or Rank Math > Redirections, so none point to another redirected URL.
Shopify
Shopify handles HTTPS and primary-domain redirects itself. Set the primary domain in Settings > Domains. Edit URL redirects under Online Store > Navigation > View URL redirects, where you can export them to CSV, fix targets that point to other redirected paths, and re-import. You cannot edit server rules, so focus on flattening redirect targets and fixing internal links.
Cloudflare
Avoid splitting the job between SSL/TLS > Edge Certificates > Always Use HTTPS and a separate www Redirect Rule. Together they create two hops. Use a single Redirect Rule under Rules > Redirect Rules with a dynamic target such as concat("https://www.example.com", http.request.uri.path) that matches both http and non-www, and enable Preserve query string. Bulk Redirects lists should also point to final URLs.
Next.js
Entries in the redirects() function of next.config.js can chain into each other and into the trailingSlash setting. Set each destination to the final path, using the slash style that matches trailingSlash. Set permanent: true, which sends a 308. If you host on Vercel, set the www/apex redirect in Project > Settings > Domains rather than in code.
Webflow
Choose the default domain under Site settings > Publishing > Production. Webflow then redirects the other domain in a single hop. Fix legacy chains under Site settings > Publishing > 301 redirects, where each Old Path should point straight to the final path. Republish the site afterwards.
Check that it worked
✅ How to verify
- Run curl -sIL on a sample of previously flagged URLs: each should show one 301/308 line followed by HTTP/2 200
- Re-crawl in Screaming Frog and confirm Reports > Redirects > Redirect Chains is empty
- Re-run the audit and confirm the Redirect chains check reports 0 URLs passing through 2+ redirects
- In Google Search Console, use URL Inspection on the old http/non-www URL and confirm the reported redirect target is the final canonical URL
⚠️ Common mistakes
- Fixing the server rule but leaving a CDN or CMS redirect active, so a second hop comes back from another layer
- Deleting the middle redirect (B→C) after flattening A→C, which breaks backlinks and bookmarks that still point to B
- Using 302 or JavaScript/meta-refresh redirects for permanent moves, which keeps chains ambiguous for search engines
- Updating redirects but leaving internal links, sitemaps and canonicals pointing at old URLs, so users and crawlers still hit a redirect on every visit
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
How many redirects are too many for SEO?
Aim for one. Googlebot follows up to 10 hops before giving up, but each hop adds latency and uses crawl budget, and many other bots stop much sooner. This audit flags any URL that needs two or more redirects to resolve.
Do redirect chains lose link equity?
Google says 3xx redirects don't lose PageRank. However, long chains are fetched less reliably, can be dropped by crawlers, and often contain a 302 or a broken hop. Collapsing them to one 301 removes that risk and speeds up the page.
Should I use a 301 or 308 redirect?
Both are permanent and treated the same by Google. 308 keeps the request method, which matters for form POSTs and APIs. 301 is fine for normal page URLs. What matters is that each old URL reaches its final destination in one hop.
Can I delete old redirects once the chain is fixed?
Keep any redirect that still receives traffic or has external backlinks, and just point it at the final URL. Remove only redirects with no traffic and no links after checking your server logs and backlink data over at least several months.
How to Fix Redirect Loops (ERR_TOO_MANY_REDIRECTS)
How to Fix Server Errors (5xx) Found in Your Site Audit
How to Fix 302 Redirects Used for Permanent Moves
How to Fix Broken Internal Links That Return 4xx Errors
How to Fix Soft 404 Pages and Return a Real 404 Status
How to Fix Missing or Inaccurate Sitemap lastmod Dates