Skip to content

WordPress to Webflow,
with every URL kept.

A plain guide to moving your WordPress site to Webflow. What comes across, what does not, and how to keep your rankings while you do it.

Typical time
3 to 6 weeks
Typical cost
$4,000 to $10,000
Old addresses
Each one redirected

What moves, and what does not

Comes across

  • Page and post text, and the order of your content
  • Images and files, uploaded again with their alt text
  • Page titles and meta descriptions
  • Categories, tags and authors, set up as CMS content
  • Your URLs, kept where we can and redirected where we cannot
  • The look of your site, rebuilt in Webflow

Stays behind

  • Plugins and themes. Webflow does not run WordPress code, so each plugin feature needs a Webflow feature or another tool.
  • Page builder layouts such as Elementor or Divi. They are rebuilt by hand, not converted.
  • The WordPress admin and its user accounts.
  • Comments. Webflow has no built-in comments, so they need a separate tool or are left behind.
  • Online stores. A WooCommerce shop is a different job. See the ecommerce service.

Protect your search rankings

Rankings follow addresses. If an old address stops working, the page loses its place in search. This is the work that protects them.

  1. Redirect map

    List every address on the old site. Pull them from your sitemap, a crawl of the site, Search Console and your analytics, so pages with traffic and links are not missed. For each one, decide: keep the same path, or send it to a new one with a 301 redirect. WordPress permalinks often look like /2024/05/post-name/. In Webflow, CMS items sit under their collection, such as /blog/post-name, so many posts need a 301. Add the redirects in Webflow's site settings before the domain switches. Do not forget category, tag and author pages.

  2. Metadata

    Titles and descriptions are the first thing search engines and people read. If you use Yoast or Rank Math, export those fields with your content. In Webflow, every page has an SEO title and a meta description, and a CMS template can build them from fields. Check the Open Graph image, the canonical tag and the heading structure of each page after the move.

  3. Sitemap

    Webflow can generate a sitemap.xml for you. Turn it on in the SEO settings and check that it lists the pages you expect. Old sitemap addresses from WordPress, such as /wp-sitemap.xml, should redirect to the new one.

  4. Search Console

    Verify your domain in Google Search Console before the move, ideally with a DNS record, because that kind of proof survives a change of platform. After launch, submit the new sitemap and check the key pages with the URL Inspection tool. Then watch the Pages report for errors and the Performance report for drops. Every 404 you find gets a redirect.

Content and CMS mapping

In WordPressIn WebflowNote
PagesStatic pagesRebuilt in the Designer. Your design is the guide.
PostsA CMS collectionOne item per post, with its own template page.
Categories and tagsOption or reference fieldsA reference to a Categories collection lets you build category pages.
AuthorsAn Authors collectionEach post points to its author with a reference field.
Featured imageAn image fieldAlt text moves with it.
Custom post typesOne collection eachA team, a portfolio or a list of services.
Custom fields (ACF)CMS fieldsMatched by type: text, image, link, number, date.
Menus and widgetsNavbar and componentsBuilt once and reused on every page.

Each Webflow plan has a limit on CMS items. Compare it with your post count before you choose a plan.

Forms and integrations

  • Forms

    Contact Form 7, Gravity Forms and similar plugins do not move. Rebuild each form with Webflow's own forms, then set who gets the email and test it. Turn on spam protection.

  • Analytics and tags

    Add Google Analytics, Tag Manager and any ad pixels in the site settings. Webflow needs a paid site plan to add custom code. Check that events and conversions still fire.

  • Email and CRM

    Newsletter sign-ups and CRM forms either use an embed from the tool or connect through Zapier or Make. List every one before the move, because a missed form means missed leads.

  • Plugin features

    Write down what each plugin does: search, popups, redirects, sliders, cookie notices. Some are native in Webflow. Others need a third-party tool. A few are not worth keeping.

The steps, in order

  1. Audit the old site

    List every page, post, image, form, plugin and redirect. Record your best pages and their rankings so you can compare later.

  2. Build the redirect map

    One row for every old address: the new address and the status, keep or 301. This file drives the whole project.

  3. Map the content

    Decide the Webflow collections and fields. Match each WordPress field to a Webflow field before any content moves.

  4. Build in Webflow

    Build the pages, the CMS templates and the navigation on a staging address, not on your live domain.

  5. Move the content

    Bring over posts, pages and images. Move metadata with them. Then check the formatting by hand, because long posts often need tidying.

  6. Connect forms and tools

    Rebuild forms, add analytics and tags, and connect your CRM and email tools.

  7. Test on staging

    Click every link, send every form, check the pages on a phone and run every old URL through the redirect map. Nothing goes live until this passes.

  8. Switch the domain

    Point the domain at the new site by changing its DNS records. The new site is already built and tested, so the change takes minutes to take effect. Keep the old site and its backup until you are sure.

  9. Watch the first 30 days

    Check Search Console for errors, compare traffic and rankings with the weeks before, and fix any address that returns a 404. Our migration service includes 30 days of ranking and traffic monitoring.

Time and cost

Time3 to 6 weeks

Cost$4,000 to $10,000

The range depends on the number of pages, how complex the platform is and any custom needs. We scope it after an audit. Large sites with thousands of pages can take longer.

The same move, done for Brau

Case study

How we moved Brau from WordPress to Webflow, then rolled it out across the UAE and Saudi Arabia.

  • A beauty salon business across the UAE and Saudi Arabia.
  • Moved from WordPress to Webflow for better stability and speed, so the team can edit pages day to day.
  • Set up in English and Arabic, with the Saudi site built from the same core.
  • The case study reports +70% growth after the Webflow migration.
Read the Brau case study

More migration guides

Tell us what you are building.

Scope, cost, and timeline, mapped with you.

Book a Free Call

Trusted by 150+ teams worldwide