The fastest route to a working website is a drag-and-drop : a template, your text, your photos, your domain, and by the end of one evening your site is online. But that launch speed has a price that shows up a year or two later: when you want a page the template can’t do, when you move to another provider and find the site can’t be exported, or when search engines need data the builder won’t let you edit. This article sets the smart website builder beside a and custom code on measurable criteria, gives you what to check in any builder before you build on it, and a checklist to go through before launch.
01Three ways to build a website
- Website builder: A visual editor where you assemble pages from ready-made sections; it takes care of the code and often the hosting and updates too. You need no technical knowledge, and you move within the limits of what it offers.
- Content management system: A system such as WordPress separates content from design: you write in an admin panel, a theme you pick or adapt displays the content, and plugins add features. It runs on any hosting with PHP and MySQL, and you own all its files and its database.
- Custom code: A site a developer writes with a framework such as Laravel or Next.js, or a static site generated by Hugo. Maximum control and performance, and with them an ongoing cost for development and maintenance.
02Six criteria, side by side
| Criterion | Website builder | WordPress | Custom code |
|---|---|---|---|
| Speed to launch | Hours to days | Days to weeks | Weeks to months |
| Control | Within what the editor and template allow | Wide, through themes, plugins and code edits | Complete |
| Performance | Usually good, but you control neither the server nor the generated code | Varies with the theme, plugins and caching | The highest, if built well |
| SEO controls | Usually title, description and URLs; less for structured data and redirects | Almost complete, through plugins | Complete |
| Lock-in and export | Highest: many builders can’t export a site that works elsewhere | Low: files and a database you can move to any host | None, as long as you own the code and its repository |
| Cost over time | A fixed subscription for as long as the site lives | Hosting, sometimes paid themes and plugins, and time for updates | A high build cost, then maintenance by the hour |
The short rule: a builder for a brochure site of five to ten pages that rarely changes; WordPress for a blog, a store or a site that gains content every week; custom code for a digital product with its own business logic, such as a booking platform or a service portal, that themes and plugins can’t deliver.
03Builder lock-in: the question people ask too late
is the biggest hidden cost of builders. The site you built is stored in a format only that editor can read, so if you want to leave, you rebuild it from scratch. Check three things before you write the first page:
- Does the builder export the site as HTML and CSS files that run on any host? Does the export include images and form submissions?
- Does the builder run on your own hosting, so the content stays in your account and inside your backups, or only on the builder’s platform?
- Will page URLs stay the same if you move, or will you need a permanent (301) redirect for every URL that changes?
A builder that runs inside your own hosting softens this lock-in. Illevante’s cPanel hosting plans include a drag-and-drop website builder at no extra cost, and all three Plesk editions on VPS servers include the Sitejet builder. The export question still applies to any builder, so try it on a test page before you build the whole site.
04What to check in any builder before you build on it
- Your domain and SSL certificate: The site lives on your own domain, such as ward-irbid.com, not on a subdomain of the builder, with an SSL certificate that renews automatically and every request redirected to HTTPS.
- Page speed: Publish a test page and run it through PageSpeed Insights or Lighthouse in Chrome. Look at the on mobile: LCP up to 2.5 seconds, INP up to 200 milliseconds, and CLS up to 0.1.
- SEO controls: A title and description for every page, URLs whose wording you choose, an XML sitemap that updates automatically, 301 redirects, and a place to add in JSON-LD, such as your business name, address and opening hours.
- Forms and consent: Where are contact form submissions stored, and who can reach them? Does the builder offer a consent banner that blocks analytics and tracking until the visitor agrees? That’s a requirement under GDPR if some of your visitors are EU residents.
- Backups: Does the builder keep earlier versions of each page you can go back to? Can you take a full copy yourself?
- Permissions: An account for each editor with their own rights, not one password the whole team shares.
After publishing, four commands reveal in a minute what the builder’s interface won’t show you:
# Does HTTP redirect to HTTPS with a permanent (301) redirect?curl -sI http://ward-irbid.com/ | grep -iE "^(HTTP|location)"# Where is the sitemap? robots.txt usually declares itcurl -s https://ward-irbid.com/robots.txt | grep -i sitemap# Is there structured data on the home page? The output is the number of JSON-LD blockscurl -s https://ward-irbid.com/ | grep -o "application/ld+json" | wc -l# Size of the home page HTML after compression, in bytescurl -s -o /dev/null --compressed -w "%{size_download}\n" https://ward-irbid.com/
If the HTTP line shows status 200 with no location line, the site opens unencrypted for anyone who types the address without https. If the count of structured data blocks is zero, search engines can’t find your business name and address in a format they read directly.
05Pre-launch checklist
- 01Connect the domain and follow its records’ propagation with the DNS propagation check, then confirm the certificate and its chain of trust with the SSL certificate check.
- 02Open every page on a real phone over a mobile network, not on a computer alone.
- 03Give every page a unique title of up to about 60 characters and a description of up to about 155.
- 04Compress images as WebP or AVIF, at a width no larger than the page actually displays.
- 05Try the contact form yourself, and make sure the message reaches a mailbox someone watches.
- 06Add the site to Google Search Console and submit the sitemap.
- 07Take a backup or export the site before the first major change after launch.
- 08Write down the accounts: builder, hosting, domain and analytics, all in the company’s name and on its email, not in individuals’ names.
Here are common problems after launch, and what lies behind them:
- ProblemThe site looks great on a computer but is slow on a phone
- FixCheck image sizes, the number of fonts and any background video; these weigh down builder pages the most, and all of them can be trimmed without changing the design.
- ProblemSearch engines don’t show the new pages
- FixCheck that the page isn’t set to noindex and that the sitemap includes it, then request indexing in Search Console.
- ProblemYou want a store or appointment booking the builder doesn’t support
- FixThat’s a sign the site has outgrown the builder. Plan the move to WordPress now, before the content you’ll have to move by hand grows any larger.
06Before you decide
If your site is a business card for your company, five pages that change twice a year, a builder is a sensible choice: launch it in a week and spend your time on the content. If you expect a blog, a store or content added every week, start with WordPress on day one; on cPanel hosting plans Softaculous installs it in under a minute, and the extra effort up front is small next to the cost of rebuilding later.
Either way, make export the first feature you test, not the last. A site you can take with you stays yours, whatever tool you built it with.
