The pitch was compelling. Visual interfaces that let anyone build websites. No coding required. Drag elements onto pages, drop them into place, adjust settings through panels. Web development democratised, accessible to all, freed from the gatekeeping of technical expertise.

Elementor, Divi, WPBakery, Beaver Builder—the page builders delivered on their promise. Millions of users now build websites without writing code. The barrier to creating a web presence has never been lower. By that measure, page builders have succeeded spectacularly.

But success by one measure can mean failure by others. Page builders have not merely democratised web development; they have transformed it in ways that damage both outcomes and practitioners. The profession that once required genuine skill is being eroded by tools that substitute clicking for coding.

The Deskilling of a Profession

Every profession rests on a foundation of specialised knowledge and skill. Doctors understand medicine. Lawyers understand law. Engineers understand physics and mathematics. This expertise justifies professional status and the compensation that accompanies it.

Web development once rested on technical expertise. Practitioners understood HTML semantics, CSS layout models, JavaScript interaction patterns, server-side processing, and database design. This knowledge took years to acquire and enabled work that non-experts could not produce.

Page builders abstract this expertise away. The practitioner no longer needs to understand how layouts work—they drag sections into position. They no longer need to understand CSS—they adjust sliders and colour pickers. They no longer need to understand responsive design—the page builder handles breakpoints automatically.

This abstraction enables people without technical backgrounds to produce functional websites. It also means that people who call themselves web developers may lack the foundational knowledge that historically defined the profession. They know interfaces, not principles. They know tools, not techniques. They know how to operate page builders, not how the web actually works.

The profession has been deskilled. What once required years of learning now requires days of tutorial-watching. What once commanded respect for expertise now involves skills anyone can acquire over a weekend. The professional standing of web development has been diluted by the very tools that made it accessible.

The Output Problem

Page builders produce a distinctive type of code. Examine the source of any page-builder website and you find deeply nested divs, inline styles, generated classes with meaningless names, and JavaScript libraries loading regardless of whether their functionality is used.

This code is bloated by design. Page builders must accommodate any possible use case, so they include code for features that most sites never use. They must enable visual editing, so they embed structural information that browsers do not need. They must work for users who do not understand optimisation, so they skip optimisations that would complicate the interface.

The bloat has consequences. Page-builder sites load more slowly than hand-coded alternatives. They consume more bandwidth, disadvantaging users on limited data plans or slow connections. They score poorly on performance metrics that search engines increasingly weight in rankings.

The code structure has consequences too. Accessibility features that semantic HTML provides automatically must be manually added in page builders—and often are not. Search engine crawlers that rely on document structure find page-builder markup harder to parse. Maintainability suffers as the codebase consists of tool-generated output that humans struggle to read or modify.

These problems are not bugs that better page builders will solve. They are inherent to the paradigm. Visual editors that generate code will always produce code optimised for editing rather than performance. The abstraction that makes page builders accessible ensures that their output will be inferior to expert hand-coding.

The Training Gap

A generation of practitioners has learned web development through page builders. They can produce websites—of a sort—but they lack foundations that previous generations considered basic.

Ask a page-builder practitioner to explain the CSS box model. Many cannot. Ask them to write a media query by hand. Many struggle. Ask them to debug why a layout breaks in certain browsers. Many have no idea where to start.

This training gap creates professional vulnerabilities. Page-builder practitioners are dependent on their tools in ways that properly trained developers are not. When they encounter problems that page builders cannot solve—and they will—they lack the knowledge to address them. They must either abandon the requirement or hire someone with genuine skills.

The gap also creates market distortions. Page-builder practitioners compete with skilled developers for the same clients. Their lower costs—reflecting lower skill investment—undercut pricing. Clients cannot distinguish between outputs, so they choose cheaper options. Skilled developers lose work to practitioners whose tools mask their knowledge deficits.

Over time, this dynamic pushes skilled developers out of the market or into niches where page builders cannot follow. The mainstream of web development becomes dominated by practitioners whose skills begin and end with tool operation. The profession hollows out.

The Client Deception

Clients hiring page-builder practitioners often do not know what they are purchasing. The agency presents itself as offering web development services. The deliverable appears to be a functional website. The underlying reality—that the "development" consisted of dragging and dropping in a visual editor—remains hidden.

This concealment matters because it affects what clients receive. A hand-coded website and a page-builder website may look similar at launch. But the hand-coded site will load faster, rank better, maintain more easily, and last longer. The client who unknowingly received page-builder output has been short-changed, even if they cannot perceive the difference immediately.

Some argue that client ignorance is acceptable if clients are satisfied. This argument fails on examination. Clients make decisions based on expectations. When they hire a web developer, they expect development to occur. When they pay professional rates, they expect professional work. Delivering page-builder output while charging development rates and creating development expectations is deceptive regardless of client satisfaction.

The deception is particularly problematic because its consequences are delayed. Page-builder sites deteriorate over time as updates introduce conflicts, as performance degrades, as search rankings slip. By the time these problems manifest, the connection to the original page-builder choice is obscured. The client suffers without understanding why.

The Industry Transformation

Page builders have not merely created an alternative approach to web development; they have transformed the industry structurally.

Training programmes have shifted focus. Why teach CSS when graduates will use page builders? Why emphasise JavaScript fundamentals when visual interfaces handle interactivity? Educational content increasingly targets page-builder proficiency rather than foundational knowledge.

Hiring criteria have changed. Agencies seek practitioners who know Elementor or Divi, not practitioners who understand web standards. Tool certification replaces computer science education. The skills that employers value have narrowed to tool operation.

Professional identity has fragmented. Is someone who builds websites exclusively through page builders a web developer? By historical standards, no—they do not develop in any meaningful sense. By current market practice, yes—they produce websites and charge for the service. The title has been stretched to include activities it was never meant to describe.

Client expectations have adjusted. Many clients now assume that web development means page-builder work. They budget accordingly. They evaluate providers based on page-builder portfolios. They do not know that alternatives exist or what those alternatives would provide.

The Defence of Craft

Against this transformation, some practitioners defend craft. They continue writing code by hand. They learn foundational technologies rather than tool interfaces. They produce work that page builders cannot match.

This defence is increasingly difficult. Craft-based practitioners must charge more to compensate for slower production. They must educate clients about differences that clients cannot perceive directly. They must compete against a market that has normalised page-builder practices.

But the defence matters. Craft-based development produces better outcomes: faster sites, cleaner code, greater flexibility, longer lifespan. Clients who receive craft-based work benefit even if they cannot articulate why. The web benefits when skilled practitioners maintain standards that tools cannot achieve.

Preserving craft requires conscious commitment. Practitioners must invest in foundational skills despite market pressure toward tool dependency. Clients must seek out and value genuine expertise. The industry must maintain space for work that transcends what visual editors can produce.

The Honest Position

Page builders are not inherently evil. They serve legitimate purposes for people who need simple web presences without professional budgets. A small business owner maintaining their own site benefits from page-builder accessibility.

The problem is professional adoption. When agencies and practitioners use page builders to deliver services marketed as web development, they debase the profession. They substitute tool operation for genuine skill. They deceive clients about what they provide. They compete unfairly with practitioners who maintain craft standards.

An honest position acknowledges page builders' legitimate uses while resisting their professional adoption. It distinguishes between non-professionals using accessible tools and professionals claiming expertise they do not possess. It maintains standards that page-builder output cannot meet.

The drag-and-drop paradigm has made website creation accessible. It has also eroded professional standards, deskilled practitioners, and transformed an industry in ways that damage both outcomes and integrity.

Those who care about web development as a profession—not merely an activity—must reckon with what page builders have wrought. The decline is real. The response must be equally real: a commitment to craft that tools cannot replicate and shortcuts cannot achieve.