Redirects to the homepage
Thousands of old product URLs pointed at the homepage or a generic collection. Google treats most of them as soft 404s and the rankings go with them.
Shopify-only SEO: the technical base, the collection pages that earn revenue, and the content and links that push them up.
See allGet your store cited when shoppers ask ChatGPT, Google AI Mode and Perplexity what to buy.
See allTwo kinds of brands: Western brands selling $1,000+ products, and Chinese brands selling to the West.
See allA new platform should not cost you the rankings you spent years earning. We crawl every URL you have, map each one to its Shopify equivalent, check the new store before it goes live and watch Search Console for 90 days after launch.
Most lost traffic after a move to Shopify traces back to a handful of avoidable mistakes. Migrations commonly lose 10 to 30 percent of organic traffic when redirects are mishandled, and some never recover it.
Thousands of old product URLs pointed at the homepage or a generic collection. Google treats most of them as soft 404s and the rankings go with them.
Someone exported the best sellers and stopped. The long tail of old products, blog posts and image URLs that carried backlinks gets a 404.
Category copy, FAQs and size guides did not fit the new theme, so they were cut. The page keeps its URL and loses its reason to rank.
Product structured data, review stars and breadcrumb markup disappear with the old platform. Rich results fade within weeks.
A password page left on, a noindex copied from staging, or a robots rule carried over. Small switch, large damage.
The agency that built the store moves on. Crawl errors and dropped pages pile up in Search Console for months before anyone looks.
SEO teams usually count nine kinds of site migration. On Shopify, each one changes something different, and several often happen at once. The more you change in one launch, the harder it is to tell what caused a drop.
WooCommerce, Magento, BigCommerce, Salesforce Commerce Cloud or a custom build moves to Shopify. Every URL pattern changes because Shopify uses fixed prefixes like /products/ and /collections/.
Same URLs, new templates. Risks: copy removed from collection pages, headings rewritten, internal links lost from menus and footers, heavier JavaScript.
Renaming handles, merging collections or reshaping navigation on an existing Shopify store. Small on paper, large in Search Console if the redirects are skipped.
A rebrand, a move from a myshopify or marketplace-style name, or dropping a hyphenated domain. Needs redirects plus a change-of-address in Search Console.
shop.brand.com folds into brand.com, or a blog on WordPress moves under /blogs/ on Shopify. Authority can move with it if every URL is mapped.
Two brands, two stores or a legacy site merge into one. Overlapping products need a single winning URL and a decision on duplicate content.
Country stores or ccTLDs move into one store with Shopify Markets, using subfolders or domains. Hreflang, currency and redirects all change together.
Discontinued products, retired collections and thin blog posts get removed. Each one needs a redirect to the closest live page, or an honest 410 when nothing fits.
Moving to a headless Hydrogen storefront or a heavy app-driven theme. URLs may stay the same while what Googlebot can actually render changes.
We crawl the old site and pull every URL with clicks, impressions or backlinks from Search Console, Ahrefs and analytics. We save rankings, traffic and revenue by page type so there is a baseline to measure against.
Every old URL is matched to its closest Shopify equivalent: product to product, category to collection, post to article. Discontinued items go to the nearest relevant collection, never to the homepage.
We build the CSV Shopify imports, check it for chains, loops and reserved paths, and plan how query-string and filter URLs will be handled, since Shopify redirects cannot catch all of them.
Titles, meta descriptions, H1s, category copy, FAQs and internal links are carried over or improved, page by page. Nothing ranking today gets thinner by accident.
Product, Offer, AggregateRating, BreadcrumbList and Organization markup is rebuilt on the Shopify theme and validated, so rich results survive the move.
We crawl the unpublished store, test a sample of redirects, check canonicals, hreflang, robots.txt, sitemaps and page speed, and confirm the store is not indexable before launch.
Redirects imported, password removed, sitemaps submitted, key templates fetched with URL Inspection. We crawl the old URL list against the live store within hours.
Weekly checks on crawl errors, indexed pages, clicks by page type and revenue against the baseline. Anything that drops gets a named cause and a fix.
Every old URL with its clicks, impressions, backlinks and revenue, in one sheet.
Ready for Shopify import, checked for chains, loops and reserved paths.
Old and new title, meta, H1 and body word count for every indexable page.
Product, breadcrumb and organization markup validated on each template.
Who does what, in which order, with a rollback plan for each step.
Day 7, 30, 60 and 90 reports against the pre-launch baseline.
Each platform breaks in its own way. These pages cover the URL patterns, redirect details and data problems we see for each one.
A WooCommerce to Shopify migration that keeps your rankings: /product/ and /product-category/ URLs mapped one by one, Yoast data carried over, WordPress blog moved without losing its links.
Magento to ShopifyMagento and Adobe Commerce to Shopify migrations that protect rankings: .html URLs, category-path duplicates, layered navigation parameters, store views and years of old URL rewrites all mapped.
BigCommerce to ShopifyBigCommerce to Shopify migrations that keep rankings: root-level short URLs, legacy .html paths, brand pages, faceted search parameters and custom fields all planned before launch.
Shopify Plus migrationSEO for Shopify Plus migrations: upgrading to Plus, consolidating several stores into one, and moving country expansion stores into Shopify Markets without losing rankings.
Salesforce Commerce Cloud to ShopifySalesforce Commerce Cloud to Shopify migrations that protect enterprise rankings: product-ID URLs, locale paths, variation parameters, static mappings and multi-site setups mapped before launch.
Amazon to ShopifyFor Amazon sellers, often Chinese brands, launching a Shopify brand site that ranks on Google and shows up in AI answers: listing data rewritten for search, A+ content rebuilt, brand facts made consistent.
Shopify handles 301 redirects well, but it has rules that catch teams out. We plan around them before the first line of the redirect map is written.
Redirects are managed in the Shopify admin under Content, Menus, URL redirects, or imported as a CSV with "Redirect from" and "Redirect to" columns. Standard plans allow up to 100,000 redirects. Shopify Plus allows up to 20 million. A store with 30,000 products, five years of blog posts and a few thousand image URLs can get close to the standard limit faster than you would think, so we remove chains and redundant rules first.
A Shopify redirect only works when the old path returns a 404 on the new store. If a page, product or collection already exists at that path, the live page wins and the redirect is ignored. This matters when old and new URLs overlap, which happens often with WooCommerce and BigCommerce stores that already used short slugs.
Some paths are reserved and cannot be redirected, including /collections/all, /collections/vendors and /collections/types. Collection tag URLs such as /collections/sofas/leather cannot be redirected either, because Shopify still treats them as valid pages. URLs with query strings, like faceted-search parameters from Magento or BigCommerce, "might not work as expected" in Shopify's own words. We handle those with canonical tags, clean internal links and, where needed, a theme or app-level rule.
If you sell in several markets with Shopify Markets subfolders, a redirect created on the primary domain covers the market subfolders too, but a locale-specific redirect needs its own rule for each subfolder. International moves get their own section in the map. For the wider picture on markets, see international SEO.
We also write about migrations on the migrations blog. If you are rebuilding the store at the same time, our Shopify development team builds SEO-first from day one.
It depends on how much changes at once and how carefully URLs are mapped. A well-planned replatform often sees a short wobble of a few weeks while Google recrawls, then recovers. Migrations with incomplete redirects commonly lose 10 to 30 percent of organic traffic, sometimes for good. We cannot guarantee a flat line, but we measure against your pre-launch baseline and fix every drop we can trace.
Ideally before the new store is designed, and at the latest six to eight weeks before launch. That gives time to crawl the old site, agree on collection structure, build the redirect map and check content parity on staging. Teams that call us after launch can still be helped, but some ranking loss is harder to reverse once Google has recrawled broken URLs.
Our focus is the search side: URL mapping, redirects, content and schema parity, QA and monitoring. We work alongside your developer or migration app, or our Shopify development team can build the store SEO-first. Either way, we own the checklist of what must be true on launch day for rankings to survive.
No. You can connect your existing domain to Shopify, and in most cases you should. Keeping the domain removes one whole layer of risk. If a rebrand requires a new domain, we treat it as a second migration: domain-level redirects, a change-of-address request in Search Console and a longer monitoring window.
Most stores see Google recrawl their important pages within two to four weeks, and positions settle over one to three months. Large catalogs take longer because Google recrawls deep product pages less often. We report at day 7, 30, 60 and 90, and keep monitoring beyond that if pages are still moving.
The cheapest time to protect your rankings is before the build starts. Send us your current domain and target launch date and we will tell you what the migration needs.