Most WordPress to Webflow migrations win on design and lose on search traffic. The pages look better, the plugin stack is gone, and three months later the organic numbers are a third of what they were. This guide is the order of work that stops that happening.
Two definitions first. WordPress is an open-source website platform where features come from third-party plugins and the hosting is your own problem. Webflow is a website platform where the design, the content system and the hosting sit in one place. A marketing team can edit and publish there without an engineering ticket.
Why do sites lose rankings when they move from WordPress to Webflow?
A site loses rankings in a migration when the pages Google already trusts stop existing at the addresses Google knows. It also loses rankings when those pages come back saying less than they did. Neither of those is a Webflow problem. Both are mapping problems, and the team building the migration decides both before designing the first page.
The mechanism is simple. Every page that ranks has earned that position through its address, its words and the links pointing at it. Change the address without a redirect and the links point at nothing. Cut the words to fit a tidier template and the page no longer answers what it used to answer. Rebuild the page and leave the title tag and structured data behind, and Google is reading a new page.
The tidy design is the easy half. What decides whether the migration was a success six months later is whether the search equity came across.
What should you inventory before anything is designed?
Every URL that earns something. Pull every address with impressions, clicks, backlinks or conversions from Search Console, your analytics and a full crawl, and put them in one sheet. The team judges the whole migration against that sheet, and it has to exist before the new site has a shape.
The order matters more than it looks. Design work naturally throws pages away, merges sections and renames things, and it should. But it should do that against a list of what each page currently earns. That way, a page carrying a third of the organic traffic does not quietly become a paragraph on another page.
For each URL, record five things: monthly clicks and impressions, the queries it ranks for, and the number of referring domains linking to it. Also record whether it converts, and what its title tag and description say. Then sort by clicks. The top of that list is what the migration exists to protect.
How do you build a redirect map that keeps your SEO?
Map every URL on the inventory from one old address to one new address. The new address is always the closest equivalent page, never the home page. Where no equivalent exists, record that as a decision in the sheet before launch. Do not let it surface later as a 404.
Bulk-redirecting everything to the home page is the standard shortcut, and it throws away most of the equity the redirect was there to keep. Google treats a redirect to an unrelated page much like a soft 404: the old page’s signals do not carry across.
Use permanent (301) redirects, and keep the redirects live for as long as the site exists. Old links from other sites, bookmarks and citations in AI answers keep pointing at the old addresses for years.
Watch the small changes as well as the big ones. Trailing slashes, upper case in slugs, and www versus the bare domain each produce a distinct URL to a search engine. When K2 Group retired a legacy domain, 261 URLs were still earning something. We mapped every one of them to a home across a six-site estate. Site health rose on five of the sites in the month that followed. The number that mattered was 261, and it was only visible because the inventory came first.
What has to move with the content besides the words?
Titles, meta descriptions, structured data, canonical tags, image alt text and internal links. Each of these is part of what the old page earned. Each is easy to leave behind when the team rebuilds a page in a new template.
Webflow handles this differently from WordPress, and it is worth knowing where. Titles and descriptions sit in each page’s settings and in the CMS fields for collection pages. A marketing team can set them per page and per item. Structured data has no plugin equivalent. It goes into the page as custom code, either per page or through a CMS field bound to a code embed. The team sets canonical tags once for the whole site, in the SEO settings. That single field is where a migrated site most often ends up pointing every page at the wrong hostname.
Internal links deserve their own pass. WordPress sites accumulate thousands of links between posts, in sidebars, related-post widgets and body copy. On the new site those links have to point at the new addresses directly rather than bounce through a redirect. A crawl of the new site before launch is the cheapest fix in the whole project. Check it for any internal link that returns a redirect or a 404.
How do you carry the substance of a page and not just its layout?
Move the words, the headings and the media that made the page rank, and resist the template. A page that ranks does so because of what it says. Cutting a thousand words to fit a cleaner layout is the most common self-inflicted loss in a migration. It stays invisible until the rankings move.
That does not mean every WordPress page comes across untouched. It means the team makes every cut as a decision against the inventory. If a page ranks for forty queries and the redesign turns it into three cards and a heading, the forty queries go with the words.
Blog content is where this goes wrong most often. Teams usually import a WordPress blog with several hundred posts into a Webflow CMS collection through a spreadsheet. That import strips whatever the collection’s rich text field cannot hold: embedded tables, custom HTML blocks, some image captions. Check a sample of the highest-earning posts by hand after the import, against the live WordPress version, before the old site goes dark.
What does the launch itself look like?
The old site stays live until the new one is proven. Publish the new site to a staging domain first, then crawl it against the inventory. Switch the domain, and keep the old hosting for at least a month so the team can recover anything missed.
Before the switch, three checks. Every URL on the inventory either exists on the new site or has a redirect in place. The site-wide canonical setting points at the domain the site will actually serve on. The team verifies Search Console and analytics on the new domain, and submits the sitemap.
After the switch, request indexing on the pages that matter most rather than waiting for the crawler. Watch the Coverage report for redirect errors and soft 404s in the first week. Most migration damage is cheap to reverse in the first month and expensive after it, because by then Google has re-crawled and re-scored.
How long should you monitor rankings after the migration?
Ninety days, weekly, against the pre-launch inventory. Crawl the site, compare clicks and impressions per URL to the baseline sheet, and fix what moved. A migration is finished when the numbers have held for a quarter.
Some movement is normal in the first fortnight while Google re-crawls. What is not normal is a page on the inventory dropping out of the results altogether, or a cluster of pages losing position together. Both usually trace back to a redirect that points somewhere unhelpful or a template that dropped the substance. The team can fix both if it catches them early.
What do you gain from Webflow that WordPress cannot give you?
Once the equity is safe, the reasons B2B marketing teams make the move come into their own. A component library the team can run without a developer queue replaces the plugin stack. Patching stops being someone’s permanent job, because Webflow hosts and secures the platform. And the marketing team edits and publishes pages directly, so the site keeps pace with the campaigns rather than waiting on a PHP developer.
None of that is worth losing rankings for, and none of it has to. The migration playbook above is what we run on every move. If you would rather hand the mapping to someone who has done it before, our WordPress to Webflow migration service starts with the inventory.
Frequently asked questions
Does migrating from WordPress to Webflow hurt SEO?
Only when the migration skips the mapping. Rankings belong to addresses, words and links. If the team redirects every earning URL one-to-one, the content and metadata come across. If it also monitors the site after launch, rankings transfer with the content instead of resetting.
Can you keep the same URLs when moving to Webflow?
Mostly. Static pages can keep any slug you like. Collection pages, such as blog posts, sit under a collection folder such as /blog/. A WordPress post at /my-post/ becomes /blog/my-post/ and needs a redirect. Webflow supports 301 redirects in its hosting settings, including wildcard rules for whole folders.
How long does a WordPress to Webflow migration take?
It depends on how many pages, templates and plugins the migration involves. Every migration should start with a full audit that scopes the work and sets a realistic timeline before anything moves. The inventory step above is that audit.
What happens to WordPress plugins in Webflow?
Most plugin functionality maps to a native Webflow feature or a component built once and reused. Forms, SEO fields, redirects, CMS collections and hosting are all native. The team scopes exceptions, such as membership systems or complex e-commerce logic, during the audit rather than discovering them afterwards.
