Every website builder demos beautifully. What separates them shows up later — when you need a page type nobody anticipated, when the site gets slow, and when you want your content out.
A website builder is software that lets you make and publish a site without writing code. The category is crowded, the demos are uniformly impressive, and the decision is genuinely hard for a reason nobody advertises: what you are choosing is not how the first five pages look, but how much friction you meet in month eight, when you need something the tour never showed.
The useful way to evaluate one is to stop comparing feature lists and instead ask four questions about the future: can I make a page type nobody planned for, does the site stay fast as it grows, can I get my content out, and what happens to search rankings when I change something.
The most expensive mistake in this category is choosing on visual templates. Templates are the part you will replace first — usually within a year, as soon as the brand settles — while the structural decisions you barely noticed at signup are the ones you live with. Pick for the structure and treat the template gallery as decoration.
Three different answers suit three different situations. A builder suits a site your own team will keep changing — marketing pages, a catalogue, a booking flow — where speed of change matters more than bespoke design. A developer suits a site whose value is in something custom, and the honest signal here is whether the interesting part of your site is the interface or the logic behind it. A platform with a plugin ecosystem suits teams who need a specific integration badly enough to accept the maintenance that comes with it. Most small businesses need the first, buy the third, and end up maintaining something nobody on the team understands.
Ettex Sites is the builder half of that trio: structured pages, a catalogue and checkout when you sell things, forms that land in Ettex Forms, and the same account as the rest of your tools. The surrounding pieces have their own write-ups — the catalogue in product catalog, the payment step in checkout page, and the ongoing tuning in conversion rate optimization.
And the boundaries, plainly: there is no plugin marketplace, no server-side code you can deploy, no third-party theme store, and no bespoke design service. If your requirement is a specific integration that only exists as a plugin for one particular platform, that platform is your answer and we are not going to pretend otherwise.
URL control and redirects, real export, performance of the published page rather than the preview, a permission model for multiple editors, and structured content types if the site will grow past a handful of pages.
For a first site, often yes. The limits that bite later are usually the custom domain, the ads inserted on free plans, and export — check those three before investing time in content.
Keep the URLs identical where you can, and set up redirects for every one you cannot. A builder without redirect control makes a clean migration impossible, which is why it belongs on the evaluation list rather than in the fine print.
When the valuable part of the site is the logic rather than the pages — a calculator, an integration, a workflow. If the interesting part is the interface and the content, a builder your own team can change is usually the better investment.
The question is not which is better. It is which parts of a small business site actually need a designer — and for most, that turns out to be a smaller list than the quotes suggest.
A cookie notice tells visitors what your site stores on their device and lets them decide. Most of the bad ones fail for the same reason: the site sets the cookies before anyone has answered.
Conversion rate optimization gets sold as testing. For most small sites the wins are earlier than that — in the offer, the form, and the sentence at the top of the page.