Migrating from WordPress to Webflow without losing what you rank for
A replatform fails in two places: the content arrives as a mess, or the rankings do not arrive at all. Both are avoidable, and both are avoided before launch rather than diagnosed after it.
Most WordPress sites are not left because WordPress stopped working. They are left because the site has become a stack of plugins nobody wants to update, and every change has to go through a developer. Webflow answers that. What it does not answer by itself is the thing everyone actually worries about, which is whether the traffic survives the move.
Inventory the old site before you touch the new one
Crawl the whole thing and put every URL in a spreadsheet, then pull twelve months of Search Console data in beside it. What you want is not a list of pages, it is a list ordered by what each page earns. Most sites discover at this point that a handful of old posts carry a third of the organic traffic, and that nobody on the team would have thought to protect them.
Export the content, do not copy and paste it
WP All Export will give you posts, pages and custom post types as CSV, and the fields that matter are title, slug, content, excerpt, featured image URL, categories and date. The slug is the one people forget, and it is the one the redirect map is built from. Import that CSV into the Webflow CMS rather than rebuilding entries by hand, because a hundred posts retyped is a hundred chances to change a URL without meaning to.
Rebuild the structure. Do not trace the old one
A page-for-page copy is tempting because it feels like the safe option, and it carries every accumulated mistake across with it: the four category pages nobody reads, the tag archives generating thin duplicates, the service page that was never finished. Model the CMS around what you actually publish now. Then decide deliberately which old URLs survive as pages and which survive only as redirects.
The redirect map is the migration
Every old URL needs a 301 to its closest equivalent, and closest means the page that answers the same question, not the homepage. Sending everything to the homepage is the single most common way a migration loses its rankings: Google reads a mass redirect to one page as a soft 404 and drops the lot. Webflow takes these under Site Settings, Publishing, 301 Redirects, and past a couple of dozen the Finsweet Chrome extension will upload a spreadsheet instead of making you paste rows one at a time.
Know what does not come with you
Anything that was a plugin is now a decision. Forms, search, memberships, multilingual, bookings, reviews: each one becomes a Webflow native feature, a third-party embed, or something you drop. Make that list during the inventory rather than the week before launch, because two of them will turn out to be load-bearing and one will need a budget.
Launch week is a monitoring job
Submit the new sitemap, then watch Search Console daily for a fortnight. You are looking for two things: 404s appearing in the page indexing report, which means a redirect is missing, and pages moving to Crawled, currently not indexed, which means the new page is thinner than the one it replaced. Both are cheap to fix in the first week and expensive in the second month.
A dip in the first fortnight is normal and recovers. A flat line three weeks later is not a dip, it is a missing redirect nobody has looked for yet.
