A Shopify product redirect should take the exact old address to a useful, current destination. Before changing a product handle, save its existing URLs, decide what should replace them and verify the redirect after saving. Shopify's native URL redirects work from broken addresses; they do not override a product page that still loads.
These 11 checks cover renamed, merged and retired products on Shopify's Online Store. They also address the links that are easy to miss: older handles, collection-context paths, translated URLs and variant selections.
A product title edit or temporary stock shortage does not automatically require a URL change. Start with the product's future, then choose its URL behavior. For a custom Hydrogen storefront, routing needs a separate implementation review; Screpy's Hydrogen SEO checks cover that environment.
1. Choose the right action for the product change
Decide whether the product is staying, moving or disappearing before choosing a redirect target.
| Product change | URL decision to make |
|---|---|
| Only the title or description changes | Keep the existing handle unless there is a separate reason to change it |
| The same product gets a new handle | Map the old product URL to its new address |
| A product is temporarily unavailable | Consider keeping its useful page with accurate stock information |
| A product is permanently retired | Use a genuinely relevant replacement, or allow a proper not-found response when none exists |
Shopify's Liquid handle documentation says changing a resource title after creation does not update its handle. Renaming “Summer Mug” in the product title is therefore different from moving /products/summer-mug.
For retired goods, ask whether the destination answers the original shopper's need. A successor mug may fit; an unrelated homepage usually does not. A collection can be appropriate when it genuinely helps someone find the replacement range.
Google's URL-move guidance warns against sending many old URLs to one irrelevant destination, which may be treated as a soft 404. An intentional 404 for a vanished product without a replacement is not automatically a redirect failure.
2. Save every old product URL before editing
Record the current handle and the actual URLs people use before renaming, merging or deleting a product. Include historical redirect sources that already point to it.
Your inventory may contain several forms:
- The plain product path:
/products/old-mug. - A collection-context path:
/collections/gifts/products/old-mug. - A localized path with a translated handle.
- A shared link containing
?variant=and a real variant ID.
Find these in your existing redirect export, relevant search and analytics reports, internal links and important campaigns. Do not reconstruct every address by replacing a product name with hyphens.
Shopify's within filter reference shows how a theme can generate collection-context product URLs. Saving only the plain product path can miss a real link your store has used.
Keep the product identifier, old handle, intended destination, reason and owner with the map. Shopify explains that deleted products cannot be restored. Saving a URL list before deletion preserves information that a later product export may no longer contain; it does not make the deletion reversible.
3. Confirm the old path can trigger a native redirect
Shopify's URL redirect rules say a redirect works only when its source is broken. If the old path still loads a valid product page, a saved redirect does not take priority over that page.
This matters when you duplicate a product. Publishing the new copy does not free the original product's handle. The old page may still be active, so the redirect record can exist without forwarding visitors.
Check the old URL's response and the product's actual publication state. If the business intends to keep selling that original product, reconsider the redirect instead of deleting it to force the rule to activate. When content should be hidden, Shopify documents product Draft status or removal from all sales channels as ways to make its URL eligible.
Also plan for the product's return. The same help page says making hidden content visible again automatically deletes its redirect, and says this behavior applies to products. Recheck both the live page and redirect list after republishing or reusing an old handle. A previously working rule is not proof of its current state.
4. Verify the redirect after a handle change
In the product editor, open Search engine listing, select the edit control and inspect URL handle. Keep a copy of the old address before saving a change. If the editor offers a redirect option for that change, review its old and new paths and leave it selected when a permanent move is intended.
Then verify the resulting record. Do not assume every editing method, bulk operation or integration creates the same redirect automatically.
The current manual workflow is:
- Open Content > Menus > View URL Redirects.
- Search for the exact old product path.
- Inspect its destination.
- If the required mapping is absent, choose Create URL redirect and enter the old path in Redirect from.
- Enter the intended current destination in Redirect to, then select Save redirect.
Use a relative destination for a move within the primary domain and a full URL for an external destination, following Shopify's rules.
Finish by requesting the old URL. Finding the right row in the admin proves that a mapping was saved; it does not establish that the source is eligible, that the destination is available or that the customer reaches the expected product.
5. Check the destination as a real customer
Open the proposed destination directly, before relying on the old URL to reach it. Use the public storefront context for the intended market, without an administrator session that might show a preview.
Confirm that the page contains the expected product or replacement range. Check its title, relevant variant, availability and purchase path. A successful response containing a password screen, an error message or the wrong product is not a completed move.
For a product destination, verify that it is published to the intended storefront. An item existing in the catalog does not mean that customers can access it in every market.
Inspect the destination's canonical URL and indexing controls as well. A redirect can forward the customer correctly while the destination declares an obsolete canonical or carries an unintended noindex. A canonical tag is a separate signal; it does not forward visitors. Screpy's canonical tag guide explains that distinction.
Record the actual final destination, not just the text in the redirect form. If another redirect occurs there, resolve that path before accepting the product change.
6. Validate the product redirect map before importing
Export the existing redirect list before a batch change. Keep that baseline separate from your proposed additions, and check whether any source already has a destination that needs deliberate updating.
Use one source-to-destination mapping per row. This fictional two-column working example maps a renamed mug and a retired mug to useful destinations:
Redirect from,Redirect to
/products/old-blue-mug,/products/blue-mug
/products/retired-travel-mug,/collections/travel-mugs
Compare the headers with a fresh native redirect export or the sample offered in your Shopify admin before importing. Keep audit columns, notes and timestamps in a separate file. Review the import preview; uploading a file is not the final acceptance check.
Check source paths character by character, including their prefix and spelling. Shopify reserves paths such as /cart and the bare /products route. That restriction is different from an individual product path such as /products/old-blue-mug.
Also distinguish a collection-context product path from a collection tag-filter URL. Shopify explicitly says tag-filter paths such as /collections/shirts/red cannot be redirected, even when no products match the tag.
After importing, verify the affected records and test their URLs. Preserve unrelated existing mappings; a catalog cleanup is not a reason to delete the whole redirect list.
7. Point historical URLs at the final product
A product can accumulate several old handles. If it moved from mug-v1 to mug-v2 and now to blue-mug, check both historical sources.
| Historical source | Intended direct destination |
|---|---|
/products/mug-v1 |
/products/blue-mug |
/products/mug-v2 |
/products/blue-mug |
Pointing the first source at the second leaves a chain when the second forwards again. Search the existing redirect export for destinations matching the handle you are changing, not only for rows whose source matches it.
Google advises redirecting directly to the final destination where possible. Check for loops too, especially if a product is renamed back to a previously used handle. A rule that sends the restored product away from itself needs investigation.
Screpy's redirect chain guide covers tracing longer paths. For this catalog change, the acceptance test is simpler: every affected historical product URL reaches its intended current destination without an avoidable intermediate product handle.
8. Test each affected language and market
Build a small list of the old product URLs used in each affected market. Use their actual translated handles and domains; adding a language prefix to the English path may produce an address the store never used.
Test each old URL and confirm the final product, language and market. A redirect to an available English product is not necessarily the correct result for a French product link.
Shopify's current redirect help page contains conflicting subfolder guidance. Its limitations section says redirects do not automatically apply to all market subfolders, while a later example describes one base mapping carrying through to a market subfolder. It also allows individual subfolder redirects for different destinations.
Treat that conflict as a reason to verify the actual localized paths, rather than assume either universal inheritance or universal failure. Add an explicit mapping where it is needed and supported, then test again. Record an unavailable or untested market as such.
After changing localized destinations, review the affected alternate and canonical references. Screpy's Shopify hreflang checks cover the wider language relationship; this redirect check is complete only when each recorded old product URL reaches the intended localized destination.
9. Check variant and collection-context links
Test complete old URLs, including relevant query parameters. A redirect reaching the right product handle can still lose the shopper's selected size or color.
Shopify documents variant deep links in the form ?variant=[variant-id]. That ID identifies a variant; it is not a generic instruction meaning “choose the blue one.”
If you replace or duplicate a product, establish the new variant mapping from the catalog. Do not assume an old variant ID identifies the matching option on the replacement product. Check the visible selection, price and availability after following the old link.
Shopify also warns that query-string URLs might not behave as expected with native redirects. Do not promise that every parameter survives or that different query strings can always be managed as separate redirect rules.
For collection-context links, request the actual path captured before the change, such as /collections/gifts/products/old-mug. Verify its response independently of /products/old-mug. A working redirect for one does not prove the other was handled.
Keep the outcome specific: “old medium-blue link reaches the replacement with medium-blue selected” is stronger evidence than “the product page opened.” If native routing cannot preserve an important selection, record the limitation for the storefront implementer rather than silently accepting the default variant.
10. Read the HTTP response and final product body
Use a fresh HTTP request as well as a customer check. Shopify says URL redirects start working immediately, and warns that browsers can cache 301 redirects. An old browser result is therefore a reason to inspect the current response, not to recreate the rule repeatedly.
These read-only commands use an illustrative address. Replace it with a URL from your map; on Windows, use curl.exe if curl names a different command.
First, save the source response without following redirects:
curl --silent --show-error --max-time 30 --dump-header source.headers --output source.html 'https://example.com/products/old-blue-mug'
Read the status and Location header. Then capture the followed path and final body:
curl --silent --show-error --location --max-redirs 5 --max-time 30 --dump-header chain.headers --output destination.html --write-out 'final_url=%{url_effective}\nstatus=%{http_code}\nhops=%{num_redirects}\n' 'https://example.com/products/old-blue-mug'
The five-hop cap is a diagnostic stop, not a recommendation to build five redirects. Inspect every response in chain.headers and read the final product content. A permanent product move should produce the intended permanent redirect and a useful final page; Google distinguishes permanent and temporary redirects.
Keep a separate audit file. This is an uncompleted record, not sample test results:
source_url,expected_final_url,market,expected_variant,first_status,location,final_url,final_status,body_matches,checked_at_utc,result
https://example.com/products/old-blue-mug,https://example.com/products/blue-mug,US,default,pending,pending,pending,pending,pending,pending,pending
Close the row only after checking the actual response, destination body and relevant selection. An HTTP 200 alone does not establish the correct product or search visibility.
11. Update references and keep a recovery record
Replace old URLs in the places you control: menus, product descriptions, blog posts, theme settings, campaign destinations and product feeds. Review hard-coded handle references with the theme owner. A resource-linked menu item and a pasted text URL may behave differently after an edit, so check the actual public links.
Compare the new product's canonical, relevant language alternates and sitemap entry with the intended destination. These signals should support the move rather than continue advertising a retired address.
Keep the original redirect export, the approved product map and the completed response records together. Note what changed and who can reverse each part. Restoring a product, changing its handle back and restoring a redirect are different operations; recheck the public result after any reversal.
Google's site-move guidance recommends keeping redirects for as long as possible, generally at least a year, and notes that users may benefit from indefinite retention. Treat this as migration guidance, not a countdown after which a product redirect becomes safe to delete. Useful external links and bookmarks may still use it. Correct an irrelevant or broken rule when found; retention is not a reason to preserve a bad destination.
Later, compare available Search Console evidence with its last crawl date. A working current redirect and Google's processing of the change are separate observations, with no guaranteed ranking recovery date.
This checklist is based on Shopify and Google documentation checked on November 16, 2026, with illustrative maps and commands. It does not report tests on your store or an independent human review. Repeat the affected URL checks after subsequent handle, publication, market or variant changes.