For a decade, the argument for page builders was honest enough: the native WordPress editor couldn’t do what they did. Drag-and-drop layouts, mega menus, responsive controls — if you wanted them, you bought a builder and accepted the weight. WordPress 7 is the release where that argument quietly ran out.
What changed
- Navigation grew up. The navigation block now handles the mobile overlay as a designable template part — the last piece that used to send teams back to a builder or a custom header. This very site’s menu, mega panel and all, is the native block.
- Layout stopped needing CSS. Grids that stack themselves, spacing presets, per-block responsive behaviour — the things builders sold as features are now block settings an editor can see and change.
- The editor edits the whole site. Headers, footers, templates, archive layouts. The gap between “what the agency can change” and “what your team can change” has mostly closed.
The costs never went away
Meanwhile, the things page builders were excused for are still being paid for: markup three times the size it needs to be, render-blocking scripts on every page, lock-in that turns a redesign into a rebuild, and licence renewals for capabilities WordPress now ships free. We measure this often, because conversion is part of our work — it is common to see page weight halve when a builder site is rebuilt natively, with no visual change a stakeholder can spot.
Is your site ready to move?
- Count the builder-only features you actually use. Most audits find three or four — typically a mega menu, a slider, a form styler, and one animation. All have native or lighter equivalents now.
- Check who edits what. If only one person dares touch the homepage, the builder isn’t empowering your team; it’s gatekeeping them.
- Look at your renewal invoices. Builder, add-on pack, template library. That budget funds a meaningful slice of a one-off conversion that removes the dependency permanently.
- Test your content’s portability. Paste a builder page into a plain editor and see what survives. What you lose is what you’re locked into.
A conversion done properly preserves URLs, content, and rankings — the change your visitors notice is that the site got faster. The change your team notices is that they can edit it. The argument is over; what remains is scheduling the work.
