Ecommerce Migration: Build a Redirect Map You Can Verify

By Dave TanguayPublished Updated Editorial draft

Quick Answer

Plan redirects by inventorying the old URLs, identifying equivalent destinations, and reviewing every proposed match. AI can suggest candidates, but a person must confirm the page’s meaning and the actual destination. Test redirects, internal links, canonicals, and important customer tasks before and after migration. URL mapping is one part of the wider platform move.

A migration spreadsheet can look complete while sending a useful buying guide to an unrelated collection. A reliable map records why each destination fits, who approved it, and what happened when the redirect was tested.

Inventory the site before matching URLs

Collect URLs from the current site, XML sitemaps, internal links, and available search and analytics evidence. Where available and authorized, include valuable incoming-link information. A crawl alone can miss an orphaned page or a URL people still visit through an old link.

Record the current status, canonical, page title, content purpose, and relevant identifiers. For ecommerce, distinguish products, variants where applicable, collections or categories, articles, downloads, and account-related routes. Keep source data and the date of collection with the inventory.

Preserve an established URL when the new platform and content decision allow it. A new visual design does not require a new address for every page.

Build a map around equivalent content

Start with exact identifiers and clear relationships. A product’s SKU or a known article migration can be a stronger clue than a similar title. Then review the content and destination in context.

Useful redirect-map fields
Field Why it matters
Old URL and page purpose Shows what the visitor expected to find.
Proposed destination Identifies the final public URL, not only a staging address.
Match evidence Records identifiers, content equivalence, and any important differences.
Decision and reviewer Distinguishes approved matches, preserved URLs, and unresolved cases.
Test result Records the response, final destination, and whether the destination serves the intended content.

Google’s site-move guidance covers URL mapping, permanent redirects, and related migration checks. Avoid redirecting many unrelated pages to the homepage. When content has no suitable replacement, make an explicit retirement decision and use the appropriate response rather than inventing a match.

Use AI suggestions as a review queue

An AI tool can help compare titles, descriptions, or other approved content and suggest possible destinations. Treat those suggestions as candidates. The output may overlook a changed product, confuse two similarly named services, or propose a URL that does not exist.

Give reviewers the old page purpose and candidate evidence, not just a confidence score. Check every proposed mapping. Prioritize important pages and unusual cases, but do not treat a high score as approval for the rest.

As an illustrative example, a discontinued “travel mug lid” could be matched to a current “travel mug” because the words are similar. The product is different. The business must decide whether a compatible replacement exists or whether the original URL needs a useful unavailable-product page or another documented treatment.

Use tools appropriate to the information being processed. Do not upload customer records, private analytics exports, credentials, or confidential material without an approved reason and handling arrangement.

Check how the destination platform handles redirects

The map must fit the platform’s actual routing. For Shopify, the official redirect documentation describes supported redirects and restrictions. Check these before assuming every path or still-active page can be overridden with a redirect entry.

Confirm who will implement the map and how it will be reviewed before activation. Keep the intended old domain, protocol, paths, and query-string behavior visible in testing. Update internal links to the new final destinations where appropriate, rather than relying on a redirect for every visit.

Preserve more than URLs during a platform move

Redirects help people reach content. They do not transfer product data, customer access, subscriptions, order history, inventory, or integrations. Record which information can move, what requires another method, and what cannot be carried over in the same form.

  • Catalog: Products, options, images, identifiers, collection relationships, and availability.
  • Operations: Payment, shipping, inventory, fulfillment, notifications, and refund workflows.
  • Content: Service pages, articles, downloads, metadata, and useful internal links.
  • Accounts and records: Supported customer migration, permissions, exports, and business-owned access.
  • Measurement: Approved analytics configuration and a record of the change date.

The ecommerce planning guide helps define operating requirements, while the accounting data handoff guide covers records that need coordination with the business’s accountant.

Verify the map before and after launch

Test the approved map for loops, unnecessary chains, missing destinations, and incorrect content. Review canonical URLs, navigation, internal links, XML sitemaps, and any temporary search restrictions used in development.

After the move, verify the actual public URLs and repeat essential inquiry or purchase tasks. Monitor search reports, server responses, and reported problems over time. Search visibility can fluctuate during a move; a redirect map cannot guarantee that every ranking or visit will be preserved.

Keep a dated change record, a recovery plan, and owners for unresolved issues. The website project-stages guide explains how deliverables and review points can be coordinated.

Key Takeaways

  • Inventory old URLs and preserve useful established addresses where possible.
  • Map by meaning and verified identifiers, with a human decision for every candidate.
  • Check platform restrictions and test final public destinations.
  • Plan data, operational workflows, measurement, and after-launch review alongside redirects.

Frequently Asked Questions

Can AI approve a redirect map automatically?

It can suggest matches, but the business meaning and actual destination still need review. A similarity score does not establish that a replacement product, service, or article answers the original visitor’s need.

Should every old URL redirect to the homepage?

No. Use a relevant equivalent destination when one exists. If there is no appropriate replacement, document the content decision and return an appropriate response instead of sending unrelated requests to the homepage.

Do redirects preserve all search rankings?

No migration method can promise that result. Correct mapping, working destinations, useful content, and monitoring help manage the move, but search systems need time to process changes and results can vary.

Does a redirect move customer and order data?

No. It changes where a URL request goes. Customer records, orders, subscriptions, and integrations need separate migration decisions, supported methods, and verification.

Planning a platform change or a website restructure? Contact Interactive Online about migration review and Shopify development requirements.

Archives