A redirect chain occurs when a URL redirects to a second URL, which then redirects to a third URL (or more) before reaching the final destination. Each additional hop in the chain dilutes link equity, slows page load time, and increases the risk of crawl errors.
Quick Answer
A redirect chain occurs when a URL redirects to a second URL, which then redirects to a third URL (or more) before reaching the final destination. Each additional hop in the chain dilutes link equity, slows page load time, and increases the risk of crawl errors.
Two-hop maximum — any redirect chain longer than 2 hops should be consolidated to a direct 301 to the final destination
Link equity loss — each redirect hop reduces PageRank passed to the destination; chains on high-authority pages have measurable ranking impact
Crawl budget waste — on large sites, hundreds of redirect chains can significantly reduce the number of pages Google crawls per day
Key Takeaways
Two-hop maximum — any redirect chain longer than 2 hops should be consolidated to a direct 301 to the final destination
Link equity loss — each redirect hop reduces PageRank passed to the destination; chains on high-authority pages have measurable ranking impact
Crawl budget waste — on large sites, hundreds of redirect chains can significantly reduce the number of pages Google crawls per day
How Redirect Chain Works
A redirect chain is a sequence of two or more redirects between an original URL and its final destination. For example: URL-A redirects to URL-B, which redirects to URL-C. Even if all redirects are 301 (permanent), each additional hop in the chain introduces latency (typically 100–300ms per redirect) and reduces the amount of PageRank passed to the destination page. Google's John Mueller has confirmed that PageRank is partially lost at each redirect hop, though the exact percentage is not publicly disclosed. Most SEO practitioners treat the loss as meaningful beyond 2 hops.
Why Redirect Chain Matters for B2B Marketing
Redirect chains accumulate over time through normal site operations: URL A redirects to B after a page rename, then B redirects to C after a site migration, then C redirects to D after a domain change. The result is a tangle of chained redirects that quietly erodes the site's link equity and crawl efficiency. For large sites, redirect chains affecting high-authority pages can represent a significant drag on overall domain performance — particularly if those pages have substantial external backlink profiles.
Redirect Chain: Best Practices & Strategic Application
The fix for redirect chains is straightforward: update each chain so that every hop points directly to the final destination URL. In the A→B→C example, URL-A should be updated to point directly to URL-C, and URL-B should also be updated to point directly to URL-C. This collapses the chain to a single-hop redirect for all historical inbound links and internal links. After fixing chains, run a Screaming Frog crawl to verify no chains remain, and check Google Search Console for crawl anomalies.
Agency Perspective: Redirect Chain in Practice
Agencies often discover redirect chains during technical audits and find chains 4–7 hops long on important product or service pages — particularly on sites that have undergone multiple migrations or rebrands. These chains are rarely intentional; they're the accumulated residue of decisions made years apart by different teams. MV3's technical audits always include a full redirect chain analysis using Screaming Frog's "Response Codes" report, prioritizing chains on pages with significant referring domains or organic traffic.
Frequently Asked Questions: Redirect Chain
A redirect chain occurs when a URL redirects to a second URL, which then redirects to a third URL (or more) before reaching the final destination. Each additional hop in the chain dilutes link equity, slows page load time, and increases the risk of crawl errors.
Yes, particularly on pages with significant external backlinks. Each hop in a chain reduces the PageRank passed to the destination and adds server response latency. For most sites, fixing redirect chains is a quick win — the technical fix is simple and the ranking impact can be measurable within 4–8 weeks of Googlebot re-crawling the affected URLs.
Screaming Frog SEO Spider is the standard tool — run a full crawl and filter the Response Codes report for redirect chains (chains of 2+ hops). Ahrefs' Site Audit also flags redirect chains in its crawl report. For large sites, focus first on chains affecting pages with the highest number of referring domains, as those represent the greatest link equity recovery opportunity.
A redirect chain eventually reaches a final destination (A→B→C→final URL). A redirect loop never resolves — URL-A redirects to URL-B, which redirects back to URL-A, creating an infinite cycle. Redirect loops cause 5xx errors in browsers and prevent Googlebot from crawling the affected URLs at all, making them a more severe issue than chains.
MV3 Marketing helps B2B companies apply these strategies to drive measurable pipeline growth. Our team executes technical seo audit for technology, SaaS, and professional services companies.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
