Webflow vs
custom-built website

In our general article CMS vs custom-built website we compare CMS platforms in general with custom-built websites.

Here we zoom in on Webflow. Webflow isn't a CMS with plugins, but a visual design platform with its own hosting. We find out what's true — and what isn't — about the idea that Webflow is bad for SEO, and which downsides actually matter.

Webflow in a nutshell.

Marnix Zandijk
Marnix Zandijk | DYKZ

Webflow in a nutshell.

Can't code, but still want to impress? Then you'll likely end up at Webflow. Drag, drop, and within no time you've got a design that looks like custom work — while in reality, you're just renting a spot under Webflow's roof.

Is it true:
Webflow and SEO?

The idea that Webflow is beautiful but bad for SEO is an outdated assumption. Webflow generates clean, semantic HTML by default, without needing any separate plugins. You set your own title and meta description per page. Sitemaps, 301 redirects, and canonical tags are native to the platform.

The consensus among specialists in 2026 is that the platform itself is rarely the reason a Webflow site fails to rank. What often does go wrong: a weak content strategy, poor internal linking, or — specific to Webflow — a sloppy migration where old URLs aren't properly redirected. That last point, by the way, isn't a Webflow problem, but an execution problem that can happen with any platform switch.

Webflow website

  • Clean HTML, native technical SEO tools
  • × Vendor lock-in, tied to Webflow hosting
  • × Costs rise with more content/traffic
  • × Hard limits on CMS items
  • × Limited for iDEAL/complex webshops

DYKZ custom-built website

  • 100% W3C valid, proprietary HTML
  • No platform dependency, free choice of hosting
  • No recurring monthly subscription
  • No artificial content limits
  • Complete freedom in integrations and functionality
 

What exactly is Webflow?

Webflow is a visual design and CMS platform. You build a website on a canvas, similar to design software like Figma, while the system generates working code in the background. There's no need for separate plugins. Functionality like CMS, forms, and hosting are built into the platform by default. That makes it attractive for designers and marketing teams who want a unique design quickly, without needing to be able to write code themselves.

It's also not an open-source CMS that you host yourself, but a closed SaaS platform. You're essentially renting a spot within Webflow's own infrastructure, rather than owning a website you can move anywhere you like.

Why DYKZ doesn't use Webflow

At DYKZ, we deliberately don't build Webflow sites, but hand-written custom work instead. First of all: with Webflow you're always a tenant on a platform you have no control over. At DYKZ, the website and the code are entirely yours. No subscription that runs indefinitely, and no dependency on decisions another company makes for you. You're free to decide what you do with your website and where you host it.

Webflow in practice.The real downsides

1. Vendor lock-in

Webflow: This is the most commonly cited structural downside. Your website runs entirely on Webflow's own hosting and infrastructure. You have nowhere else to go. If you ever want to switch to another provider, in practice you don't take a working website with you — you start a complete rebuild. As long as you stay with Webflow, you're always dependent on their decisions about pricing, features, and policy.

DYKZ: You own the code, the website, and the domain entirely yourself. You choose your own hosting, or have DYKZ arrange it for you, but you're not locked into anything. If you want to move, you simply take your fully working website with you.

2. Costs that add up

Webflow: A simple website starts at around $14 a month, but a business site with more CMS content quickly reaches $23 to $39 a month, excluding extras. Multilingual support costs extra, around $29 per language per month. Add more team members, and those extra seats count too. That's a structural, ongoing monthly cost, no matter how long you've been a customer.

DYKZ: A higher one-off investment upfront, but no ongoing platform subscription afterward. Hosting costs whatever it costs with a regular hosting provider, with no platform markup on top. You have complete freedom in choosing your hosting.

3. Hard content limits

Webflow: Every plan has a maximum number of CMS items. On the standard business plan, that limit sits around 10,000 items. Grow beyond that, and you need to move to an expensive Enterprise plan. For businesses with a lot of content or complex data structures, that can start to pinch.

DYKZ: No artificial limit on how much content, how many pages, or how many products you have. The structure is built specifically for your scale.

4. Limited for Dutch e-commerce

Webflow: The built-in webshop functionality isn't tailored to the Dutch market. iDEAL and Mollie aren't natively available, and things like tiered pricing, complex product variants, or extensive inventory management require custom work or external integrations. For a serious Dutch webshop, this is often a dealbreaker.

DYKZ: A payment integration like the one we've built with Mollie and iDEAL connects directly to what Dutch customers expect, with no platform restrictions.

5. Deeper integrations and user accounts

Webflow: Complex integrations with CRM, ERP, or ticketing systems always require external middleware or custom development. The platform itself doesn't go deep enough for that. On top of that, Webflow discontinued its own built-in user accounts feature: for customer portals or private member areas, you're now dependent on third-party apps.

DYKZ: No platform ceiling dictating what is and isn't possible. Complex integrations and your own login environments are simply part of the custom build.

6. Performance with heavy animations

Webflow: For a simple site, Webflow's hosting is fast by default. But as soon as a site includes a lot of custom interactions and animations, Webflow's own JavaScript adds noticeable delay to page load — meaning complex, animation-heavy Webflow sites can end up scoring lower on Core Web Vitals than you'd expect.

DYKZ: Because no platform JavaScript you don't use is ever loaded, a DYKZ custom-built website stays consistently lightweight, even with extensive functionality, with Google PageSpeed scores of 95 to 100 as the standard.

When is Webflow a good choice?

 

Despite the downsides above, Webflow is a solid choice in a number of situations:

  • You're a designer or marketer without coding knowledge and want to build and adjust a unique design quickly and visually, without a developer.
  • You have no need for a Dutch webshop with iDEAL, or your e-commerce needs are simple.
  • A monthly subscription isn't an issue for you, and full ownership of your hosting isn't a priority.
  • Your content stays comfortably under the CMS limits of your chosen plan.
  • You work with a team of multiple designers/marketers who want to build on the same website simultaneously.

In short: for a fast, visually strong marketing site without complex Dutch e-commerce needs, Webflow can be a perfectly reasonable choice.

When is DYKZ custom-built the better choice?

 

Specifically compared to Webflow, custom-built at DYKZ is the better choice if:

  • You don't want a recurring subscription that keeps running for as long as your site is online.
  • You need a Dutch webshop with iDEAL, without having to bolt on external integrations.
  • You don't want to depend on a single platform company for your pricing, features, and hosting.
  • You expect significant growth in content or products, without running into artificial limits.
  • You need deeper integrations, for example with a CRM, booking system, or your own customer portal.
  • You'd rather have one dedicated point of contact than a platform whose limits you keep running into.

The conclusion

The honest answer to "is Webflow bad for SEO" is: no, that's an outdated view. The real trade-off with Webflow lies in vendor lock-in, rising costs, hard content limits, and restrictions around Dutch e-commerce and deeper integrations.

Want to build a fast, visually strong marketing website with no Dutch webshop needs? Then Webflow is a serious option. Want a website that's fully yours, with no ongoing subscription, no platform limits, and complete freedom? Then a DYKZ custom-built website is the more logical choice.

Still not sure, or want to know what this means for your specific situation? Feel free to get in touch for a no-obligation consultation.

Frequently asked questions
About switching from Webflow

Frequently asked questions
About switching from Webflow

Can DYKZ take over my existing Webflow website?

Yes, there are absolutely possibilities for this. We take over the design, content, and structure of your current Webflow site and rebuild it as hand-written custom code, completely independent of the Webflow platform. You're no longer a tenant afterward — you own your own website.

Can I simply bring over my Webflow CMS content?

Yes. We export text, images, and CMS items from Webflow and rebuild them within your new custom structure, without you losing any content or having to re-enter it.

Will I lose my Google rankings if I switch from Webflow?

Not if the switch is handled carefully. We set up 301 redirects from every old URL to the new page and preserve or improve your existing metadata and content structure. Ranking loss during a platform switch is almost always caused by a sloppy migration, not by the switch itself. A migration through DYKZ is handled with great care, so you don't need to worry about your rankings.

What happens to my Webflow subscription after the switch?

You cancel that yourself. Usually only once the new website is live and you've confirmed everything works properly. As soon as that subscription ends, the ongoing monthly cost that comes with Webflow disappears too.

Can you rebuild the animations and interactions from Webflow?

In most cases, yes. We rebuild animations and interactions by hand in clean code, often even lighter and faster than the Webflow version, because no platform JavaScript you don't use is loaded along with it.

How long does switching from Webflow to DYKZ custom-built take?

That depends on the number of pages and how many custom interactions your site contains, but expect a timeline similar to a new website. Usually two to three weeks once the content and images are available.

Ready  for a website without a subscription?

Get in touch for a no-obligation conversation about your project. Together we'll figure out which approach best fits your goals and budget.

I'll think along with you and give honest advice on what DYKZ can do for you. Even if something else turns out to be a better fit.