how do i make a website without coding? what builders give you, and what they quietly take

web · Sep 27, 2026 · 5 min read

you do not need to code to make a website. this was true ten years ago and it is truer now. what you need instead is a clear-eyed view of the trade you are making, because no-code does not mean no-trade. it means the trade is written somewhere you have not read yet.

what a builder actually is

wix, squarespace, webflow, shopify: you pay a subscription, choose a template, pour your content into the slots. hosting, ssl, updates, backups: included, invisible, handled. for a showcase site on your own, the realistic cost is 0-300 euro a year, and you can be live in a weekend. shopify is the same deal pointed at selling: a bit more per month, and the checkout is handled.

this is a genuinely good deal. i want to say that first, because most of what follows sounds like a critique and it is not. for a professional who needs to be findable without becoming a project manager of their own website, a builder is the right answer. i wrote the same thing in quanto costa un sito web: this is not a post that curses builders. it is a post that reads the contract.

what the subscription buys

  • speed to live: a weekend, not a quarter.
  • zero maintenance decisions: no updates to break things, no backups to forget.
  • hosting that scales without you: traffic spikes are the provider's problem, not yours.
  • a working editor: change text, swap photos, publish. from a phone, if you must.

for a showcase site of a professional who wants to be found without overthinking it, this is enough. truly.

what it quietly takes

  • a generic layout. the template was designed for a category, not for you. the same bones are under your competitors' sites. some visitors feel it without being able to name it.
  • urls that follow the builder. page addresses come with the builder's structure attached, which limits how clean your search footprint can get.
  • speed you do not control. load times depend on your plan and on how the builder builds. some builders are fast. none are as fast as a small, well-built site, and none let you fix the parts you would want to fix.
  • the exit problem. this is the big one, and it is quiet: your content lives in the builder's format. exporting to a real, movable site later is possible to varying degrees and painful in all of them. the site is hard to leave once it holds everything.

the exit problem matters because of when it bites: not on day one, when everything is cheap and fast, but in year two or three, when the business has grown and the site has become the thing holding it back. that is the day the subscription price stops being the point.

when each way is the right call

  • builder: you need it live now, the words exist, the budget is small, the job is "be findable and look put together". right call. ship it.
  • template plus tweaks: the builder's shapes are close but not quite, and a small budget for a designer closes the gap. 300-1000 euro, still yours to edit.
  • a person: the site is the product, or the brand is the product, and generic bones would argue against you. 1500-5000 for a done-with-care site. this is not the expensive way; it is the way that does not need redoing in year three.

the one question to ask before you pick

not "which builder is best" — they all work, and reviews online are mostly people defending their own choice. ask instead: will i need to leave this someday, and how much will leaving cost? if the answer is "probably never, and if i do, i will rebuild": go builder, happily. if the business is likely to outgrow the template — more services, content, selling — start on the land you intend to keep, even if you start smaller.

rebuilding later costs more than building right-sized now. that sentence is the whole economy of this decision.

FAQ

which builder should i pick?

the one whose editor you can tolerate and whose export you have checked. editor comfort beats feature lists: the builder you actually use is better than the one you abandoned.

is webflow better because designers use it?

webflow gives you more control and takes more time to learn, which puts it between builder and code. right tool for the middle case, overkill for a weekend site.

can i move from wix to a real site later?

you can move your text and photos by hand, one page at a time. the layout and the structure do not travel. plan for a content copy-paste week, not a magic export.

what about ai site builders?

they generate a plausible site from a prompt, which is a faster template. same trade underneath, one step less customized. my honest take on building things with ai is here.

the closing thought

coding was never the barrier. clarity was. a builder removes the code and keeps the decisions, and the decisions were always the hard part: what the site is for, what it says, what it asks the visitor to do. pay for whatever removes the code. do not expect anything to remove the decisions.

and if you want the decisions made with you rather than for you, near Parma:

no-code is real. no-decisions is not. choose accordingly.