Redirect Chains: How to Find Them, Fix Them and Stop New Ones
A redirect chain is a URL that takes more than one hop to reach its final page. One redirect is normal. Three in a row is slow for visitors, extra work for search engines, and usually a sign that old rules were stacked on top of each other. Here is how to find every chain on a site and flatten it.
What Is a Redirect Chain?
A redirect sends a request for one URL to another. A redirect chain is two or more redirects in a row before a page answers 200:
http://example.com/shoes
301 -> https://example.com/shoes
301 -> https://www.example.com/shoes
301 -> https://www.example.com/shoes/
200
That is three hops for one page. Each hop is a full request: DNS, connection, response, then the next one. A redirect loop is a chain that comes back to a URL already in it, so it never ends on a page at all. Browsers stop and show an error, and crawlers give up.
Why Redirect Chains Matter for SEO
- Crawling. Google says its crawlers follow up to 10 redirect hops (see its page on HTTP status codes). Its crawl budget guide also lists long redirect chains as something that hurts crawling. On a big site, every extra hop is a request that could have fetched a real page.
- Speed. Visitors wait for every hop, and on a phone each one can add a noticeable delay before the page even starts loading.
- Mixed signals. A chain that mixes a 302 into a row of 301s sends a weaker signal about which URL is the real one.
- Dead ends. The longer the chain, the more likely one hop eventually breaks and the whole path ends on a 404.
| Number | Value | Source |
|---|---|---|
| Hops Googlebot follows | 10 | |
| Hops to aim for | 1 | Old URL to final page |
| Hops that make a chain | 2 or more | Redirect Chain check |
| Keep redirects after a move | 1 year or more |
Fixing chains is rarely the one thing that moves rankings. It is cheap hygiene that makes every crawl, migration and audit easier, which is why it sits in step 6 of the technical SEO audit checklist.
301 vs 302, and the Other Redirect Types
Google's guide to redirects splits them into permanent and temporary. A permanent redirect is a strong signal that the target should be the canonical URL. A temporary one is a weak signal, so Google may keep showing the old URL.
| Redirect | Type | Keeps POST | Use for |
|---|---|---|---|
| 301 | Permanent | ◐ | Moves, merges, https |
| 308 | Permanent | ✓ | Moves, forms, APIs |
| 302 | Temporary | ◐ | Short changes |
| 303 | Temporary | – becomes GET | After a form post |
| 307 | Temporary | ✓ | Short changes, APIs |
| Meta refresh, 0 seconds | Permanent | n/a | No server access |
| Meta refresh, delayed | Temporary | n/a | Avoid |
| JavaScript | Seen after rendering | n/a | Last resort |
308 and 307 are the same as 301 and 302, except the browser must keep the request method (RFC 9110, section 15.4), which matters for forms and APIs, not for ordinary pages. If a move is permanent, use 301 or 308. A 302 left in place for years is one of the most common findings in any redirect audit.
Where Redirect Chains Come From
- Host and protocol rules written separately. One rule adds https, another adds www, a third adds the trailing slash. Each is fine alone; together they make three hops.
- Migrations stacked on migrations. The 2019 redesign redirected A to B. The 2023 move redirected B to C. Nobody went back to point A at C.
- Changed slugs. Many CMSs add a redirect each time a slug changes, so a page renamed three times has a three-hop history.
- Internal links to old URLs. The redirect works, but menus, footers and old posts still link to the first URL in the chain, so every visit starts at the top.
- Letter case and slash normalization added by a plugin, a CDN rule and the server, all at once.
The opposite mistake: no redirect at all. We found this on our own site. In our SEO pass on November 20, 2026, http://neova.app answered 200 instead of a 301 to https, so every page existed twice. One server rule fixed it. A quick test for your own site:
curl -sI http://example.com/ | head -1
# want: HTTP/1.1 301 Moved Permanently
SEO ProCheck covers more causes in redirect chains and loops: causes and fixes.
How to Find Redirect Chains
One URL: curl
To see every hop of a single URL, ask for the headers and follow the redirects:
curl -sIL https://example.com/old-page | grep -iE '^(HTTP|location)'
Each HTTP line is one response and each location line is where it sends you. More than one 3xx means a chain. Some servers answer a HEAD request differently from a GET, so if the result looks odd, open the URL with your browser's network tab and Preserve log turned on.
A whole site: a redirect chain checker
A crawler is the redirect chain checker for a whole site. Crawl from the home page, then list every internal URL that redirects with its number of hops, its final status and the pages that link to it. That last part tells you which links to update.
Old URLs: a list crawl
Chains often live on URLs no link points to any more: old campaign links, URLs from the previous site, backlinked pages. Crawl those as a list, from an export of top linked pages or an old sitemap, and see where each one ends.
Search Console and logs
Redirected URLs that still get clicks in Search Console show which old URLs people and Google still use. A server log shows how many bot requests end on a 3xx; if that share keeps rising, new chains are appearing. The log file analysis guide covers how to read that.
How to Fix Redirect Chains
- Export every chain with its first URL, each hop and the final URL.
- Check the final URL. It should answer 200, be indexable and be its own canonical. If it is not, decide the right destination first.
- Point every old URL straight at the final one. Rewrite the first rule of each chain so it skips the middle hops. Keep the middle rules too, pointing at the final URL, since other sites may link to them.
- Merge host and protocol rules into one hop. See the example below.
- Update internal links to the final URL, starting with navigation and footer links, which repeat on every page. SEO ProCheck looked at whether 301 internal links harm SEO.
- Update XML Sitemaps and canonicals so they list final URLs only.
- Crawl again and confirm every old URL now takes one hop.
A single redirect in Apache (.htaccess) and nginx:
# Apache, .htaccess
Redirect 301 /old-page/ https://www.example.com/new-page/
# nginx
location = /old-page/ {
return 301 https://www.example.com/new-page/;
}
http and non-www in one hop instead of two, in Apache with mod_rewrite:
RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule ^ https://www.example.com%{REQUEST_URI} [L,R=301]
And in nginx, one server block catches every http request and sends it to the final host:
server {
listen 80;
server_name example.com www.example.com;
return 301 https://www.example.com$request_uri;
}
You still need an https server block for example.com that redirects to www, with its own certificate. Google's site move guide recommends keeping redirects in place for as long as possible, generally at least a year.
Redirect Loops: How to Spot and Break Them
A loop is usually two rules that disagree. A common one: the CMS adds a trailing slash while a server rule removes it.
/shop 301 -> /shop/ (CMS)
/shop/ 301 -> /shop (server rule)
| Loop cause | Where | Fix |
|---|---|---|
| Slash added, then removed | CMS and server | One slash rule |
| https rule behind a proxy | Proxy or CDN | Pass the original protocol |
| Language redirect, back and forth | App or CDN | Redirect once, then stop |
| URL redirects to itself | Any rule | Delete the rule |
To fix one, list every rule that touches the URL, at the CDN, the server and the CMS, decide which version is final, and remove the rule that points the other way. Then test the URL with curl and with a fresh browser profile, since browsers cache 301s.
Find Redirect Chains With Neova
Neova's Redirects category shows where redirects go, how many hops they take, loops, temporary redirects, meta refresh and JavaScript redirects, and the links that point at them. Status codes are colored the same everywhere: 2xx green, 3xx orange, 4xx and 5xx red. The checks behind it include:
- Internal URL Is in a Redirect Chain, for 2 or more hops
- Internal URL Is in a Redirect Loop
- Internally Linked URL Redirects, with the links to update
- Internal URL Uses a Temporary Redirect, leaving login and sign-in targets alone
- Internal Redirect Ends on a 4xx or 5xx
- Meta Refresh Is Used as a Redirect and HTML Page Redirects Through JavaScript
- Redirecting URL Is Listed in an XML Sitemap and Canonical Points to a Redirecting URL
- Redirected URL Received Clicks in Search Console, with Search Console connected or imported
For old URLs, List Crawl crawls only the URLs you paste or upload. For a migration, Redirect Map matches every URL of the old site crawl to the new one, and Live Redirect Check flags old URLs whose live redirect is wrong or missing. Every check runs on every plan, Free included, on Mac, Windows, Linux and in the browser with Neova Online. See Features, the full feature list, or download Neova. For links that end on errors instead of redirects, see the broken link checker guide.
Questions
What is a redirect chain?
A URL that passes through two or more redirects before it reaches a page that answers 200, such as http to https, then to www, then to a trailing slash version.
How many redirects in a chain are too many?
Aim for one hop from any old URL to its final page. Google says its crawlers follow up to 10 hops, but every hop adds a request and a delay, so treat any chain of two or more as something to flatten. The redirects and HTTP status codes FAQ on SEO ProCheck answers more of these.
Is a 301 or a 302 better for SEO?
Neither is better in general; they mean different things. Use 301 or 308 for permanent moves, which Google treats as a strong canonical signal. Use 302 or 307 only for changes that will be undone.
Do redirect chains lose link equity?
Google does not document a loss per hop. The practical problems are clearer: slower pages, more crawl requests, and chains that break when one hop fails. Flatten them and link to final URLs either way.
How do I fix a redirect loop?
Find every rule that touches the URL at the CDN, server and CMS, pick the final version, and remove the rule that sends it back. Then test with curl and a fresh browser profile, since browsers cache 301 redirects.