Skip to main content

Walkthrough · Beginner · an evening of testing

How to Pick a WordPress Page Builder

How to decide between the block editor and a builder plugin with the trade-offs in plain view, without the guessing — the steps in order, the snag ahead of time, and the tip our support team repeats daily.

The short answer

One line covers it: decide between the block editor and a builder plugin with the trade-offs in plain view — a beginner-level job of roughly an evening of testing.

Below is the full run of steps, the error most people trip over, and the short cut worth remembering. On Hosting & Domains plans several steps are already automated away — the guide marks each one.

By the Hosting & Domains team · Reviewed 18 August 2026

Beginner

Skill rating

Quick

Time budget

5

Steps in total

24/7

Support on call

No prior knowledge assumed — a hosting account, a browser and evening of testing of attention is the whole entry requirement. Every instruction runs on our platform exactly as printed, and carries over to any standard cPanel host.

A promise before step one: nothing here is a one-way door. Any step with teeth is flagged, and the way back is printed beside it.

The route, mapped end to end

Over the whole job, you will exhaust the built-in editor first, face the lock-in honestly, measure what visitors receive, fit it to the actual editor and standardise on the winner.

No part of this needs code or a terminal unless the guide says so plainly — and where it does, the exact commands are printed. The step-by-step is below, with the surrounding sections supplying the context that makes it hold.

Where it comes off, and how to stay on

Choosing a builder for one showpiece homepage, then dragging its weight and its licence across two hundred ordinary pages. A flagship decision quietly turns into a tax on the entire site.

Forewarned is genuinely forearmed here. This one mistake accounts for most of the frustration the topic ever causes — and it disappears entirely once somebody points it out.

A habit worth borrowing

Watch where the block editor is heading. Each WordPress release closes the gap, so backing core keeps your skills and your content gaining value instead of resting on one vendor's roadmap.

Habits this small are what separate the people who find hosting effortless from the people who find it draining. The same tools on both sides — a different way of working.

The parts that look after themselves here

Steps that never deserved your time are taken out: certificates issue and reissue themselves, the installer handles application setup, the daily copy absorbs the what-ifs, and per-site settings live in a panel rather than a configuration file. The guide covers the remainder — the part that is actually about your site.

Should a step still misfire, support answers at any hour with an actual fix rather than a knowledge-base link and a shrug. Half the guides on this site began as repeat patterns in our ticket queue.

A WordPress build coming together on a plan that keeps it patched

The hosting these steps were tested on

Tutorials written against imaginary hosting go stale fast. Ours are written against the real thing: the same panel, installer and defaults waiting in your account.

A copy is taken daily on every plan, and putting a file or a database back is one click in the panel rather than a support ticket.

  • Every step checked exactly as published
  • The snag named before it arrives
  • The dull steps taken out of your way
  • People reachable at any hour you stall

Why Hosting & Domains

Standard on every plan

Help that keeps your hours, not ours

Stuck on step three at midnight? Support answers at any hour, mid-walkthrough included.

5 steps, nothing padded

Each stage is a few minutes of steady clicking, and the fiddly moments are labelled fiddly.

Honest about how big it is

Decide between the block editor and a builder plugin with the trade-offs in plain view is a beginner-level job — set aside an evening of testing, with the platform-absorbed steps marked.

Every undo written out

Any step that could bite is marked, together with the exact way to wind it back.

Works exactly as printed

Every step is proven on the platform we run — none of the 'your host may vary' hedging.

The snag, flagged up front

The classic error for this particular task is named before step one, which is how an evening of testing stays an evening of testing.

Quick Start

Order placed to site online

  1. 1

    Exhaust the built-in editor first

    A current block editor with a capable block theme handles most layouts on its own. Establish that you genuinely need a builder before you start comparing them.

  2. 2

    Face the lock-in honestly

    Builder content is stored as builder markup. Deactivate the plugin and the pages fall apart into shortcode debris. What you are choosing is a long-term dependency, not a tool you can put down.

  3. 3

    Measure what visitors receive

    Build the same page in each candidate and speed-test the results. Builders differ several times over in the CSS and JavaScript they send to every visitor on every page.

  4. 4

    Fit it to the actual editor

    Work out who will be maintaining pages next month and sit them in front of the shortlist. Whichever builder the person doing the real work never argues with is the best one.

  5. 5

    Standardise on the winner

    Commit across the whole site. A mixture of builder and block pages doubles every future maintenance question, and nobody ever remembers which page was made with what.

Built In

Fitted to every plan

  • Spam and virus screening on every mailbox by default
  • LiteSpeed caching in the server itself rather than bolted on by plugin
  • cPanel, which is what most of the industry already runs
  • WordPress Toolkit, with the updates seen to for you
  • NVMe SSD storage on every tier, not only the dear ones
  • Webmail in the browser plus IMAP, POP and SMTP for any client
  • No set-up charge at any point, and no joining fee
  • 99.9% uptime as the target, watched around the clock
  • Softaculous included for one-click application installs
  • The name's first year included when you order annually

Frequently Asked

The questions that come up most

Does a page builder hurt SEO?

Not in itself. But the heavier markup and slower pages some builders produce feed straight into the vitals that do get measured. Judge on output weight and clean semantics rather than the length of the feature list.

Can I move from a builder back to the block editor?

Only as a page-by-page rebuild, because builder markup converts cleanly into nothing. That one-way door is exactly why the decision deserves an evening of testing beforehand rather than a year of regret after.

Does hosting include mail?

Yes — every hosting plan includes mailboxes at your own name, with webmail, IMAP, POP and SMTP plus spam filtering on from the start. There is standalone email hosting too, for a name whose website lives somewhere else.

Is the free SSL certificate genuinely free?

Entirely, on every plan. The certificate is issued as soon as the name points here and reissues itself well before it lapses. On encryption it matches any paid DV certificate — the paid options exist for wildcard coverage or organisation validation, which most sites never need.

Keep reading

Changing hosts? Run through our checklist first.

A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.

What arrives is the checklist, and then the occasional note on keeping a site quick. Leave whenever you like; the privacy policy covers the rest.

Start on a plan priced without games.

NVMe hosting with SSL and the migration included, people answering at any hour, and a price that stays where it was.

View Email Hosting plans