WordPress vs Webflow,how I choose without regrets

When a company rebuilds its brochure or B2B website, the question "WordPress or Webflow?" almost always comes up. Often the answer is there before the discussion starts: WordPress because everyone uses it, Webflow because the demo looked good. Both build good websites. What separates them tends to show two years later.

I have worked for clients on WordPress sites and on Webflow sites. For Moonworkers, my own company, and for this site, I made a third choice, Next.js and Sanity. So I have no tool to sell you, and here is the grid I use to decide.

01What Google looks at, and what it ignores

Let's set aside a false criterion first: search rankings. In a video on the Google Search Central channel, John Mueller answers the question very directly (Google Search Central, Does a CMS matter for ranking in Google Search?). I read the transcript: Google's systems don't look for any particular CMS to treat it differently, a CMS is just one way of creating pages, and Google looks at the final result. In his view, all mainstream CMSs can produce pages that work well in search.

What matters is what you do with it: titles and descriptions filled in, clean URLs, fast pages, useful content. WordPress gets there with a plugin and a few settings, Webflow with its built-in fields. If someone tells you one "ranks better" than the other, ask them what they are measuring.

02Two different models: open source software and a platform

The real difference lies elsewhere, in the model.

WordPress is open source software, released under the GPL licence, which gives you the freedom to run it, study it, change it and redistribute it (WordPress.org, About WordPress). In practice, you choose your host, install whatever theme and plugins you like, and can take the whole site (files and database) to another supplier. That freedom comes with a catch: someone has to look after all of it.

Webflow is a platform. The design tool, the CMS and the hosting come together, from the same company. You manage neither a server nor updates, and the visual editor lets you separate the people who design from the people who write. I described that split of roles in my article on Webflow for a B2B website. In return, you stay within the frame the vendor has set.

I don't think one is better than the other. The question is which constraint bothers you least: maintaining the site yourself, or depending on a platform.

03Maintenance, the hidden cost of WordPress

With WordPress, the first thing I look at is who will do the maintenance, and I write it into the specification. The official documentation is clear: you should always keep up to date with the latest version, because older versions no longer receive security fixes (WordPress Developer Resources, Hardening WordPress). The same page advises taking themes and plugins only from the official directory or from well-known companies, keeping them updated, and deleting the ones you no longer use.

Automatic updates help, but not with everything. By default, they cover minor core releases, meaning maintenance and security; for plugins and themes, they only run in special cases decided by the WordPress security team, unless you switch them on yourself (WordPress Developer Resources, Upgrading WordPress). The documentation also recommends a backup before each update.

On launch day, everything is fine. It's afterwards that upkeep starts to slip: a plugin installed for a one-off need stays put, another is no longer maintained by its author, and nobody dares touch anything for fear of breaking a page. If nobody in your team has that role, plan for it with a supplier, or choose a tool that takes care of it.

04Leaving, the weak spot of Webflow

With Webflow, the question to ask before signing is about leaving: what can you take with you on the day you go?

The Webflow Help Center answers precisely (Webflow Help Center, How do I export my Webflow site code?). Code export (HTML, CSS, JavaScript and images) is only available on Workspace plans, not on Site plans. And it doesn't include CMS content, ecommerce, user accounts, secondary languages, site search or form handling. On an exported site, collection lists show up empty. Collections can be exported separately as CSV files, which you will then have to import somewhere else.

For a brochure site of a few pages, that's not a problem: you rebuild quickly. For a site with a blog of several hundred articles, case studies and two languages, leaving Webflow becomes a project in its own right. That doesn't rule Webflow out. You just need to know it beforehand, and add the CSV export of your collections to your regular backups.

05My grid in five questions

Here are the questions I ask, in this order. I write the answers down, because a tool decision made out loud gets reopened at every meeting.

The five questions

1. Who will edit the site every week, and do they want to learn a tool? A marketing team that launches campaign pages on its own leans towards Webflow.
2. Who, by name, will run the updates and backups? If the answer is "nobody", WordPress becomes risky.
3. What must the site do beyond presenting the company? A catalogue, a customer area or calculations point towards WordPress and its plugins, or towards a custom-built site.
4. What do you want to be able to take with you if you change supplier or tool? If the answer is "everything, effortlessly", WordPress is easier to move.
5. How much content will you have in two years, and in how many languages? The more there is, the more leaving and the organisation of the CMS matter.

How I read the answers

If the team wants to publish on its own, no developer is planned and the site is mostly pages and articles, I lean towards Webflow. If the site has to do specific things, you have someone to maintain it and you want to be able to move everything, I lean towards WordPress.

And if the site has to handle calculations, automated publishing at scale or content tightly linked across several languages, I look at a custom-built site. That's what I did for Moonworkers in May 2026, and I described it in my article on migrating a website to Next.js and Sanity. It is not a default choice: it needs someone to maintain the code. I explain what that model brings and what it costs in my article on Sanity as a headless CMS.

06If you switch tools, change only one thing at a time

Many "WordPress or Webflow" requests are really migrations: the site exists and you want to change the tool. Google advises making one change at a time: if you want to change your domain name, your CMS and your layout, do it in separate steps (Google Search Central, How to move a site). The same page asks for a mapping of old URLs to new ones, permanent redirects (301 or 308), no mass redirects to the home page, and redirects kept for at least a year. It also warns that rankings may fluctuate for a few weeks.

My checklist before switching

1. I export the list of every URL on the current site, including PDF files and images that get visits.
2. I write the new address of each one in a versioned table. On a complex integration, I learned that a document that changes at every meeting needs a version number, so that everyone talks about the same one.
3. I rebuild the content, then check titles, descriptions and canonical tags page by page on a sample.
4. I test the forms all the way to the CRM, with a real submission.
5. After the switch, I check the site as a visitor would: private browsing, no session, on the public address. I once saw a site that looked fine to the logged-in team and was broken for visitors, because of the cache.

If you are starting from an existing site, a technical audit before the redesign will tell you what you absolutely need to preserve.

07Where to start

This week, take half an hour to answer the five questions in writing, with the real names of the people involved. Add the list of pages your team created or edited over the last twelve months. With those two documents, the choice between WordPress and Webflow often becomes obvious, and it goes straight into your website specification.

If you would like an outside view on this choice, with no stake in either tool, my services page explains how I work, and my projects show what I have already built. Happy to talk it through.