Redirect chains are one of those silent SEO killers that slowly drain your crawl budget, slow down your pages, and dilute the link equity flowing through your site. The worst part? Most site owners don’t even know they exist until rankings start slipping.
In this practical walkthrough, we’ll show you exactly how to identify redirect chains using Screaming Frog and Google Search Console, then fix them by pointing every redirect directly to its final destination URL.
What Is a Redirect Chain?
A redirect chain happens when there is more than one redirect between the originally requested URL and the final destination URL. Instead of going straight from point A to point B, the browser (and Googlebot) has to hop through several intermediate URLs.
Here’s what a typical chain looks like:
URL A → URL B → URL C → URL D (final)
Each hop costs time, server resources, and a small amount of PageRank. A clean setup should always be:
URL A → URL D (final)
Redirect Chain vs Redirect Loop
Don’t confuse the two:
- Redirect chain: Multiple redirects ending at a valid destination.
- Redirect loop: Redirects that cycle back on themselves, never reaching a destination (URL A → URL B → URL A).
Why Redirect Chains Hurt Your SEO
Redirect chains aren’t just a technical annoyance. They actively damage performance and crawlability.
| Issue | Impact |
|---|---|
| Wasted crawl budget | Googlebot spends time following hops instead of discovering new content. |
| Slower page load | Each hop adds latency, hurting Core Web Vitals and user experience. |
| Link equity loss | While Google says 301s pass full PageRank, long chains still reduce signal clarity. |
| Crawl abandonment | Google may stop following a chain after 5 hops, never indexing the final URL. |
| Broken tracking | UTM parameters and referrer data can get stripped along the way. |
Common Causes of Redirect Chains
Before fixing them, it helps to understand where chains usually come from. The biggest culprits include:
- CMS migrations: Moving from WordPress to Shopify, or restructuring your URLs, often leaves old redirects pointing to URLs that have since been redirected again.
- HTTPS switches: Going from HTTP to HTTPS without consolidating older redirects creates chains like http://example.com → https://example.com → https://www.example.com.
- Domain changes: Rebrands and domain consolidations stack redirects from old domains on top of existing ones.
- Trailing slash policies: Inconsistent trailing slash handling adds an extra hop.
- WWW vs non-WWW: Server rules redirecting between subdomain versions add unnecessary steps.
- Plugin conflicts: Multiple redirect plugins or rules in .htaccess overlapping with each other.
Step 1: Find Redirect Chains with Screaming Frog
Screaming Frog is the gold standard tool for auditing redirect chains. Here’s the exact process.
1. Configure the crawler
- Open Screaming Frog SEO Spider.
- Go to Configuration → Spider → Advanced and tick “Always Follow Redirects”.
- Also tick “Always Follow Canonicals” to get a full picture.
2. Crawl your site
Enter your domain and let the crawl complete. For larger sites, consider crawling in segments by directory.
3. Run the Redirect Chains report
- Once the crawl finishes, go to Reports → Redirects → Redirect Chains.
- Export the CSV file.
The export gives you a table with every chain on your site, the number of redirects in the chain, the final status code, and the final destination URL. The column labelled “Number of Redirects” is what you want to focus on first. Anything with 2 or more hops needs attention.
4. Prioritize what to fix
Sort by:
- Chains with the most hops (longest first).
- Chains affecting high-traffic URLs (cross-reference with your analytics).
- Chains involving internal links you control directly.
Step 2: Cross-check with Google Search Console
Google Search Console gives you the search engine’s perspective. While GSC doesn’t have a dedicated “redirect chains” report, you can spot issues through several signals.
Pages report
Head to Indexing → Pages and look for these statuses:
- “Page with redirect”: URLs Google found but didn’t index because they redirect. Click in to see which URLs are involved.
- “Redirect error”: Often a sign of chains that exceed Google’s hop limit or contain loops.
URL Inspection tool
For any suspicious URL, paste it into the URL Inspection tool. Check the “Page indexing” section. If Google reports redirects, you can see the destination it ultimately reached, which helps confirm whether a chain exists.
Crawl Stats
Under Settings → Crawl stats, look at the response code breakdown. A high percentage of 301/302 responses signals that Googlebot is spending too much time on redirects rather than real content.
Step 3: Fix Redirect Chains by Pointing to the Final URL
The fix is conceptually simple: every redirect should point directly to the final destination URL, not to another redirect.
The before and after
| Before (Chain) | After (Clean) |
|---|---|
| /old-page → /temp-page → /new-page | /old-page → /new-page /temp-page → /new-page |
How to implement the fix
Depending on your setup, here’s where to update your redirect rules:
- Apache (.htaccess): Edit each
Redirect 301orRewriteRuleto target the final URL. - Nginx: Update
return 301directives in your server block. - WordPress (Redirection plugin or Yoast): Open each redirect rule and replace the destination with the final URL.
- Shopify: Go to Online Store → Navigation → URL Redirects and update each entry.
- Cloudflare: If using Page Rules or Bulk Redirects, edit them at the edge to skip intermediate hops.
Update internal links too
Don’t stop at the redirect rules. Update internal links so they point to the final URL directly. This eliminates the need for the redirect entirely on internal navigation. Use Screaming Frog’s “All Inlinks” report to find every internal link pointing to a redirected URL.
Step 4: Verify the Fix
After applying changes, you need to confirm the chains are actually broken.
- Re-crawl with Screaming Frog and re-run the Redirect Chains report. Aim for zero entries with 2+ hops.
- Use a Chrome extension like Redirect Path or Link Redirect Trace to manually check key URLs.
- Check the response headers using browser DevTools (Network tab) to confirm a single 301 hop.
- Request indexing in Search Console for important fixed URLs to speed up recognition.
Best Practices to Prevent Future Chains
- Maintain a single, authoritative redirect map spreadsheet for every migration.
- Before adding any new redirect, check whether the destination URL is already a redirect target.
- Schedule a quarterly Screaming Frog audit to catch chains early.
- Consolidate redirect rules in one place (avoid mixing .htaccess, plugins, and CDN rules).
- After every HTTPS, domain, or CMS change, run a full redirect audit within 48 hours.
FAQ
How many redirects in a chain are too many?
Google can follow up to 10 hops but typically gives up after 5. From an SEO standpoint, anything beyond a single redirect is too many. Always aim for zero hops or one 301 maximum.
Do redirect chains pass link equity?
Each 301 redirect in a chain passes link equity, but the longer the chain, the higher the risk of Google not following it fully. Direct redirects are always safer for preserving PageRank.
What’s the difference between a redirect chain and a redirect hop?
A single hop is one redirect (URL A → URL B). A chain occurs when there are two or more hops between the original URL and the final destination.
Can redirect chains affect Core Web Vitals?
Yes. Each redirect adds network latency, which directly impacts Largest Contentful Paint (LCP) and Time to First Byte (TTFB). Fixing chains is one of the simplest performance wins.
Should I fix 302 chains the same way as 301 chains?
Yes, but also evaluate whether the 302 should be a 301. 302s are meant for temporary redirects. If the destination is permanent, convert to a 301 while you flatten the chain.
Will fixing redirect chains recover lost rankings?
Often yes, especially if chains were preventing Google from indexing the final URLs or wasting crawl budget on important sections. Expect to see improvements within a few weeks after re-crawling.
Final Thoughts
Redirect chains are easy to create and easy to overlook, but they have a measurable impact on crawl efficiency, page speed, and ranking signals. With Screaming Frog and Search Console working together, you can find every chain on your site within an hour and fix the majority in an afternoon.
The rule to remember is simple: every redirect should point straight to the final destination URL. Audit regularly, especially after migrations, and you’ll keep your site fast, crawlable, and ranking-ready.