A website you cannot move is a website you cannot leave. That is the whole argument for caring about ownership, because every other problem with a site, slow pages, bad copy, dated design, has a fix, and the fix only becomes available the day you control the parts. Most business owners only discover what they do not own at the worst moment: the developer has gone quiet, or a quote for changes came back triple what it should be. Here is what the parts are, what owning each one means, and what to get in writing before you pay.
The four parts, and who should hold each one
Every small business website is made of the same four pieces. The differences between a site you control and a site that controls you show up in who holds the account for each piece.
| Part | Owning it means | The red flag |
|---|---|---|
| Domain | Registered in an account in your name, with your email | Registered in the developer’s account, “we handle renewals” |
| Hosting | The hosting account is in your name, or you get a full admin login | Hosting bundled invisibly with the build, no access offered |
| Code and design | Written permission to take the code anywhere | A licence that only works while you stay with the builder |
| Content | Your copy, photos and logo files, exported on request | Stock images licensed to the builder, not to you |
Two minutes on the phone answers all four. Ask who the domain is registered with and whose name the account is under. Ask for the hosting control panel login. Ask whether you can export the content as files. If any answer is vague, that is the finding.
Domain first, because it is the one you cannot rebuild
Code can be rewritten and content can be recovered from old drafts or backups. A domain that sits in someone else’s registrar account cannot be replaced: it is your address, your email history, your Google ranking. If the registration lapses or the account holder stops responding, you are into a dispute process with no guaranteed outcome.
The fix costs almost nothing. Registrars transfer domains between accounts with a couple of clicks. If yours sits in your developer’s account, ask for a transfer or an account change into your name today, while the relationship is good. Check the contact email on the registration too: if it is an old address you no longer read, renewal warnings are going nowhere useful.
Hosting, and the “we include everything” trap
Bundled hosting is not automatically bad. Plenty of builders run your site on their own plan, patch it, and answer support email, and that can be a fair deal. The trap is the version with no admin access: the day you want to leave, there is no export path, because you never had one.
What fair looks like: you hold (or can be given within a day) an administrator login, you can see the site files and database or a static export, and the monthly cost of the bundle is stated in pounds rather than folded into an unexplained figure. If the builder’s hosting is good, you will stay. Locking someone in is what businesses do when they expect to lose the comparison.
Code, themes and the licence question
There are two honest models here, and a written line in a contract distinguishes them. In the first, you own the code outright: it was written for you, you can take it to any developer. In the second, the builder owns the platform and licenses it to you: common with subscription site builders and with agencies whose whole stack is their own. Both are legitimate. What is not legitimate is the third case, where the ownership is simply never discussed and each side assumes the other.
Ask one question: “If we part company, what do I walk away with?” A good answer is specific: a copy of the site, the domain transfer, and the content exports, listed in the contract. An answer like “you would not want to leave anyway” is an answer too.
Content is yours, get it backed up anyway
Copy, product photos, the logo your cousin designed: these belong to you as work you paid for, but stock photography and licensed fonts often do not transfer, and rebuilds have stalled over a handful of images. Keep your own copy of everything: the text in a document, the images in a folder, the logo files with their original formats. A ten minute export after launch is the cheapest insurance on this list.
You should be able to fire your web company with an email and a login. If leaving would require their cooperation, you have not bought a website, you have rented a relationship, and the rent only ever goes up.
If the site is already built and you never checked
Do the four checks now, before anything goes wrong. Request the domain transfer. Ask for an admin login and test it. Export the content and put it in cloud storage. Ask for the ownership question in writing and file the answer. If the responses are slow or evasive, that is useful information, because the difficulty of getting access today tells you exactly what leaving will cost later.
None of this is hostile. Good builders volunteer all of it, because confident companies do not need locks on the door. The ones who hedge are telling you their business model depends on the door.
Ownership is cheap on day one and expensive on day three hundred. Four accounts, four logins, one folder of exports, and the next conversation with a developer starts from choice rather than necessity.