How to Check Redirect Chains Before a Website Migration

Redirects accumulate quietly. A site that has been live for several years, gone through a rebrand, shifted from HTTP to HTTPS, or merged with another domain almost certainly has redirect chains buried inside it — URLs that redirect to URLs that redirect to other URLs before landing on the final page. During a website migration, those chains compound. Old paths get new redirects stacked on top of existing ones, and what was a two-hop chain becomes a four-hop chain overnight.

The damage is technical and measurable. Link equity passed through each redirect hop is not fully preserved. Googlebot has a documented tendency to abandon crawl sequences when it encounters long chains, which means the destination page may go unindexed. Site speed suffers for real users too, because each additional HTTP request adds latency before the browser renders anything useful. The time to check redirect chains is before migration day — not after you notice rankings have dropped.

If you're looking for expert help in this area, explore how our technical SEO services can drive measurable results for your business.

What Redirect Chains Are and Why They Cost You Rankings

A redirect chain is a sequence of two or more redirects between the URL a user or crawler requests and the URL where they ultimately land. The simplest version looks like this:

• http://example.com/old-page → 301 → https://example.com/old-page → 301 → https://example.com/new-page

That is three URLs and two hops. A clean redirect would be a single 301 from the first URL directly to the final destination. Every intermediate URL in that sequence is dead weight.

Link Equity Dilution Across Hops

Google has confirmed that PageRank is passed through 301 redirects, but the signal is not perfectly preserved — some is lost at each hop. The exact percentage Google applies has never been disclosed, but the principle is consistent: the more hops between a backlink's source and your target page, the less authority that backlink contributes. For a page that has accumulated meaningful external links over years, a two- or three-hop chain before migration can materially reduce the ranking power those links provide after the migration goes live.

Crawl Budget Consequences

Google's crawl budget guidance acknowledges that Googlebot will stop following redirects after a certain number of hops in a single chain. Google's own documentation on redirects recommends avoiding chains longer than five hops and ideally keeping them to one. For large sites with thousands of redirected URLs, unresolved chains collectively consume crawl budget that could otherwise be spent discovering and re-indexing your new content.

How to Check Redirect Chains: Tools and Methods

There is no single tool that catches every type of redirect chain on every site. HTTP redirects, JavaScript-triggered redirects, and meta-refresh redirects each require different detection methods. The following are the most reliable approaches used in professional migration audits.

Screaming Frog SEO Spider

Screaming Frog is the standard tool for this task because it crawls the site the way a search engine does and surfaces redirect chains in a dedicated report. The workflow is straightforward:

1. Load your list of URLs (current live URLs, or the full redirect mapping file from your migration plan) into Screaming Frog using the List mode.
2. After the crawl, navigate to Reports → Redirects → Redirect Chains.
3. Export the report. Every URL showing more than one hop in its chain needs to be collapsed to a direct redirect before migration day.

Screaming Frog also lets you set the crawl to follow redirects and report the final destination, so you can verify that each source URL actually resolves to the intended page — not a redirect loop or a 404.

How to Check Redirect Chains on Ahrefs

To check redirect chains on Ahrefs, use the Site Audit module. Once you have run an audit of your domain, navigate to the Redirects section of the Issues report. Ahrefs flags redirect chains and redirect loops separately, which is useful because loops (A → B → A) require a different fix from simple chains. The advantage of Ahrefs here is that it cross-references your redirect chains against the site's backlink data, so you can immediately see which chained URLs have external links pointing at them — those are your highest-priority fixes, because they are the ones actively leaking link equity.

Sitebulb and Manual HTTP Header Checks

Sitebulb's visual crawl maps make redirect chains intuitive to spot, particularly for stakeholders who are not technical SEO specialists. For individual URLs, a manual check using curl -I -L [URL] in a terminal traces every hop in the redirect sequence, returning each status code and destination header in sequence. This is the fastest method for verifying a specific URL during migration testing without running a full crawl.

The Redirect Type Most Audits Miss: JavaScript and Meta-Refresh

Standard HTTP audits using Screaming Frog in its default configuration will not detect JavaScript-triggered redirects, because by default the crawler does not execute JavaScript. Meta-refresh redirects — where a page instructs the browser to navigate after a short delay using an HTML tag — are also missed by many tools.

This matters on sites built with React, Vue, or Angular frameworks, where routing is handled client-side, and on older sites that used meta-refresh as a workaround before server-side redirect rules were standard. Before a migration, you should:

• Enable JavaScript rendering in Screaming Frog (Configuration → Spider → Rendering → JavaScript) and run a second crawl specifically to surface JS-triggered chains.
• Audit your <meta http-equiv="refresh"> tags as a separate step — a simple search within your CMS or source code for http-equiv will surface them.
• Use Google Search Console's URL Inspection tool on high-priority pages to see how Googlebot actually renders and follows redirects for those specific URLs.

A JavaScript redirect that chains through an HTTP redirect is particularly problematic: the crawler sees a partial chain and may treat the JS hop as the final destination, misattributing indexation signals.

Building a Clean Redirect Map Before Migration

A redirect audit without a structured output document is an incomplete audit. The deliverable you need is a redirect map: a spreadsheet that records, for every redirected URL on the current site, the source URL, the current chain (every hop in sequence), and the correct single-destination URL it should resolve to directly.

Prioritising Which Chains to Fix First

Not all chains carry equal risk. Prioritise in this order:

Collapsing Chains to Single Hops

The fix for every redirect chain is the same: update the server-side redirect rule so the original source URL points directly to the final destination. Do not delete intermediate redirects unless you are certain no external source links to them — instead, update their destination to point directly to the final URL as well. This ensures that any crawler or user who arrives at any URL in the old chain lands correctly on a single hop rather than being passed through several.

In practice, this means editing your .htaccess file, Nginx configuration, or CDN redirect rules (Cloudflare, Fastly, and similar platforms all have redirect management interfaces). It is worth building the corrected redirect rules into a staging environment and running a post-staging crawl to confirm chains are resolved before you push to production.

Post-Migration Verification: What to Check in the First 48 Hours

Even a meticulously planned redirect audit can surface surprises after migration. Certain redirect conditions only emerge under production server configuration. In the first 48 hours after going live, run the following checks:

• Re-crawl the full redirect list in Screaming Frog List mode using your pre-migration redirect map as input. Confirm every source URL returns the correct status code and resolves to the intended destination in a single hop.
• Check Google Search Console for crawl errors. A sudden spike in redirect errors or 404s on previously redirected URLs indicates a misconfigured rule in the new environment.
• Monitor crawl rate in Search Console's Crawl Stats report. A drop in pages crawled per day after migration is an early signal that Googlebot is encountering redirect chains or loops and abandoning sequences.
• Verify backlink destinations using Ahrefs or a similar tool. Confirm that external links pointing to your highest-authority old URLs are now resolving to the correct new URLs in a single redirect hop.

FAQ

How many redirects in a chain is too many?

Google's guidance recommends keeping redirect chains to a single hop wherever possible and advises avoiding chains longer than five hops. In practice, any chain longer than two hops is worth collapsing before a migration, because the cumulative effect on crawl budget and link equity becomes measurable above that threshold. Two-hop chains that exist for a legitimate technical reason (such as an HTTP-to-HTTPS upgrade combined with a www-to-non-www canonicalisation) can be tolerated, but should still be collapsed to a single rule when infrastructure allows.

Do 302 temporary redirects pass link equity the same way 301s do?

Google has stated that it treats 301 and 302 redirects similarly for PageRank passing purposes in most cases. However, 302 redirects signal that a move is temporary, which can create indexation uncertainty: Googlebot may continue indexing the original URL rather than the destination, depending on how long the 302 has been in place. For migrations, all permanent moves should use 301 (or 308 for POST requests) to communicate finality clearly.

Is Ahrefs or Screaming Frog better for a redirect chain audit?

They serve complementary roles. Screaming Frog is superior for crawling the full site and producing a comprehensive map of every redirected URL and its hop sequence. Ahrefs adds the dimension of backlink data, letting you see which redirected URLs have external links and therefore which chains are actively affecting link equity. For a migration audit, use Screaming Frog to find and map all chains, then cross-reference the high-priority ones against Ahrefs to identify the URLs where fixing the chain will have the greatest ranking impact.

Can redirect chains directly cause post-migration ranking drops?

Yes, in several ways. First, if a chained redirect causes Googlebot to stop crawling before reaching the final destination, that page may lose its indexed status. Second, if the chain dilutes the link equity from high-authority backlinks, the destination page may rank below its potential. Third, if a chain introduces a redirect loop — where two or more URLs redirect to each other — the page becomes entirely unreachable and will drop from the index. All three scenarios are avoidable with a pre-migration audit.

What to Do This Week

If your migration is within the next 90 days, start with these specific steps:

1. Export your current redirect rules from your server or CMS. This is your baseline — a complete list of every redirect currently in place, regardless of whether it chains to another.
2. Run a Screaming Frog crawl in List mode using that export as input. Filter the results to show only URLs with more than one redirect hop. That filtered list is your audit backlog.
3. Cross-reference with Ahrefs backlink data. Pull the backlinks report for your domain and filter by target URL. Any chained URL that appears in that report is a Priority 1 fix.
4. Update your redirect rules on staging to collapse every chain to a direct single-hop redirect. Use curl -I -L to spot-check at least the top 20 by traffic or backlink count.
5. Schedule a post-launch crawl for 24 hours after migration goes live. Build it into the migration project plan now, before it gets deprioritised under launch-day pressure.

The sites that maintain rankings through migrations are not the ones that get lucky — they are the ones that ran the audit before the move, not after.

Related Reading

• What Are Common SEO Mistakes? — A broader look at the technical and strategic errors that most frequently undermine search performance.
• Why Does SEO Still Matter in 2026? — The case for sustained technical investment in search, even as AI-driven discovery grows.
• How Google's AI Overviews Work (And How to Appear in Them) — Understanding how Googlebot and AI systems interact with your site's structure and signals.
• What Is Topical Authority and How Do You Build It? — How content architecture and internal linking support the authority signals that redirects are meant to preserve.
• Content SEO: How to Create Content That Ranks, Converts and Gets Cited by AI — The full framework for aligning technical health with content strategy to drive measurable organic results.