Moving from WordPress to Webflow: content, URLs and SEO, step by step

Moving from WordPress to Webflow is more than switching a site's platform: the design is rebuilt, the content moves into a new model and the URL structure often changes. A well-planned migration gives the team less maintenance and a faster publishing workflow; an unplanned one costs organic traffic.

This post is a step-by-step roadmap for marketing and web teams considering the move. The technical details come from Webflow's own help documentation. For a detailed checklist on the redirect and monitoring side, see our website migration SEO checklist.

First, the decision: do you really need to migrate?

Webflow and WordPress are different models. Webflow is a SaaS platform that manages hosting, updates and infrastructure itself; WordPress is open source, installed on your own server or with a hosting provider, and extended with plugins. In its own migration guide, Webflow highlights having no plugin dependency, built-in hosting and visual design.

Typical cases where migrating makes sense:

• The marketing team constantly depends on a developer to publish pages and content.
• Plugin and theme updates create a steady maintenance load and security risk.
• The site is going to be redesigned anyway.

There are also cases where migrating is hard: sites that rely on many custom plugins, custom post types or server-side processing. For a general comparison of the platforms, see our Webflow vs WordPress page. For those who do not want to move completely, Webflow also has a WordPress plugin: the Webflow Pages plugin lets you publish pages designed in Webflow on your existing WordPress site.

1. Inventory: what do you have?

The foundation of the migration is a complete inventory. Make three lists:

• URL inventory: every page, post, category, tag, author and media URL on the site, with those that get traffic and external links flagged.
• Content types: posts, pages, custom post types and the custom fields of each.
• Plugins: the job each plugin does on the site: SEO, forms, caching, multiple languages, redirects, analytics, security.

The plugin list is the one most often skipped. A page or a form generated by a plugin can quietly disappear after the move.

2. Content model: translating the WordPress structure to Webflow

Each content type in WordPress maps to a CMS collection in Webflow. A typical mapping:

Two Webflow limits affect which plan you choose. As of October 2026, the Basic site plan has no CMS; a site with a blog needs Premium, and Premium is limited to 20,000 CMS items and 40 collections. On plans other than Enterprise, you can add at most 10 reference fields per collection. For details, see our Webflow CMS guide.

The budget changes too. On WordPress, hosting, the theme and paid plugins are paid for separately; on Webflow, hosting is included in the site plan, while add-ons such as team seats and languages are billed separately. As of October 2026, the Premium site plan is US$25 a month billed yearly; on a two-language site, the Localize add-on comes on top of that. For plan and total-cost calculations, see our Webflow pricing 2026 guide.

3. URL structure: know what will change

Webflow publishes collection pages under a folder: in a collection whose Collection URL is blog, a post's address becomes /blog/post-name. If your WordPress posts sit at the root (/post-name) or use a dated structure (/2024/05/post-name), these URLs change and each needs a redirect.

The order of decisions should be:

1. Keep valuable URLs wherever you can. Most static pages can be rebuilt with the same slug.
2. For URLs that have to change, define the new structure once and do not change it afterwards.
3. If you will not rebuild category, tag and author archives in Webflow, redirect them to the closest page.

4. Importing the content

The route in Webflow's WordPress migration guide is this: WordPress exports content as XML by default; the XML is converted to CSV with a converter; then you create a collection in Webflow, import the CSV and map the columns to fields. Webflow notes that CSVs coming from WordPress usually have a compatible structure.

Points to watch during the import, according to Webflow's CSV documentation:

• File size: 4 MB at most. Split large archives into parts.
• Images: an image field takes the image URL directly; images brought in this way do not get responsive variants. Upload important images already optimized.
• References: reference values such as category and author are converted to slugs and matched. Import the referenced collections (authors, categories) first, then the posts.
• Files: file fields cannot be filled via CSV; upload them by hand afterwards.
• Backup: Webflow recommends taking a backup before the import; it can be restored from Site settings > Backups.

If you have a large volume of content or need regular syncing, you can also use Webflow's Data API. Whichever route you choose, remember to update the internal links in post bodies to the new URLs.

5. Finding equivalents for your plugins

For every job outside this table (memberships, complex calculators, server-side processing), decide on an app, an integration or custom code before the move. For the details of the SEO settings, see our post on Webflow SEO settings.

6. The 301 redirect map

Every URL that changes is written on one row with its old and new address. In Webflow you can enter redirects one by one or upload them in bulk via CSV. The key points from Webflow's documentation:

• Plan: 301 redirects require a paid site plan or a paid Workspace plan.
• Number: there is no hard limit, but Webflow recommends at most 1,000 redirects. For hundreds of posts moving from the root to /blog/, consider a pattern instead of one rule per post.
• Folder rule: wildcard rules such as old path /category/(.*) and new path /blog/%1 move a whole folder in one line.
• Order: redirects run in the order they were added; add specific rules before broad ones.
• CSV import: the file can be 16 MB at most; a new import overwrites all existing redirects.

For the technical logic of redirects, see our 301 redirect glossary entry.

Using the migration to clean up content

A migration is a good chance to review content that has piled up over the years, but that decision should rest on the inventory, not on guesswork. For each URL, pick one of three options:

• Keep: current content that gets traffic or external links lives on at the same or a new URL.
• Merge: several weak posts on the same topic are combined into a single, up-to-date post, and all the old addresses redirect to it.
• Remove: content with no traffic, links or business value is deliberately removed; if it has no equivalent, it returns a 404 or 410.

To make this call, use Search Console impression and click data from the last 12–16 months together with landing-page traffic from your analytics and backlink data. Accidentally removing a valuable page is one of the most expensive mistakes in a migration.

Do not lose titles and descriptions in the move either. Custom titles and descriptions entered with an SEO plugin in WordPress live in the plugin's own fields, not in the post body; when you convert the XML to CSV, extract them as separate columns and bind them to the SEO fields in Webflow. On valuable pages, either keep this text exactly or deliberately improve it.

7. Launch day and after

• Connect the domain to Webflow and set the default domain.
• Turn on the global canonical URL and the automatic sitemap.
• Test every old URL in the redirect map: each one should reach the right address in a single hop.
• Submit the sitemap to Search Console; in the first weeks, watch 404s and the indexing reports.
• Try out forms and analytics tags in the live environment.
• Keep the old WordPress installation as an accessible backup until the new site is verified.

Conclusion

The success of a WordPress-to-Webflow migration depends less on the new design than on the invisible work: a complete URL inventory, a well-thought-out content model, equivalents for your plugins and a tested redirect map. When these four jobs are done before the move, launch day is just an ordinary day. If you want to plan the migration together, see our WordPress to Webflow migration service, or our Webflow agency page for all our Webflow services.

Sources

• Webflow Help Center, Migrate your site from WordPress to Webflow: https://help.webflow.com/hc/en-us/articles/33961193662739-Migrate-your-site-from-WordPress-to-Webflow (accessed October 2026)
• Webflow Help Center, How do I import content into the Webflow CMS?: https://help.webflow.com/hc/en-us/articles/33961290794771-How-do-I-import-content-into-the-Webflow-CMS (accessed October 2026)
• Webflow Help Center, Manage CMS Collections: https://help.webflow.com/hc/en-us/articles/33961244391059-Manage-CMS-Collections (accessed October 2026)
• Webflow Help Center, Reference Collection field: https://help.webflow.com/hc/en-us/articles/33961317363091-Reference-Collection-field (accessed October 2026)
• Webflow Help Center, How do I set up redirects in Webflow?: https://help.webflow.com/hc/en-us/articles/33961294898835-How-do-I-set-up-redirects-in-Webflow (accessed October 2026)
• Webflow Help Center, Import/export 301 redirects: https://help.webflow.com/hc/en-us/articles/33961211526291-Import-export-301-redirects (accessed October 2026)
• Webflow Help Center, Webflow Pages plugin for WordPress: https://help.webflow.com/hc/en-us/articles/33961370570131-Webflow-Pages-plugin-for-WordPress (accessed October 2026)
• Webflow, Plans & pricing (plan limits and the code-import FAQ): https://webflow.com/pricing (accessed October 2026)