Migrating a B2B SaaS website from WordPress to Webflow without losing SEO
- Category:
- SEO
- Updated:
- Oct 31, 2026
Ask AI about this article
Moving a B2B SaaS site from WordPress to Webflow with rankings intact: what moves, what doesn't, the Webflow CMS limits that matter, a step plan and costs.
Artyum Grebenyuk Founder, AGR Studio TLDR:
You can move a B2B SaaS site from WordPress to Webflow without losing rankings if every URL stays or gets a 301, titles, descriptions and schema carry over, and plugins are replaced before launch. Check Webflow's limits first: CMS items always sit under a Collection folder, Webflow recommends at most 1,000 redirect rules, and CSV imports cap at 4 MB per file. Platform fees run $660 to $840 a year for a 20 to 40 page site with 2 to 3 editors, as of October 2026.
Yes, a B2B SaaS marketing site can move from WordPress to Webflow without losing search traffic, if every old URL either stays the same or gets a 301, titles, descriptions and schema move with the content, and every plugin's job is replaced before launch. Check three Webflow constraints before anyone designs a page: CMS items always live under a Collection folder such as /blog/, Webflow recommends no more than 1,000 redirect rules, and CSV imports are capped at 4 MB per file. The move pays off when your marketing team wants to publish without a developer. It doesn't when plugins run part of your sales process, or when you have a developer who already keeps WordPress healthy.
Our bias, stated once: we build on Webflow, WordPress, Framer, Next.js and Astro, we're an Official Framer Expert, and our own site moved from Framer to Astro and Sanity in October 2026. Prices and limits below are as of October 2026 and link to the vendors' own pages. For the platform decision itself, read Webflow vs WordPress; for the checklist that applies to any platform, how to migrate your website without losing SEO.
What moves from WordPress to Webflow, and what doesn't?
Content moves as data; everything a plugin did has to be rebuilt or replaced.
| On WordPress | On Webflow | How it moves |
|---|---|---|
| Posts and custom post types | CMS Collections (40 on Premium) | WordPress XML export, converted to CSV, imported per Collection |
| Pages built with a theme or page builder | Static pages in the Designer | Redesigned; only the copy carries over |
| Categories, tags, authors | Their own Collections, linked with reference fields | Imported first, so posts can match their slugs |
| Custom fields (for example ACF) | Collection fields | Mapped field by field |
| Featured images | Image fields | Imported by URL, without responsive variants |
| PDFs and downloads | File fields or assets | Uploaded by hand; file fields don't import from CSV |
| Yoast or Rank Math titles and descriptions | Page settings and CMS-bound SEO fields | Crawled from the live site, imported as columns |
| Schema from an SEO plugin | Schema markup field per page and Collection template | Rebuilt; reference fields can't be bound |
| Redirects (Redirection plugin, .htaccess) | 301 redirects in site settings | CSV import |
| Form plugins (Contact Form 7, Gravity Forms, WPForms) | Webflow forms or your CRM's form | Rebuilt and tested |
| WPML or Polylang | Webflow Localize | Re-imported per locale |
| Caching, security and backup plugins | Hosting on Cloudflare, SSL and backups included | Dropped |
| llms.txt from Yoast or Rank Math | An uploaded llms.txt file | Written and uploaded |
Sources: Webflow's WordPress migration guide, CSV import guide, schema markup, hosting and pricing; WordPress's export screen.
Should a B2B SaaS company move from WordPress to Webflow?
Move if marketing is blocked by developers and nobody wants to own plugin updates. Stay if WordPress does jobs Webflow can't, or the blog's URL structure makes the move expensive.
Good reasons to move:
- Every landing page waits on a developer. On Webflow a full seat designs new layouts visually, and limited seats edit content or build pages from existing components (Webflow pricing).
- Nobody owns updates. WordPress plugins and themes only auto-update "in special cases" unless someone switches it on (WordPress). On Webflow, hosting, SSL and platform updates are Webflow's.
- You want one bill and one place to look. Webflow sites are "securely stored and delivered by Cloudflare" with SSL included (Webflow).
Reasons to stay, or to look elsewhere:
- Gated areas or member logins run on WordPress. Webflow retired its native gated-content feature, User Accounts, on 29 January 2026 and points customers to third-party tools (Webflow).
- Thousands of posts sit at the root of the domain. Each one needs its own redirect (see the URL section below), and Webflow recommends 1,000 rules at most.
- You need more than 10 languages. Localize Advanced covers up to 10 locales and Essential up to 3 (Webflow pricing).
- Many occasional editors on a tight budget. New Webflow editors need a paid seat since the legacy Editor was retired on 5 October 2026 (Webflow). WordPress roles cost nothing.
- The site is content-heavy and multilingual, and you have developers. A headless CMS with a framework may fit better; see our website platform comparison for 2026.
Which Webflow CMS limits matter for a WordPress migration?
The plan limits are generous for a marketing site. The ones that bite are about structure: folders, references, imports and redirects.
- 20,000 items and 40 Collections on Premium. Basic is "for simple sites that don't need a CMS", so a blog needs Premium, at $25 a month billed yearly or $39 monthly (Webflow pricing). Categories, tags and authors are items too.
- 4 MB per CSV upload. A blog with long posts goes in as several batches (Webflow).
- 10 reference fields per Collection on non-Enterprise plans (Webflow). A post linked to an author, a category, a product area and an industry already uses four.
- 100 items per Collection list. Beyond that you paginate or stack lists with Skip. A page can hold up to 40 Collection lists, 10 nested, three levels deep (Webflow). A "show every post" archive becomes paginated.
- One folder per Collection. Items live at /collection-url/item-slug, and "only static pages can be organized in folders" (Webflow), so /resources/blog/post-name isn't possible for CMS items.
- Schema can't bind references. "Reference, Multi-reference, and Multi-image Collection fields aren't supported in schema markup" (Webflow).
- API rate limit. The CMS API allows 120 requests per minute on Premium (Webflow pricing). That matters if you script the import or sync data, such as an integrations list, from your product.
- Redirects: no hard cap, 1,000 recommended. Each rule is added to a file visitors' browsers download, so Webflow asks you to use wildcards where you can (Webflow).
What Premium adds that WordPress teams expect: scheduled publishing, per-item publishing, RSS feeds for Collections, site search and CMS item indexing control.
How do you keep WordPress URLs on Webflow?
Match your WordPress permalink structure to a Webflow Collection URL where you can, and redirect the rest with as few rules as possible. WordPress offers several permalink structures, and each lands differently.
| WordPress URL | Example | On Webflow |
|---|---|---|
| Custom with a folder | /blog/sample-post/ | Can stay: set the Collection URL to blog |
| Post name at the root | /sample-post/ | Can't stay: posts move under a folder, and each old URL needs its own rule, since there's no folder for a wildcard to match |
| Day and name | /2024/03/31/sample-post/ | A few wildcard rules that capture the slug, tested after publishing |
| Plain | /?p=123 | One rule per post, with the special characters escaped: /%?p%=123 |
| Numeric | /archives/123 | One rule per post, because the ID isn't in the new URL |
| Category and tag archives | /category/security/ | Redirect to a matching topic page, or to the blog |
| Feed | /feed/ | Point it at the Collection's RSS feed |
Three details that save a relaunch:
- Trailing slashes. WordPress URLs usually end in a slash. Webflow strips a slash that sits directly before a query string before it matches redirects, so
/slug/%?param%=value"will silently fail to fire"; write/slug%?param%=valueinstead. Test both versions of your top URLs after launch. - Order. Webflow runs redirects oldest first, so add specific rules before broad wildcards.
- Languages. Redirects "won't apply to localized slugs or subdirectories", so /old-url and /de/old-url need separate rules (Webflow).
If thousands of posts sit at the root, you have three options: accept more than 1,000 rules, consolidate thin posts into stronger ones and redirect them in groups, or keep the blog where it is for now. Google says larger sites can move "one section at a time" (Google), and Webflow documents how to serve a site through a self-managed reverse proxy on a paid Site plan, though its support team doesn't help set up or troubleshoot third-party proxies. That's work for a developer, but it lets the marketing pages move first.
Step by step: moving a B2B SaaS site from WordPress to Webflow
1. Inventory URLs, plugins and top pages
Start from the WordPress admin, not only a crawl: it shows drafts, hidden landing pages and the redirect rules a crawl misses. Add the XML sitemap, a full crawl, and 12 months of the Search Console Performance report by page, plus the most linked pages from the Links report. List every plugin and the job it does, and export existing redirects from the Redirection plugin, your SEO plugin or .htaccess.
2. Design the content model
One Collection per post type: posts, customer stories, integrations, careers, changelog. Taxonomies and authors become their own Collections joined by reference fields. Map each custom field to a Collection field type, and keep the reference count per Collection under 10.
3. Export and convert the content
WordPress exports "posts, pages, custom post types, comments, custom fields, categories, tags, custom taxonomies, and users" as one XML file from Tools, Export (WordPress). Webflow's guide says to convert that XML to CSV with a converter, then import (Webflow). In the spreadsheet:
- Clean shortcodes. Search the body column for square brackets. Shortcodes such as
[gallery]or[contact-form-7 id="12"]and page-builder markup show up as raw text. Webflow also "may clean up embeds to remove elements, classes, and attributes it doesn't support", so decide per shortcode whether it becomes HTML, a component or nothing. - Keep slugs exactly. Same characters, same case.
- Split into files under 4 MB.
4. Import in the right order
Authors, categories and tags first, posts last. Webflow matches a reference by turning plain text into a slug ("Charles Dickens" becomes charles-dickens); if a WordPress term has a custom slug, put the slug in the CSV, or the reference stays empty. Separate multi-reference values with semicolons. Take the backup Webflow offers before each import. On a multilingual site you can import into one locale or all of them, and link translated items to their originals by re-importing with the exported item IDs (Webflow).
5. Move images and files
Image fields import from a direct URL, but these images "don't get responsive image variants (srcset and sizes)", so resize the big ones first or upload key images directly. Keep WordPress online until every import is done, so every /wp-content/uploads/ URL still resolves. After import, search the rich text for wp-content to catch images still loading from the old server. File fields don't import at all: upload PDFs by hand, and redirect old file URLs that have backlinks.
6. Carry over SEO data and schema
- Titles and descriptions. Yoast and Rank Math build them from templates. Crawl the live site and record what each URL outputs: title, description, canonical, robots tag. Import those as fields and bind them on the Collection template; set static pages in page settings. Webflow's CMS item indexing control keeps noindex choices.
- Canonicals. Set the global canonical tag to your domain with https and without a trailing slash (Webflow).
- Schema. Rebuild Article schema in the Collection template's schema field, bound to CMS fields. Since reference fields can't be bound, add a plain-text author name field. Add Organization schema to the homepage.
- Sitemap and llms.txt. Webflow generates the sitemap on each publish and adds it to robots.txt. If Yoast or Rank Math generated your llms.txt, on Webflow you upload the file yourself, and Webflow doesn't create Markdown versions of pages.
7. Replace forms and integrations
On a SaaS site these are the demo request, contact, newsletter and gated-content forms. For each one, write down the fields, the destination, the consent text and the thank-you page that counts as a conversion. Then rebuild it as a Webflow form, which stores submissions, sends notification emails and exports CSV (Webflow), or embed your CRM's own form. Re-point every automation, add GA4 through Webflow's Google Analytics integration, and send a real test through every form.
8. Load redirects, then switch the domain
Build one sheet: old URL, new URL. Point old WordPress redirects straight at their final page, so nothing chains. Import it as CSV (up to 16 MB), knowing that an import "removes any existing redirects on your site" (Webflow), then publish. Verify the domain in Search Console through DNS, so the property survives the move. Switch DNS only when the redirects are live.
9. Watch the first month, keep redirects for a year
On day one, run every old URL through a crawler: each should return a 301 to the right page, then a 200. Submit the sitemap in Search Console and Bing Webmaster Tools. Watch the Pages report for 404s and redirect errors, and compare clicks on your top pages against the export from step 1. Google says a small to medium-sized site "can take a few weeks for most pages to move", and to keep redirects "generally at least 1 year" (Google). Keep the WordPress install and a full backup until the checks are done.
What does Webflow cost compared with keeping WordPress?
On fees, WordPress is cheaper. Once you count developer time for updates, Webflow is usually cheaper for a small marketing team, unless you already pay a WordPress developer.
Assumptions: a 20 to 40 page B2B site with a blog, English only, under 50 GB of bandwidth a month, one owner plus 2 to 3 content editors, list prices in USD for one year as of October 2026, excluding tax, domain and the migration itself.
| One year | Webflow | WordPress |
|---|---|---|
| Platform | Premium: $300 billed yearly ($468 billed monthly) | $0 |
| Hosting | Included | Your host's price (no official figure) |
| 2 to 3 content editors | Limited seats: $360 to $540 billed yearly ($456 to $684 monthly) | $0 |
| An in-house designer | Full seat: $468 billed yearly ($540 monthly) | $0, but layout changes on a custom theme are developer work |
| Each added language | Localize $108 (Essential) or $348 (Advanced) per locale, billed yearly | WPML from €39, or Polylang free with Pro from €99 a year |
| Upkeep time | Close to none for updates | 24 to 48 developer hours, our estimate |
| Total for the base case | $660 to $840 billed yearly | Hosting, plugins, plus 24 to 48 hours |
Sources: Webflow pricing, WPML, Polylang. The upkeep estimate assumes a theme plus SEO, caching, security and backup plugins, and a monthly update round checked on staging; the full breakdown is in Webflow vs WordPress. Larger teams that need more seats, governance and localization in one contract can look at Webflow's Team plan, at $2,500 a month on an annual contract.
The migration is a one-off on top. We quote 3 to 5 weeks for a standard B2B site, homepage first in 1 to 1.5 weeks including feedback, then the remaining pages from its components. A big blog adds import and redirect work; several languages add more. We quoted 15 business days for a 5-language migration with QA.
What we've seen on client projects
- Why teams leave WordPress. In 101 client conversations from January to October 2026, platform choice came up in 46%, and WordPress was described as needing plugins and maintenance. Teams wanted marketing to publish without a developer.
- CMS access beats a crawl. We ask for WordPress admin access, or a full URL export, because it finds hidden pages and old redirects that a crawl misses, plus GA4 and Search Console to see what earns traffic. We pull backlinks ourselves.
- Schema is often missing before the move. A cybersecurity SaaS migrating five languages asked for "SEO and LLM optimisation". Structured data was missing, and per-locale metadata needed to be generated, not typed by hand.
- Components decide the speed afterwards. One team with "no Figma, the website is our design system" took about two weeks per new page. The plan was a CMS plus documented components to roughly halve that. On Webflow, that component library is what lets limited seats build pages.
- Redirect counts are real. When we moved our own site off Framer in October 2026, about 80 redirect rules went live at the switch, 91 today, and we compared the old and new sites page by page before moving DNS.
If you want a second opinion on what moving your WordPress site would involve, tell us about it.
FAQ
Can I migrate my WordPress site to Webflow without losing SEO?
Yes, if every old URL either keeps its path or gets a 301 redirect in Webflow before the domain switches, and titles, descriptions and schema are carried over for every page. Rankings usually move for a few weeks while Google processes the new site, and Google recommends keeping redirects for at least a year. Lasting losses come from URLs that disappear without a redirect.
Does Webflow have a WordPress importer?
Not a one-click one. Webflow's own guide says to export WordPress content as XML, convert it to CSV with a converter, and import it into each CMS Collection, mapping columns to fields. Pages built with a theme or page builder are redesigned in Webflow; only their copy carries over.
Will my WordPress URLs change on Webflow?
Blog posts that already sit in a folder, such as /blog/post-name, can keep their URLs. Posts at the root of the domain can't, because Webflow serves every CMS item under its Collection's folder, so each one needs its own 301. Dated, numeric and ?p= URLs also need redirects.
What happens to Yoast or Rank Math when I move to Webflow?
The plugin doesn't come with you, but its output can. Crawl the live site to capture each URL's title, description, canonical and robots tag, import them as CMS fields and bind them on the Collection template. Schema is rebuilt in Webflow's schema markup field, which can't bind reference fields, and llms.txt is a file you upload yourself.
How many redirects can Webflow handle?
Webflow has no hard limit but recommends 1,000 rules at most, because each rule adds to a file visitors' browsers download. Use wildcard rules with capture groups, such as /blog/(.*) to /articles/%1, wherever a whole folder moves. Redirects can be imported from a CSV file of up to 16 MB, but an import replaces every existing rule.
Is Webflow cheaper than WordPress for a B2B SaaS website?
Not on fees: a Webflow site with a blog needs Premium at $25 a month billed yearly, plus $15 a month per new content editor, about $660 to $840 a year with 2 to 3 editors as of October 2026. WordPress software and roles are free, but hosting and, in our estimate, 24 to 48 developer hours a year of updates usually make Webflow cheaper for a small team without a developer.
Blog