WooCommerce migration SEO covers moving a store onto WooCommerce, or moving an existing WooCommerce store to new hosting or a new structure, without losing organic revenue. Because WooCommerce runs on WordPress, the constraints are almost the opposite of a hosted platform’s.
You can reproduce virtually any URL structure, which is an advantage. The corresponding risk is that nothing is decided for you, so structure, plugins and performance all become choices that can be made badly.
The general method is on SEO migration and catalogue-scale concerns on ecommerce platform migration. This page covers WooCommerce specifics, including moves from Shopify.
Permalink structure decisions
WooCommerce permalink settings are set once and are expensive to change later. Decide them before importing the catalogue.
- The product base, by default
/product/, can be changed or removed. - Product category base, by default
/product-category/, likewise. - Whether product URLs nest inside their category path, which affects every product URL.
- Whether the shop page sits at the site root or under a path.
Nesting products inside categories looks tidy but couples product URLs to category structure, so any later recategorisation becomes a migration. Flat product URLs under a single base are usually the more durable choice for growing catalogues.
Moving from Shopify to WooCommerce
This is a common direction and has a predictable shape, because Shopify’s enforced prefixes disappear.
- Every
/collections/URL needs mapping to its WooCommerce category equivalent. - Every
/products/URL needs mapping to the new product base. - Collection-scoped product URLs from Shopify need redirecting to the single new product URL.
- Shopify’s
/pages/and/blogs/paths both flatten, so both need explicit rules. - Reviews held in a Shopify app usually need exporting separately, since they do not travel with a product CSV.
Plugin conflicts to resolve before launch
Most WooCommerce SEO faults after a migration come from plugins rather than from WooCommerce itself.
- Two SEO plugins active at once, producing duplicate titles, canonicals or conflicting structured data.
- A redirect plugin and server-level rules both handling the same paths, creating chains or loops.
- Caching plugins serving stale pages to crawlers during the cutover window.
- Filter or faceted-search plugins generating crawlable parameter URLs by default.
- Product structured data emitted by both WooCommerce and an SEO plugin.
Performance, which is a WooCommerce-specific risk
WooCommerce is heavier than a hosted platform and is only as fast as its hosting and configuration. Performance regressions after migration are common and affect category pages first.
- Confirm object caching and page caching are configured before the catalogue import, not after.
- Check category pages with many products, which are usually the slowest templates.
- Watch database query load on filtered and sorted views.
- Establish a Core Web Vitals baseline on the old store so the comparison is real rather than assumed.
Frequently asked questions
Should product URLs include the category?
Usually not. Nesting products inside categories means any recategorisation changes product URLs, turning routine merchandising into a migration. A flat product base is more durable, particularly for catalogues that will grow.
Can we change the /product/ base after launch?
Technically yes, but it changes every product URL and requires a full redirect map, so treat it as a second migration. Decide before importing the catalogue rather than after.
Do we need a redirect plugin or server rules?
Either works. Server-level rules are faster and do not depend on WordPress loading. A plugin is easier to manage for large, frequently changing maps. Use one or the other, not both, or you will create chains that are hard to trace.
Why did our site get slower after moving to WooCommerce?
Usually hosting or caching rather than WooCommerce itself. Shared hosting sized for a brochure site will struggle with catalogue queries. Check caching configuration and category template query load before concluding the platform is at fault.
Consulting CTA
If you are migrating a store to WooCommerce, book an SEO consultation before permalink settings are fixed and the catalogue is imported, since both are costly to change afterwards.