Redirect Chain
A redirect chain occurs when multiple redirects link sequentially — URL A redirects to URL B, which redirects to URL C — forcing users and search engine crawlers through several HTTP hops to reach the final destination.
Individual redirects are a normal part of managing a site. A single 301 redirect is clean and transmits link authority well. The problem starts when redirects stack. Every hop in a chain adds latency for users and forces Googlebot to make multiple requests to follow the trail. Google historically follows up to five hops — pages at the end of a long chain risk being skipped entirely on a given crawl pass.
The more significant SEO cost is link authority dilution. A single 301 passes most of a page's link equity; each additional hop introduces incremental loss. If high-authority backlinks point to URL A, and A redirects to B, which redirects to C, the equity arriving at C is lower than it would be with a direct redirect. At scale — especially after site migrations — this compounds into measurable ranking loss.
Redirect chains most commonly accumulate after sequential CMS migrations or URL restructures. A URL gets redirected during one migration, then that destination URL gets redirected again in the next. If the original chain is never cleaned up, it grows. The fix is straightforward: audit chains with Screaming Frog, then update the original source to point directly to the final destination, bypassing all intermediate hops.
Don't confuse redirect chains with redirect loops, where two URLs redirect to each other indefinitely. That's a different problem — crawler timeout rather than latency — but the same root cause: redirect management that treats each migration in isolation rather than auditing the cumulative state.
Each redirect hop adds page load latency — chains of three or more redirects are measurable in Core Web Vitals and page speed scores, both of which are page experience signals
Link equity dilutes across every hop — backlinks pointing at the original URL deliver less authority to the final destination than a single clean 301 would, which compounds into ranking loss at scale
Deep chains can exceed Googlebot's crawl hop limit — pages at the end of long chains risk being skipped entirely during a crawl pass, delaying or preventing indexing of content that should rank
Want to put this into practice?
Content Torque builds B2B content programs that apply every one of these principles. Book a free strategy call.
Book a free callExplore More Terms
Full glossary301 Redirect
A 301 redirect is a permanent HTTP redirect that tells browsers and search engines a URL has moved permanently — passing the SEO authority accumulated by the original URL to the new destination.
SEOCrawl Budget
Crawl budget is the number of pages Googlebot will crawl on your site within a given timeframe — determined by your server's capacity and how much Google values your content. For most B2B content sites it isn't a daily concern, but at scale it becomes critical.
SEOBroken Link
A broken link is a hyperlink pointing to a URL that returns a 4xx or 5xx error — typically a 404 Not Found — meaning the destination page no longer exists or the link was never correct.
SEOPillar Page
A pillar page is a comprehensive, long-form piece of content that covers a broad topic in depth and serves as the anchor for a topic cluster.
SEOKeyword Intent
Keyword intent (also called search intent) is the underlying goal a searcher has when they type a query — informational, navigational, commercial, or transactional.
SEOGEO (Generative Engine Optimization)
Generative Engine Optimization (GEO) is the practice of structuring content so it gets retrieved and cited by AI tools like ChatGPT, Perplexity, and Google AI Overviews.