Fixing internal redirect chains in Screaming Frog

Last Tuesday, a client’s dev team pushed a “minor” site migration that resulted in roughly four hundred internal links passing through two different redirect layers. By the time I ran the audit, the site was sluggish, and our primary category pages were seeing a drop in crawl frequency. Fixing internal redirect chains in Screaming Frog isn’t just about cleaning up a spreadsheet; it’s about making sure your site’s link equity reaches its target without losing steam along the way. Most people try to fix these one by one, which is a massive waste of time. If you’ve failed at this before, it’s likely because you were looking at the wrong reports or didn’t have a clear path for the update.

The mechanics of the crawl

When you run a standard crawl, Screaming Frog follows links until it hits a destination. If your link points to URL A, which redirects to URL B, which then redirects to URL C, you have a chain. The crawler sees this, but it’s inefficient. You need to configure your crawl settings to ensure you aren’t ignoring these intermediate steps.

Go to Configuration > Spider > Advanced and ensure “Always follow redirects” is checked. If this is off, your crawl will only show you that a page is a 301, but you won’t see the full breadcrumb trail leading to the eventual 200 OK. By default, many crawlers stop after the first hop to save memory. In an agency setting, I always set “Maximum Redirects” to at least 5. If you find a chain longer than 5, you have bigger systemic problems than just SEO—you have a broken CMS architecture.

Finding chains with the redirect report

Don’t waste time manually clicking through every 301 response code in the main view. Instead, use the dedicated reporting tools. Once the crawl is complete, head to the top menu bar under ‘Reports’ and look for ‘Redirects’.

The ‘Redirect Chains’ report is your primary target. It breaks down the entire sequence for you. If you don’t see any data here, you haven’t configured the spider to follow chains deep enough. Go back to the Spider configuration and check the “Maximum Redirects” setting; if it’s set to 1 or 2, you might be missing longer chains that are actively killing your internal link structure. I recommend running a fresh crawl with these settings specifically after any major content update or seasonal SKU rotation.

Identifying link sources via inlinks

Once you have the list of chains, you need to know where these links live. This is the part most people mess up by deleting the redirect before updating the source.

Click on a specific URL in your redirect report, then navigate to the ‘Inlinks’ tab at the bottom of the Screaming Frog interface. This shows you every page that contains a link to that specific redirecting URL. You are looking for the ‘Anchor Text’ column here. This is exactly what you need to provide to your dev team or to fix yourself via a search-and-replace plugin or database script.

The danger of fixing the wrong end

A common mistake is fixing the redirect on the server side before updating the internal links. If you change a 301 redirect to a 200 OK on the destination, you might “fix” the chain, but you’ve done nothing to clean up the actual link pointing to the old URL.

Always update the internal link to the final destination URL first. If you remove the redirect before the internal link is updated, you break the user experience and create 404s. The goal is to reach a state where your internal links point directly to the content intended for the user, removing the server as an intermediary.

Using bulk exports to coordinate

If your site has hundreds of these, don’t try to fix them through the UI. Use the ‘Bulk Export’ feature. Export your ‘Redirect Chains’ report to a CSV.

You can hand this CSV directly to a developer. It maps out the “from” and “to” logic perfectly. If you are doing this yourself using a tool like WP-CLI or a SQL query, you have all the mapping you need in this file. When handing this to a dev team, I typically include a column for “Link Location” (e.g., Header, Footer, Sidebar, Body Content) so they can prioritize which changes require a global template update versus a manual page-by-page edit.

Why most redirect chains persist

Most teams fail to clear chains because they view them as a “one-time” clean-up task rather than a maintenance process. When we discuss why most internal linking structure advice is outdated for agencies and freelancers, it’s usually because people aren’t accounting for the dynamic nature of CMS-generated links.

Every time a product category or a permalink structure changes, a new chain is born. If you aren’t auditing these on a monthly cadence, you’re just patching holes in a sinking ship. Treat redirect monitoring as a core component of your technical SEO roadmap, not an afterthought. You can also review what nobody tells you about orphan page fixing to understand how redirect chains often hide pages from the crawler entirely, making them orphans in the eyes of search engines.

Step-by-step resolution process

To manage this at scale, I follow this specific sequence to ensure nothing slips through the cracks:

1. Perform a full site crawl with “Always follow redirects” enabled in the Spider settings.
2. Navigate to the ‘Reports’ tab and export the ‘Redirect Chains’ report as a CSV.
3. Open the CSV in Excel or Google Sheets and use a filter to identify chains with more than one redirect hop.
4. For each chain, use the ‘Inlinks’ tab in Screaming Frog to find the source pages.
5. Update the source links to point directly to the destination URL documented in your export.
6. Run a scoped crawl on the affected source pages to confirm they return a 200 OK.
7. Remove or update the server-side redirect rule only after verifying that all internal references have been pointed to the destination.

Handling edge cases with loops

Sometimes you’ll find a loop (A goes to B, B goes to A). These are not chains; they are errors. Screaming Frog will flag these in the ‘Status’ column as a 301 or 302, but the ‘Redirect URL’ will point back to an earlier step in the crawl.

If you encounter these, you need to look at the server-level .htaccess or Nginx configuration. Often, this is caused by a trailing slash mismatch or a poorly written regex rule in the server configuration. Don’t try to fix these by changing the links—fix them by deleting the conflicting redirect rule. A loop usually indicates that your server is fighting with itself to decide what the “canonical” version of a URL is.

Prioritizing by link authority

Not all links are created equal. If you are struggling with a massive list of chains, prioritize the ones located on pages with the highest PageRank or internal traffic. You don’t need to stress as much about a link on a dusty, orphan page in a footer as you do about a link in your main navigation.

If you are curious about the mechanics of how these links pass value, it’s worth taking a moment to verify if a redirect link passes value. While 301s generally pass value, the loss of efficiency during the crawl process is measurable. I typically use the ‘Crawl Depth’ metric to identify pages that are getting pushed further away from the homepage due to these redirect inefficiencies.

The long-term fix: Internal link hygiene

The ultimate goal is to avoid creating redirects in the first place. Whenever you update a URL, implement the redirect, but then immediately update the internal links. If you need a refresher on best practices, what nobody tells you about internal linking structure is that static, direct links will always outperform dynamic redirection paths.

Fixing these chains is tedious, but it is the most effective way to ensure your site is readable and efficient. Once you clear the backlog, your crawl budget will stabilize and your pages will be indexed with the full authority they deserve. OptiLink helps automate the monitoring of these link structures so you don’t have to manually check for new chains every time a link is updated.

Fixing internal redirect chains is a fundamental part of maintaining a healthy site architecture that scales. If you follow these steps, you will stop wasting your crawl budget and start seeing more stable rankings. OptiLink tracks these internal link shifts automatically, letting you catch chains before they become a massive headache for your team.

Keep reading

Playbook

Broken link building, step by step: find, fix, and pitch

Broken link building works when your replacement does the dead link's job. Here is how to find dead links, verify them, match a fix, and pitch honestly.

Sofia Meyer October 9, 20262 min read

Playbook

Competitor backlink analysis that finds real opportunities

Competitor backlink analysis pays off when you sort rivals' links by how they were earned. Use the intersect, a repeatable-link test and a dated action list.

Sofia Meyer September 26, 20262 min read

Playbook

Digital PR: the most durable link building there is

Digital PR earns links from journalists through original data, timely news and expert commentary. Here's the campaign workflow and how to measure it honestly.

Sofia Meyer October 13, 20262 min read

Explainer

Dofollow vs nofollow in 2026: what still passes value

The link attributes changed, Google's treatment changed, and a lot of advice is out of date. Here's what dofollow, nofollow, sponsored and ugc actually do now.

The OptiLink Team October 10, 20262 min read