Migrating from WordPress to Webflow without losing what you rank for

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.

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.

How do you migrate off WordPress without losing rankings?

The redirect table is where that answer lives, and Webflow's behaves differently from the .htaccess file you are leaving behind. Rules run in the order they were added rather than by specificity, and every rule ships in the site's manifest to every visitor, which is why wildcards are worth the effort. Both are set out in how Webflow 301 redirects actually behave, and both are easier to get right on the day than to unpick a month later.

Every old URL needs a 301 to its closest equivalent, and closest means the page that answers the same question, not the homepage. The step-by-step route is on the WordPress to Webflow migration page. 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.

What doesn't transfer from WordPress to Webflow?

Anything that was a plugin. Forms, site search, memberships, multilingual, bookings, reviews, and whatever else was installed years ago and quietly became part of how the business runs: none of it crosses over, because none of it is content. Each one turns into a decision instead: a Webflow native feature, a third-party embed, or something you deliberately drop. Make that list during the inventory rather than the week before launch. Two of them will turn out to be load-bearing, one will need a budget nobody scoped, and discovering that with the old site already switched off is how a migration becomes an emergency.

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.