--- title: Redirect Chains: The Crawl Budget You Are Wasting on Nothing description: One hop is fine. Thousands of hops across a site is a tax you pay on every crawl. url: https://moxseo.com/redirect-chains-crawl-budget date_modified: 2026-07-29 author: Ashish Khan language: en_US --- A single redirect costs almost nothing. Thousands of them, encountered on every crawl, create a tax you pay on discovery forever. Redirect chains waste crawl budget, slow page access, and force search engines to spend resources on unnecessary hops. They are one of the few [technical SEO](/technical-seo-guide) problems where the fix is genuinely simple, but continued neglect can become expensive. ## What a chain actually is A chain is more than one hop between the URL requested and the URL served. Request A, get sent to B, which sends you to C, which finally returns the page. Each hop is a separate request. Each costs time for the visitor and a fetch for the crawler. Google follows a limited number of hops before giving up entirely. Chains accumulate quietly. A site migrates HTTP to HTTPS, later adds trailing slashes, later restructures a section. Each change adds a rule, and rules layer rather than replace. When we consolidated eleven cannibalising posts on this site, the redirects themselves took minutes. Repointing the internal links so nothing routed through them took considerably longer, and it is the step that actually matters — 33 links across 32 pages had to be rewritten to reference the destination directly. ## Where the cost actually lands Not usually in rankings for a single page. The cost is spread and therefore easy to ignore. - **Crawl budget** spent on hops rather than pages, which matters most on large sites - **Page speed**, since every hop is a full round trip before anything renders - **Signal dilution** across long chains, though modern handling is better than it was - **Broken loops**, where a chain eventually points back at itself and the page becomes unreachable ## Find them, then fix the source Our [on-page audit tool](https://moxseo.com/tools/on-page-audit/) follows up to five hops and lists each one, so you can see the full path rather than just the destination. The fix is always the same: update the link to point at the final URL. Not the redirect rule — the link itself. Rewriting internal links is the part most people skip, and it is the part that matters. A redirect exists to catch external links and old bookmarks. Your own site should never need it. ## Which Redirects to Keep ![Redirect cleanup showing how to keep useful redirects, flatten chains and update internal links to final URLs.](https://moxseo.com/wp-content/uploads/2026/08/fix-redirect-chains-and-update-internal-links-1024x576.webp)Image Source: AI-generated visual by MoxSEO Do not remove old redirects simply to make a redirect report look cleaner. An old URL may still receive visitors through backlinks, saved bookmarks, email campaigns, social posts, downloadable documents, or previously indexed search results. If the redirect is deleted while those references still exist, the old URL will return a 404 error, creating a poor user experience and potentially wasting the authority earned through external links. The better solution is to flatten the redirect path. If URL A redirects to URL B and URL B redirects to URL C, update the rule for URL A so that it points directly to URL C. The redirect from B to C can remain for users and crawlers that request B directly, but anyone requesting A reaches the final destination in a single hop. This preserves the value of both old URLs without maintaining an unnecessary chain. You should also update every internal link that still points to A or B so it references C directly. Redirect rules are safety nets for outdated external references; they should not be part of your website’s normal navigation. A comprehensive [SEO audit](https://moxseo.com/services/seo/) can identify redirect chains hidden within content links, menus, breadcrumbs, canonical tags, hreflang annotations, and XML sitemaps. Permanent redirects are inexpensive to retain but potentially costly to remove too early. Keep redirects that continue to serve a valid purpose, flatten any chains they create, and correct the internal links that trigger them. Consider removing a redirect only after confirming that the old URL no longer receives meaningful traffic, has no valuable backlinks, and is not referenced by important external sources. ## Finding chains across a whole site Checking one URL tells you about one URL. The pattern is what matters, and there are three places it usually hides. - **Internal links in content** — old URLs written into posts years ago and never updated - **Navigation and footers** — a single stale menu link multiplied across every page - **Sitemaps** — listing URLs that redirect, which asks Google to crawl a hop The navigation case is the highest-leverage fix on most sites. One link in a menu that appears on 500 pages is 500 redirect hops per crawl, fixed by editing one thing. ## Redirect types, and when each is right The status code carries meaning. Using the wrong one is a common and quietly expensive mistake. - **301** — permanent. The correct default for a page that has moved for good. - **302** — temporary. Signals that the original will return, so consolidation is treated differently. - **307** — temporary, method-preserving. Rarely relevant to content pages. - **Meta refresh** — not a redirect in any useful sense. Avoid it. - **JavaScript redirect** — works, but only after rendering. Slower and less reliable. A 302 left in place for years is one of the more common findings on older sites. It usually started as a genuine temporary move and nobody went back. ## The migration checklist that prevents this Chains are overwhelmingly created during migrations, and almost entirely preventable with one discipline: map every URL before launch, not after. - Export every indexable URL from the current site before anything changes - Map each to its destination on the new structure, one to one where possible - Point every rule at the final destination, never at another redirect - Update internal links, navigation and sitemaps to the new URLs directly - Test the full map before go-live, not after traffic drops When we consolidated eleven posts on this site, that last step is what caught a rule pointing at a URL which itself redirected. Testing before launch turned a live problem into a five-minute correction. ## Stop Wasting Crawl Budget on Redirect Chains Redirect chains may appear harmless individually, but across a large website they can waste crawl resources, slow page access, and delay the discovery of important URLs. MoxSEO can review your redirect paths, internal links, navigation, canonicals, and XML sitemaps to identify unnecessary hops and redirect loops. You can [request a free technical SEO audit](https://moxseo.com/get-free-quote/) to uncover redirect chains and other crawlability issues across your website. If you are planning a migration or need a safe redirect-cleanup strategy, [schedule an SEO consultation](https://moxseo.com/schedule-consultation/) for recommendations based on your current URL structure. ## Sources and further reading - [Redirects and Google Search](https://developers.google.com/search/docs/crawling-indexing/301-redirects) - [Crawl budget management for large sites](https://developers.google.com/search/docs/crawling-indexing/large-site-managing-crawl-budget) ## Frequently asked questions ### How many redirects will Google follow? Around five hops in a single chain, though it may stop consolidating signals sooner. One hop is the sensible target. ### Do 301 and 302 differ for chains? A 302 signals a temporary move and consolidates differently. Chains of either are worth flattening; use 301 for permanent moves. ### Should I ever remove an old redirect? Only when you are confident nothing external still points at the old URL, and even then the rule costs almost nothing to keep. ### Do redirect chains hurt page speed? Yes. Each hop is a full round trip before rendering begins, which is most noticeable on mobile connections.