A replatform is also a search migration
Moving an ecommerce website changes more than its appearance. Product URLs, categories, templates, canonical tags, internal links, structured data, and rendering can all change at once. A successful migration needs an inventory of what works today and a tested plan for what replaces it.
No checklist can guarantee unchanged rankings. Google must crawl and process the changes, and temporary fluctuations can happen. The aim is to remove avoidable mistakes and make it clear which new pages replace the old ones.
Before design: inventory your valuable pages
Export existing URLs from the sitemap, analytics, search reporting, and a crawl. Include pages with organic visits, useful backlinks, revenue, and customer-support value. A sitemap alone will not reveal every historically important URL.
Record titles, main headings, descriptions, canonical targets, indexability, and important on-page content. This is your comparison baseline. Decide which pages are staying, being consolidated, or being removed before the new navigation is finalized.
- Collect products, collections, articles, and campaign pages.
- Record traffic and business value where data is available.
- Assign every important old URL a migration decision.
Build a direct redirect map
Where a URL changes permanently, point the old page directly to its closest relevant replacement using a permanent server redirect. Avoid chains and generic homepage destinations. A product with no genuine replacement may need a proper not-found or gone response rather than a misleading redirect.
Keep the map understandable enough for a merchandising or SEO reviewer to spot mismatches. Google recommends keeping migration redirects for at least a year. Valuable legacy URLs may justify keeping redirects longer.
- Test old URLs, not just links on the new site.
- Check that each destination returns a successful response.
- Remove redirect chains and irrelevant destinations.
Is your store making buying harder than it should?
Let’s look at your websiteTest templates and catalog edge cases
Validate a normal product, a product with variants, an out-of-stock item, a deep collection, a filtered result, and an article. Search engines and customers should receive consistent product information. Check that staging noindex settings or crawler blocks are not accidentally carried into production.
Make sure canonicals use the live domain and intended URLs. Structured data must describe visible, accurate information. A schema validator can catch syntax issues but cannot prove that price and availability match the actual store.
- Check titles, one clear H1, canonicals, and crawlable links.
- Validate product data against visible price and stock information.
- Confirm sitemap URLs are canonical and accessible.
Treat checkout and tracking as launch requirements
Complete purchases using the supported payment and delivery methods in a safe test environment. Include discount codes, failed payments, refunds where relevant, and mobile checkout. Search traffic cannot compensate for a broken transaction flow.
Confirm that measurement distinguishes a purchase from a checkout start. Record the launch date so later reports can be interpreted in context. Do not compare launch-day traffic with an unrelated peak season and assume the difference is caused by the platform.
Monitor the move, then fix the pattern
Watch indexing, crawl errors, landing-page traffic, orders, and support reports after launch. A drop concentrated in one template or directory often deserves a different response from a sitewide change. Inspect examples before rolling out a broad correction.
Falcon's portfolio includes Shop The Sample, JoyJolt, and Milliard Bedding. For a proposed migration, ask us to review your existing URL inventory and show how design and development decisions will preserve the useful parts of your current site. A launch plan should include named owners for redirects, catalog data, checkout, and monitoring.
