How to Migrate from WordPress to Webflow Without Breaking SEO

Map every URL, content type and plugin before you build, rebuild the content in Webflow's CMS, redirect every URL that changes, and check indexing after launch.

Key takeaways

• Most SEO losses in a WordPress to Webflow migration come from changed URLs, missing 301 redirects and lost metadata, not from Webflow itself.
• Webflow CMS items always sit under a collection path like /blog/, so WordPress posts that live at the root of the domain need redirects.
• Plugins don't migrate. Each one is replaced by a native Webflow feature, an integration, or dropped.
• Content comes across as a CSV import into CMS collections, theme and page builder layouts are rebuilt, not converted.
• Treat the move as a rebuild of the content model, not a one-to-one copy. That is how Beqi moved Loom's marketing site to Webflow in three weeks.

This guide is for marketing teams moving a WordPress site to Webflow who can't afford to lose the organic traffic they have built. It follows the work in the order it happens: before the build, during it, and after launch.

If you would rather hand the move over, see how Beqi runs Webflow migrations.

What breaks SEO in a WordPress to Webflow migration?

Four things, and none of them is the platform: URLs that change without a redirect, SEO titles and descriptions that don't carry over, internal links that point to old paths, and pages left blocked from indexing at launch.

WordPress keeps most SEO settings inside plugins like Yoast or Rank Math. When the site moves, that data stays behind unless someone exports it and maps it to Webflow fields. The same goes for redirects WordPress was already handling through a plugin, which disappear with it.

What should you do before you start building?

Record what exists and what performs, so you know exactly what has to survive the move.

1. Crawl the live site: export every URL, its title, meta description, H1 and canonical with a crawler such as Screaming Frog, plus the URLs in your XML sitemap.
2. Save a baseline: export the top pages and queries from Google Search Console for the last 3 to 6 months. These are the pages you protect first.
3. List content types: posts, pages, categories, tags, authors and any custom post types, each with its fields.
4. List plugins: note what each one does on the live site, so you can decide how Webflow will handle it.

How do you export content from WordPress?

WordPress exports XML by default (Tools > Export), and Webflow imports CSV, so convert the file with an XML to CSV converter or use an export plugin that writes CSV directly. Include the slug, title, body, SEO title, meta description, featured image URL, category, author and publish date for every item. Dates import cleanly in YYYY-MM-DD format.

How do you rebuild WordPress content in Webflow's CMS?

Create one CMS collection per content type, add a field for everything you exported, then import the CSV into each collection. Webflow can't create collections during an import, so the structure has to exist first.

Import categories and authors first: reference fields match on slugs, so posts can only link to items that already exist. Keep the WordPress site online during the import, because Webflow fetches images from their public URLs and stores them on its own CDN. Imported items arrive as drafts, which gives you a review step before anything goes live.

Then clean the rich text. Basic formatting and links come across, but WordPress shortcodes, page builder blocks and inline styles turn into stray code, and each affected post needs a pass. Update internal links in the body to the new URLs while you are in there.

Kreshnik's take: Most WordPress sites we take over aren't slow or fragile because of WordPress. They are that way because of years of plugins, themes and shortcuts stacked on top of each other. Copy that 1:1 and you have moved the problem to a new platform. Use the migration to rebuild the content model properly, the first time: merge thin posts, drop dead categories, and redirect what you remove.

Should you keep the same URL structure?

Keep slugs identical wherever you can, and change paths only where Webflow requires it. Static pages can keep their exact paths. CMS items can't sit at the root of the domain, so posts at /post-name/ will move to something like /blog/post-name and need a redirect each. Decide the collection path once, before import, and keep it.

How do you set up 301 redirects in Webflow?

Add them under Site settings > Publishing > 301 redirects, one old path and one new path per rule, then publish. For a full migration, import them all at once from a two-column CSV of old and new paths.

• Export before you import: a CSV import overwrites every existing redirect, so export the current list first if the site already has some.
• Redirect to the closest match: send each old URL to the page that replaced it. Redirecting everything to the homepage wastes the links and rankings those pages earned.
• Use wildcards for whole folders: a rule like “/2023/(.*) to /blog/%1” moves every post from a date-based path in one line. Webflow recommends wildcards to keep the total under about 1,000 rules.
• Order matters: Webflow runs redirects in the order they were added, so add specific rules before the wildcards that would otherwise catch them.
• Avoid chains: each old URL should go straight to its final destination in one hop.
• Don't forget media: important images and PDFs under /wp-content/uploads/ can be redirected too, if they rank or are linked from other sites.

How do you check SEO before and after launch?

Check the staging site before you switch DNS, then crawl the old URL list again once the new site is live.

Before launch, confirm every page has a title, meta description and H1, that indexing is enabled for the production domain, and that forms and tracking fire. After launch:

1. Crawl the old URLs: every one should return a single 301 to a live page.
2. Submit the sitemap: add the new sitemap.xml in Google Search Console and inspect your top pages. Webflow's sitemap now carries a last-modified date for every page, which helps search engines recrawl what changed.
3. Compare against the baseline: check clicks and impressions for the protected pages every week. Some movement in the first weeks is normal, but a page that keeps dropping usually has a redirect or metadata problem.
4. Keep the old export: don't delete the WordPress install or its files until the redirects are verified.

What does a Webflow migration look like in practice?

At Loom, it took three weeks and changed how fast marketing could ship: page launches went from about two weeks to one or two days.

Where did Loom start?

Loom's product was moving fast, but the marketing site couldn't keep up. Every meaningful page update needed engineering, so launches, feature pages and campaigns waited for tickets and sprint capacity. A page that should have supported a launch could take two weeks to go live.

What changed in the migration?

We treated the move as a rebuild of how the team publishes, not a copy of the old site:

• A new component architecture: rebuilt from scratch, so new pages are assembled from tested sections instead of built one by one.
• A CMS structured for marketing: fields and collections set up around how the marketing team publishes, so routine updates no longer need a developer.
• Support after launch: we trained the team, onboarded them to the new system and stayed on as new page needs came up.

What were the results?

• 3 weeks to migrate the marketing site to Webflow
• 10x faster page launches, from about two weeks to one or two days
• +25% conversion lift

Engineering got its time back too: routine marketing updates stopped competing with the product roadmap. Loom was later acquired by Atlassian. Watch Loom's video testimonial or read the full case study.

What should your team do next?

1. Crawl and export: get the full URL list and a Search Console baseline before anything else.
2. Map every URL: write the old-to-new mapping in one sheet - it becomes your redirect list.
3. Decide on each plugin: native feature, integration or drop.
4. Plan the launch checks: agree who verifies redirects, indexing and tracking on launch day.

If you want a team that has done this before, Beqi plans and runs WordPress to Webflow migrations for B2B marketing teams, with redirects, tracking and integrations in place at launch.

Frequently asked questions

How long does a WordPress to Webflow migration take?

It depends on page count, content types and integrations. A marketing site with a blog typically takes a few weeks, Beqi's migration of Loom's marketing site took three. Large blogs with years of posts take longer, mostly because of content cleanup.

Can you convert a WordPress theme to Webflow automatically?

No. Themes and page builder layouts don't convert into Webflow. The design is rebuilt in Webflow's Designer. Content can be imported, which is usually the larger part of the work.

Will I lose my Google rankings when I migrate?

Not if every changed URL is redirected and the metadata comes across. Some movement in the first weeks after launch is common while Google recrawls the site. A sustained drop on specific pages usually points to a missing redirect or a lost title or description.

What happens to my WordPress plugins?

They stay behind. SEO plugins are replaced by Webflow's built-in SEO fields, caching and security plugins by Webflow hosting, and forms by Webflow forms or your CRM's forms. Features like comments or memberships need a third-party tool or a decision to drop them.

Can Webflow handle a large WordPress blog?

Yes, within the CMS item limit of your Webflow plan. Count posts, categories, tags and authors together before choosing a plan, since each one is a CMS item. Very large blogs import best in batches of a few thousand rows.

Should I keep WordPress hosting after the migration?

Keep a full export and the old files until the redirects are verified and Search Console looks stable. After that, the hosting can go - Webflow hosts the new site.