Migrate an Ecommerce Site Without Losing SEO

Treat search visibility as a migration workstream

To migrate ecommerce site without losing SEO, make search continuity part of the project from discovery onwards. It is not a task for the final week. Search engines and customers rely on established addresses, page content, internal links and signals about what each page represents. A new design can look correct while important category pages, product information or guides have quietly disappeared.

Begin by crawling the current public site and collecting a list of indexable URLs, titles, descriptions, headings, canonicals, status codes and internal links. Combine that with analytics, search performance data, paid landing pages, backlinks where available and a list of pages used in email or social campaigns. This identifies pages that receive traffic or have business value, including older pages that are easy to overlook.

Create a page-by-page redirect map

Every important old URL needs a considered destination. Map an old product to its replacement product where it still exists, an old category to the closest relevant category and an obsolete item to a useful alternative or parent category only when that genuinely helps the visitor. Do not send large groups of unrelated URLs to the homepage. That is confusing for customers and makes the relationship between old and new content unclear.

Use permanent server-side redirects for moved pages and keep the mapping in a version-controlled spreadsheet or migration document. Include the old URL, the new URL, page type, owner, status and notes about exceptions. Test the redirects in batches before launch. Check that they go straight to the final destination, not through chains, and that query parameters used for campaigns are handled appropriately.

• Include products, categories, editorial pages, filters where justified and downloadable resources
• Flag pages deliberately removed and record the reason for each decision
• Avoid redirect loops, redirect chains and broad catch-all rules
• Retain the map after launch for support and future checks

Keep useful content and metadata continuous

A platform migration is a chance to improve weak copy, but it is risky to rewrite everything at once. Carry across the useful substance of category descriptions, product details, buying guides, FAQs and editorial articles. Preserve clear heading structure and ensure images retain meaningful alternative text where it serves users. If products are consolidated or renamed, explain the new range well enough that a customer can understand the change.

Bring across page titles, meta descriptions, canonical intentions and structured data only where they accurately describe the new page. Metadata should be reviewed, not copied blindly. The key is continuity of topic and purpose: a category that previously explained a specific product range should still have a clear, indexable page that explains that range after migration.

Control crawling and indexing on staging

A staging site needs to be available to the people testing it without becoming a competing version in search results. Use access controls appropriate to the environment and make sure any temporary noindex controls are understood, documented and checked before launch. Do not rely on a robots.txt file alone to protect unfinished content. The production domain should also be protected from accidental changes while the new site is being prepared.

Before launch, crawl the staging site as a search engine would. Look for blocked CSS or scripts that affect rendering, noindex directives left on templates, missing canonicals, internal links pointing to staging addresses and pages returning errors. Confirm the intended production URL format, including the preferred protocol and host, so that redirects and canonicals tell a consistent story.

Run disciplined launch checks

Launch day should have an agreed checklist and named people who can make decisions quickly. Confirm that the new site is accessible, pages return the expected status codes, redirects are live, sitemap URLs are current and robots directives are suitable for production. Test the key customer journeys too: search, navigation, product selection, basket, checkout, account access and transactional emails. SEO is damaged when a site is technically crawlable but customers cannot complete a purchase.

Check representative URLs rather than only the homepage. Include top categories, high-value products, long-standing content, discontinued products and pages with parameters. Compare the page source and rendered page where necessary. Add the new sitemap to the relevant search tools and retain access to the old platform long enough to investigate unexpected behaviour, subject to security and operational requirements.

Monitor after launch and respond to evidence

For several weeks, monitor crawl errors, indexed pages, redirect activity, organic landing pages, conversions and revenue alongside the normal operational measures. Some movement is normal when a site changes, but a sustained loss on an important page type needs investigation. Check the redirect map, canonical tags, internal links, content changes and server responses before making broad changes based on a single day of data.

Keep a launch log of deployments, fixes and decisions so that changes can be matched with observed effects. Customer service feedback can reveal broken routes that analytics misses. The safest way to migrate ecommerce site without losing SEO is methodical: know what exists, preserve what is valuable, test the technical handover and keep watching once real visitors and crawlers arrive.