Page builders are not evil. They solve a real problem for a real audience. They let a non-developer ship a presentable website in a weekend. For some people, in some situations, that is exactly the right call.
But for a business website that has to perform — drive leads, build trust, stay fast, stay maintainable, age well, integrate with other systems — the page-builder approach quietly creates costs that do not show up in the first 90 days. Those costs eventually become the reason for an expensive rebuild.
This is not a "page builders bad" rant. It is the honest version of where they help, where they hurt, and what to do instead when long-term ownership is the goal.
What page builders are good at
Speed to first publish. Visual editing for people who cannot read or write HTML. Inline preview that matches what the visitor will see. Drag-and-drop layouts. Pre-designed blocks for common patterns.
For a one-person business, a temporary campaign site, an internal-only tool, or an early-stage landing page that needs to ship before anyone has the budget for custom development, a builder can be the correct tool. We would not argue against it.
What we would argue against is using one for a business website that is meant to last more than 18 months, drive real revenue, integrate with other systems, or be handed off to a future developer.
The four costs that show up later
1. Page weight you cannot defend. Most builders ship a runtime — a JavaScript engine plus a stylesheet plus a parser for the builder's own DSL — on every page that uses a builder block. Plus inline styles for each block. Plus a few hundred lines of helper CSS the page does not need but cannot easily remove. The result is pages that weigh 2-3x what they should and load noticeably slower on real devices.
This affects Core Web Vitals, which affects ranking, which affects how often an AI engine decides to cite the site. Core Web Vitals in the AI era covers why this matters more than it used to, not less.
2. Editor experience that gets worse over time. Day one in a builder feels great. By month three, the marketing person who built the site is wondering why the "save" sometimes takes 12 seconds, why a particular block randomly stopped rendering, why the page editor keeps adding empty spacers, and why a "minor" plugin update broke three pages.
The instinct is to add another plugin to fix the problem. That usually works briefly. By month nine, the site has a dozen plugins each trying to patch around the limitations of the builder, each adding its own version conflicts.
3. Lock-in that costs you when you want to leave. Try exporting a page-builder page to plain HTML. Try migrating a page-builder site to a different builder. Try handing the site to a developer who does not know that specific builder. Each of those things is technically possible. None of them are cheap.
The HTML a builder produces is rarely readable by another tool. The data the builder stores (its custom JSON, its custom shortcodes, its serialized block format) does not survive being moved. Rebuilds are usually faster than migrations.
4. SEO that quietly underperforms. Cluttered HTML, lots of nested divs, inline styles, runtime JavaScript that delays paint, generic block names that do not communicate page structure. Search engines and AI engines are forgiving up to a point — they will rank and cite builder sites — but they are not as kind to them as they are to clean, semantic HTML. Over a few years, the difference accumulates into a visible ranking gap.
The honest exception
The block editor in modern WordPress (Gutenberg) is not a page builder in the same sense as the third-party ones. It is the native editor for WordPress block themes. It produces semantic HTML, ships almost no runtime, and does not lock you into a third-party plugin's data format. We use it heavily.
If "page builder" to you means "I want my content team to edit visually," the block editor — paired with a well-built block theme — gives you that without the costs above. It is what we recommend for almost every business site that needs editorial flexibility.
Why we still see so many builder sites
Because the early-stage tradeoff is genuinely good for a particular kind of project. Because the "shipped in a weekend" story is real. Because cheap agencies use builders to deliver fixed-price work that would otherwise lose money. And because the costs are invisible to the buyer for the first year.
None of those are bad-faith reasons. But they are reasons that do not survive contact with a business that needs the website to compound value for a decade.
What we recommend instead
For a business site you want to keep and grow, the modern WordPress stack — block themes, ACF Pro, modern PHP, hand-written CSS and minimal JavaScript — gets you most of the editor experience benefit without the maintenance debt. We covered the details in why we still build WordPress sites by hand.
The build takes a bit longer up front. The total cost over a five-year ownership window is usually lower, because you are not rebuilding the site at year three because the builder rotted, and you are not paying a steady tax in performance and SEO during years one and two.
If you are already on a builder
If you are reading this from inside a builder-based site that is starting to feel painful, you have three paths.
Stay and patch. Sometimes the right answer for another year. We can usually help squeeze meaningful performance out of a builder site without a rebuild, especially if the builder is one of the better ones.
Rebuild on the modern WordPress stack. Higher up-front cost, lower lifetime cost, much better performance and SEO ceiling. The right call if the site is going to keep mattering and you have the appetite for one focused project.
Stage the migration. Build the new site on a staging environment while the existing one stays live. Migrate at the right moment with minimal downtime. We do this routinely and there is more on the underlying migration discipline in our upcoming piece on migrating without breaking SEO.
If you want a read on which path fits your situation, tell us about the site. We will give you the honest version — including "stay where you are for now" if that is the truthful answer.
