Moving an ecommerce store changes more than its checkout and administration screens. Product addresses, category relationships, image paths and stock rules can all change beneath a familiar design. SEO safeguards belong in the migration specification before anyone imports the catalogue. This guide explains how to preserve useful customer journeys, document unavoidable changes and decide whether the new store is ready to replace the old one.
Define what the move must preserve
Start with a catalogue of business dependencies. Which categories introduce new customers? Which product pages answer detailed compatibility questions? Which buying guides link customers to the right range? A migration that copies products but abandons those supporting pages may preserve inventory while losing the information shoppers need to buy confidently.
Build the URL inventory from several sources: a crawl, existing sitemaps, analytics landing pages, Search Console exports and known external links. Include discontinued items, campaign landing pages and downloadable instructions. Record page type, intended destination, commercial importance and the person responsible for approving changes. An export from the product database alone will miss parts of the public website.
Make a destination decision for every old URL
Separate unchanged URLs, moved equivalents, merged content and genuinely removed pages. Preserve existing addresses when the new platform supports them sensibly. Where an address must change, map it to the closest equivalent that satisfies the original visitor's need. Do not treat a redirect to the homepage as a universal solution for products that failed to import.
Google's site-move guidance recommends mapping old URLs to new ones, implementing permanent redirects and monitoring the transition. It also warns that search visibility can fluctuate during processing. Those safeguards reduce avoidable mistakes; they cannot promise an unchanged ranking position or a fixed recovery date.
Consider a hypothetical discontinued fitting with no compatible replacement. Sending its visitors to an unrelated bestseller would be misleading. Depending on the continuing usefulness of its information, retain an honest reference page or return a proper removal response. If a true replacement exists, document why that destination is appropriate before approving the redirect.
Test platform rules against awkward catalogue cases
Happy-path testing usually covers an available product in one category. Real catalogues contain variants, bundles, temporarily unavailable items and products accessible through several collections. Choose examples of each before accepting the platform's default URL and canonical behaviour. A technically successful import can still produce multiple competing addresses for the same product.
Use Google's canonicalisation documentation to distinguish a preferred URL signal from a redirect. A canonical link does not move a visitor, and Google may select a different canonical. Agree which product and category versions should be discoverable, then align internal links, canonical declarations and sitemap entries with that decision.
- Open a product through its category, search results and a saved direct link.
- Change colour or size and inspect the resulting address and visible details.
- Check filtered collections for unintended indexable combinations.
- Verify that unavailable products describe their actual stock state.
- Confirm that pagination still exposes products beyond the first screen.
Protect product information and merchandising links
Create a field comparison for descriptions, specifications, delivery information, images and associated documents. Check representative records manually as well as comparing counts. Equal product totals do not establish that dimensions, variant labels or installation instructions survived the import correctly. Ask someone who understands the range to review the information customers use to distinguish similar items.
Review category introductions and buying-guide links separately from product fields. Navigation changes can leave useful pages technically available but hard to discover. Give every important range an understandable place in the site. Update links to their final destinations rather than relying on visitors to pass through old redirects indefinitely.
Inspect structured product information after the new theme and applications are installed. Google's structured-data guidelines require markup to represent the page accurately. Check that displayed price and availability agree with the machine-readable version. Passing validation establishes neither eligibility for every search feature nor a promise that a feature will appear.
Rehearse the switch with evidence
Keep a staging comparison that pairs old and new examples, expected responses and actual results. Test the redirect map against the environment that will serve production requests, including rules applied by the hosting layer. Check for loops, chains, incorrect query handling and redirects that work only when entered in one particular format.
Prepare separate staging and production indexing settings. Record who removes launch restrictions and who checks the public response afterwards. A deployment checklist should also cover certificates, image delivery, search verification and the final sitemap. Give each task an owner; an unassigned instruction to “check SEO” is not a release control.
Make recovery operationally possible
Agree what would justify delaying launch or restoring a previous application version. Broken checkout, missing core ranges and widespread incorrect redirects deserve clear escalation paths. A rollback also needs to account for orders and account changes received after the switch. Restoring an old application without reconciling new transactions can create a second problem.
After launch, compare affected page groups rather than judging the entire move from one traffic total. Watch destination response codes, missing images, search impressions and completed orders alongside customer support reports. Annotate stock changes and promotions so their effects are not automatically attributed to the platform. Keep a record of fixes and recheck the same examples after each release.
Visuosofts' SEO migration services provide a starting point for discussing a platform move. Use the related technical SEO launch acceptance checklist to turn the plan into release evidence. To discuss your catalogue, constraints and proposed launch, contact Visuosofts with the current and intended platforms.