Redirect chains are one of those silent SEO killers most site owners never notice until rankings start slipping or crawl budget gets wasted on hop after hop. If you manage a site with any real history (migrations, HTTPS moves, category renaming, product cleanups), chances are you already have dozens, sometimes thousands, of chains hidden in your architecture.
In this practical walkthrough, we will show you exactly how to find and fix redirect chains using Screaming Frog, how to read the crawl reports properly, and how to prioritize what to fix first so you preserve link equity and improve crawl efficiency.
What Is a Redirect Chain?
A redirect chain occurs when there is more than one redirect between the initial URL requested and the final destination URL. Instead of URL A pointing directly to URL C, it passes through URL B (or B, then C, then D) before landing on the final page.
Example of a chain:
- URL A (http://site.com/page) → 301 →
- URL B (https://site.com/page) → 301 →
- URL C (https://www.site.com/page) → 301 →
- URL D (https://www.site.com/new-page) ✅ Final destination
And a redirect loop happens when the chain circles back on itself, for example URL A redirects to URL B, which redirects back to URL A. The browser or crawler eventually gives up, and the page becomes inaccessible.
Why Redirect Chains Hurt SEO
- Link equity dilution: each hop can leak a small amount of ranking signal.
- Crawl budget waste: Googlebot spends resources following hops instead of discovering new content.
- Slower page load: each redirect adds latency, hurting Core Web Vitals.
- Risk of abandonment: Google may stop following after 5 hops in a single crawl attempt.
- Broken user journeys when a chain eventually resolves to a 404 or a loop.
Step 1: Configure Screaming Frog Properly Before Crawling
Before hitting Start, take two minutes to configure the crawl. This is where most audits go wrong.
- Open Screaming Frog SEO Spider.
- Go to Configuration > Spider > Advanced and make sure the following are checked:
- Always Follow Redirects
- Always Follow Canonicals (optional but useful)
- Go to Configuration > Spider > Limits and increase Max Redirects to Follow to at least 10 (default is 5).
- Under Configuration > Spider > Crawl, make sure Internal Links, Canonicals, Redirects and External Links are all ticked.
Without these settings, Screaming Frog will stop at the first hop and you will completely miss the chain.
Step 2: Run the Crawl and Locate Redirected URLs
Enter your domain in the top bar and launch the crawl. Once it finishes, head to the Response Codes tab and filter by Redirection (3xx). This gives you every URL on your site that responds with a redirect status code.
Here is what the key status codes mean:
| Code | Type | SEO Impact |
|---|---|---|
| 301 | Permanent | Passes link equity, preferred for content moves |
| 302 | Temporary | Should not be used for permanent moves |
| 307 | Temporary (HTTP/1.1) | Same as 302, method preserved |
| 308 | Permanent (method preserved) | Modern alternative to 301 |
Step 3: Generate the Redirect Chains Report
This is the magic moment. Screaming Frog has a dedicated export made exactly for this.
- In the top menu, click Reports > Redirects > Redirect Chains.
- Save the CSV or XLSX file on your machine.
- Open it. You will see one row per chain with the following columns:
- Number of Redirects (the hop count)
- Redirect Loop (True/False)
- Address (initial URL)
- Final Address (where the chain ends)
- Each intermediate URL and its status code
Sort the file by Number of Redirects descending. Chains with 3+ hops go to the top of your fix list. Then filter Redirect Loop = True and treat those as emergencies, they are effectively broken pages.
How to Read the Report Fast
A typical actionable row looks like this:
- Address: /old-blog/seo-tips
- Redirect URL 1: /blog/seo-tips (301)
- Redirect URL 2: /blog/seo-tips/ (301)
- Redirect URL 3: /guides/seo-tips/ (301)
- Final Address: /guides/seo-tips/ (200)
Fix action: update the original rule so /old-blog/seo-tips redirects directly to /guides/seo-tips/ in a single 301 hop.
Step 4: Prioritize What to Fix First
You probably will not fix every chain today. Use this priority framework:
- Redirect loops: fix immediately, they are effectively 404s.
- Chains linked from internal pages: these waste crawl budget on every crawl. Use the Inlinks tab in Screaming Frog to find internal links pointing to redirected URLs, then update the anchor URLs directly in the CMS.
- Chains on high-authority URLs: cross-reference with Ahrefs or Google Search Console. Any chain sitting on a URL with backlinks is bleeding equity.
- Chains with 4+ hops: Google may abandon these.
- Mixed protocol/host chains: HTTP to HTTPS to www to non-www, very common after migrations, easy to flatten at the server level.
Step 5: Fix the Chains
There are two levels of fix, and both matter.
1. Update Internal Links (the clean fix)
Every internal link should point to the final destination URL directly. Use the Bulk Export > Response Codes > Redirection (3xx) Inlinks option in Screaming Frog. You get a full list of every internal link that points to a redirected URL, with the source page. Update those links in your CMS or theme templates.
2. Flatten the Server-Side Redirects
Even if you fix internal links, external backlinks and old bookmarks will still hit the chain. So you must also flatten the rules on the server:
- Apache (.htaccess): consolidate multiple RewriteRule lines so the origin URL points straight to the final one.
- Nginx: update rewrite or return 301 directives in the server block.
- WordPress: plugins like Redirection or Rank Math let you edit redirect targets directly. Look for entries where the target is itself a redirected URL and update them.
- Cloudflare / CDN: check page rules and bulk redirect lists, they often add an extra hop after HTTPS rewrites.
Step 6: Re-Crawl to Validate
After deploying fixes, run Screaming Frog again with the same configuration and re-generate the Redirect Chains report. Your goals:
- Zero redirect loops.
- Zero chains with 3+ hops.
- Every remaining redirect resolves in a single 301 hop.
- Zero internal links pointing to redirected URLs.
Bonus: Automate Redirect Chain Monitoring
Redirect chains reappear over time, especially on large sites with multiple editors. Set up a recurring audit:
- Schedule a monthly Screaming Frog crawl using the Scheduling feature.
- Auto-export the Redirect Chains report to a shared folder.
- Compare with the previous month to spot regressions.
- Combine with log file analysis to see which chains Googlebot is actually hitting.
Common Mistakes to Avoid
- Using 302 for permanent moves: always use 301 (or 308) when the change is permanent.
- Chaining language or country redirects: hreflang setups often stack multiple geo redirects. Serve the correct version in one hop.
- Redirecting to a canonicalized URL: if your redirect target has a canonical pointing elsewhere, you effectively created a soft chain.
- Ignoring trailing slash inconsistency: /page and /page/ redirecting to each other is the number one source of accidental chains.
FAQ
How many redirects in a chain are too many?
Google has stated it will follow up to about 10 hops in total but may give up after 5 in a single crawl attempt. Aim for zero chains, meaning every redirect resolves in exactly one hop.
Do redirect chains lose PageRank?
Google has said 301 redirects pass full PageRank, but in practice most SEOs observe small dilution over multiple hops, and John Mueller has confirmed that consolidating chains is good practice for crawl efficiency and signal clarity.
Is Screaming Frog free for redirect chain audits?
The free version crawls up to 500 URLs, which is enough for small sites. For larger sites or to unlock the Reports > Redirects > Redirect Chains export, you need the paid license.
What is the difference between a redirect chain and a redirect loop?
A chain eventually resolves to a final 200 URL through multiple hops. A loop never resolves because URLs redirect back to each other in a cycle, resulting in a broken user experience.
Can I detect redirect chains without Screaming Frog?
Yes, tools like Sitebulb, JetOctopus, Ahrefs Site Audit and httpstatus.io can identify chains. But Screaming Frog remains the most flexible and affordable option for deep, configurable crawls.
Final Thoughts
Fixing redirect chains is one of the highest ROI technical SEO tasks you can do this quarter. It is fast, measurable, and directly improves crawl efficiency, page speed, and link equity flow. Run a Screaming Frog audit today, generate the Redirect Chains report, and start flattening. Your rankings, your users, and Googlebot will thank you.
Need help auditing a large or migrated site? The team at Wicked SEO handles technical audits end to end, from crawl to deployment.