How to Bulk Create Shopify URL Redirects When You Change Product Handles

Every product in your Shopify store has a URL handle — the slug at the end of the URL that identifies the product page. When you change that handle, the old URL stops working. Unless you create a redirect, every external link pointing to that product — from Google, social media, email campaigns, affiliate sites — sends visitors to a 404 page. Here’s how Shopify handles redirects, where the gaps are, and how to manage them at scale.

What Happens When You Change a Shopify URL Handle

A Shopify product URL follows the pattern yourstore.com/products/your-handle. The handle is generated automatically from the product title when you first create the product, but you can change it at any time in the product editor or via the API.

When you change a handle, the old URL immediately returns a 404 error — unless a redirect exists. This has three consequences that compound over time:

• External links break instantly. Every link from Google search results, social media posts, email newsletters, QR codes on packaging, and affiliate sites now leads to a dead page. Visitors see a “page not found” error instead of your product.
• SEO equity is lost. Google has been building authority for the old URL based on backlinks, click-through rates, and indexing history. A 404 response tells Google the page no longer exists. That accumulated ranking equity doesn’t transfer to the new URL automatically — it evaporates.
• Internal links may break too. If you’ve linked to the product from blog posts, collection descriptions, or custom pages using hardcoded URLs rather than Liquid objects, those internal links also break.

A properly configured 301 redirect from the old handle to the new one solves all three problems. It sends visitors to the right page, tells Google to transfer ranking signals to the new URL, and does it transparently — no one even notices the change happened.

How Shopify’s Native Redirect Creation Works

Shopify does have automatic redirect creation — but only in one specific scenario. When you change a product’s URL handle using the product editor in the Shopify admin (the SEO section at the bottom of the product page), Shopify automatically creates a 301 redirect from the old handle to the new one.

This is a sensible default, and it works well for individual, one-off handle changes. The problem is that this auto-redirect behaviour is limited to the admin product editor. It does not apply when handles are changed through other methods:

• CSV imports — If you export your products, change handles in a spreadsheet, and reimport the CSV, Shopify updates the handles but creates no redirects. Every old URL breaks silently.
• The Shopify API — If you or a developer updates handles programmatically through the Admin API, no redirects are generated. You need to create them separately via the Redirect API.
• Third-party apps — Most apps that modify product data use the API under the hood. Unless the app specifically creates redirects as a separate step, handle changes made through apps won’t have redirects either.

This gap catches a lot of merchants off guard. They assume Shopify always handles redirects, make bulk changes via CSV or an app, and discover weeks later — often through a drop in organic traffic — that hundreds of product URLs are returning 404 errors.

The CSV Import Method for Bulk Redirects

If you need to create redirects after the fact, Shopify offers a CSV import tool specifically for URL redirects. You can access it at Online Store > Navigation > URL Redirects > Import.

The CSV format is simple. It requires two columns:

• Redirect from — the old path, starting with a forward slash (e.g., /products/old-handle)
• Redirect to — the new path (e.g., /products/new-handle)

Each row represents one redirect. You create the CSV in a spreadsheet, upload it, and Shopify processes the redirects in bulk.

While this method works, it has significant practical limitations:

• Manual CSV creation is tedious. You need to know both the old and new handle for every product. If you changed 200 handles via a CSV import, you need to reconstruct what the old handles were — Shopify doesn’t provide a before/after log.
• No validation. The import doesn’t check whether the “from” path actually existed or whether the “to” path is valid. Typos in either column create broken redirects that look correct in the admin but don’t work.
• No redirect chain detection. If you change a handle multiple times, you can end up with redirect chains (A → B → C). Each hop adds latency and dilutes SEO value. The CSV import doesn’t detect or resolve these chains.

Why Redirects Still Matter Even with Auto-Create

Even if you know about Shopify’s automatic redirect behaviour in the admin editor, there are many real-world scenarios where redirects get missed:

• CSV imports for data cleanup. When merchants clean up product data — standardising handle formats, removing special characters, fixing spacing issues — they often export to CSV, make bulk changes, and reimport. No redirects are created for any of those handle changes.
• API-driven changes from apps. SEO audit tools, product management apps, and migration tools frequently modify handles via the API. Unless the app explicitly creates redirects (most don’t), you’re left with broken URLs.
• Platform migrations. When migrating from another platform to Shopify, product URLs almost always change. The migration tool may import your products, but setting up redirects from the old URL structure to the new Shopify handles is a separate task that’s easy to overlook.
• Rebranding or restructuring. If you rename product lines, change your URL naming convention, or restructure your catalogue, you may need to update hundreds of handles at once. Doing this one-by-one in the admin to preserve auto-redirects is impractical at scale.

How AssetScope’s URL Handle Editor Handles Redirects

AssetScope’s URL Handle Editor was built with this exact problem in mind. When you use it to clean up messy handles — removing special characters, fixing double hyphens, stripping trailing hyphens, or standardising formatting — AssetScope automatically generates a 301 redirect from the old handle to the new one for every product you modify.

There’s no separate step. You don’t need to build a CSV, you don’t need to remember what the old handles were, and you don’t need to navigate to a different section of the admin to set up redirects after the fact. The redirect is created as part of the same operation that updates the handle.

This means you can clean up 500 product handles in a single operation and know that every old URL will continue to work — both for visitors and for search engines. The SEO equity built on the old URLs transfers seamlessly to the new ones.

When to Skip Redirects

Not every handle change requires a redirect. There are a few situations where creating redirects is unnecessary overhead:

• Brand new stores with no external links. If your store just launched and you haven’t shared any product URLs publicly, there are no external links to preserve. Fix your handles before you start marketing.
• Products that were never indexed by Google. If a product page was blocked by robots.txt, noindexed, or simply too new to have been crawled, Google hasn’t built any equity on that URL. A redirect adds no SEO value.
• Internal test products. Products created for testing that were never published to your online store don’t need redirects. No one outside your team has ever seen those URLs.

For everything else — any product that has been live, shared, or indexed — creating a redirect when you change the handle is a best practice that protects your traffic and your search rankings.