Moving platforms changes every URL, template, and tag on your site. Here's the process I use so the rankings you've already earned come with you.
Most SEO losses after a migration aren't caused by the new platform. Shopify is perfectly capable of ranking. They're caused by three avoidable things: old URLs that lead nowhere, titles and content that quietly change in transit, and nobody checking the results after launch.
The principle behind everything below is simple. Search engines need to find every important old page, land on its closest new equivalent, and find the same content and signals when they arrive. A migration that does that keeps most of what it had. One that doesn't spends months recovering.
On a Webflow-to-Shopify migration for a motorcycle brand, I audited the Webflow storefront first and then built the product import with Matrixify. This is the process I follow, in five phases: baseline, map, build, launch, monitor.
First: Does the Whole Site Need to Move?
Before planning redirects, check whether a full migration is actually the right call. Many brands keep Webflow for the marketing site, the blog, and the landing pages, and move only the store to Shopify.
That changes the SEO plan significantly. Your blog and brand pages stay put, and the redirects only need to cover commerce URLs: products, categories, and anything tied to the cart. Less moves, so less can go wrong. If your marketing content ranks well and your problem is store functionality, this split is worth considering. It's the kind of architecture I cover under Webflow development alongside the Shopify build.
If you are moving everything, the rest of this post applies in full.
Phase 1: Baseline Everything Before You Touch Anything
You can't tell whether a migration worked without a record of what you had. Capture this before any build work begins:
A full crawl of the Webflow site. Use Screaming Frog or a similar crawler. Export every URL with its status code, title tag, meta description, H1, canonical, and indexability. This spreadsheet becomes the source of truth for everything that follows. Don't rely on the Webflow designer's page list, because it won't show you everything search engines have indexed.
Search Console data. Export top pages and top queries. Search Console only keeps around sixteen months of data, so export it now rather than after launch.
Analytics by landing page. Pull organic sessions and revenue by landing page from GA4. This tells you which pages actually earn money, which is not always the same as which pages get traffic.
Backlinks. Export the pages on your site that have external links pointing at them (Search Console's links report is free, and paid tools show more). These URLs must redirect precisely, because they carry authority from other sites.
Existing Webflow redirects. Copy out everything in Webflow's 301 redirect settings. Redirects that live in Webflow stop working the moment your domain points at Shopify, so every one has to be rebuilt.
Custom code. Note everything in Webflow's head and footer code: analytics, ad pixels, schema markup, verification tags. None of it carries over automatically.
Then rank your pages. Anything with organic traffic, revenue, or backlinks is tier one. These get hand-checked at launch. Everything else is tier two.
One more thing worth doing at this stage: audit the conversion flow of the existing store. A migration is the cheapest moment to fix leaks you'd otherwise carry across to the new platform. A CRO and website audit done before the build means the new store launches better than the old one, not merely equal to it.
Phase 2: Map the URLs
This is the phase that decides most of the outcome. Webflow and Shopify structure their URLs differently, so a large share of your pages will change address.
Typical patterns look like this, though your crawl is the source of truth because Webflow setups vary:
| Page type | Typical Webflow URL | Shopify URL |
|---|---|---|
| Homepage | / |
/ |
| Product | /product/slug |
/products/handle |
| Category | /category/slug |
/collections/handle |
| Blog post | /blog/slug |
/blogs/blog-handle/slug |
| Static page | /about |
/pages/about |
Shopify's prefixes (/products/, /collections/, /pages/, /blogs/) are fixed. You can't remove them, so every one of these URLs needs a redirect.
Keep slugs identical to handles wherever you can. If the Webflow product slug is carbon-slip-on-exhaust, make the Shopify handle carbon-slip-on-exhaust. The mapping becomes mechanical, and mechanical means fewer mistakes.
Build the redirect map in a spreadsheet. Columns: old URL, new URL, page type, priority tier, notes. Shopify redirects are exact-path matches and, in the built-in tool, there are no wildcards. You can't write "send everything under /product/ to /products/" as one rule. Generate the full list with a spreadsheet formula instead. If you need pattern-based rules, redirect apps support them.
Import in bulk. Shopify accepts a CSV with two columns, "Redirect from" and "Redirect to", using relative paths that start with a slash. Matrixify can also import redirects as part of the same migration job. Check the current redirect limit for your plan against the size of your list, because standard plans have a cap.
Redirect to the closest equivalent, not the homepage. When a product won't exist on the new store, send it to the most relevant collection or a similar product. Mass redirects to the homepage can be treated by Google as soft 404s, and the visitor who arrives gets nothing useful anyway.
Flatten chains. If an old Webflow redirect sends A to B, and B is now being redirected to C, update A to go straight to C. Chains slow things down and leak authority.
Remember images. Image files on Webflow's CDN can't be redirected to Shopify's CDN. If images bring you search traffic, expect some movement. Keep file names descriptive and alt text intact on the new store to give those images the best chance.
Phase 3: Build for SEO Parity
The goal on the new store is parity first, improvement second. Rebuild what's ranking before you try to make it better.
Match titles, descriptions, and H1s. Take them straight from the baseline crawl. In Shopify, each product, collection, page, and blog post has its own search engine listing fields. If you're using Matrixify for the product import, SEO title and description can be imported in the same sheet instead of being typed in by hand.
Migrate the catalogue deliberately. Webflow lets you export products as CSV from the Ecommerce panel. Map that export to Shopify's structure, with particular attention to variants and options, which Webflow and Shopify model differently. Shopify's native importer handles simple catalogues. Matrixify handles complex ones, including metafields. Check the plan limits against your catalogue size, because the free tier only covers a small number of items per file.
Move the blog and pages. Export Webflow CMS collections as CSV, then import them into Shopify blogs and pages. Preserve publish dates and slugs. Blog URLs will change shape because of the /blogs/ prefix, so they need redirects like everything else.
Rebuild structured data. Shopify themes include product schema out of the box, but Webflow custom code won't carry over. Test product pages in Google's Rich Results Test, and re-add any Article, FAQ, or Organization schema you were using.
Re-implement tracking. Recreate analytics, conversion tracking, and ad pixels deliberately, and test that they fire. Missing tracking after launch makes every later comparison unreliable.
Update internal links. Links inside your content that point to old URLs should be rewritten to the new ones. Redirects work, but internal links that rely on redirects waste crawl budget and slow pages down.
Check the theme's speed on staging. Premium themes plus a pile of apps is how many Shopify stores end up slower than the Webflow site they replaced. Test Core Web Vitals before launch, not after.
Resist changing everything at once. If rankings matter, don't rewrite all copy, restructure all URLs, and redesign every template on the same day you switch platforms. Migrate like-for-like first, then iterate. If you are redesigning, keep the content and headings of your top-ranking pages as close to the original as you can.
Phase 4: The Launch Checklist
Before the cutover:
- Import the full redirect list before pointing the domain, so redirects are live the moment traffic arrives
- Lower your DNS TTL a day or two ahead so the change propagates quickly
- Pick a low-traffic window, avoid launching just before a peak sales period, and don't launch when no one can monitor it
- Freeze content changes on the Webflow site during the migration window, so nothing new needs redirecting at the last minute
At the cutover:
- Update DNS using the values shown in Shopify's domain settings, and confirm HTTPS works on both the root domain and www
- Set the primary domain so one version of the URL is canonical
- Remove the storefront password. A password-protected store can't be crawled, and leaving it on after launch is one of the most damaging mistakes on this list
Immediately after:
- Crawl your tier-one URLs from the redirect map and confirm each returns a 301 to a page that returns a 200, with no chains
- Submit the new sitemap (
/sitemap.xml) in Search Console - If the domain name has stayed the same, you don't need Search Console's change-of-address tool. That's only for moving to a different domain
- Keep the Webflow project as a backup until you're confident the redirects are working. Don't delete anything yet
Phase 5: Monitor for the First 90 Days
Launch isn't the finish line. Most recoverable problems get found in the first few weeks, and only if someone is looking.
Daily in the first week:
- Search Console's page indexing report, for new 404s, redirect errors, and pages excluded unexpectedly
- Crawl errors on tier-one URLs
- GA4 organic landing pages compared against your baseline
Weekly after that:
- Clicks and impressions for top pages and queries, compared against your pre-migration export
- Rankings for your priority keywords
- A fresh crawl to catch redirect chains, broken internal links, and canonical problems
When you find a 404 that had traffic or backlinks, add the redirect immediately and note it for the next review.
Some movement in rankings in the weeks after a migration is normal while search engines reprocess the site. What matters is the pattern. A sustained drop on pages you redirected correctly points to something else: changed titles, thinner content, slower pages, or weaker internal linking. Compare against the baseline and investigate those first.
The Mistakes I See Most Often
If you only take a short list from this post, take this one:
- Redirecting everything to the homepage instead of mapping page by page
- Leaving the storefront password on after launch
- Forgetting the blog, or forgetting that blog URLs change
- Ignoring old Webflow redirects, which then break or form chains
- Rewriting titles and content during the move, so you can't tell what caused any drop
- Losing tracking and structured data because it lived in Webflow custom code
- Launching with no baseline to compare against
- Deleting the old site before the redirects are verified
Every one of these is preventable with the spreadsheet from Phase 1 and the crawl from Phase 4.
The Principle Underneath
A migration is a data problem more than a design problem. Everything that earned you rankings, the URLs, the titles, the content, the links pointing in, has to arrive intact at the other end. The store you're moving to can be better than the one you're leaving. But it can only inherit the old one's search performance if you treat the move as something to be mapped, built, verified, and monitored, rather than something that happens on launch day.
If you're planning a move from Webflow and want it handled with the SEO work built in, I do Shopify development and migrations through Webko, and I offer a free three-page mockup so you can see the new design before committing to anything.
I'm a freelance web designer and developer specializing in Shopify web design and Webflow development for e-commerce brands globally. I run Webko, a web design studio focused on high-converting e-commerce storefronts.
Top comments (0)