WordPress to Webflow Migration: A Step-by-Step Guide That Protects Your SEO

Moving a WordPress site to Webflow is one of the most common projects I get asked about. The reasons are usually the same: too many plugins, slow pages, constant updates, or a design the team can no longer change without a developer. The fear is also the same: “Will we lose our Google rankings?”

A WordPress to Webflow migration protects your SEO when you plan the URLs, content and redirects before you touch the design. This guide is the order I follow when I build Webflow sites like the Northman law firm website, and when I help clients move away from WordPress. If you are still deciding between platforms, read my Webflow vs Framer vs WordPress comparison first.

Key takeaways

• A migration to Webflow is a rebuild. There is no automatic converter.
• Content moves through WordPress XML export, a CSV file and a Webflow CMS import.
• Every changed URL needs a 301 redirect to its closest equivalent, not the home page.
• Plugins, forms and SEO-plugin metadata do not transfer on their own. List them first.
• Keep redirects live for at least a year and watch Search Console after launch.

Can you migrate WordPress to Webflow automatically?

No. Webflow’s own migration overview says there is no automated way to convert a site from another platform, and that a migration is a rebuild rather than a transfer. You can move content in bulk, but the design, structure and features are built again in Webflow.

That is not bad news. A rebuild is your chance to drop old plugins, thin pages and dated layouts. It does mean you should treat the project as a new website that must keep the old site’s search value.

What should you do before you migrate?

Before you build anything, audit the old site. Google’s site move guidance is built around knowing your old and new URLs, so the audit is the foundation of the whole project.

Work through this list:

1. Crawl the site and export every URL: pages, posts, categories, tags, media pages and PDFs.
2. Pull performance data from Google Search Console and your analytics, so you know which pages bring traffic and links.
3. Record the SEO basics for each important page: title tag, meta description, H1, canonical URL and schema.
4. List plugins and features: forms, popups, memberships, booking, search, comments, e-commerce.
5. Decide what to keep, merge or retire. Not every old post deserves a place on the new site.
6. Back up the WordPress files and database.

Metadata deserves special attention. If your titles and descriptions live in an SEO plugin, they are not automatically part of the content export, so copy them into your spreadsheet.

How do you plan URLs and redirects?

Keep each URL the same wherever you can, and give every URL that must change a 301 (permanent) redirect to its closest equivalent. Google recommends permanent redirects for moved content, and recommends sending visitors straight to the final page rather than through a chain.

Webflow builds URLs in set patterns, so some WordPress permalinks will change. A blog Collection with the Collection URL post produces addresses like /post/your-blog-post, as explained in the Webflow Collections guide. You can place a Collection inside a parent folder, and some slugs are reserved, so read the Page URLs documentation before you decide on a structure.

Build this map in a spreadsheet with two columns: old path and new path. It becomes your redirect file later.

How do you move WordPress content into Webflow?

Export from WordPress, convert the file to CSV, then import it into a Webflow CMS Collection. Webflow’s WordPress guide describes this route: WordPress exports XML, you convert it with an XML to CSV tool, and you import the CSV into a Collection and map the fields.

1. Export from WordPress

Go to Tools → Export and choose all content, posts, pages or media, as explained in the WordPress Learn lesson. The file contains posts, pages, comments, custom fields and taxonomies. Two catches: media files in the Media Library that are not used in a post are left out, and the export holds references to images rather than the image files themselves.

2. Clean the CSV

Before importing, tidy the data in a spreadsheet: remove drafts and junk, fix slugs, shorten titles, and add your meta title and description columns. This is the best time to retire weak posts.

3. Create the Collection and import

Build a Collection with the fields your design needs (title, slug, date, author, cover image, body, category). Then follow Webflow’s CMS import guide. Points worth knowing from that guide:

• Column headers become field labels, and matching names map automatically.
• Image fields take public image URLs, which Webflow downloads and hosts.
• Rich text fields accept HTML, but Webflow can remove elements, classes or attributes it does not support. Always check a few posts after import.
• Check your plan’s CMS item limit before importing a large blog. Webflow’s pricing has changed in 2026, so see my Webflow pricing changes guide.

4. Try the WP to Webflow app for blog posts

Webflow’s Marketplace has a free WP to Webflow app. Its listing says it moves posts, images, tags and categories, and does not move custom fields, static pages, design, plugin features, custom post types or WooCommerce data. It is a time-saver for a plain blog, not a full migration.

How do you rebuild the design and features in Webflow?

Build the design as a fresh Webflow project, using the audit as your brief. Recreate the layout with proper heading order, real HTML lists and tables, and descriptive alt text. This is where Webflow helps SEO and speed, but only if you build cleanly.

Map each plugin to a replacement:

For a WordPress and Elementor site such as Aisare, this mapping step takes longer than the content import, because the design is tied to the page builder. If you are weighing builders, my Webflow vs Framer vs WordPress guide covers the trade-offs.

How do you set up 301 redirects in Webflow?

Add them in Site settings → Publishing → 301 redirects, or import a CSV. Webflow’s redirect documentation covers single rules, and the import and export guide covers bulk files.

What matters in practice:

• A CSV needs old paths and new paths, one redirect per row.
• Importing replaces your existing redirects. Export the current list first, add new rows, then import.
• Redirects only take effect after you publish.
• Rules run in the order added, so put specific rules before wildcard rules.
• Wildcard rules use a capture group and a %1 placeholder, with no regex support.
• Webflow suggests staying around 1,000 redirects as best practice.

Test a sample of old URLs on the staging site and again after launch, and make sure none redirect through more than one hop.

How do you switch the domain without downtime?

Finish and test the Webflow site on its staging address, then update DNS. Webflow’s DNS guide for live migrations recommends lowering your TTL well before the switch, then adding the A record for the root domain, a CNAME for www and a TXT verification record.

Launch day checklist:

1. Lower the DNS TTL a few days ahead.
2. Publish the final Webflow site and the redirect list.
3. Switch the DNS records.
4. Confirm HTTPS works on both the root domain and www.
5. Make sure the site is indexable (no leftover noindex setting) and that Webflow’s staging subdomain is not the indexed version.
6. Submit the new sitemap in Google Search Console.

What should you check after the migration?

Check redirects, indexing and rankings for the first weeks. Google notes that it crawls a moved site more heavily than usual, and its guidance says to keep redirects for as long as possible, generally at least one year. Old URLs can also linger in search results for a while without it meaning something is wrong, as long as they keep redirecting.

Post-launch audit:

• Search Console: watch the Pages report for errors, “Not found” spikes and unexpected exclusions.
• Crawl the new site and compare it to your old URL list.
• Check key pages: titles, descriptions, H1s, canonical tags and schema match your audit sheet.
• Test forms by submitting each one.
• Compare traffic for your top pages against the baseline you saved.
• Fix broken internal links so users and crawlers do not rely on redirects.

What are the most common migration mistakes?

• Redirecting every old URL to the home page instead of the closest matching page.
• Forgetting category, tag, image and PDF URLs that earned links.
• Losing titles and descriptions that lived in an SEO plugin.
• Importing rich text without checking how Webflow handled the HTML.
• Leaving the staging site indexable, or leaving a noindex setting on the live one.
• Cancelling the WordPress host before everything is verified.
• Changing content, URLs and design all at once, which makes problems hard to trace.

Final thoughts

A good WordPress to Webflow migration is mostly planning: know your URLs, move the content carefully, rebuild what matters, redirect everything that changes and watch the results. Webflow gives you cleaner control over design and a CMS that editors can use without plugins, but the platform alone does not protect your rankings.

If you’d like help planning or running the move, from the URL audit to redirects and launch, get in touch. I’m happy to look at your current site and tell you honestly whether Webflow is the right move.

Frequently Asked Questions