WordPress to Webflow Migration: A Step-by-Step Guide (2026)
How to migrate from WordPress to Webflow without losing SEO: what moves, URL changes, content import, redirects and a 7-step process with timings.
Moving from WordPress to Webflow is one of the most common website migrations today. Marketing teams want a site they can edit without a developer, without plugin updates and without security worries. The move is very doable, but it is not a one-click import: done carelessly, it can cost you the search rankings you spent years building.
This guide covers what moves, what does not, and the step-by-step process we use to move sites without losing traffic.
Should you move from WordPress to Webflow?
Webflow is a good fit when your site is mainly a marketing site: pages that explain what you do, a blog, case studies and landing pages. Teams usually move for three reasons:
- Less maintenance: no plugin, theme or core updates, and hosting, SSL and security are handled for you.
- Design control: designers build visually, and marketers edit content without breaking layouts.
- Speed: pages are published as fast static files on a global CDN.
WordPress is still the better home if your site depends on complex features: a large WooCommerce store, membership areas, learning platforms or heavily customised plugins. Our Webflow vs WordPress comparison covers that decision in detail.
What moves, and what has to be rebuilt
Content moves; design and functionality are rebuilt. Here is how the main parts of a WordPress site map to Webflow:
| WordPress | Webflow | How it moves |
|---|---|---|
| Posts | CMS collection (e.g. Blog) | Imported with an app or a CSV file |
| Categories and tags | CMS collections, referenced from posts | Imported, then linked to posts |
| Pages | Static pages | Rebuilt in the Designer |
| Theme | Your Webflow design | Rebuilt, usually improved |
| Custom post types | CMS collections | Exported to CSV and imported |
| Yoast or Rank Math settings | Page and CMS SEO fields | Mapped into Webflow fields |
| Contact forms | Webflow forms or an embedded tool | Rebuilt and reconnected |
| Redirects plugin | 301 redirects in site settings | Re-entered or imported |
Step 1: Audit and back up your WordPress site
Start with a full backup, then build an inventory of every URL on the site. A crawler such as Screaming Frog will list pages, posts, categories, tags, author pages and attachments.
Next, pull 12 months of data from Google Search Console and your analytics tool. Flag every URL that gets traffic, ranks for valuable keywords or has backlinks. These are the pages you cannot afford to lose, and they get the most care during the move.
This is also a good time to prune. Thin tag pages, old event posts and duplicate content can be consolidated or dropped, as long as each removed URL redirects somewhere relevant.
Step 2: Plan your new URL structure
This is the step most migrations get wrong. Webflow places every CMS item inside a collection folder: a post lives at /blog/post-name, not at /post-name. Many WordPress sites publish posts at the root of the domain or under date-based paths like /2024/05/post-name.
That is fine, as long as you plan for it. Decide the new structure up front, then build a redirect map: a spreadsheet with every old URL in one column and its new address in the next. Keep slugs identical wherever possible, so only the folder changes.
Step 3: Design and build in Webflow
Rebuild the design in Webflow rather than trying to copy the theme pixel for pixel. Set up a style system and reusable components first, then build the key templates: home, service or product pages, the blog listing and the blog post template.
Model your CMS before importing anything. Create the collections (posts, categories, authors, case studies) and their fields, including SEO title, meta description and Open Graph image, so your existing metadata has somewhere to go.
Step 4: Move your content into the Webflow CMS
There are two common routes:
- An import app: the free WP to Webflow app in Webflow’s app marketplace connects to your live WordPress site and imports posts, categories, tags and images.
- CSV export: a WordPress export plugin turns posts, pages and custom post types into CSV files that Webflow’s CMS importer reads.
Both need a Webflow plan with the CMS. Whichever you use, check the results by hand. Rich text often brings across stray formatting, embedded shortcodes from old plugins will not work, and images may need resizing and alt text.
Step 5: Recreate SEO settings and functionality
Copy over each page’s title tag, meta description and Open Graph image, along with any structured data you rely on. Then replace each plugin’s job:
- Forms: use Webflow forms, or embed a tool such as HubSpot or Typeform.
- Analytics and tags: add Google Tag Manager or your analytics script in the site settings.
- Search, comments, pop-ups: use integrations or embeds where you still need them.
Step 6: Set up redirects and test before launch
Enter every row of your redirect map as a 301 redirect in Webflow’s site settings. Then test on the staging domain. Every old URL should redirect once, straight to the right page, with no chains or loops. Also check:
- Internal links point to the new URLs, not through redirects.
- Every page has its title, description and canonical tag.
- Images load, forms submit and the site works on mobile.
- The XML sitemap lists the new URLs.
Step 7: Launch and monitor
Point your domain at Webflow, publish, and submit the new sitemap in Google Search Console. Some movement in rankings during the first few weeks is normal while Google processes the redirects.
Watch Search Console’s page indexing and 404 reports daily for the first two weeks, and fix any missed redirects straight away. Compare traffic to your top pages against the baseline you recorded in step 1. Our SEO website migration checklist has the full pre- and post-launch list.
How long does a WordPress to Webflow migration take?
A typical marketing site with up to about 50 pages and a few hundred blog posts takes 3–6 weeks from audit to launch. Most of that time goes into the design and build, not the content transfer. Larger sites with custom post types, multiple languages or thousands of posts take longer.
Common mistakes to avoid
- Forgetting the folder change: posts move under /blog/, and missing redirects send old links to 404 pages.
- Importing without cleaning: shortcodes, inline styles and broken embeds come across in rich text.
- Losing metadata: titles and descriptions are not carried over automatically unless you map them.
- Redirecting everything to the home page: each old URL should point to its closest matching page.
- Launching without a baseline: without before-and-after data, you cannot spot problems quickly.
Planning a move? Our website migration service handles the whole process, from audit and redirect map to rebuild and launch, so your rankings come with you.
