Migrating from WordPress to Webflow
The realistic plan for moving a content-heavy WordPress site to Webflow without losing your SEO.
Migrating WordPress to Webflow is bigger than people expect. The content moves, the design rebuilds, the SEO needs preserving. Here is the realistic plan.
Step 1: Audit what is actually on the site
Most WordPress sites have years of accumulated cruft. Old posts nobody reads, plugins doing nothing useful, custom fields nobody documents. Export everything, then make a hard decision: what comes with you, what gets archived, what dies.
A typical migration cuts the content by 30-50%. That is usually a feature, not a bug.
Step 2: Map the URL structure
Webflow URL patterns and WordPress URL patterns rarely match by default. Map every old URL to its new home before you touch anything. Spreadsheet. One row per page.
Most studios get this right for the top 50 pages and lazy on the rest. You will then 404 half your indexed long-tail traffic. Don't be lazy on the rest.
Step 3: Set up the Webflow CMS
For each WordPress post type and custom field, design the equivalent Webflow collection and fields. The closer the schema matches the old site, the easier the content import.
Webflow collections are flatter than WordPress custom post types. Some restructuring is inevitable.
Step 4: Import the content
Webflow has CSV import for collections. Export from WordPress via a plugin (WP All Export) or directly via WP-CLI. Clean the data in a spreadsheet. Import.
Images are the painful part. WordPress media library URLs do not work in Webflow. You either upload all images manually, or write a script to download from WordPress and upload to Webflow.
Step 5: Rebuild the design
You are not porting the WordPress theme. You are building a Webflow site that happens to use the same content. This is the right time to update the design rather than trying to recreate something that was already dated.
Step 6: Redirects
Before you flip DNS, set up 301 redirects from every old URL to its new home. Webflow has a redirect manager but it has limits (1000 redirects per plan tier on Site plans last we checked). For larger sites, consider Cloudflare in front of Webflow for redirect handling.
This is the step that protects your SEO. Skip it and you nuke your search rankings for weeks.
Step 7: Cutover
Update DNS, monitor analytics for 404 spikes, check Google Search Console daily for the first two weeks for crawl errors. Expect a temporary dip in organic traffic — Google needs to re-crawl and re-index the new URLs.
Timeline
A small WordPress site of 30-50 pages: 3-4 weeks. A medium publication of a few hundred posts: 6-10 weeks. A large editorial site: hire help.
Should you actually do it
Only if WordPress is causing real pain — performance, maintenance burden, designer frustration. "We want to look more modern" alone is not enough to justify the work. A WordPress redesign with a better theme costs a fraction of a Webflow migration.