Field guide · technical workflow
Map Magento catalogue URLs before a Shopify cutover
A Magento catalogue and a Shopify storefront may express products and collections through different URL structures. A successful import of inventory does not prove that the former search landing pages now reach relevant destinations. Build a specific URL map first.
Who this is for: Help an ecommerce migration owner avoid losing valuable Magento category and product paths when moving to Shopify.
Editorial preview — facts, worked examples and publication approval are still being checked.
The practical problem
A practical map magento catalogue urls before a shopify cutover exercise: Build an old Magento URL inventory from real traffic and crawl sources. The outcome is a documented decision backed by approve semantic product/category successors instead of guessing from url patterns. The final check is to test redirects, canonical targets and reachable products before and after cutover.
What you will be able to check
- Build an old Magento URL inventory from real traffic and crawl sources.
- Approve semantic product/category successors instead of guessing from URL patterns.
- Test redirects, canonical targets and reachable products before and after cutover.
Reproducible scenario
Worked example: Map Magento catalogue URLs before a Shopify cutover
A hypothetical enterprise retailer moves its catalogue from Magento to Shopify. The Magento site contains product paths under categories, category landing pages, an older promotional collection and several products with historic inbound links. The Shopify export has the products, but many old addresses have no obvious matching route. The migration owner must decide where each visitor will land rather than assuming that a completed product import is a completed SEO migration.
Starting assumptions
- A pre-move crawl and Search Console landing-page export are available for the Magento hostname.
- The planned Shopify collection and product routes can be inspected in a staging environment before switching production traffic.
Decisions and checks
Separate Magento product and category source paths
Take a representative range including direct product URLs, category-product routes and layered filters. Record the old page's buying purpose, source traffic and any historical redirect. An automatic slug transformation can map a product to an unrelated Shopify collection.
What to verify: A deduplicated source inventory with one actual source URL and commercial role per mapping decision.
Choose Shopify successor routes by meaning, not matching slug fragments
An old category should arrive at a Shopify collection that genuinely represents the same product family. For discontinued products, document real replacement or removal decisions. A generic /products/ prefix replacement does not solve URL identity or category consolidation.
What to verify: Each priority old path receives an approved destination with a written relevance rationale and checked visible content.
Test redirects and templates before and after platform cutover
Request old source URLs, record each Location header and inspect Shopify destination content and canonical. Include a few product variants and collection pagination routes. After launch, replay the identical sample on production and retain rollback ownership.
What to verify: A real HTTP and HTML acceptance report shows the selected product and category routes reach relevant, crawlable destinations.
Expected output: The migration output should be a reviewed source-to-destination register, verified product route samples and a production retest schedule. The new platform must preserve real customer intents, including older pages that no longer appear in top navigation. A technically valid redirect sheet still needs a working destination and accurate product information.
This magento to shopify redirect audit migration story is hypothetical and is not an observed client cutover or verified ranking result.
Export source URLs by commercial function
Join source crawls, Search Console landing pages, sitemap exports and where available historic redirect records. Group the old Magento URLs into product, category, CMS, filter and retired content classes. Record each class before attempting to match it to a Shopify route.
Reference: official · 2026-11-07
Compare destinations rather than slug similarity
For a valuable old category, confirm that its Shopify collection provides a corresponding set of products and buyer intent. For a discontinued product, determine whether a truthful successor exists. Avoid automating redirects purely by string replacement, which can connect unrelated catalogues or omit special routes.
Reference: official · 2026-11-07
Rehearse and retest the cutover
For each mapping row, test the old response, final destination, rendered canonical, internal links and availability in a controlled release rehearsal. Flag any old URL without a defensible decision. Retest the priority sample after DNS and storefront changes, and keep a named recovery owner.
Reference: official · 2026-11-07
Decision aid
Decision table: Magento to Shopify SEO: redirect mapping audit
| Legacy issue or URL class | Relevant decision | Real evidence required |
|---|---|---|
| Old Magento category has an equivalent Shopify collection | Map to the relevant collection and preserve distinct buyer intent. | Compare old category content and new collection assortment. |
| Old product route and category-product alias refer to one item | Consolidate toward a coherent product destination without losing relevant source links. | Check both old redirects, new product identity and canonical. |
| Retired Magento filter URL has no useful unique content | Make an explicit removal or parent-category decision rather than inventing a landing page. | Inspect original query use, status, filter value and successor relevance. |
What a passing test looks like
These checks describe the evidence that should exist after a real implementation. They are not reports of tests already completed on a customer website.
Separate Magento product and category source paths
Expected result: A deduplicated source inventory with one actual source URL and commercial role per mapping decision.
Keep as evidence: Archive the exact source URL requests, final destination and reviewer signoff for separate magento product and category source paths.
Choose Shopify successor routes by meaning, not matching slug fragments
Expected result: Each priority old path receives an approved destination with a written relevance rationale and checked visible content.
Keep as evidence: Archive the exact source URL requests, final destination and reviewer signoff for choose shopify successor routes by meaning, not matching slug fragments.
Test redirects and templates before and after platform cutover
Expected result: A real HTTP and HTML acceptance report shows the selected product and category routes reach relevant, crawlable destinations.
Keep as evidence: Archive the exact source URL requests, final destination and reviewer signoff for test redirects and templates before and after platform cutover.
Scope and limitations
This example does not describe a verified Magento or Shopify installation, actual app support or inventory size. Routes and required redirects vary with site customisations. Mapping by string patterns can create irrelevant targets, so first-party URLs, source evidence and on-platform tests are mandatory.
Sources and verification
These references explain documented technical behaviour. The worked decisions are illustrative until checked on your own installation.
- official reference — Google's site move guidance recommends old-to-new URL mapping, relevant permanent redirects and monitoring after URL changes. Recorded: 2026-11-07