If you have been running a Shopify store for more than a couple of years, there is a decent chance you are carrying redirect chains you don’t know about. They don’t throw an error. They don’t break checkout. The store looks fine. But somewhere in your URL redirects list, a request for an old product page is bouncing through two, three, or even five hops before it lands on the page that actually exists today.
Redirect chains are one of those technical SEO problems that never announce themselves. Nobody notices a 400-millisecond delay on a single page load. What you do notice, eventually, is that Google seems slower to index new pages, old rankings quietly fade on pages that were “fixed” months ago, and Search Console shows crawl stats that don’t quite make sense for a store your size.
This post explains what a redirect chain actually is, why Shopify stores build them up faster than most people expect, how they affect crawl budget and page speed, and a practical process for auditing and fixing them using Shopify’s own Online Store > Navigation > URL Redirects screen. We’ll also cover when a redirect chain is a five-minute fix and when it’s a sign of a deeper structural problem that needs specialist attention.
What a Redirect Chain Actually Is
A single redirect is simple: URL A no longer exists, so you send anyone (or anything) requesting it straight to URL B. That’s clean. One hop, one instruction, done.
A redirect chain happens when URL A redirects to URL B, but URL B also redirects, to URL C. Now anyone requesting A has to be bounced twice before reaching the live page. It sounds like a small thing until you consider how these chains actually form on a real store:
- A product’s URL changes when you restructure your URL handles (A → B)
- Six months later, that same product gets merged into a different collection structure and its URL changes again (B → C)
- A year after that, you migrate themes and update the URL format store-wide (C → D)
Nobody ever touches the original A → B redirect to update it. It just keeps sitting there, still pointing at B, which now redirects to C, which now redirects to D. A shopper (or Googlebot) requesting the original URL now makes three round trips before reaching live content. Add a fourth migration and you’ve got a four-hop chain. It’s not hypothetical, this is the normal, predictable byproduct of a store that has been trading for a few years and has been through the change events every growing Shopify store goes through.
A redirect loop is a more severe cousin of this problem, where the chain eventually points back to itself (A → B → A), which browsers and crawlers will simply fail to resolve. Loops are rarer than chains but do happen, usually after a rushed bulk redirect import.
Why Shopify Stores Accumulate Redirect Chains
Some platforms are more prone to this than others, and Shopify has a few specific patterns worth understanding.
Re-platforming and migrations. Moving to Shopify from WooCommerce, Magento, BigCommerce or another platform almost always changes the URL structure, different slug conventions, different collection paths, sometimes a different handle format entirely. The redirect map built during migration maps old URLs to new Shopify URLs. If the store later migrates again (Shopify to Shopify Plus, or a second re-platform), the original redirect map often gets layered underneath a new one rather than merged with it.
URL structure changes for SEO reasons. It’s common, and often correct, to tidy up product handles or collection paths as part of an SEO clean-up, shortening a clunky handle, removing keyword-stuffed slugs, standardising naming conventions across a catalogue. Each of these changes creates a new redirect. If it happens more than once to the same URL over the store’s life, you get a chain.
Theme changes. Some themes structure collection and filter URLs differently, particularly around faceted navigation. A theme change that alters how collection URLs are built can trigger a fresh batch of redirects layered on top of whatever redirects already existed from the previous theme.
App uninstalls. Apps that generate their own landing pages, bundle pages, or custom URL structures (subscription apps, bundle builders, some page builders) sometimes leave redirects behind when uninstalled, or the store owner adds redirects manually to route traffic away from now-dead app URLs, often pointing to a page that itself later gets redirected elsewhere.
Collection restructuring. Merging collections, splitting a single “Sale” collection into more specific ones, or reorganising navigation for a category expansion all tend to generate new redirects for URLs that, in many cases, were already the target of an earlier redirect.
None of these individual actions is a mistake. The problem is cumulative: each event is handled in isolation, without anyone checking whether the “old” URL being redirected from was already the destination of a previous redirect.
How Redirect Chains Slow Down Crawl Budget and Page Speed
Two separate but related costs come from redirect chains.
Page speed, for real visitors. Every redirect hop adds a full HTTP round trip before the browser gets to the final page, DNS resolution (if applicable), connection, request, response, then repeat for the next hop. On a fast connection this might only add 100-300 milliseconds per hop, which sounds trivial. But it compounds: a three-hop chain on a paid ad landing page, or a shared link from an old blog post, or an inbound backlink from another site, adds real, measurable delay before the visitor sees anything. That delay counts against Core Web Vitals metrics like Largest Contentful Paint, and it’s dead time a shopper is waiting with nothing on screen.
Crawl budget, for Googlebot. Google allocates a finite amount of crawling attention to every site, and larger or more frequently-updated Shopify catalogues get more of it, smaller ones get less. Every hop in a redirect chain is a separate URL fetch that Googlebot has to make before it reaches content worth indexing. Multiply a handful of hops across dozens or hundreds of legacy URLs, which is entirely realistic for a catalogue that’s been through two migrations and several collection restructures, and you’re asking Googlebot to spend real crawl budget resolving chains instead of finding and re-crawling your actual product and collection pages. For large catalogues this is one of the more common, and more overlooked, causes of slow indexing on new or updated products.
Google’s own guidance has been consistent on this: it will generally still follow a chain, but it recommends keeping chains as short as possible and ideally avoiding them altogether, because there’s a practical limit to how many hops it will follow before giving up on a URL entirely.
How Redirect Chains Confuse Google’s Ability to Pass Link Equity
This is the part that quietly costs stores rankings without anyone noticing why.
When Google processes a 301 redirect, it treats it as a signal that the destination page has effectively replaced the original, link equity (the ranking value built up by backlinks, internal links, and historical ranking signals pointing at that URL) is intended to consolidate at the new URL. That works cleanly across a single hop.
Across a chain, the signal gets diluted with each additional hop, and in some documented cases Google has simply stopped resolving a chain past a certain number of redirects, meaning the final destination page never receives the equity from the original URL at all. Practically, this shows up as: a product page that has genuine backlinks and historical rankings from an old URL, but after two or three re-platforms, that value is not fully reaching the current live URL. The page looks fine, the content is fine, but the accumulated authority behind it has partially evaporated somewhere in a chain nobody has looked at in years.
This is also why “it’s already redirecting somewhere” isn’t good enough as a fix. A redirect that resolves is not the same as a redirect that’s efficient. Both example.com.au/products/old-handle → new-handle → newer-handle → current-handle and example.com.au/products/old-handle → current-handle get the shopper to the same place. Only the second one preserves link equity cleanly and loads without the extra hops.
A Practical Method for Auditing and Fixing Redirect Chains in Shopify
Shopify’s built-in redirect tool lives at Online Store > Navigation > URL Redirects in the admin. It’s a flat list, Shopify doesn’t visualise chains for you, so you need a deliberate process to find them.
Here’s a workable checklist for a store that hasn’t audited redirects before:
- Export the full redirect list. From Online Store > Navigation > URL Redirects, use the export function to get every redirect as a CSV. For stores with a long history this can run into the hundreds or thousands of rows.
- Map “from” against “to.” In a spreadsheet, check every value in the “Redirects to” column against every value in the “Redirect from” column. Any match means you have a chain, the URL in the “to” column is itself being redirected somewhere else.
- Flag chains of two or more hops. Follow each match through to its final destination. Note how many hops are in the chain and what the true end URL is.
- Rewrite each chain to a single hop. Update the original “from” URL to point directly at the final live destination, and delete the intermediate redirect entries once you’ve confirmed nothing else depends on them.
- Spot-check with a redirect checker. Before and after fixing, run key URLs, especially ones with existing backlinks, through a redirect path checker (there are several free browser extensions and tools that show the full hop sequence) to confirm you’re down to one hop.
- Cross-reference against Google Search Console. Check the Page Indexing report and any “Page with redirect” entries to see which redirected URLs Google is actually still trying to crawl, and prioritise fixing chains on those first.
- Re-check after every future migration, theme change, or major collection restructure. This is the step almost everyone skips. A one-off clean-up will drift back into chains within a year or two if it isn’t repeated as a standing habit whenever the store goes through a URL-structure-changing event.
For a small store with a modest redirect list, this is genuinely a spreadsheet-and-an-afternoon job. For a catalogue with thousands of SKUs and several re-platforms in its history, it’s a more substantial project, but the method doesn’t change, just the scale.
When a Redirect Chain Needs More Than a Quick Fix
Manually flattening chains works well when the volume is manageable and the store’s history is reasonably well documented. It stops being a quick fix when:
- The redirect list runs into the thousands and multiple migrations have happened without anyone keeping a master map of old-to-new URLs
- Chains are tangled with loops, or multiple old URLs converge and diverge in ways that aren’t obvious from a flat CSV
- The store is about to go through another migration or theme change and needs the existing redirect structure cleaned and consolidated before a new layer gets added on top
- There are signs of lost rankings or slow indexing on pages you suspect are affected, and you need to diagnose whether redirect chains are actually the cause versus something else entirely (thin content, canonical issues, crawl blocks)
This is exactly the kind of structural technical SEO issue a proper Shopify technical SEO review is built to catch, auditing the full redirect map against crawl data and Search Console signals, rather than eyeballing a spreadsheet and hoping nothing was missed. It’s also worth flagging before any future re-platform: fixing chains as part of migration planning is considerably cheaper than untangling them a year after the fact.
FAQ
What’s the difference between a redirect and a redirect chain?
A single redirect sends a URL directly to its live destination in one hop. A redirect chain happens when that destination is itself another redirect, forcing the browser or crawler through two or more hops before reaching a real, live page.
How many redirects is too many for Shopify?
There’s no fixed number that applies to every store, but any chain of two or more hops is worth fixing. Google has a practical limit on how many redirect hops it will follow before it stops trying to resolve a URL, so even a handful of long chains can mean some pages never get proper credit passed through.
Can I fix redirect chains myself in Shopify admin?
Yes, for most stores. The Online Store > Navigation > URL Redirects screen lets you export, edit, and re-import redirects. The manual process is mapping “from” and “to” values against each other to find chains, then updating each original URL to point straight at the final destination.
Do redirect chains actually hurt rankings, or just crawl efficiency?
Both. Chains slow down crawling and waste crawl budget on larger catalogues, and they can dilute or block the transfer of link equity from an old URL to its current version, which is a ranking factor in its own right, not just a technical housekeeping issue.
What causes the most redirect chains on Shopify stores specifically?
Repeated events over a store’s lifetime that each change URL structure in isolation, re-platforming onto Shopify, a later migration to Shopify Plus, theme changes, collection restructuring, and app uninstalls that leave orphaned redirects behind. Each event is usually handled without checking whether the URLs involved were already part of an existing redirect.
Next Step
If you’re not sure whether your store is carrying redirect chains, or you suspect one is quietly costing you crawl budget and rankings, a Shopify SEO audit will map your redirect structure against real crawl and indexing data rather than guesswork. If you’d rather talk it through first, you can book a call with our team.
