adminAsk store owners why they haven’t left a platform they’ve outgrown, and one answer comes up again and again: “I’m scared of losing my Google rankings.” It’s a fair worry. A careless migration can wipe out years of search traffic in a few weeks.
The good news is that rankings are rarely lost because of the move itself. They’re lost because of missing redirects, deleted content and forgotten details. Handle those carefully and most stores come through a migration with their traffic intact, and often faster pages that help them grow. This checklist walks you through all four phases of an SEO-safe move to WentoCart.
Key takeaways
- Most ranking losses come from broken or missing redirects, not from changing
- platforms.
- Map every important old URL to its closest new page with a permanent (301) redirect.
- Keep your titles, descriptions, content and images. Don’t rewrite everything during the move.
- Expect some temporary fluctuation; Google says it can take a few weeks or more to settle.
- Keep redirects in place for at least a year, ideally permanently.
Why Rankings Drop After a Migration
- Old URLs return “404 Not Found” because they weren’t redirected, so Google drops them and their links are wasted.
- Everything redirects to the home page, which Google treats much like a missing page.
- Content disappears: product descriptions, category text, blog posts or reviews aren’t migrated.
- Titles and meta descriptions change or reset to defaults.
- The staging site’s “noindex” setting goes live, telling Google not to index the new store.
- Internal links, canonical tags or sitemaps still point at old URLs.
- The new site is slower or breaks on mobile.
What Google recommends for site moves
- Use server-side permanent redirects (301 or 308) from each old URL to its new equivalent.
- Redirect to the closest matching page, not to the home page, and avoid redirect chains.
- Keep redirects as long as possible, generally at least a year.
- Permanent redirects don’t cause a loss of PageRank.
- Expect temporary ranking fluctuation; for medium-sized sites, it can take a few weeks or more for new URLs to replace old ones.
- Submit a new sitemap in Search Console and monitor indexing as it shifts.
Source: Google Search Central, “Site moves with URL changes”.
PHASE 1
Before You Move: Benchmark and 2–4 weeks
Inventory before
You can only protect what you’ve measured. Capture a complete picture of your current site.
☐ Export performance data from Google Search Console: top pages, top queries, clicks and impressions for the last 12 months.
☐ Export analytics: organic traffic, revenue and conversion rate by landing page.
☐ Crawl your current site with an SEO crawler to list every URL: products, categories, brands, CMS pages, blog posts, images and PDFs.
☐ Identify your money pages: the pages that bring most organic traffic, revenue and backlinks. These get extra care.
☐ Export backlink data to see which pages other websites link to.
☐ Save your on-page SEO: titles, meta descriptions, H1s, product descriptions, image alt text and structured data.
☐ Note what’s indexed: compare your crawl with Search Console’s indexing report.
PHASE 2
Build: Migrate Content and Map 1–3 weeks before
Every URL
Set up WentoCart on a staging site, protected by a password or “noindex” so Google can’t index it yet. Then move your data and build your redirect map.
☐ Migrate all content: products and variants, categories, customers, orders, reviews, CMS pages, blog posts and images.
☐ Carry over SEO fields: titles, meta descriptions and descriptions exactly as they are. Improve them after the migration has settled.
☐ Keep URLs the same where you can. Where the structure has to change, plan a redirect.
☐ Build a redirect map: a spreadsheet with every old URL and its new destination (see below).
☐ Handle discontinued products: redirect to the closest category or a replacement product.
☐ Update internal links, navigation menus and footer links to point directly at new URLs.
☐ Check technical SEO: self-referencing canonical tags, hreflang for multi-language stores, structured data, XML sitemap and robots.txt.
☐ Test speed and mobile on key templates: home, category, product and checkout.
Example redirect map Old URL (WooCommerce example) New WentoCart URL Type
/product/linen-shirt-blue/ /products/linen-shirt-blue 301
/product-category/men/shirts/ /categories/mens-shirts 301
/product/old-discontinued-tee/ /categories/mens-t-shirts 301
/about-us/ /about-us 301
Illustrative paths only. Use the actual URL formats of your old store and your WentoCart setup.
For larger stores, redirects are usually handled at the web-server level. With Nginx, for example, a simple lookup map keeps hundreds of redirects fast and easy to maintain:
# /etc/nginx/conf.d/redirects.conf map $request_uri $new_uri { /product/linen-shirt-blue/ /products/linen-shirt-blue; /product-category/men/shirts/ /categories/mens-shirts; }
# inside the server { } block if ($new_uri) { return 301 $new_uri; }
Common URL patterns to plan for
Moving from Typical URL patterns
WooCommerce /product/slug/, /product-category/slug/, trailing slashes
Shopify /products/slug, /collections/slug, /collections/x/products/slug, /pages/, /blogs/news/
Magento URLs ending in .html, category paths, store codes in multi-store setups
PrestaShop IDs in URLs such as /12-category or /mens/45-product-name.html
Also cover old pagination, image URLs that rank in Google Images, and redirects you set up in the past.
PHASE 3 Launch Day: Switch Over Carefully Go-live
Choose a quiet period, avoiding sales events and your busiest season, and work through this list in order.
☐ Freeze changes on the old store, then run a final import of new orders, customers and reviews.
☐ Switch DNS or point your domain at the new server.
☐ Remove staging protection: delete “noindex” tags, password protection and any robots.txt blocks.
☐ Turn on your redirects and test your top 50 money pages by hand.
☐ Crawl the old URL list to confirm each returns a single 301 to a working page (status 200).
☐ Submit the new XML sitemap in Search Console, and keep the old sitemap available so Google re-crawls old URLs.
☐ Check tracking: analytics, Search Console verification, advertising pixels and conversion goals.
☐ Place a real test order from start to finish, including payment and confirmation emails.
☐ Email customers about the new store, including how to reset passwords if accounts were migrated.
If you’re changing your domain name as well, also use Search Console’s Change of Address tool. It isn’t needed when you keep the same domain.
PHASE 4 After Launch: Monitor and Fix Fast First 3 months
Check daily for the first two weeks, then weekly for at least three months.
☐ Watch for 404 errors in Search Console and your server logs, and redirect any missed URLs right away.
☐ Track indexing: new URLs should rise in Search Console as old ones drop away.
☐ Compare rankings and traffic for your money pages against your pre-migration benchmark.
☐ Check Core Web Vitals and fix any slow templates.
☐ Ask key partners who link to you to update links to your new URLs.
☐ Keep redirects for at least a year, and ideally leave them in place permanently.
☐ Only then improve content: once traffic is stable, start optimising titles and descriptions.
Common Migration Mistakes
Mistake Do this instead
Redirecting everything to the home page Map each URL to its closest equivalent page
Using temporary (302) redirects Use permanent 301 or 308 redirects
Chains like old URL to older redirect to new URL Point every old URL straight at its final destination
Redesigning, rewriting and migrating at once Migrate first, then improve in stages
Removing redirects after a few months Keep them for at least a year, ideally permanently
Why WentoCart Makes a Good Destination
WentoCart gives migrating stores a modern foundation: search-friendly product pages, a structured catalog with categories and attributes, multi-language and multi-currency settings, and a fast React storefront built with Vite and Tailwind CSS. Because it’s open source and self-hosted, your developers have full control over URLs, redirects, sitemaps and server configuration, and can set up a private staging copy on an inexpensive server to rehearse the move before going live.
Frequently Asked Questions
Will I lose rankings when I migrate? Some short-term fluctuation is normal, even when everything is done right. With complete redirects and preserved content, most stores recover within weeks.
Can I migrate without downtime? Yes. Build and test the new store on staging, run a final data sync, then switch DNS during a quiet period.
The Bottom Line
Losing rankings isn’t an unavoidable cost of switching platforms; it’s usually the result of a rushed move. Benchmark, map every URL, keep your content, test on staging and monitor after launch.
Planning your move? Explore WentoCart’s live storefront and admin demo, read the documentation, or download v1.0 and build your staging store today.