TheSiteBench is an independent review site. Not affiliated with, endorsed by, or sponsored by Webflow, Inc.
TheSiteBench

How to Migrate From WordPress to Webflow Without Losing SEO

Updated · Prices and features checked against official sources on Nov 14, 2026 · How we review

Moving from WordPress to Webflow isn't a one-click import. Your content can move over in a structured way, but your theme, plugins and design don't come with you. You rebuild the design in Webflow and bring the content into Webflow's CMS. Done carefully, with a full redirect map, a migration can keep the search visibility you've built.

This guide follows Webflow's own migration documentation (help article updated May 12, 2026) and WordPress's export documentation, both checked on November 14, 2026. It explains each step, the limits to check first, and the mistakes that cost sites traffic.

Not sure you should switch? Read Webflow vs WordPress first. WordPress remains the better choice for some sites, especially very large ones or sites that depend on specific plugins.

See Webflow's CMS Opens webflow.com. We may earn a commission.

The migration in 8 steps (Webflow's documented process)

Webflow's help center outlines this sequence for moving from WordPress:

  1. Export your WordPress content as an XML file.
  2. Convert the XML to CSV.
  3. Create a CMS Collection in Webflow for each content type.
  4. Import the CSV into the Collection.
  5. Map fields from your CSV columns to Collection fields.
  6. Design your site and Collection templates.
  7. Set up redirects and SEO settings.
  8. Publish.

Below, we expand each step with what the documentation says and the practical checks we recommend.

Before you start: four things to check

1. Your CMS item count vs Webflow's limits

Webflow's guidance is to check Collection item limits before you import. As of November 2026, Webflow's Site plans include:

Plan (yearly / monthly billing) CMS items Collections
Starter (free) 50 20
Basic ($15 / $25) No CMS —
Premium ($25 / $39) 20,000 40
Ecommerce Standard ($29 / $42) 2,000 20
Ecommerce Plus ($74 / $84) and Advanced ($212 / $235) Up to 10,000 40
Team ($2,500/mo, annual contract) 20,000 (more for a fee) 100

Count everything that becomes a CMS item: posts, but also categories, tags and authors if you model them as reference Collections. A blog with 3,000 posts, 40 categories, 400 tags and 10 authors needs about 3,450 items. If you're near or above 20,000, ask Webflow about its larger plans or consider whether WordPress suits you better. See our Webflow pricing guide for plan details.

2. Redirects need a paid plan

According to Webflow's help center, 301 redirects require a paid Site plan or a paid Workspace plan. Make sure you're on one before launch day.

3. What can't move automatically

Plugins (forms, SEO, ecommerce, memberships, page builders) have no direct equivalent you can import. Make a list of everything your plugins do and decide how each function will be handled in Webflow: native features, a Marketplace app, an embed, or dropping it.

4. Multilingual sites need extra planning

If you run a multilingual WordPress site, plan Webflow Localize (Essential $9/mo or Advanced $29/mo per locale, billed yearly). See our Webflow localization guide. Webflow's help center notes that 301 redirects don't apply to localized slugs, so map localized URLs carefully.

Step 1: Export your WordPress content

In WordPress, go to Tools → Export. WordPress.com's export documentation describes the result as an XML (WXR) file containing posts, pages, comments, categories and tags. It includes links to media rather than the media files themselves, and it doesn't include your theme or plugins. On WordPress.com, very large sites (around 1,000+ posts) receive the export as a zipped file by email.

Practical tips:

  • Export a full backup too, separate from the content export, so you can roll back.
  • Download your media library separately if you want copies of your images.
  • Export your current URL list. Use your sitemap (often /sitemap.xml or the sitemap from your SEO plugin) and analytics data showing which pages get traffic. You'll need this for redirects.

Step 2: Convert XML to CSV

Webflow's CMS imports CSV files, not WordPress XML. You'll need to convert the export into CSV, with one row per item and one column per field (title, slug, body, excerpt, featured image URL, date, category and so on). Webflow's CMS import accepts CSV files up to 4 MB, so split large exports into multiple files.

Keep the original slugs in a column. Matching the old WordPress slugs is the simplest way to reduce how many redirects you need.

Option: the free "WP to Webflow" app

Webflow's Marketplace lists a free app, WP to Webflow (by Eclipse SRL), that moves WordPress content into Webflow. According to its listing, it migrates posts, images, tags and categories. It does not migrate custom fields, static pages, custom post types or WooCommerce data. Its listing references older Webflow plan names, so check current CMS limits on Webflow's pricing page rather than relying on the app page. We haven't tested the app, and we don't have any relationship with its developer.

Step 3: Create Collections that match your content

In Webflow, create a Collection for each content type: Blog Posts, Categories, Authors and Tags, plus any custom types such as Case Studies or Resources. Add fields that match your CSV columns: rich text for the body, image for the featured image, reference fields for categories and authors, date for the publish date, and plain text for the meta description.

Tip: add dedicated SEO Title and Meta Description fields to the Collection. Webflow can fill page titles and meta descriptions from CMS fields, so you can carry over the metadata you wrote in your WordPress SEO plugin.

Step 4–5: Import and map fields

Import the CSV into each Collection and map every column to its field. Import reference Collections (categories, authors) before posts, so the post import can link to them.

After import, spot-check:

  • Formatting in rich text bodies (headings, lists, embeds, tables)
  • Image URLs and alt text
  • Internal links inside articles. They still point to old WordPress URLs, which is fine if the slugs match, but update them where they changed.
  • Publish dates and authors

Step 6: Design the site and templates

This is the part that takes the most time. Rebuild your layout in Webflow: global header and footer, home page, static pages, and a Collection template page for each content type. Because Webflow imports content but not pages, static pages (About, Contact, landing pages) are usually rebuilt by hand. That includes them even if you use the WP to Webflow app, which doesn't move static pages.

If you're not a designer, a Webflow template or a Webflow designer can shorten this step considerably. Read our Webflow review for a realistic picture of the learning curve.

Step 7: Redirects and SEO settings (don't skip this)

This step decides whether you keep your rankings.

Build a redirect map

List every old URL that has traffic, backlinks or rankings, and map each to its new URL. Common WordPress URL patterns that change in Webflow:

WordPress URL Typical Webflow equivalent
/2024/05/my-post/ (date permalinks) /blog/my-post
/category/news/ /categories/news
/tag/seo/ Tag Collection page, or redirect to a relevant category
/author/jane/ /authors/jane
/?p=123 Matching post URL
/wp-content/uploads/... Usually no redirect needed; update links

Add redirects in Webflow

Webflow's help center explains that you add 301 redirects under Site settings → Publishing → 301 redirects. You can also import redirects from a CSV (up to 16 MB). One crucial warning from the documentation: importing a redirects CSV overwrites all existing redirects. Export your current redirects first if you've already added some.

Carry over SEO settings

  • Page titles and meta descriptions (use CMS field bindings for Collections)
  • Canonical tags. Webflow lets you set a global or page-level canonical URL.
  • Open Graph images and descriptions
  • Image alt text
  • Structured data. Webflow lists schema markup support. Recreate any schema your WordPress SEO plugin generated, such as Article or FAQ.
  • XML sitemap. Webflow auto-generates one, so resubmit it in Google Search Console after launch.

For context on how Webflow's SEO controls compare with other builders, see best website builder for SEO.

Step 8: Launch and monitor

  1. Lower your DNS TTL a day or two before launch, then point your domain to Webflow following Webflow's custom-domain instructions.
  2. Publish, then test a sample of old URLs to confirm each one 301-redirects to the right new page.
  3. Submit the new sitemap in Google Search Console and watch the Pages (indexing) report.
  4. Crawl the new site with an SEO crawler to find broken links, missing titles and redirect chains.
  5. Monitor traffic and rankings weekly for the first couple of months. Some fluctuation after a migration is common. Big drops on specific pages usually point to a missing or wrong redirect.

Migration checklist

  • [ ] Count CMS items and confirm your plan's limit
  • [ ] Full WordPress backup + XML export + media download
  • [ ] Crawl and save every current URL, with traffic data
  • [ ] Plugin audit: decide how each function will be replaced
  • [ ] Collections created with SEO fields and reference fields
  • [ ] CSV(s) under 4 MB each, original slugs preserved
  • [ ] References imported before posts
  • [ ] Templates designed, static pages rebuilt
  • [ ] Redirect map complete; existing redirects exported before any CSV import
  • [ ] Titles, metas, canonicals, Open Graph and schema checked
  • [ ] Paid Site or Workspace plan active (for redirects)
  • [ ] Launch, test redirects, submit sitemap, monitor

How much does a WordPress to Webflow migration cost?

The software cost is your Webflow plan. For a blog, that usually means Premium at $25/mo billed yearly ($39 monthly), plus Workspace seats if several people edit. The free WP to Webflow app can help with posts, and CSV import is built in. The labor cost depends on the size of the site and whether you redesign. We haven't seen reliable published data on typical agency fees, so we don't quote a figure. Get quotes for your specific scope.

Compare Webflow plans Opens webflow.com. We may earn a commission.

FAQ

Can I import WordPress into Webflow directly? Not as a native one-click import. Webflow's documented process is to export WordPress XML, convert it to CSV and import it into a CMS Collection. The free WP to Webflow Marketplace app can automate parts of this for posts, images, tags and categories.

Will I lose my SEO rankings? Not necessarily. The biggest risk is broken URLs. Keep slugs where possible, map every changed URL with a 301 redirect, and carry over titles, metas and structured data.

Can I move WooCommerce to Webflow? The WP to Webflow app says it doesn't migrate WooCommerce data. You'd need to export products separately and import them into Webflow Ecommerce, which is capped at 500, 5,000 or 15,000 items by plan. For large stores, compare Webflow vs Shopify.

How long does a migration take? It depends on content volume and design complexity. The content import is fast. Design, QA and redirects take most of the time.

Sources (all checked November 14, 2026)

Related guides