When is a 301 redirect needed?
A 301 redirect tells a browser and Google that a page has permanently moved to a new address. It serves two purposes at once: keeping a visitor or an external link from landing on a 404 error, and passing the ranking equity the old URL had already built — links, age, position — over to the new URL.
Without a redirect, a visitor following an external link to the old page hits a 404, and Google keeps a dead URL in its index until it recrawls and removes it — a process that can take several weeks, during which the page keeps showing up in search results while leading nowhere.
It becomes necessary every time a URL stops existing: deleting a product or a collection, merging two pages, changing the slug of an existing page, or a broader store restructuring. One important nuance, often overlooked: Shopify's native tool can only redirect a broken URL. If the old address still shows a valid page, the redirect you created simply doesn't fire.
How to create a 301 redirect on Shopify
From the Shopify admin: Content → Menus → View URL Redirects → Create URL redirect. Two fields to fill in: Redirect from (the old broken URL) and Redirect to (the destination — a relative path like /collections/shirts to stay on your domain, a full URL to redirect off-site, or / to send visitors to the homepage). The redirect is active immediately after saving, with no propagation delay.
When you directly change the handle (the URL) of an existing page, product or collection, Shopify offers a checkbox, pre-checked, to automatically create the redirect from the old address to the new one — in that specific case you have nothing more to do.
For large volumes — a migration or a full restructuring — the admin supports exporting and importing redirects as CSV, with a downloadable template. A store can create up to 100,000 redirects (20 million on the Plus plan).
E-commerce use cases
Deleted product. Unlike a handle change, simply deleting a product or a collection creates no automatic redirect. It's up to you to create it manually, usually toward the parent collection or a replacement product — otherwise the URL returns a plain 404.
Merged collections. When two competing collections are merged into one — the textbook cannibalization case we cover in our guide on the topic — the deleted collection should be redirected to the one you keep, to transfer the accumulated ranking rather than lose it.
Migration or multi-market restructuring. A redirect created on your primary domain automatically applies to all existing market subfolders (for example /en-ca/): redirect /products/old to /collections/new, and the Canadian version redirects to its local equivalent too, with no separate redirect to create — unless you want a different destination per market.
Common mistakes
Most redirects that don't work produce no visible error message in the admin — the row appears created, but it simply has no effect. The following five cases cover most of the situations where that happens.
- Redirecting a still-active URL. If the source page still shows valid content, the redirect doesn't fire — the most frequent and most silent mistake: nothing signals the failure, the redirect just stays inactive.
- Chaining redirects. Redirecting A to B, then later B to C, needlessly slows the path and dilutes the signal sent to Google. Better to update the existing redirect to point straight to the final destination.
- Reserved, non-redirectable paths. Some paths can never be redirected natively:
/products,/collections,/collections/all,/cart,/apps, among others — as well as collection tag-filter URLs. - Confusing 301 and 302. Shopify's native tool offers only one type of redirect: permanent. There is no native temporary (302) redirect — a genuine need for a 302 requires a third-party app.
- Re-publishing a hidden page without a second thought. If a collection is hidden and then redirected, the redirect is automatically removed as soon as you make it visible again — logical, since it only works on a broken URL. If you hide it again later, the redirect must be recreated: it doesn't come back on its own.
In short
A well-placed 301 redirect protects the ranking equity built by a page that disappears. The most useful rule to remember is also the easiest to forget: it only works on a genuinely broken URL, never on a still-active page. For collections created in bulk — see our guide on creating collections in bulk — this redirect discipline matters more and more as the number of pages grows.