WordPress to Webflow Migration Without Losing SEO: The Steps, the Limits and the Redirect Traps

Key takeaways

• There is no one-click move. WordPress exports an XML file; Webflow imports CSV files into CMS Collections. Webflow's help centre says to convert the XML to CSV, then import and map the fields.
• Your post addresses will probably change. In Webflow, CMS item pages sit inside a Collection folder, such as /blog/your-post. If your WordPress posts live at /your-post/ or /2024/05/28/your-post/, each needs a redirect.
• A redirect CSV import replaces every existing redirect. Webflow's help says new imports overwrite all existing redirects, so export first, merge, then import.
• Escape special characters in old paths. Webflow lists the hyphen among the characters to escape with % in old paths, which matters because almost every WordPress slug has hyphens.
• Keep the rule count sensible. Webflow has no hard limit but recommends 1,000 redirects at most, and suggests wildcard rules where possible.
• Imported images lose responsive versions. Images imported by URL through CSV do not get responsive variants, per Webflow, so optimise them first or upload them in Webflow.

Before you start: is Webflow the right move?

A migration is a rebuild, so be sure the reason is worth it. Moving makes sense when plugin updates, security patches and developer time for small edits cost you more than they should, or when your team wants to edit pages visually. It makes less sense if your site depends on a plugin with no equivalent, or if you publish thousands of posts with a complex taxonomy. Our Webflow vs WordPress comparison covers that decision, and our Webflow cost guide covers the plan you will need.

Check the plan before you import. Webflow's Premium site plan includes 20,000 CMS items and 40 collections (read on its May 2026 plan-change page on 22 October 2026), and its help centre says the number of items you can import depends on your plan.

Step 1: Record what you have

Before anything changes, take a copy of everything that earns traffic:

• Every URL. From your XML sitemap, a crawl, Search Console's page report and your analytics. No single list is complete.
• Top pages by clicks and by links. These are the pages whose redirects you test first.
• Titles, descriptions and canonical tags for each URL.
• Your permalink setting in WordPress under Settings, then Permalinks.
• Forms, scripts and plugins that do something visitors see: booking, search, popups, membership.

Our redesign SEO checklist has a fuller version of this inventory and a sheet to record it.

Step 2: Export the content from WordPress

WordPress's documentation says Tools, then Export, creates an XML file in its WordPress eXtended RSS (WXR) format, containing posts, pages, custom post types, comments, custom fields, categories, tags, custom taxonomies and users. You can export everything or filter by posts or pages, category, author, date range and status.

That list does not include the media files themselves, so plan to collect images and downloads separately.

Step 3: Turn it into CSV and import it

Webflow's WordPress migration article says to convert the XML file to CSV with an XML to CSV converter, create a Collection, import the CSV and map each column to a field. Its CMS import article adds the limits that catch people out:

Shortcodes are the most common surprise. WordPress plugins turn text such as a gallery or button shortcode into HTML when the page loads; in the export it is stored as plain text, so search the rich text for square brackets after import.

Step 4: Decide the new addresses

Webflow's help describes the Collection URL as the slug for the folder that holds a Collection's item pages. A blog Collection with the URL "blog" gives you /blog/post-name. That means:

Static pages such as /about or /services/web-design can usually keep their exact address, so keep them. The WordPress permalink documentation lists the six settings and notes that category and tag archives use a base such as /category/name, which also needs a destination.

Step 5: Write the redirects

Webflow's redirect help gives the rules. They are what most migration guides leave out:

1. Escape special characters in the old path. Webflow lists %, -, &, *, (, ), =, _, +, and ? as characters to escape with a % in front, in old paths and wildcard paths. A WordPress slug such as /my-first-post/ is written /my%-first%-post in the old path. The new path needs no escaping.
2. Use capture groups for patterns. (.) captures a segment and %1, %2 and so on reuse it. A date-based structure can be handled with one rule, for example an old path of /20(.)/(.)/(.)/(.*) sent to /blog/%4. Test patterns like this on staging, because a broad pattern can catch addresses you did not mean it to.
3. Order matters. Webflow runs redirects in the order they were added, oldest first, so add specific rules before broad wildcards.
4. A query-string quirk. Webflow removes a trailing slash directly before a query string before matching, so an old path of /slug%?param%=value works and /slug/%?param%=value silently fails.
5. Locales are separate. Redirects are relative to the root domain and do not apply to localised paths, so /es/old-url needs its own rule.
6. Mind the count. Webflow recommends 1,000 redirects at most, because each rule is added to a file browsers download. For a Post name site with thousands of posts, that is a real constraint: consider whether every old post needs to move, merge thin posts, and redirect retired ones to their closest topic page.

For bulk work, Webflow's import accepts a two-column CSV of old and new paths, up to 16 MB. Three rules apply: an import overwrites all existing redirects, an invalid row makes the whole import fail, and nothing takes effect until you publish. Export the current list, add your rows, then import the merged file.

Step 6: Launch and check

• Publish the redirects before you switch the domain, so no visitor or crawler meets a 404.
• Test your top pages by hand, then test the full old URL list with a crawler: each should return one 301 to the right page, not a chain.
• Make sure the staging subdomain is not what gets indexed, and that canonical tags point at the live domain.
• Submit the new sitemap in Search Console and watch the pages and 404 reports for the first few weeks.

What the ranking guides say on time and price

We read the top results for this search on 22 October 2026. None of the pages listed below mentions the 4 MB import limit, the redirect overwrite, character escaping or the Collection folder in addresses.

If you would rather hand the job over, our list of migration studios compares what each one commits to in writing.

How we run a WordPress to Webflow move

At Amariq we start with a full inventory of URLs, ranking pages, forms and tracking, and the redirect map is agreed during design rather than the night before launch. Our Webflow migration page puts most moves at four to ten weeks, driven by the number of pages and posts, the clean-up needed and whether the design changes too. Rahat Khondokar, our founder, is a certified Webflow developer. Pricing follows the scope, never the hours, and payment is staged: 40% to begin, 30% at design approval and 30% before launch. The design, copy and code transfer to you with the final payment, and the domain, hosting and analytics accounts are kept in your name.

Frequently asked questions

Can I migrate WordPress to Webflow automatically?

Not in one step. Webflow's help centre describes exporting WordPress content as XML, converting it to CSV and importing it into a Collection. The design is rebuilt in Webflow.

Will I lose SEO moving from WordPress to Webflow?

Not if every changed address has a working 301 redirect and titles, descriptions and content come across. Rankings can wobble for a few weeks after any move, so watch Search Console and fix 404s quickly.

Can I keep my WordPress URLs in Webflow?

Static pages, yes. Blog posts usually not exactly, because Webflow puts CMS item pages inside a Collection folder such as /blog/. Posts that move need a redirect.

How many redirects can Webflow handle?

Webflow says it has no hard limit but recommends 1,000 at most, and suggests wildcard rules to keep the number down.

Why did my redirects disappear after a CSV import?

Webflow's import replaces all existing redirects with the contents of the file. Export your current redirects first, add the new rows to that file, then import it.

Why does my redirect not work?

The usual causes are an unescaped character in the old path (Webflow lists the hyphen among them), a broader wildcard added earlier that catches the address first, a slash before a query string, or a site that has not been published since the redirect was added.

How long does a WordPress to Webflow migration take?

The pages we read give 2 to 4 weeks for small sites and several months for enterprise sites. Our own service page says four to ten weeks for most migrations.