# What happens to my categories when I move from WooCommerce to Shopify?

> Your WooCommerce product categories become Shopify collections, but the URL pattern changes (WooCommerce uses /product-category/, Shopify uses /collections/), so every old category URL needs a 301 to its new collection or it loses rankings. Category pages often rank well, so they matter as much as product pages. WPBuildAI maps every category and product URL to its Shopify equivalent before launch, so the structure moves without dropping traffic.

Source: https://wpbuildai.com/what-happens-to-categories-moving-woocommerce-to-shopify/
By lawrence-arya · 2026-06-20

---
When you move from WooCommerce to Shopify, your product categories become Shopify collections, but the URL pattern changes, and that is where traffic gets lost. WooCommerce serves categories under /product-category/, while Shopify uses /collections/, so every old category URL stops existing the moment you switch. Each one needs a 301 redirect to its new collection, or it forfeits the rankings it built. Because category pages often rank as well as products, this is not a detail to leave for later. WPBuildAI maps every category and product URL to its Shopify equivalent before launch, so the structure moves without dropping traffic.

Plan the export around the release calendar: [WooCommerce 11.0 is scheduled for 28 July 2026](https://developer.woocommerce.com/2026/07/13/woocommerce-11-0-pre-release/) and retires the Product Editor beta, so a category structure captured from a store mid-upgrade may not match what the store looks like a fortnight later.

## How the URL patterns differ

The platforms disagree on how to address a category, and that disagreement is the whole problem. WooCommerce, by default, puts categories under a /product-category/ base, so a "running shoes" category lives at something like /product-category/running-shoes/. Shopify uses a fixed /collections/ base, so the equivalent becomes /collections/running-shoes. The slug may even survive, but the path around it does not, which means the full URL changes and the old one ceases to resolve. There is no setting that makes Shopify reuse WooCommerce's /product-category/ structure, so this is not avoidable by configuration; it is a guaranteed change you plan for with redirects. Knowing the two patterns up front is what lets you build the map mechanically rather than discovering the breakage after launch.

## Why category pages matter more than people expect

Category and collection pages tend to rank for broad, high-intent searches, the way people actually look for a type of product rather than one specific item. Someone searching "running shoes" is far more likely to land on a category page than on a single product, which makes those pages some of the most valuable URLs in a store. Ahrefs found in its [search traffic study](https://ahrefs.com/blog/search-traffic-study/) that a small share of pages carries most organic traffic, and in a store those high-value pages are frequently the categories. Lose a category URL without a redirect and you can lose more than a whole cluster of product pages would have cost, which is why categories deserve the same care as products, not an afterthought.

## What transfers and what changes

It helps to separate the two halves. Your category content, the name, the description, the set of products it groups, transfers: you recreate each WooCommerce category as a Shopify collection holding the same products. What does not transfer is the URL, and to a search engine the URL is the identity of the page. So a category can "move" perfectly in terms of content while still losing all its rankings, because at the old address there is now nothing. This is the same distinction that catches people with analytics and metadata: the content survives, the addressing breaks. Holding the two apart makes the fix obvious, recreate the collection for the content, and add a 301 for the address.

## Building the two maps

Google's [site move guidance](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) treats a complete old-to-new URL map as the core of a safe move, and a store has two maps to build, not one:

1. **Categories to collections.** Inventory every /product-category/ URL, create the matching Shopify collection, and 301 each old URL to it.
2. **Products to products.** Map each product URL to its new Shopify product URL separately, the issue covered in [do product pages lose rankings when migrating](/blog/do-product-pages-lose-rankings-when-migrating-an-online-store/).

Treating these as one job is where stores slip, because the patterns and the matching logic differ. Google's [redirects guidance](https://developers.google.com/search/docs/crawling-indexing/301-redirects) confirms it is the 301 that carries the ranking signals across, so both maps have to be complete, not just the products or just the categories.

## A worked example: a merged category

Suppose WooCommerce had separate /product-category/mens-trainers/ and /product-category/womens-trainers/ categories, and on Shopify you decide to consolidate them into one /collections/trainers collection. The content move is straightforward, one collection holding both ranges, but the URL map now has two old URLs pointing at one new one, which is fine for a 301. The trap is forgetting that both old URLs each earned their own rankings and links, so both need their own redirect to the merged collection; mapping only one strands the other. Worked through deliberately, the merge keeps the equity of both old categories flowing into the new one. Skipped, it quietly drops whichever category you forgot, often the lower-traffic one you assumed did not matter.

## Categories that merge or split

Real migrations rarely map one-to-one, and the merges and splits are where traffic leaks. A merge sends several old category URLs to one new collection, and every old URL still needs its own 301. A split is harder: one old category becomes two or three collections, so you must choose the single best destination for the old URL, usually the broadest or highest-traffic successor, and accept that one redirect cannot point to two places. Decide each of these deliberately and record the reasoning in your map, because these are exactly the cases a bulk auto-match gets wrong. The mechanical slug-to-slug matches are easy; the merges and splits are the judgement calls that protect or lose your best category traffic.

## Do not forget filtered and paginated category URLs

A category is rarely just one URL. WooCommerce generates paginated category pages, /product-category/running-shoes/page/2/, and often filtered or sorted variants, and some of those accumulate rankings and links over the years. When you crawl the old store, these surface alongside the main category URLs, and a complete map accounts for them rather than only the top-level category. Shopify handles pagination and filtering differently, so the right move is usually to redirect the old paginated and filtered URLs to the relevant new collection rather than trying to recreate each variant. The point is that "map the categories" means every category URL the crawl finds, not just the clean primary one, because the forgotten paginated URL is a real lost page.

## Products in multiple categories

A product that sat in several WooCommerce categories simply belongs to several Shopify collections, which the platform handles without trouble. What this does not change is that the product's own URL still needs its own 301, independent of how many collections it appears in. People sometimes assume that redirecting the categories a product lived in covers the product, but the product page is a separate URL with its own rankings and backlinks, and it 404s without its own redirect. So multi-category products are a content convenience, not a redirect shortcut: map the collections for the grouping, and map every product URL separately for the addressing, the two-map discipline again.

## Preserving the hierarchy and internal links

Redirects keep the old URLs alive, but rankings also depend on how the new store is structured internally. Backlinko's analysis of [11.8 million search results](https://backlinko.com/search-engine-ranking) underlines how much site structure and internal linking matter, so recreate the category hierarchy on Shopify and keep the internal links into your collections, the navigation, the related-collection links, the in-content links from articles. A category that is redirected but then orphaned, with nothing linking to its new collection, loses some of the strength the redirect was meant to preserve. The goal is not only that each old URL resolves, but that the new collection sits in a structure as well-linked as the old category was, so the equity has somewhere to flow.

## Verifying after launch

A map is only proven once it is live. After launch, crawl the old category and product URLs and confirm each returns a single 301 to the right destination, not a chain, a 404, or a homepage catch-all. Check Search Console's coverage report for category URLs slipping into not-found or soft-404 states, and prioritise verifying your highest-traffic categories first, since Ahrefs' finding about traffic concentration means those are the rows you cannot afford to get wrong. Spot-check the merged and split categories specifically, because those are where the map most often has a gap. Verification turns "we built a map" into "every old category URL provably lands on real content," which is the actual goal.

## Common mistakes mapping categories

The recurring errors are predictable. Redirecting products but forgetting categories, on the assumption that only products rank, drops the store's highest-intent pages. Mapping only the primary category URL and ignoring its paginated and filtered variants leaves real pages to 404. Sending merged categories' old URLs to the homepage instead of the new collection creates soft 404s. And skipping post-launch verification means a broken redirect goes unnoticed until rankings fall. Each comes from treating categories as a minor part of a product migration, when they are often the part carrying the most traffic, which is why they get their own complete, verified map. The broader store move, cart, checkout, and media, is scoped in [migrating a WooCommerce store without losing sales](/blog/how-to-migrate-a-woocommerce-store-without-losing-sales/).

## Key points to remember

WooCommerce categories become Shopify collections, but the URL pattern changes from /product-category/ to /collections/, so every old category URL needs its own 301 or it loses rankings, and category pages often rank better than products. Build two complete maps, categories to collections and products to products, handle merges and splits as deliberate judgement calls, and do not forget paginated, filtered, or multi-category URLs. Preserve the hierarchy and internal links so the equity has somewhere to flow, then verify every redirect after launch starting with your highest-traffic categories. It all begins with a complete crawl, as in [mapping a site's structure first](/best-tool-to-scrape-website-structure-hierarchy/), and follows the care behind [301 redirects preserving SEO](/blog/do-301-redirects-preserve-seo-when-changing-platforms/). WPBuildAI builds the full category and product redirect map before launch, so the whole store moves without losing traffic; send your store URL for a fixed quote.

Not affiliated with WooCommerce, Shopify, WordPress, or Lovable.