Here's something worth knowing before you start: Google doesn't care which platform your website runs on. Moving to Webflow won't cost you rankings. Skipped redirects, forgotten blog posts and URLs that quietly changed shape will.
We're Digital Mast. We build websites exclusively in Webflow for businesses around the world, and we come from an SEO background. So when someone tells us "we'd love to move to Webflow, but we're terrified of losing our Google traffic", we don't wave it away. It's the right thing to worry about, and it's very fixable. This guide walks through how a WordPress to Webflow migration works when it's done properly, plus the shorter version for Wix and Squarespace sites.
Still deciding whether to move at all? Start with our honest Webflow vs WordPress comparison. This post is for once you've decided, and you'd like to arrive with your rankings intact.
When a move makes sense (and when to stay put)
Nobody migrates a website for fun. Usually something forces the issue:
- A redesign is overdue, and you'd be paying for a rebuild anyway
- Your team can't update the site without ringing a developer
- Plugin updates and security on WordPress have become a job in themselves
- You've outgrown a DIY builder like Wix or Squarespace and want a fully custom, professionally built site
- The site is slow, and fixes keep getting layered on top of fixes
If your current site loads quickly, ranks well, brings in enquiries and your team can manage it, there's no prize for moving. A migration is a project. It's worth doing when the new site will be meaningfully better, not just different.
What "losing rankings" actually means
People usually mean one of two very different things.
A temporary wobble. When URLs change, Google has to recrawl the old addresses, follow the redirects and work out that the new pages have replaced the old ones. Google's own site-move guidance says to expect ranking fluctuations while that happens, and that a small to medium-sized site can take a few weeks for most pages to move. That's normal, and it settles.
A permanent loss. This is the one that hurts, and it's nearly always self-inflicted. A page that ranked well now returns a 404, or gets bundled off to the homepage, so the links and history it built up go nowhere useful. Google says plainly that 301 redirects don't cause a loss in PageRank. The damage comes from missing or careless redirects, not from redirects themselves.
So the platform switch is the low-risk bit. The risk lives in the URL changes, and that risk is very manageable.
Step by step: a WordPress to Webflow migration with SEO safeguards
1. Take a Search Console baseline
Before anything changes, record where you stand in Google Search Console: your top pages by clicks, the queries they rank for and how many pages are indexed. Export it. Note your top landing pages and conversions in analytics too. Without a baseline, you can't tell a normal wobble from a real problem, and launch week turns into guesswork.
While you're in there, check how Search Console is verified. If it relies on a meta tag or an HTML file on the WordPress site, that verification disappears with the old site. A DNS-verified domain property carries on regardless, or you can add the tag to Webflow's Google site verification field before launch.
2. Build a full URL inventory
Crawl the current site with a tool such as Screaming Frog and list every URL that matters: pages, blog posts, category and tag archives, and any PDFs or images that earn traffic or links. Cross-check against your XML sitemap and the pages report in Search Console, because crawlers miss orphaned pages that Google still knows about.
Then flag the high-value URLs, the ones with organic traffic, conversions or backlinks from other websites. They get the most care.
3. Decide what stays, merges or goes
A migration is a great excuse for a tidy-up. For each URL, decide:
- Keep: move it across with its content, title and description intact
- Merge: fold thin or overlapping pages into one stronger page, and redirect all of them to it
- Retire: let genuinely worthless URLs (old test pages, empty tag archives) return a 404, which Google's guidance allows for content you're deliberately removing
Go gently on rewrites. Reworking a page that ranks well for its main keyword adds a second risk on top of the move. Google's advice is to change one thing at a time where you can, so save the big copy overhaul for after the dust settles.
4. Map every old URL to its new home
This is the heart of it: a spreadsheet with the old path in one column and the new path in the other. Every URL that changes gets a one-to-one 301 redirect to its closest equivalent. Not the homepage. Not the blog index. The page that actually replaces it.
WordPress URLs often change shape in Webflow, so expect plenty of rows:
- WordPress posts can sit at the root (
/my-post/), under dates (/2024/05/my-post/) or under categories. In Webflow, CMS items live under their Collection's folder, such as/blog/my-post, so root-level posts will get new URLs. - WordPress URLs often end in a trailing slash. Webflow's page URLs don't.
- Category, tag, author and paginated archives (
/page/2/) each need a decision: keep an equivalent, redirect to the nearest relevant page, or retire. - Sites still on WordPress's default "plain" permalinks use addresses like
/?p=123. Webflow can redirect those too, with a little escaping in the old path.
Where a whole folder moves and the slugs stay the same, one Webflow wildcard redirect can do the work of hundreds of rows. Webflow recommends a maximum of about 1,000 redirects as best practice, and using wildcards wherever possible.
5. Build and test in staging
Build the new site on its webflow.io staging address and keep it out of Google while you work, by turning staging indexing off (Site settings → SEO → Indexing) or password-protecting it.
Webflow is a professional visual development platform, with real HTML and CSS structure, a proper CMS and built-in SEO controls. It also has a real learning curve, which is why the build is where a Webflow expert earns their keep. Bring content across deliberately, page by page: titles, meta descriptions, headings, alt text and body copy. On the CMS, connect the SEO fields to the Collection template so every blog post gets its own title and description.
Rebuild any schema markup as well, and point internal links at the new final URLs, not old WordPress addresses that would bounce through a redirect.
6. Add the 301 redirects in Webflow
In Site settings → Publishing → 301 redirects, you can add redirects one at a time or import a CSV. Two things catch people out:
- A CSV import overwrites all existing redirects. Export your current list first, add the new rows to it, then import the combined file.
- Order matters. Webflow runs redirects in the order they were added, so specific redirects need to go in before broad wildcards.
301 redirects need a paid Site plan, or a site in a paid Workspace plan. Most business sites with a blog will be on Premium anyway, at $25 a month billed yearly or $39 billed monthly, plus applicable taxes. A site that doesn't need a CMS can use Basic, at $15 a month billed yearly.
7. Launch day
Connect the domain, set the default domain and global canonical, remove any staging-only noindex or password protection, and publish. Then:
- Test the old URLs, every high-value one at least, and check each lands on the right page in a single hop
- Submit the new sitemap in Search Console
- Use the URL Inspection tool on your most important pages
- Update the links you control: Google Business Profile, social profiles, email signatures and ad campaigns
Changing domain at the same time? Then use Search Console's Change of Address tool. If you're keeping the same domain, you don't need it.
8. Monitor, then keep the redirects
Over the following weeks, watch Search Console for spikes in "Not found" errors, compare clicks and impressions on your top pages with your baseline, and fix problems at the source. Where valuable links from other websites point at old URLs, ask the site owners to update them.
And keep the redirects. Google's guidance is to keep them for as long as possible, generally at least a year, and from a visitor's point of view, indefinitely.
Moving from Wix or Squarespace
The good news: Wix and Squarespace sites usually have fewer, simpler URLs than a WordPress site with years of archives behind it. The less exciting news: the redirect discipline is exactly the same.
- Wix blog posts default to
/post/your-post, and store products to/product-page/your-product. If your Webflow blog lives at/blog/and the slugs stay the same, one wildcard rule can often move every post. - Squarespace blog post URLs start with the blog page's slug (often
/blog/), and store products on version 7.1 include/p/. Plan for those patterns when you set up your Webflow Collections. - Content often needs more hands-on moving than it does from WordPress, so allow time to check titles, descriptions and alt text page by page.
Moving from a DIY builder to Webflow is a real step up: full design control, a proper CMS and professional SEO settings. And yes, we'll happily move a five-page Wix site. Small sites deserve good redirects too.
The mistakes that actually cost rankings
- Redirecting everything to the homepage. It's quick, it confuses visitors, and Google may treat it as a soft 404. Map each URL to its real equivalent.
- Forgetting blog posts. Old posts quietly pulling in long-tail traffic are the most common casualties. If it's in the inventory, it's in the map.
- Unbound CMS SEO fields. Every post ends up with the same title tag. Easy to fix, easy to miss.
- A CSV import that wipes earlier redirects. Export, merge, then import. Every time.
- No Search Console baseline. If you didn't measure before, you can't prove anything after.
- Leaving noindex on after launch. Google lists leftover noindex rules and robots.txt blocks among the most common site-move mistakes.
- Redirect chains. Old URL to an older redirect to the new URL. Point redirects and internal links straight at the final page.
For a deeper check once you're live, our guide to technical SEO audits covers what to look for, and our post on on-page optimisation covers the page-level basics worth carrying across.
How long until things settle?
Honestly, it varies, and anyone who guarantees a date is guessing. Google says it can take a few weeks or more for a medium-sized site's new URLs to replace the old ones in results, and longer for big sites. Googlebot also has to visit every old and new URL at least once before the move is complete. Webflow suggests checking your key pages at the one-, two- and four-week marks.
What you can control is the evidence. With a baseline, a redirect map and a few weeks of monitoring, you can tell the normal reshuffle from a specific page that needs fixing. A page that drops and stays down usually points to a missing redirect, a changed title, or content that didn't make the trip.
How we handle migrations at Digital Mast
Because we come from SEO, the migration plan starts before the design does. In practice, that means:
- A Search Console and analytics baseline, so we know exactly what we're protecting
- A full URL inventory, with your high-value pages flagged
- A redirect map you can see and sign off, including every "merge" and "retire" decision
- A custom Webflow build in staging, with CMS SEO fields, schema and internal links set up properly
- Redirects tested before and after launch, and Search Console monitored afterwards
You can see the kind of Webflow sites we build in our work for Habello, a new brand, site and blog for a fast house-buying company, and Experience Charters, a redesign with online booking for a Poole boat charter company. There's more on how we design and build websites and our SEO services.
Whether you're moving a WordPress site with years of blog posts or a five-page Squarespace site, the process is the same, and you're very welcome. Still choosing who to work with? Our guides on how to hire a Webflow expert, what a Webflow expert costs, Webflow freelancer vs agency and the questions to ask a Webflow developer will help. (Do ask whoever you hire how they'll handle your redirects.)
Ready to move without the drama?
Tell us what you're on now, roughly how big the site is, and what you'd like the new one to do. We'll tell you straight how we'd approach the move, and whether it's worth doing at all.
Talk to Digital Mast about your migration →
Frequently asked questions
Will I lose my Google rankings if I move to Webflow?
Not if the move is handled carefully. Rankings are lost through missing redirects, deleted pages and changed content, not because of the platform. Expect some temporary fluctuation while Google recrawls the site, then rankings should settle if every changed URL has a 301 redirect to its closest new page.
How do I set up 301 redirects in Webflow?
Go to Site settings, then Publishing, then 301 redirects. Add each old path and its new path one at a time, or import a CSV file, then publish the site. A CSV import overwrites all existing redirects, so export your current redirects first, add the new ones to that file, and import the combined list.
Do I need a paid Webflow plan to use 301 redirects?
Yes. Webflow says 301 redirects need a paid Site plan, or a site in a paid Workspace plan. Most business sites with a blog use the Premium plan, at $25 a month billed yearly or $39 billed monthly, plus applicable taxes.
How long does it take for rankings to settle after a migration?
It varies with the size of the site and how often Google crawls it. Google says a small to medium-sized site can take a few weeks for most pages to move, and larger sites take longer. Track your key pages in Search Console against a pre-launch baseline, and keep the redirects for as long as possible, generally at least a year.
Can I move a Wix or Squarespace site to Webflow?
Yes. Wix and Squarespace sites usually have fewer URLs than a large WordPress site, but they need the same care: list every URL, map each one to its new Webflow page, add 301 redirects, and carry titles and descriptions across. Wix blog posts default to a /post/ prefix, so a single wildcard redirect can often cover them.
Should I keep the same URLs when I migrate to Webflow?
Keep them where you can, because an unchanged URL needs no redirect. Some URLs will change, for example WordPress posts at the root of the site, which move under a Collection folder such as /blog/ in Webflow. Every URL that changes needs a 301 redirect to its closest new page.
Do I need a Webflow migration expert, or can I do it myself?
The SEO steps are a checklist any organised person can follow. The harder part is rebuilding the site properly in Webflow, which is a professional platform with a real learning curve, and getting the CMS, SEO fields and redirects right first time. If your site brings in enquiries from Google, whatever its size, it's worth having someone who has done it before.
Header photo by Serpstat on Pexels
