The argument about page builders is usually tribal and therefore useless. A builder is not a moral failing and it is not a development skill either — it is a tool with a defined range, and the professional question is only whether the project sits inside that range.
Where it is the right answer
- A marketing site whose owner will add pages weekly without calling anyone.
- Layouts that repeat with variation, where small inconsistencies cost nothing.
- A short timeline where a bespoke theme cannot be justified by the budget.
- A client who has already committed to it and has a team that knows it.
The four signals it has become the constraint
- You are writing custom CSS to undo the builder's output rather than to style your own.
- The same section exists on nine pages as nine independent copies, and a change means nine edits.
- Performance work has hit a floor made of the builder's own runtime and DOM depth.
- A required interaction does not exist as a widget, so it arrives as a third-party add-on with its own runtime.
The second signal is the expensive one and it is the least discussed. A builder without reusable, globally-edited blocks turns every layout into content, and content does not refactor. Two years later the site cannot be restyled at all — not because the CSS is hard, but because there is no single place where the layout lives.
Leaving without a rebuild
You rarely need to migrate a whole site at once, and proposing that is usually how the conversation ends. Move the templates that matter — the product page, the article, the landing page that receives the ads — into real theme templates, and leave the long tail of one-off pages where they are. The high-traffic routes get the performance and the maintainability; nobody pays for rebuilding a page that gets forty visits a year.
Sources
Related services
Related work
