A redirect chain occurs when one URL redirects to a second URL, which then redirects to a third URL (A > B > C). Redirect chains damage your SEO by wasting crawl budget, diluting page authority, and slowing down page load times for users. To fix them, edit your server rules so the initial URL redirects directly to the final destination (A > C).
Redirect Chains vs Infinite Loops
Both waste crawl budget, but they behave differently:
| | |
| | Eventually reaches a live page |
| | Never resolves, browser shows an error |
A chain is inefficient but functional; visitors and crawlers eventually land somewhere real. A loop is broken entirely; the browser displays "This page isn't working" or "Too many redirects" and gives up.
Why It Matters: Googlebot's Patience Has a Limit
Googlebot follows roughly 10 redirect hops before it abandons the crawl of that URL entirely. If your final destination sits beyond that threshold, Google may never index it.
Even chains well under that limit carry real costs:
- Each hop is a separate server request, multiplying time to reach content
- Crawl budget gets consumed on redirects instead of new or updated pages
- Page authority signals weaken slightly with each hop
- Core Web Vitals like LCP and TTFB suffer
For most sites, one redirect hop is the practical ceiling. Anything more should be flattened.
Diagnosing the Chain
Screaming Frog: The industry-standard desktop crawler. The free version handles up to 500 URLs and includes a Redirect Chains report showing every hop and status code.
Ahrefs Site Audit: A cloud-based option that flags chains alongside broader site health and backlink data, useful if you already use it for other SEO work.
Chrome DevTools (free): Open DevTools → Network tab, reload the page, and check the request list. Each hop appears as its own entry, letting you trace the path without any paid tool.
The Most Common Chain: HTTP to HTTPS to WWW
The single most frequent chain on the web follows this exact pattern:
http://site.com → https://site.com → https://www.site.com
This happens because three separate systems each enforce their own rule independently: the server forces HTTPS, a CDN or CMS setting forces www, and neither rule accounts for the other. A visitor typing the bare HTTP address gets bounced through two unnecessary hops before reaching the final page.
The fix is consolidation: one rule sending http://site.com directly to https://www.site.com in a single 301 redirect, skipping the intermediate stop.
Implementation Steps: Flattening the Chain
Step 1: Identify every chain using Screaming Frog or DevTools, noting the first URL and final destination for each.
Step 2: Access your site's .htaccess file (Apache) or Nginx config block via your hosting file manager.
Step 3: Locate the redirect rules causing each hop. Common culprits are separate rules for HTTPS enforcement and www normalization.
Step 4: Rewrite the rules so the first URL points directly to the final destination in one 301 redirect, removing the intermediate step.
Step 5: Update internal links, canonical tags, and sitemap entries to reference the final URL directly, so crawlers and users never trigger the redirect at all.
Step 6: Re-crawl the site to confirm each URL now resolves in a single hop.
What This Means for You
If you're forwarding a domain rather than hosting content directly, NameSilo's domain forwarding supports a clean 301 redirect straight to your final destination, avoiding unnecessary hops. For sites you host directly, NameSilo Hosting gives you full .htaccess access to flatten chains yourself. Frequently Asked Questions
What is a redirect chain?
A sequence of two or more redirects before reaching the final URL.
How do redirect chains affect SEO?
They waste crawl budgets, dilute authority, and slow page load times.
How do I find redirect chains on my website?
Use Screaming Frog, Ahrefs, or Chrome DevTools' Network tab.
A chain that cycles back on itself and never reaches a live page.
How many redirects will Google follow?
Roughly 10 hops before Googlebot abandons the crawl.
How do I fix a redirect chain in WordPress?
Update permalink settings and redirect plugin rules to a single hop.
The finite time and resources Google allocates to crawling your site.
Does NameSilo domain forwarding create redirect chains?
No, when configured correctly it delivers a single 301 redirect.
.png&w=2048&q=75)
.png&w=3840&q=75)
.png&w=3840&q=75)