Migrating to WooCommerce without losing your Google rankings

The worst moment of a migration is not the switchover day. It is the third week after, when the store owner opens Google Search Console and sees that half the pages have dropped out of the index and organic traffic is down by half. That is usually when they call me. And the cause is almost always the same: someone moved the products to WooCommerce but did not move what Google already knew about that store.

Because migrating to WooCommerce is not just shifting products and images across. It is moving your entire history in the search engine - the links pointing at your categories, the positions built over years, and the addresses Google has on file as “the product lives here”. Done sloppily, you start from zero even though the store has been running for ten years.

The good news: losing rankings is not inevitable - it is the result of specific, predictable mistakes. Below I break down how to migrate from PrestaShop, Shoper or Shopify to WooCommerce so that Google barely notices the engine changed.

First measure what you have - otherwise you do not know what you are losing

Before anything moves, I do a full inventory of the old store. Without it you do not know which pages earn from Google traffic, so you do not know what to protect. What I collect at the start:

A full list of URLs - every product, category, static page and blog post. From the store export or with a crawler such as Screaming Frog.
Which URLs have traffic and rankings - from Google Search Console (the “Performance” tab) and Analytics. Usually a handful of addresses accounts for most of the traffic. Those are the ones that matter.
Inbound links - if someone external links to a specific category, that address has to keep working after the migration or redirect properly.

What helps: export the pages report from Google Search Console for the last 12 months BEFORE the migration. That is your treasure map - right after the switch you know immediately which addresses you have to keep under control.

Only with that list in hand do I know what I am really moving - not all addresses equally, but deliberately the ones that earn.

URL mapping and 301 redirects - the heart of the whole operation

This is the most important part and where most migrations die. PrestaShop, Shoper and Shopify build addresses differently from WooCommerce. An old product might have lived at /123-product-name.html, and in WooCommerce it will naturally land at /product/product-name/. Those are two different addresses for the same thing.

If you do nothing about it, the old address returns a 404 - “no such page”. After a few such visits Google drops it from the index, and with it your position and every link that pointed there.

The answer is a 301 redirect - a permanent message to the search engine: “this product has moved here, move its ranking too”. I do it like this:

An old address → new address map - a table where every important address from the old store has its counterpart in WooCommerce. One to one.
301 rules on the server or in a plugin - ideally in the server config (fastest) or with a good redirect plugin. Every old address leads to the new one, with no hops.
Pattern handling - with thousands of products you do not write rules by hand. For repeatable schemes I write a pattern rule and pin down the odd cases individually.

What helps: a redirect should lead straight to its target - one hop. A chain of old address → redirect → another redirect dilutes link strength and slows everything down. After the migration, crawl the store and catch chains like that.

It is tedious work, but it is what decides whether you keep your rankings. The rest is hygiene.

Google understands a store partly through its structure - what is a category, what is a subcategory, how products are grouped. If you rebuild the whole category tree while you are at it, you signal that this is a completely different store. That is why migration and a structural redesign are two separate operations for me: first I move the store 1:1 - same structure, same groupings, same names - and only later do I tidy up categories, one at a time, with a redirect for every change. The same goes for internal links, breadcrumbs and menus. The more stays the same, the fewer reasons Google has to recalculate the store from scratch.

Move the meta titles, descriptions and headings

SEO titles (meta title), descriptions (meta description) and the H1 headings of products and categories are often the result of years of tinkering - someone tuned them so they get clicked in Google. During a migration they are easy to lose, because the new engine generates its own default versions.

What I move along with the products:

Meta title and meta description - exported from the old store (PrestaShop and Shoper keep them in the database, Shopify in the product SEO fields), imported into WooCommerce via an SEO plugin.
H1 headings - usually the product name, but if they were set by hand they have to be preserved.
Image alt attributes - image descriptions carry SEO weight too, especially in Google Images.
Description content - full, unique product and category descriptions. Those are what rank on long-tail phrases.

If you move a product but lose its carefully tuned SEO title, technically everything works - but Google shows a worse, automatic title and your click-through rate drops. A detail that makes a difference in the results.

Sitemap and Google Search Console - tell Google what happened

After a migration you have to lead Google by the hand rather than wait for it to work things out. I do it in a few steps:

A new XML sitemap - WooCommerce with an SEO plugin generates it automatically. I check that it contains the important addresses and no junk (cart, account, thank-you pages).
Submitting the sitemap in Google Search Console - right after the switch, so Google finds the new addresses faster.
The old sitemap stays for a while - it helps Google revisit the old addresses sooner, hit the 301 redirects and connect the old address with the new one.
The indexation report - I watch how many addresses Google has accepted, how many it rejected and why.

What helps: if the domain is changing, or you are adding or removing www, use the change of address tool in Google Search Console. For an engine change on the same domain it is not needed, but for a domain move it is mandatory.

Staging, or: you only switch once everything works

The most expensive mistake is migrating live - rebuilding on a working store. That guarantees downtime, a half-working checkout and panic.

So I always build the new WooCommerce on a staging copy, at an address invisible to Google and blocked from indexing, so the work-in-progress version does not compete in the results with the real store. There I have the full set: products, structure, redirects, meta, payments, shipping. I only switch once everything passes the tests:

Whether a sample of old addresses (especially the highest-traffic ones) redirects correctly to the new ones.
Whether checkout, payments and the order email work end to end.
Whether the meta titles and descriptions really came across rather than reverting to defaults.
Whether a stray “noindex” or a block in robots.txt has been left anywhere.

That last point is a classic - a perfect migration, and then the store is invisible for weeks because the indexing block from the staging version was carried over to production. I check it on the first day after the switch, every time.

After the switch, watch indexation like a hawk

A migration does not end on switchover day - it ends when Google has fully digested the change, which takes from a few days to a few weeks. During that time you look at numbers, not at gut feeling.

What I monitor over the first weeks:

The indexation report in Google Search Console - the number of indexed pages should settle close to the pre-migration level. A sudden drop is a problem to fix on the spot.
404 errors - if old addresses show up without a redirect, I add the missing 301 rules.
Rankings and traffic - slight movement right after the migration is normal. A lasting, deep drop after 2-3 weeks is a signal that something moved across badly.

What helps: in the first week, check the pages report in Google Search Console and the 404 errors every day. Most migration problems can be fixed within 48 hours - but only if you spot them before Google has thrown the addresses out of the index.

The most common mistakes that kill traffic

Almost every ranking loss during a migration comes down to one of these:

No 301 redirects - old addresses return 404, Google drops them from the index along with their rankings. Mistake number one.
Changing every address at once alongside a structural redesign - engine migration plus category rebuild plus new addresses in one move. Google cannot keep up connecting old to new.
Redirect chains - the old address hops through several redirects before reaching its target. It dilutes link strength and slows indexation.
Lost meta and descriptions - the products came across, but with default titles instead of the tuned ones. Click-through rate falls.
A staging indexing block left on production - “noindex” or a block in robots.txt survives the switch. The store works, but it is invisible in search.
No monitoring after the migration - nobody looks at Search Console, so the problem only surfaces when sales drop, a month too late.

All of them are avoidable. None requires magic - they require a plan and watching the numbers.

Sometimes the best migration is no migration

Before you plan a migration, it is worth stepping back and checking whether WooCommerce is the right direction for your stage of business - not every store should move to it. If the store runs stably and the only problem is the look or the speed, moving to WooCommerce is often overkill; a redesign without rebuilding from scratch, without touching addresses and without risking SEO, pays off better. But if you are on an engine that limits you - expensive licences, no flexibility, trouble developing it further - a WooCommerce store gives you freedom and full control. Migration makes sense then, provided it is planned rather than rubber-stamped - this is what a migration I run looks like.

The whole craft comes down to one thing: do not force Google to learn your store from scratch. Move the addresses with 301 redirects, keep the structure and the meta, test on a staging copy, switch once and properly, and watch indexation for a few weeks. It is not complicated - it is laborious and it does not forgive shortcuts.

If you are planning a move to WooCommerce and do not want to hand Google back positions built over years, send me the address of your current store. I will do a free review: I will show you where the risks are and how to run the migration so organic traffic survives the move. You get the quote in writing within 24 hours, with no “from X PLN”.

Frequently asked questions

Will my Google rankings drop after the migration? Slight movement over the first days and weeks is normal - Google needs time to digest the change of addresses. A lasting drop does not come from the migration itself but from a specific mistake: missing 301 redirects, lost meta, or an indexing block left over from the staging version. That is why I check the indexation report daily for the first few weeks.

How long do 301 redirects need to stay in place? Permanently is safest. Google usually rewrites an address to the new one within a few weeks, but old addresses live on in other people’s links, bookmarks and emails - if you switch the redirects off after a month, those people hit a 404. The 301 rules cost nothing, so there is no reason to delete them.

Can a migration be done with no break in sales? Yes, and that is how I do it. The new store is built on a staging copy blocked from indexing while the old one sells as usual until the switch. I only rewire once redirects, checkout, payments and meta have passed the tests - the switch itself is a matter of minutes, not days.

Traffic has already dropped after a migration - can it be undone? It can be fixed, but the sooner the less work. I start with the list of pre-migration addresses from Google Search Console and check which return 404 or hop through a redirect chain, then whether a “noindex” from the staging copy is still on production. Once the missing 301 rules are in place, Google starts reconnecting old addresses with new ones - it simply takes longer than it would have if it had been done right away.

On Shopify, PrestaShop or a local SaaS and thinking about moving? I run migrations to WooCommerce without losing search positions and without pausing sales. Describe the store and you will get a quote with a date.