Can you keep your WordPress URLs when you move to Webflow?

Sometimes. Static pages can keep their paths. Wherever the new structure differs from your WordPress permalinks, each changed URL needs a 301 redirect to its new address. The URL map built before the move shows which URLs change, and Google advises building that map for any move that changes URLs.

Do you need 301 redirects when you migrate from WordPress to Webflow?

Yes, for every URL that changes. A 301 is a permanent redirect, and Google recommends permanent server-side redirects for site moves. Webflow takes redirects one at a time in Site settings or in bulk from a CSV file. A bulk import replaces your existing redirect list, so export the current list before you import a new one.

Can you migrate WordPress blog posts to Webflow automatically?

Largely, yes. Webflow documents a route where you export your WordPress content as an XML file, convert it to CSV, and import it into a CMS Collection, matching fields as you go. Each imported post still needs a check for formatting, images, internal links, and SEO fields before it goes live.

Will your site go offline during the migration?

A planned migration does not need downtime. The WordPress site can stay live while the Webflow site is built and tested on a staging copy, and the switch happens when the domain is pointed at the new site. Google advises lowering the DNS TTL about a week ahead and keeping the old setup until its traffic reaches zero.

Guides

Updated October 7, 20269 min read

How to migrate from WordPress to Webflow without losing SEO

Q: How long do rankings take to settle after a migration?

Nobody can give you a date. Google says to expect temporary ranking fluctuation during a move, and for a medium-sized site it can take a few weeks or more before the new URLs are shown. Watch indexing, crawl activity and 404 errors in Search Console, and keep your redirects for at least a year.

Q: What happens to your WordPress plugins when you move to Webflow?

Plugins do not move to Webflow. Each plugin's job is covered by a Webflow feature, an integration, or custom code, unless that job is dropped. List every active plugin during the audit and decide which of the three applies. SEO fields, redirects, sitemaps, and forms all have native Webflow equivalents.

To migrate from WordPress to Webflow without losing SEO, plan the URLs before you build anything. Map every old URL to its new address, and carry over the content that already earns traffic along with its titles and descriptions. Redirect every URL that changes with a 301, and watch Google Search Console after launch.

How do you migrate from WordPress to Webflow without losing SEO?

You migrate without losing SEO by treating the move as a URL project first and a design project second. Every old URL gets a planned destination, and every page that earns traffic arrives with its content and search fields intact. The work runs in eight steps.

Benchmark the WordPress site. Crawl it, list every indexable URL, and record current rankings and organic traffic. The "after" needs a "before" to be compared with.
Map every old URL to a new one. Keep URLs unchanged where you can, and record the old and new address for every URL that changes. Google calls this map an important step in any move that changes URLs.
Rebuild the structure in Webflow. Build a template for each type of page, and use CMS Collections for repeating content such as posts and case studies.
Move the content and the SEO fields. Titles, meta descriptions, headings, image alt text, canonical tags, and internal links should all travel with the content. For posts, Webflow documents an export route: export the WordPress content as XML, convert it to CSV, and import it into a Collection with field mapping.
Set up 301 redirects for every URL that changes. A 301 is a permanent, server-side redirect, the kind Google recommends for a move. Webflow takes redirects one at a time or in bulk from a CSV file, and it supports wildcard rules.
Test before the switch. Keep the staging copy out of the search index, crawl it, and check canonicals, robots rules and the sitemap. Check the redirect list against the URL map so that no old URL is left without a destination.
Launch. Lower the DNS TTL about a week ahead, remove the staging block, publish the sitemap, and confirm the site is verified in Search Console.
Monitor after launch. Watch indexing, crawl activity, and 404 errors in Search Console. Keep the redirects for at least a year, and expect rankings to move around for a while.

The sequence above follows Google's guidance on moving a site with URL changes and without URL changes, and Webflow's article on migrating from WordPress.

1Benchmark
2Map URLs
3Rebuild
4Move content
5Redirect
6Test
7Launch
8Monitor

How long does a WordPress to Webflow migration take?

The timeline depends mostly on five things: the number of templates, the volume of CMS content, the number of redirects to map, the integrations involved, and how many review rounds your team needs. A site of 15 pages with no blog is a smaller job than a site with hundreds of posts, a store, and three integrations.

To get a real number from any agency, send the page count, the number of posts, and the tools your site depends on, such as forms, a CRM, site search, and consent management.

Will you lose rankings when you migrate from WordPress to Webflow?

Rankings can move for a while after any migration, and Google tells site owners to expect temporary fluctuation. What costs rankings is an unplanned move, and its causes are known and checkable.

What goes wrong in a migration, why it matters, and how to prevent it
What goes wrong	Why it matters	How to prevent it
A staging block is left on after launch	A noindex tag or crawl block tells Google not to index the pages. Google says to remove temporary blocks at the switch.	Remove crawl blocks and noindex from the live site at launch, then check the live page source and robots rules.
Old URLs have no redirect	Visitors, bookmarks, and links from other sites reach an error page instead of the new page.	Map every old URL before the build, and give every URL that changes a 301 redirect.
Redirect chains, or temporary redirects where permanent ones belong	Google recommends permanent server-side redirects and advises against chaining them.	Send each old URL straight to its final address with a permanent redirect.
Titles, descriptions, headings, or content are dropped in the move	These fields tell search engines and readers what each page is about.	Carry them over per URL with Webflow's page SEO settings and CMS template fields.
The sitemap is not updated, or Search Console does not cover every site version	Google advises submitting the new sitemap and verifying every variant of the site.	Publish the sitemap, submit it, and verify every version of the domain.
Nobody watches after launch	Crawl rates and rankings move after a launch, and problems show up first in Search Console.	Review indexing, crawl activity, and 404 errors on a schedule, and keep the redirects for at least a year.

Google expects temporary ranking fluctuation during a move, and for a medium-sized site it can take a few weeks or more before the new URLs are shown. Google also suggests timing the move for a period of lower traffic.

What happens to your WordPress plugins, forms, and integrations?

WordPress plugins do not move to Webflow. Each plugin's job is covered by a Webflow feature, an integration, or custom code, unless that job is dropped. List every active plugin during the audit and decide which of the three applies.

Common WordPress plugin jobs and what covers them in Webflow
What the plugin did	What covers it in Webflow
SEO titles and meta descriptions	Page settings hold the title tag and meta description for each page. On CMS template pages they can be filled from Collection fields.
XML sitemap	Webflow generates a sitemap.xml and updates it when you publish. You can switch it off and paste a custom sitemap.
Redirect manager	Site settings accept 301 redirects one by one or from a CSV file, including wildcard rules.
Contact and lead forms	Webflow's native forms store submissions in Site settings and can email notifications, send data to a webhook, or connect to apps such as HubSpot, Zapier, and Make. A spam inbox collects suspected spam.
Schema and structured data	Structured data is added as a script through custom code for the whole site or a single page.
Analytics, tag manager, and consent scripts	Custom code in the site or page head, or before the closing body tag, holds these scripts.
Site search	Webflow's site search is a component you add in the Designer. It searches pages and CMS items.

Webflow's plan requirements and limits for forms, redirects, and search change over time. Check the linked Webflow documentation for the current limits on your plan before you commit to a design.

What should you prepare before you start a WordPress to Webflow migration?

Before you build anything, gather access to the old site, a benchmark of its search performance, a list of plugins and integrations, and a named owner for each group of pages. Five things save the most time later:

Access. Admin access to WordPress and its hosting, to the domain registrar or DNS host, and to Google Search Console and your analytics account.
A benchmark. A crawl of the live site, plus current rankings and organic traffic for the pages that matter, so the "after" can be compared with a "before".
A plugin list. Every active plugin, the job it does, and who depends on it.
Content owners. A person who approves each group of pages, and a date after which nobody edits the old site.
An integration list. Forms, CRM, analytics, consent management, and anything else that sends or receives data.

Is moving from WordPress to Webflow the right call for your site?

For most B2B marketing sites, the decision comes down to who edits the site and how much custom functionality depends on plugins. If your team wants to edit pages without a developer, a visual platform such as Webflow is worth testing against that need. A site that depends on heavy custom plugins needs a closer look first. These situations need a check before you commit:

Large volumes of CMS content. Check Webflow's current Collection and item limits for your plan. Webflow's own migration guide tells you to check them before you export.
Store logic, such as WooCommerce. Check whether Webflow's e-commerce features cover your catalog, checkout, and tax needs, because Webflow's migration article does not cover stores.
Membership or gated content. Check how logins, paywalls, and member-only pages will work on the new platform.
Heavy custom plugins. List what each plugin does, and decide whether a Webflow feature, an integration, or custom code replaces it.
Multi-language sites with complex rules. Check how language structure, URLs, and hreflang tags will carry over. Google advises updating hreflang annotations when a move changes URLs.

A migration is a recommendation, not a reflex. If none of these situations applies and the site works for your team, staying on WordPress and fixing the site you have is a legitimate answer.

How was this guide written and checked?

This guide is based on Google Search Central's documentation on site moves and on Webflow's Help Center. Each fact was read on the source's own page on 6 October 2026, the sources are listed at the end, and the guide is rechecked every 30 days because Webflow changes its settings and limits. We plan and run migrations for B2B companies, so we have an interest in the topic. The guide says where staying on WordPress is the better answer. To hand the work to BenorMedia, see its WordPress to Webflow migration service.