Shopify Plus Migration URL Redirects: Mapping and Verification

A Shopify Plus migration needs a URL map that connects each important old address to the correct new page. Prepare the rules before the domain moves, then verify the original addresses after launch. Shopify's migration guide describes this sequence. A saved redirect is only the configuration; acceptance also needs the actual response and the intended content.

This workflow uses Shopify's native Online Store redirects. The examples are hypothetical, and the instructions were checked against official documentation on October 11, 2026. They do not report a merchant-store test.

Build a map with an explicit decision for each old URL

Collect the old CMS URL export, sitemap, and URLs with visits or incoming links. Google's site-move guidance identifies these as useful inputs. Keep the full original address in your working sheet so the hostname, locale prefix, and any query parameters remain visible.

Give each row an owner and one decision: keep the same address, redirect to a relevant replacement, or retire the content without a replacement. Add the intended destination, the reason for that choice, and a place for the later verification result. An unresolved destination is a review item, not a rule ready for import.

For a hypothetical store keeping example.com, a mapping could be:

• Original address: https://example.com/legacy/canvas-bag.
• Shopify destination: /products/canvas-bag.
• Reader expectation: the same canvas bag, with its product information and buying options.
• Acceptance evidence: the original request redirects to that destination, whose final response is successful and whose content meets that expectation.

Open the proposed destination directly before creating the rule. A page with a similar title but the wrong product or language is a failed mapping. Avoid sending unrelated retired pages to the home page; Google warns that such redirects can be treated as soft 404 errors.

If the domain also changes, assign an owner to the old hostname's routing. A Shopify path rule does not demonstrate that a request to the old host reaches the system serving that rule. Keep domain routing and page mapping as separate checks.

Check whether the old path is eligible for a native redirect

Shopify's native rules require a broken source path on the Shopify store. Active pages, reserved paths such as /cart, and empty collection tag-filter routes are not eligible. Query-string behavior is limited; removing only a matching .html suffix is unsupported. Check the complete restrictions before approving the map.

Put excluded cases in a separate queue for routing review, with the original address and the relevant limitation. Resolve the route's ownership before choosing another implementation.

Do not remove a working product or collection merely to activate a redirect. Decide whether its URL should remain live as part of the content migration.

Treat each market or language address as a verification case. Where destinations differ by locale, Shopify supports individual subfolder rules. Record each observed destination rather than assuming one base rule proves every language route.

Save a rule from the approved mapping

Start with one eligible path and a destination you have already opened.

1. In the Shopify admin, open Content > Menus > View URL Redirects.
2. Choose Create URL redirect.
3. Enter the old path in Redirect from. For the hypothetical example, use /legacy/canvas-bag.
4. Enter /products/canvas-bag in Redirect to, then choose Save redirect.

These controls are documented in Shopify's migration instructions. For an external destination, supply its complete URL; an internal destination can use a relative path, as explained in the redirect guide.

Export the existing redirect list before bulk changes. For CSV uploads, use Shopify's current sample and import instructions. Keep owner, reason, and verification notes in your separate working sheet.

Check the resulting entries against the approved pairs. A completed import still leaves response verification outstanding. When the old domain has not moved yet, label checks on the Shopify destination as prelaunch checks; they do not establish what visitors currently receive at the old hostname.

Verify the original request and the final page

After launch, first enter an original URL in a browser, as Shopify's migration guide recommends. Then inspect the network sequence instead of relying only on the address bar.

In Chrome DevTools, open Network, enable Preserve log and Disable cache, and navigate to the full original address. Select the document requests and inspect Headers: record the requested URL, response status, and redirect destination. Chrome's Network reference documents these controls and the response-header view.

For the hypothetical same-domain pair above, your expected record is:

• The original document returns HTTP 301, with a Location pointing to the intended product.
• The final document returns HTTP 200 and shows the expected product and language.
• The sequence has no loop or unnecessary intermediate page.

For migrated URLs, Shopify's Plus launch checklist specifies 301 redirects. Google's redirect documentation explains the meaning of that status and the destination header. A real domain or HTTPS transition may add another hop: record each hop and its owner, and direct the page rule to the final content destination.

Write the result, test time, and evidence reference into the map. Repeat for important old URLs and the locale variants you actually used. Checking only the new destination misses whether the old entry point works.

Use the failed response to choose the next action

Keep failed rows open with a specific symptom and owner:

• The old page returns 200: check which storefront answered, then revisit the eligibility decision. The request may still reach the old host, or the Shopify source path may remain active.
• The old page returns 404 without a redirect: compare the exact requested path with the saved rule, then check excluded paths and spelling.
• The redirect reaches a 404: open the destination directly and correct the target or its publication state.
• The final page is 200 but wrong: review the product, content, or locale mapping. Successful transport does not make an unrelated destination acceptable.
• The sequence loops or chains through old rules: inspect the existing pairs and point each page rule at the intended final destination.
• Results differ between browsers after an edit: repeat without cached responses. Shopify's troubleshooting guidance explains redirect caching and recommends a fresh-device check.

Update your own internal links to the new destinations, and submit the current sitemap after launch. Continue reviewing missing-page reports alongside the URL map. Google's migration guidance recommends these follow-up actions and notes that search visibility can fluctuate. Passing redirect checks establishes routing and content acceptance; it does not promise unchanged rankings.