How to migrate to Webflow without losing SEO?

Migrating to Webflow does not have to cost you rankings - but it will if you skip the technical groundwork. The two biggest SEO risks in a Webflow migration are broken redirects and CMS structure changes that alter URL patterns. Get those right and most sites maintain or improve their organic performance within 60 to 90 days of launch. Here is what the process actually looks like.

How to switch to Webflow without losing SEO?

A lot has been written about Webflow migrations going wrong. Most of it skips the detail that matters: not whether Webflow is capable of supporting good SEO - it is - but whether the migration itself was executed in a way that preserves what was already working.

We've run migrations for B2B SaaS companies ranging from 40-page sites to 300-page platforms with complex CMS structures, HubSpot integrations, and years of accumulated URL debt. The sites that come out with their organic traffic intact are not the ones built on luck. They're the ones where someone mapped every redirect, audited the CMS structure before touching a single template, and ran a full crawl before the DNS transfer.

This guide covers the full process - the risks, the fixes, and the checklist we use on every migration.

Why do sites lose rankings during a migration - and is Webflow more at risk?

Sites lose rankings during migrations for three reasons: URL structure changes that break inbound links and redirect equity, crawlability gaps during the transition period, and metadata that gets lost or rewritten badly during the rebuild.

Webflow is not inherently more risky than any other platform. If anything, its performance characteristics - fast CDN, clean HTML output, automatic sitemap generation - give migrated sites a structural advantage. The risk comes from how migrations are executed, not from the platform itself.

The specific Webflow consideration worth knowing: the CMS enforces URL slug patterns at the collection level. A blog post that lived at 

/blog/my-post-title  →  automatically becomes  /resources/my-post-title  (or whatever your collection slug is)

If you don't account for that in your redirect mapping - and many agencies don't - you will break every inbound link and internal link pointing to those URLs. That's where most Webflow migration SEO losses actually come from.

What are the biggest SEO risks in a Webflow migration?

Here are the five issues we see most often, in order of how damaging they tend to be.

1. Redirect mapping errors

This is the single most common cause of post-migration ranking drops. A redirect map that looks complete on paper often isn't - because sites accumulate URLs over time that never made it into any sitemap. Old campaign landing pages. Renamed blog posts. Redirected redirects. Legacy product pages.

On a recent 180-page migration, our crawl surfaced 340 redirect mappings. The client's original URL export contained 94. The other 246 were URLs generating backlink equity that would have gone dark without the crawl.

Fix: crawl the live site with Screaming Frog or Ahrefs before starting the build. Export every URL with incoming links. Map all of them, not just the ones in your sitemap.

2. CMS slug structure conflicts

As described above: Webflow CMS collections assign slugs based on collection name. If your WordPress site had posts at /blog/[slug] and you create a Webflow collection called "resources," every post URL changes. Those are different URLs as far as Google is concerned - even if the content is identical.

Fix: name your Webflow CMS collection to match the URL pattern of the source site. Or map every old URL to its new equivalent and implement 301s before launch. Both work. Skipping this step does not.

3. Page speed regression

Webflow sites are generally fast. But a migration that imports heavy images, adds unnecessary animations, and includes multiple third-party scripts can end up slower than the site it replaced - especially if the previous site was already well-optimised.

Core Web Vitals are a ranking factor. A post-migration site with an LCP above 4 seconds will take a performance hit regardless of how clean the redirect map is.

Fix: run a Lighthouse audit on the live site before migration starts. Use that as your performance baseline and build to beat it, not just match it.

4. Metadata loss

Title tags, meta descriptions, Open Graph data, and canonical tags do not migrate automatically. If you are moving from WordPress, your existing metadata is sitting in a plugin (usually Yoast or RankMath) that has no direct equivalent in Webflow.

Fix: export all metadata from the source CMS before the build starts. Map it to Webflow's SEO fields during the migration. Verify every page against the export after launch.

5. Staging environment crawl blocks

This one sounds obvious but it still catches teams out. Webflow's staging environment is blocked from search engine indexing by default - which is correct. The problem is when that block doesn't get removed before the DNS transfer, or when the live site inherits a robots.txt from the staging configuration.

Fix: check robots.txt and the Webflow noindex setting as part of your pre-launch checklist. Do not launch without confirming that the live domain is indexable.

How do you handle 301 redirects in a Webflow migration?

Webflow has a built-in redirect manager in the Hosting settings. For most migrations it handles the load fine - you can import redirects in bulk via CSV, which makes it practical for large redirect maps.

Two limitations worth knowing:

• Webflow's redirect manager does not support wildcard redirects or regex patterns. If you need to redirect an entire URL structure (e.g., all URLs starting with /old-blog/* to /resources/*), you'll need a workaround - typically a Cloudflare Page Rule, a middleware layer, or a JavaScript-based redirect at the edge.
• Webflow also has a redirect limit that varies by plan. Enterprise plans have significantly higher limits. For large sites with hundreds of legacy URLs, this is worth checking before you start building the redirect map.

‍

Here is the redirect process we use on every migration:

1. Crawl the live site and export every URL - not just the sitemap
2. Cross-reference the crawl against Ahrefs or Semrush to identify URLs with backlink equity
3. Map every source URL to its destination in a spreadsheet, with a column flagging whether the URL has backlinks, internal links, or both
4. Build the Webflow site using URL structures that minimise the redirect volume - every URL you can preserve is one fewer redirect to manage
5. Import the redirect map into Webflow's redirect manager before the DNS transfer
6. After launch, crawl the site again and verify every redirect returns a 301 (not a chain of redirects, not a 302)

‍

Does Webflow support the technical SEO requirements for a B2B site?

It does. Here is a quick reference for the features that matter most, and where the limits are.

‍

The one area that sometimes surprises teams: structured data. If you need breadcrumb schema, FAQ schema, or product schema, these need to be added as custom code embeds. Webflow does not generate them automatically. This is also a very imporant issue for AI search visibility and a huge part of Webflow technical AEO optimisation.

How do you rebuild CMS structure in Webflow without breaking URL patterns?

The CMS structure decision is one of the first you need to make, because it affects URL patterns, template design, and the redirect map. Do it wrong and you're creating extra work at every stage.

The key question: does the new site's URL structure need to match the old one exactly, or is a clean break acceptable?

When to preserve existing URL patterns

Preserve the existing structure when the site has significant backlink equity distributed across many URLs, when the existing URL patterns are clean and logical, or when the migration timeline is short and there's no appetite for a large redirect mapping exercise.

In Webflow, you do this by naming your CMS collections to match the existing URL structure. If your blog lived at /blog/[slug], create a Webflow collection called "blog." If resources lived at /resources/[slug], name the collection "resources." This preserves URLs at the collection level without any redirect mapping needed for those pages.

When a clean break makes sense

A clean break makes sense when the existing URL structure is disorganised, when the site is consolidating content from multiple collections into a new information architecture, or when there is a parallel rebrand or redesign happening alongside the migration.

In this case, build the new structure from scratch in Webflow, map every old URL to its new equivalent, and implement 301s. It is more work upfront, but it's the right approach when the old URL patterns are not worth preserving.

Whatever you choose, document the decision and the rationale before the build starts. It affects scope, timeline, and the redirect map - and it is the kind of decision that causes problems when it gets revisited halfway through a migration.

What does SEO recovery look like after a Webflow migration - and how long does it take?

Expecting some short-term volatility is the right starting position. Even a technically clean migration will typically show some movement in rankings during the first four weeks as Google recrawls and reindexes the site. This is normal. It is not a signal that something went wrong.

Here is what recovery typically looks like based on migrations we've run:

‍

The sites that recover slowly - or don't fully recover - usually have one of two problems: a redirect map that was incomplete at launch, or a crawl error that wasn't caught before the DNS transfer. Both are avoidable with the right pre-launch process.

Worth noting: the 60 to 90 day recovery window assumes you started with a solid baseline. If the source site had existing technical SEO issues - broken internal links, duplicate content, thin pages - the migration is an opportunity to fix them. Sites that went into the migration with clean technical foundations and came out with clean foundations recovered fastest.

Webflow migration SEO checklist

This is the checklist we work through on every migration. It is not exhaustive - every site has its own quirks - but it covers the things that most commonly go wrong.

Before the migration

• Crawl the live site - use Screaming Frog, Ahrefs, or a similar tool. Export every URL.
• Identify URLs with backlink equity - cross-reference the crawl against Ahrefs or Semrush. Flag these for priority redirect treatment.
• Export all metadata - title tags, meta descriptions, canonical URLs, and OG data from the source CMS. This is your mapping document.
• Snapshot current rankings - take a position snapshot in Semrush or Ahrefs before any changes. This is your recovery benchmark.
• Map all redirects - source URL to destination URL, every one. Flag chains and broken existing redirects to clean up during the migration.
• Decide on CMS slug structure - preserve existing URL patterns or document the new ones and build the redirect map accordingly.
• Run a Lighthouse audit - record Core Web Vitals on the source site. Build to match or exceed them.

‍

During the migration

• Build on staging with noindex enabled - Webflow does this by default. Verify it is active before anyone shares the staging URL externally.
• Map all metadata into Webflow - title tags and meta descriptions per page. For CMS collections, use dynamic field bindings from your content fields.
• Rebuild internal linking - check that all internal links point to the correct destination URLs on the new site, not the old ones.
• Import the redirect map - into Webflow's redirect manager via CSV before go-live. Verify the import completed without errors.
• Set up GSC for the new domain - if the domain is changing, add it as a new property in Google Search Console before launch. If the domain is the same, verify the existing property is still active.

‍

After launch

• Verify the live site is indexable - check robots.txt, confirm the Webflow noindex setting is off, and do a site: search in Google within 24 hours of launch.
• Crawl the live site - run a full crawl of the new site immediately after launch. Check for broken links, redirect chains, and any 404s that weren't anticipated.
• Verify every redirect - use a bulk redirect checker to confirm every 301 in your map is returning the correct response code. Redirect chains (301 → 301 → destination) should be collapsed to single hops.
• Submit the sitemap in GSC - submit the new XML sitemap and request indexing for key pages.
• Monitor GSC coverage for 30 days - watch for crawl errors, indexed but not submitted pages, and any pages dropping from the index unexpectedly.
• Re-run Lighthouse - verify Core Web Vitals on the live domain. Fix anything that regressed from the pre-migration baseline.

Planning a Webflow migration?

We've run migrations for B2B SaaS companies from 40-page sites to 300-page platforms. If you want to know what your migration would actually involve - timeline, cost, risk areas, and what we'd do differently from most agencies - we can give you a straight answer in a 30-minute call.

Talk to our team about your migration.