How to find and fix redirect chains on your website
A redirect chain sends visitors through two or more hops before the final page. How to find chains, fix them at the source, and stop new ones forming.
By Sohail Hussain21 November 20265 min read
A redirect chain is a URL that redirects to another URL that also redirects: /old to /newer to /newest. To fix one, change the first redirect so it points straight at the final page, combine your protocol and hostname redirects into a single rule, and update your internal links so they never hit a redirect at all. On most sites that is an afternoon of work after a crawl.
Chains build up quietly. Each redesign adds redirects on top of the last one, and nobody goes back to update the old rules. Redirect audits are part of our technical SEO and performance work and one of the URL checks in our technical SEO checklist.
Why do redirect chains matter?
They slow visitors down. Every hop is another request and response before the page starts loading. On a mobile connection that delay is noticeable, and it lands before anything has rendered.
Google stops following eventually. Google's documentation on HTTP status codes says its crawlers follow up to 10 redirect hops by default. Past that, or in a loop, Search Console reports a "Redirect error" in the Page indexing report and the page is not indexed.
They waste crawling. Google's crawl budget guide says to avoid long redirect chains because they have a negative effect on crawling. Each hop is a request Google spends on your site without reaching a page.
They hide weak links. A chain that passes through a 302, a URL that now returns 404, or an old domain whose renewal lapses can break without anyone noticing, because the first URL still "redirects".
301 vs 302 redirects covers which status code each hop should use. This post is about removing the extra hops.
Where do redirect chains come from?
| Cause | Example | Fix |
|---|---|---|
| Separate protocol and host rules | http://example.com to https://example.com to https://www.example.com | One rule that sends every variant to the final host |
| Migration on top of a migration | 2019 redirects point to 2022 URLs, which now redirect to 2026 URLs | Update the 2019 rules to the 2026 destinations |
| Trailing slash normalisation | /about to /about/ to /company/ | Page rules point to the normalised final URL |
| CMS slug changes | WordPress auto-redirects an old slug, then a plugin rule redirects again | Keep one source of redirects |
| Server and plugin both redirecting | .htaccess sends to https, a plugin then sends to www | Move all host rules to one layer |
| Internal links to old URLs | The menu still links to /services-old | Link to the final URL directly |
The first row is the most common. It affects every old link pointing at the non-preferred host, which often includes links from other sites that you cannot change.
How do you find redirect chains?
Crawl the site. A desktop crawler such as Screaming Frog, or any crawler with a redirect report, lists every internal URL that redirects and the hops each one takes. Also crawl the old URL list from your last migration or from the sitemap of the previous site, because old URLs are where chains live.
Check single URLs from a terminal. This prints every hop's status line and destination:
curl -sIL https://example.com/old-page | grep -iE "^(HTTP|location)"
More than one location line means a chain. In a browser, the Network tab in developer tools shows the same, with "Preserve log" ticked.
Check Search Console. In the Page indexing report, "Redirect error" lists URLs where Google gave up: a chain that was too long, a loop, a URL that grew beyond the maximum length, or a bad URL in the chain. "Page with redirect" lists URLs that redirect successfully; it is normal, but a large count of internal URLs there means your own links point at redirects.
How do you fix them, step by step?
- List every redirect and its final destination. Export from the crawl: source URL, each hop, final URL, final status.
- Point each rule straight at the final URL. Edit the destination of every rule to the final, absolute URL that returns 200. Put page-level rules before host rules where your server allows it, so an old path on an old host still reaches its new page in one hop.
- Combine protocol and host redirects into one rule. On Nginx, every non-canonical host and protocol goes to the final host in one response:
server {
listen 80;
server_name example.com www.example.com;
return 301 https://www.example.com$request_uri;
}
server {
listen 443 ssl;
server_name example.com;
# ssl_certificate and ssl_certificate_key go here
return 301 https://www.example.com$request_uri;
}
On Apache, in .htaccess:
RewriteEngine On
RewriteCond %{HTTPS} off [OR]
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule ^ https://www.example.com%{REQUEST_URI} [L,R=301]
If HTTPS ends at a CDN or load balancer in front of the server, %{HTTPS} is always off and that rule loops; do the host redirect at the CDN instead. On Vercel, Netlify and similar hosts, set the preferred domain in the dashboard and let the platform redirect the others.
- Update internal links, canonicals and the sitemap. Menus, footers, buttons and links inside content should use the final URL. Canonical tags and sitemap entries should never name a URL that redirects.
- Re-crawl and confirm one hop. Every old URL should reach a 200 page in one redirect, and no internal link should redirect at all.
- Validate in Search Console. If "Redirect error" appeared in the Page indexing report, click "Validate fix" on it.
If you are rebuilding the redirect list, our redirect generator turns a two-column list of old and new URLs into Apache, Nginx and Next.js rules.
How do you stop new chains forming?
Keep every redirect in one place, as one file or one table, rather than split across the server, a plugin and the CMS. When you add a redirect, search that list for any rule whose destination is the URL you are now moving, and update it to the new destination at the same time. That one habit prevents most chains.
After any migration, run the old site's URL list through a crawler once the new site is live, and again a month later. A website migration without losing SEO depends on that check more than on any other.
For the redirect rules themselves, Google's guide to redirects and Google Search lists every method it recognises, from server-side 301s to meta refresh, and how each is treated.
Was this guide useful?