November 20, 2026 · 5 min read

Why Your Shopify URL Redirect Does Nothing When the Old Page Is Live

A Shopify URL redirect cannot take over a live page. Learn how to clear the old path, create the redirect, and verify the response.

Why Your Shopify URL Redirect Does Nothing When the Old Page Is Live

A Shopify URL redirect will not take effect while its source URL still loads a valid page. To make it work, first remove that page from the old path, then create the redirect and verify that a request to the old URL returns a redirect response rather than the original page. A saved redirect record alone does not prove that visitors will be redirected.

Key takeaways

  • Shopify's redirect rule applies to broken source URLs, not live pages you want to override.
  • Free the old path by changing a handle, hiding the resource from the Online Store, or deleting it when appropriate.
  • Test the HTTP response at the source URL, not just the redirect entry in admin.
  • In the 2026-10 Admin GraphQL API, urlRedirectCreate can save a rule, but storefront behavior still needs a separate check.

Why the redirect can exist but do nothing

Shopify's URL redirect documentation is explicit: redirects work from broken URLs. If /products/old-jacket still serves a product, that product wins. Adding a rule from /products/old-jacket to /products/new-jacket does not turn the live product page into a 301.

That distinction matters during catalog cleanup. An out-of-stock product can still have a valid page. So can a product you have removed from a collection. Neither action necessarily frees its product URL. Check the source path on the published storefront before changing anything; an admin preview is not the same test.

ApproachWhen it fitsWhat happens to the old path
Change the resource handleThe same product or page is moving to a new URLThe old handle becomes available for a redirect
Hide the collection or unpublish the product from the Online StoreThe resource must remain in admin but its storefront page should go awayThe old URL can return 404 and become redirect-eligible
Delete the resourceThe resource is genuinely obsoleteIts old URL can be redirected, but deletion is harder to undo
Keep the page liveThe old page still has a useful purposeA Shopify URL redirect cannot replace that page

Shopify also documents a less obvious consequence: if you hide a collection, redirect its old path, and later make that collection visible again, Shopify automatically deletes the redirect. The same visibility principle applies to products. Treat a temporary redirect as part of the publishing workflow, not a permanent rule you can forget about. Shopify's visibility example describes this behavior directly.

The workflow that actually clears the path

I use this order because it separates a path conflict from a typo or a cached 301:

  1. Record the exact source and target. Include /products/, /collections/, or /pages/. Check the current handle in admin rather than deriving it from a title.
  2. Choose what happens to the resource. For a rename, change its handle and enable the option to create a redirect from the old URL. For a discontinued product that must remain in admin, set it to Draft or remove its Online Store availability. For a seasonal collection, hide its Online Store visibility. Do not delete a resource merely to make a redirect pass.
  3. Check the old URL before adding a manual rule. It should now return a 404 unless Shopify already created a redirect when you changed the handle. If it still returns a valid page, find the remaining published resource or route occupying that path.
  4. Create or inspect the rule. In admin, go to Content > Menus > URL redirects. Use the old path as Redirect from and the intended destination as Redirect to. If the handle change created a rule automatically, check it before adding another.
  5. Test the response and destination. Confirm that the old URL redirects to a working, relevant page. Update internal links to point directly to the destination so they do not depend on the redirect.

Changing a handle is often the cleanest solution when the content itself is moving. The 2026-10 productUpdate input exposes redirectNewHandle: when you provide a new handle and set that field to true, Shopify creates the old-to-new redirect automatically. This is different from trying to redirect away from a product while leaving that product at its original handle.

Verify the storefront, not just the admin record

Run these requests against the public domain, with no admin preview parameters:

curl -sS -o /dev/null -D - https://example.com/products/old-jacket
curl -sS -L -o /dev/null -w 'final=%{url_effective} redirects=%{num_redirects} status=%{http_code}\n' https://example.com/products/old-jacket

The first command exposes the initial status and Location header. The second follows redirects and checks where a visitor ends up. A 200 for the old product in the first response means you have not cleared that live path. A 404 means the path is free but a working redirect has not been observed. A 301 with the intended Location, followed by a successful final page, is the expected result for a working Shopify redirect. If results differ between a fresh request and your browser, account for cached 301 responses; Shopify notes that browsers and search engines can retain them.

For app-driven changes, the 2026-10 urlRedirectCreate mutation requires write_online_store_navigation. Inspect both the returned urlRedirect and userErrors. You can query saved rules through urlRedirects, which supports a path search filter. Neither query proves that the public URL redirects. Follow it with the HTTP test above.

Before blaming a live page, rule out paths Shopify will not redirect. Its documentation excludes fixed paths such as /products and /collections/all, and reserved prefixes including /cart, /apps, and /orders. Collection tag-filter URLs can also remain valid paths even when a tag has no matching products. Query strings are another source of misleading tests, so start with the plain path and add parameters only after that works. These restrictions and examples are listed in Shopify's redirect guidance.

Check markets before closing the ticket

As documented on November 20, 2026, Shopify says a root-path redirect normally applies across language or market subfolders, preserving the relevant subfolder. A redirect from /products/old-jacket can therefore affect a corresponding /en-ca/products/old-jacket URL. But a different destination for a specific locale needs its own rule; redirects do not automatically translate one market's destination into another market's content. Test the actual domain and subfolder your customers use, especially if market-specific pages have different availability. See Shopify's subfolder redirect examples.

The next technical step is simple: request the old URL without following redirects. Until that response stops serving the live page, editing the redirect rule will not solve the underlying problem.

If you need this built rather than doing it in house, Lintel, the studio I run, takes on Shopify performance and technical SEO projects like this.

shopifyurl redirectsshopify seographqlstorefront debugging

Frequently asked questions

Why is my Shopify URL redirect saved but not working?

The source URL may still load a valid page. Shopify redirects work from broken URLs, so clear the old path and test its public HTTP response.

Do I have to delete a product to redirect its URL?

No. You can change its handle or make the product unavailable on the Online Store, then redirect the old path if needed. Choose based on whether the product should remain available in admin or other channels.

What happens if I make a hidden collection visible again?

Shopify says it automatically deletes the redirect from that collection's path when the collection becomes visible again. If you hide it later, you will need to recreate the redirect.

Seven years of Shopify, on one page.

Roles, projects, stack and certifications are on the resume.

Resume Download PDF LinkedIn