Founder Playbook
How to replatform without losing half your traffic
Ratik5 min readPlan URL changes, verify destination-specific product data and monitor a migration against your own baseline.
The Three Risks That Kill Migrations
Eighty-three percent of platform migrations fail or exceed their budget. The failures tend to cluster around three problems, and most teams only plan for the first one.
The first is SEO traffic loss from broken URL transitions. Inventory the old product, category and landing-page URLs rather than assuming every page is indexed. Use sitemaps, analytics, server logs and Search Console to identify URLs people and crawlers use, then check what each will return after the move.
The second is data integrity failure. Customer accounts, order history, product metadata, reviews, subscription records. Moving all of it from one system to another without losing or corrupting data is harder than most teams estimate. A single malformed CSV import can wipe loyalty tier assignments for thousands of customers.
The third is the lift-and-shift trap. Teams migrate their broken workflows unchanged to the new platform. The checkout flow that was losing conversions on WooCommerce gets rebuilt identically on Shopify. The product page layout that buried key information moves over pixel for pixel. You spend six months and six figures to end up with the same problems on a newer system.
The URL Redirect Problem
WooCommerce makes this especially painful. WordPress lets you configure permalinks in multiple formats, which means two WooCommerce stores almost never have the same URL structure. Some use /product/product-name, others use /shop/category/product-name, and others have entirely custom structures built by whatever developer set up the site.
Google’s site-move guidance calls for a URL mapping. Preserve unchanged URLs. For permanently moved content, use a server-side 301 or 308 redirect to its relevant replacement. Retired content without a replacement should return 404 or 410. Do not send unrelated old pages to the homepage. Test the mapping in staging and verify it after launch.
Source: Google Search: Site moves with URL changes
Category pages are where most teams slip up. Products get mapped because they are obvious. But category pages, tag archives, paginated listing pages, and blog posts often get overlooked. These pages frequently carry significant search authority, and losing them means losing the long-tail traffic that feeds your discovery funnel.
The Structured Data Problem
Your product pages serve shoppers and can supply information to search and shopping systems. Before migrating, identify the destinations you use and the inputs they consume: visible content, supported structured data, merchant feeds or connected tools. Their requirements are not interchangeable.
A migration can change those inputs. Compare the same products before and after the move: check access, product URLs, visible facts, markup and feed values. A missing recommendation or a referral drop alone does not establish which input, if any, caused it.
Audit structured data before launch against the feature you use. For Google product rich results, choose the applicable product-snippet or merchant-listing requirements and keep markup consistent with visible product facts. Add ratings and reviews only when supported by real review data. Google’s AI Search guidance requires no special AI schema and does not guarantee inclusion; FAQ and Review markup are not universal admission requirements.
Source: Google Search: Product structured data
The Pre-Launch Checklist
Before you flip the switch, five things need to be verified and documented.
A URL inventory with an expected outcome for each entry: unchanged page, relevant permanent redirect, or deliberate retirement. Test status codes, redirect destinations and destination content in staging, then repeat after launch. Include URLs found outside the old sitemap.
A structured data audit on every page template. Use Google’s Rich Results Test for supported Google rich-result types, then manually compare visible facts, rendered markup and relevant feeds for the same products. A valid test does not certify AI recommendations or guarantee a Google rich result.
Source: Google Search Console: Rich Results Test
Google Search Console verification on the new domain or URL structure. If your domain is changing, use the Change of Address tool. If only the URL structure changes, submit the new sitemap and monitor the Index Coverage report.
Consistent canonical annotations, internal links and sitemaps. Give each preferred page a self-referencing canonical; duplicate versions should point to the intended preferred URL. Do not require every duplicate to name itself. Prevent staging pages from being indexed, and remove temporary indexing restrictions from the public destination at launch.
Source: Google Search: Canonical URLs and duplicate content
A monitoring plan for the first 30 days. Define what you will track and what thresholds trigger action.
The First 30 Days
The migration is not complete on launch day. It is complete when your traffic, rankings, and conversion rates have stabilized on the new platform.
Monitor organic traffic by page daily for the first two weeks, then weekly. A 10 to 15 percent dip in the first week is normal as Google recrawls and reindexes. A 30 percent dip that persists into week two means something is broken.
Watch indexing and crawl reports in Search Console. Compare 404s with your retirement plan to distinguish intentional removals from broken moved URLs. Inspect soft 404 reports for empty pages, errors presented as successful responses or irrelevant redirects.
Track your indexed page count. It should recover to pre-migration levels within two to three weeks. If it plateaus significantly below the old count, pages are being excluded from the index.
Check identifiable AI referral traffic separately against the pre-migration baseline. If it drops, inspect tracking, access, redirects, page content and the inputs used by the relevant destination. Do not diagnose a structured-data fault from a referral change alone.
The difference between a successful migration and a damaging one is almost always preparation. The teams that build the redirect map, audit the structured data, and set up monitoring before launch day recover their traffic within weeks. The teams that treat these as post-launch tasks spend months trying to get back to where they started.
What could work better for your customers?
30 minutes with the founders. We look at the journey you want to improve, your current setup and a sensible first scope.
