Shopify redirect mapping guide

The redirect map is where a migration either protects value or loses it

A Shopify migration can look successful on launch day and still lose search value because the old URLs were not handled carefully enough.

The new theme may work. Products may import. Checkout may function. The homepage may look better than the old site. But if old WooCommerce categories, WordPress posts, product URLs, landing pages, filters and backlinks are not mapped to useful Shopify destinations, the migration leaves search engines and visitors with broken context.

That is why redirect mapping should not be treated as an admin export. It is the transfer plan for the store’s history.

A good redirect map answers one question over and over:

When someone or something requests this old URL after launch, where should they land so the intent is still satisfied?

That “someone or something” might be a customer clicking an old product link, Googlebot recrawling an indexed page, a journalist’s backlink, a paid campaign, an email link, an affiliate URL, an old Pinterest pin, a supplier link, or a saved bookmark.

If the answer is lazy, the migration becomes noisy. Old category rankings soften. Backlinks point through weak redirects. Search Console fills with avoidable not found reports. Customers land on the homepage instead of the product family they expected.

The redirect map is how you stop that happening.

Start by accepting that not every old URL is equal

The biggest mistake is treating the old site like a flat list of addresses. A store migration is not flat.

Some old URLs carried revenue. Some ranked for product-led searches. Some attracted links. Some only existed because WooCommerce, WordPress, filters, tags or plugins generated them. Some were already redirects. Some were outdated but still useful as signals. Some should disappear.

Before any redirect is written, classify the old URL by role:

This prevents the “everything goes somewhere” problem. The goal is not maximum redirect count. The goal is the right destination for every URL that matters.

Build the old URL inventory from more than one source

A redirect map built from a single crawl is usually incomplete.

A crawl shows what the crawler can currently discover. It may miss pages that are orphaned, blocked, noindexed, removed from navigation, still ranking, still linked externally, or only present in historic sitemaps and exports.

Use a combined evidence set:

• current crawl of the old site
• old XML sitemaps
• Search Console top pages
• GA4 or analytics landing pages
• ecommerce revenue or assisted conversion pages
• backlink export
• WordPress page and post export
• WooCommerce product and category export
• SEO plugin metadata and redirect export
• paid campaign landing URLs
• email and affiliate landing URLs
• old redirect rules
• server logs if available

When two sources disagree, do not guess. Mark the URL as investigate. It is better to pause on a valuable URL than to send it to the wrong place because the spreadsheet needed finishing.

Score redirect priority before choosing destinations

A practical redirect map needs priority. Otherwise every URL gets the same attention, and the team wastes time perfecting low-value junk while risky pages are still unresolved.

Use four levels:

This is where the human judgement happens.

A product with two monthly organic visits but a strong backlink may be P1. A tag archive with thousands of crawlable combinations but no value may be P4. A category that looks small in analytics might still be vital if it maps to a future Shopify collection.

Choose destinations by intent, not by URL similarity

A common migration mistake is matching URLs by words rather than by user intent.

Old URL:

/product-category/womens/winter-boots/

Possible Shopify destinations:

• /collections/womens-boots/
• /collections/winter-boots/
• /collections/womens-winter-boots/
• /collections/boots/

The right destination is not automatically the closest string. It is the page that best satisfies the old search intent and product expectation.

Ask:

1. What did the old page represent?
2. What products did it contain?
3. What queries did it attract?
4. What page on Shopify best covers that demand?
5. Will the destination remain live after launch?
6. Does the destination canonicalise to itself?
7. Is the destination strong enough to inherit the signal?

If no destination is good enough, the answer may be to build one before launch.

Here is the kind of judgement the sheet should force:

• Old URL: /product-category/womens/winter-boots/
  Weak destination: /collections/boots/
  Stronger decision: build or use a women’s winter boots collection if products and demand justify it.

• Old URL: /blog/how-to-clean-suede-boots/
  Weak destination: /blogs/news/
  Stronger decision: rebuild the guide or redirect to a care guide that still answers the query.

• Old URL: /product/old-waterproof-jacket/
  Weak destination: /collections/jackets/
  Stronger decision: use the replacement product if one exists, otherwise the closest waterproof jackets collection.

• Old URL: /tag/sale-running-shoes/
  Weak destination: /collections/all/
  Stronger decision: retire unless it had real search value, or create a focused collection if demand exists.

The strongest redirect is not always the narrowest page. It is the page that best preserves the old search job.

Do not send ecommerce URLs to the homepage by default

Homepage redirects are one of the clearest signs of a weak migration.

They are sometimes used because they are easy, not because they are useful. For ecommerce URLs, they usually break the promise of the click.

Better alternatives:

Homepage redirects should be rare and justified. If the best available destination is the homepage, ask whether the old URL should be retired instead.

WooCommerce categories need special care

WooCommerce categories often carry a lot of SEO value because they behave like commercial landing pages. Shopify collections can replace them well, but only if the migration team plans the translation.

Do not assume every old category becomes a one-to-one Shopify collection.

Some categories should become exact collections. Some should merge. Some should split. Some should become supporting guides. Some were only navigation conveniences and should not survive as SEO pages.

Use this decision test:

• Does the old category have search demand?
• Does it have enough products?
• Does the new collection match the same buying intent?
• Would a shopper feel they landed in the right place?
• Can the collection support useful copy and internal links?
• Will the product set stay stable enough to justify the page?

If the answer is yes, build the collection and redirect to it. If the answer is no, choose a more honest destination.

WordPress posts and guides are not second-class migration assets

When ecommerce teams migrate to Shopify, blog and guide URLs are often handled late. That is risky.

Some content pages attract backlinks, assist product discovery, support collection rankings, and help customers choose. If they disappear or redirect poorly, the store loses more than blog traffic.

For each old WordPress post or guide, decide:

• keep and rebuild
• merge with a stronger guide
• redirect to a Shopify page or resource
• redirect to a collection if the content was commercial
• retire if outdated and unsupported by evidence

Do not redirect all blog posts to the blog homepage. That is the content equivalent of redirecting products to the homepage.

Existing redirects should be flattened

Old platforms often already have redirect rules from previous migrations, product changes, permalink edits, discontinued items and plugin settings.

If those redirects are imported blindly, the new Shopify store can inherit chains.

Example:

Old URL A → Old URL B → Old URL C → New Shopify URL

The new map should usually become:

Old URL A → New Shopify URL Old URL B → New Shopify URL Old URL C → New Shopify URL

Flattening chains reduces crawl waste, improves reliability and makes QA easier.

Shopify redirect rules affect the plan

Shopify supports URL redirects, including import and export, but it has platform rules that matter during planning.

The important practical point is this: do not build the redirect map as if Shopify were a blank server configuration file. Shopify has fixed path patterns and active URLs cannot always be redirected in the way a developer might expect from an Apache or Nginx migration.

That means the redirect plan should be checked before launch against:

• new Shopify URL handles
• active URLs
• restricted paths
• product and collection URL conventions
• whether destinations exist
• whether redirects can be imported cleanly
• whether theme/internal links point to final URLs rather than old paths

This is another reason the redirect map belongs early in the migration, not in the last week.

The minimum redirect mapping sheet

A serious redirect map should include at least these fields:

The notes column is not optional. It protects the team from revisiting the same argument later.

For a printable review pass before launch, use the Migration Redirect Risk Review.

Launch-day redirect QA

On launch day, do not only test the homepage and a few product URLs.

Test redirect behaviour in bulk:

1. Crawl the priority old URL list in list mode.
2. Check status codes.
3. Check final destination URLs.
4. Flag chains and loops.
5. Flag homepage redirects.
6. Flag irrelevant destinations.
7. Check whether final pages are indexable.
8. Check canonical targets.
9. Compare live destination to the redirect sheet.
10. Assign issues to owners.

The goal is not a perfect launch. The goal is finding the dangerous mistakes before Google and customers keep hitting them for weeks.

First 14 days after launch

Redirect QA continues after launch because some problems only appear once the new store is live and being crawled.

During the first 14 days, monitor:

• Search Console not found reports
• old high-value URLs still receiving impressions
• new landing pages receiving traffic
• ranking changes for priority collections
• backlinks resolving to correct destinations
• crawl reports for chains and loops
• internal links still pointing to old URLs
• sitemap and canonical consistency
• analytics landing-page anomalies

Do not panic over every fluctuation. Look for patterns by page type.

If old product URLs are failing, the product mapping needs attention. If old category URLs are softening, collection architecture may be weak. If old blog URLs disappear from assisted journeys, content migration may have been under-valued.

Common redirect mapping mistakes

Avoid these:

• mapping by URL similarity only
• redirecting too many pages to the homepage
• ignoring old blog and guide content
• ignoring old category/search/filter URLs
• importing old redirect chains without flattening
• treating all 404s as equal
• failing to test destination relevance
• redirecting to draft, noindex or canonical-confused pages
• changing Shopify handles after the map is complete
• leaving paid campaign and email URLs out of the map
• assuming the developer will “sort redirects” at the end

Where this fits in the migration plan

Redirect mapping belongs after the migration scope is clear and before launch QA starts.

Recommended sequence:

1. Start with the WooCommerce to Shopify migration guide.
2. Build the working plan with the WooCommerce to Shopify migration checklist that protects SEO.
3. Create this redirect map before launch.
4. Test it during the Shopify migration QA checklist before go-live.
5. Monitor crawl/index behaviour with Shopify migration crawl and indexing checks.
6. If traffic drops, diagnose the Shopify SEO traffic drop after migration before changing page templates.

Bottom line

A redirect map is not a technical afterthought. It is the migration’s memory.

It preserves what the old site earned, decides what should survive, and gives every valuable old URL a useful future.

If the map is weak, the new Shopify store starts life with avoidable confusion. If the map is strong, the migration has a much better chance of transferring search value cleanly.