Weekly ecommerce tips, deals & news.
A redirect chain happens when a URL redirects to another URL that redirects again, before reaching the final page. A shopper or search crawler asks for page A, gets sent to B, then to C. Each extra hop adds a delay and one more place for the trip to fail.
A redirect chain works by stacking redirects that were each added for a good reason at a different time. Each rule points one old address at a newer one. Nobody goes back to update the older rules, so a visitor ends up following all of them in a row.
A redirect is like a forwarding note taped to an old front door. It tells visitors where you moved. A redirect chain is what happens when you move three times and leave a note at every old house.
On a WooCommerce store, the hops usually come from ordinary changes like these:
None of these rules is wrong on its own. The real problem, however, is the order they fire in. For example, an old http, non-www product link might hit the HTTPS rule first. Then it hits the www rule and the slug rule.
Each hop in a redirect chain is a full round trip between the browser and your server. Google’s Lighthouse tool fails a page with 2 or more redirects. It warns that each extra trip can delay loading by hundreds of milliseconds.
On top of that, crawlers pay a price. On a large catalog, every wasted hop spends part of your crawl budget on detours. Worse, Google’s Search Console lists a redirect error when a chain is too long. When that happens, the final page may never get indexed.
A redirect chain can also hide inside a product feed. Each product in a feed carries a link to its landing page. If that link still points at an old address, every ad click starts with a detour.
Google’s own product link requirements ask sellers to use as few redirects as possible. Plus, they ask that every redirect stay on the same verified domain. In Google Merchant Center, a link that bounces to the wrong page can trigger a landing page error.
AdTribes’ guide to Google Shopping feed errors names a changed permalink structure as a common cause. Its advice is simple. If you change your WooCommerce permalink structure, regenerate your feed immediately afterward.
Finding a redirect chain starts with tracing a few old URLs by hand. For example, your browser’s developer tools show every hop in the Network tab. A site crawler can then check your whole store at once and list each chain.
Flattening the chain means rewriting the rules, not deleting them. First, edit each old rule so it points at the final URL. Next, update your internal links, sitemap, and feed to use the final address. Then trace the old URLs again to confirm each one takes a single hop.
Also test old links from places you can’t edit. Ads, past emails, social posts, and backlinks on other sites all keep the original URL. Since those links never change, the redirect rule itself has to do the work.
The numbers on redirect chains come from the standards and the crawlers themselves, not from store surveys. By default, Google’s crawlers follow up to 10 redirect hops. Past that point, the page lands in the redirect error bucket.
Browsers, by contrast, set their own limits. The HTTP standard notes that an earlier version recommended a maximum of 5 redirections. It also warns that some clients might still use a fixed limit like that.
Speed is where shoppers feel it. Google’s web.dev guidance says most sites should aim for a server response under 0.8 seconds. Redirect time counts toward that total. Meanwhile, Deloitte found a 0.1-second mobile speed gain lifted retail conversions by 8.4%.
Keep in mind what these numbers don’t settle. No independent study measures how common chains are on WooCommerce stores. Still, the limits show why a short chain is safe and a long one is not.
A redirect chain in practice usually shows up as slow ad landings and a few pages that never get indexed. Here’s a hypothetical example. Imagine a small homeware store called Juniper & Clay that sells handmade mugs.
Juniper & Clay launched years ago on a plain http address without www. Later, the owner added HTTPS and moved to the www version of the domain. Then she renamed 40 products to add color names to their slugs.
Each change got its own redirect rule. However, her product feed and many blog posts still used the original http links. So an old link to the blue mug now took 3 hops before the page loaded.
As a result, shopping ad clicks landed noticeably slower than clicks from the store’s own menu. On a phone with a weak signal, the owner could count the pause. In addition, several renamed products showed landing page warnings in Merchant Center.
Meanwhile, Search Console added a handful of redirect errors. Two old category URLs had picked up a fourth hop through a leftover rule from a theme change. Those category pages stopped appearing in search.
First, the owner rewrote every old rule to point straight at the final https, www address. Next, she regenerated her product feed so each link used the current product URL. Then she updated the old blog links, since internal links should never need a redirect at all.
Within a few weeks, every old link resolved in one hop. The landing page warnings cleared after she followed the usual steps for fixing disapproved products. Finally, she added a checklist step: after any URL change, trace the old links and refresh the feed.
A redirect chain eventually reaches a real page, while a redirect loop never does. Both come from stacked rules, but they fail in different ways.
| What you’re comparing | Redirect Chain | Redirect Loop |
|---|---|---|
| Where it ends | On the final page, after extra hops | Nowhere, the rules point back at each other |
| What visitors see | A slower page that still loads | A browser error about too many redirects |
| How urgent it is | Fix soon, it costs speed and crawling | Fix now, the page is unreachable |
| Usual fix | Point old rules at the final URL | Find and remove the rule that circles back |
A redirect loop is the emergency, because nobody can reach the page. A redirect chain is the slow leak that gets worse with every site change. In practice, fixing chains often prevents loops, since cleaner rules leave fewer ways to circle back.
More than one redirect is already too many for a page you control. For example, Lighthouse flags a page with 2 or more redirects as a speed problem. Google’s crawlers stop following a chain after 10 hops, so aim for a single hop every time.
Redirect chains are not a penalty, but they can hurt SEO in practical ways. They slow pages down and waste crawling on detours. If a chain grows too long, Google reports a redirect error and may not index the final page.
To fix a redirect chain in WooCommerce, edit each old redirect rule so it points at the final URL. Then update internal links, menus, and your sitemap to the final address. Finally, regenerate your product feed so ad links skip the detour.
A redirect chain matters because it taxes every visit that starts from an old link, including paid ad clicks. It grows a little with each site change, so it rarely gets noticed. Keeping every redirect to one hop protects your speed, your crawling, and your ad spend.
Copyright © StoreOwnerTips.com. All Rights Reserved.
