Website builder: choosing one you will not have to leave in a year

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.

What actually separates website builders

• Structured content versus loose pages. A builder where every page is a free-form canvas is fast for five pages and painful for fifty; one with reusable content types costs an hour to learn and saves weeks later.
• Performance out of the box. Page weight, image handling and how much script the builder injects decide whether the site is fast, and there is usually nothing you can do about it afterwards.
• URL control and redirects. The ability to set the address of a page and redirect an old one is not a nice-to-have — without it, any restructure costs you the search traffic you had.
• Export and portability. Can you get the content out in a form something else could read? A site you cannot leave is a subscription you cannot cancel.
• Forms and what happens to submissions. Where do they go, can you connect them to anything, and are you paying per submission.
• Who can edit. If one person holds the password, the site ages at the speed of that person's calendar.

The questions to ask before committing

1. Rebuild your two hardest existing pages in the trial, not the easy ones. The homepage is designed to work; the awkward internal page is where the limits are.
2. Check the published page speed on a phone over a slow connection. Builder previews are generous and reality is not.
3. Find where you change a page URL and where you add a redirect. If either is missing or hidden, that is a serious constraint.
4. Export something, open the file, and see what you actually got. Do this before you have two hundred pages, not after.
5. Add a second editor and see what they can break. Permission models vary enormously and are usually discovered during an incident.
6. Price it at three times your current size, including the add-ons the base plan excludes.

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.

Builder, developer, or platform

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.

Where Ettex sits

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.