The moment most business owners discover what they signed is the moment they try to leave. They ask for their site, and the conversation gets awkward. Sometimes the outcome is fine. Sometimes they find out they own almost nothing and the last three years of reviews, rankings and content live somewhere they cannot reach.
None of this requires a dishonest agency. It usually requires a vague contract and a customer who never asked the right questions — because the right questions are not obvious unless somebody tells you what they are.
Ownership is four things, not one
Separate these before you sign anything. They are independent, and each one can be held by a different party:
- 01The domain name — the address itself. This is the one that matters most and the one most often mishandled.
- 02The content — your text, your photos, your logo, your service descriptions.
- 03The code — the actual build: templates, styling, custom functionality.
- 04The data — form submissions, customer records, bookings, analytics history, email lists.
A perfectly reasonable arrangement can have you owning the domain, content and data while the agency retains the code and platform. A bad arrangement has the agency holding the domain. Those two situations look identical in a proposal and are worlds apart when you want to leave.
The domain is the one to fight for
If somebody else controls your domain, they control your email, your rankings and every business card you have ever printed.
Everything else is replaceable. A site can be rebuilt in days. Content can be rewritten. A domain cannot be recreated — it is either registered to you or it is not, and if the registration sits in an agency's account you are relying on their goodwill to hand it over.
You should be the registrant, with the registrar login in your own name and your own email. Not the agency's email. Not 'we manage that for you'. If an agency is unwilling to have the domain in your account, there is no technical reason for it — that is a retention strategy, and you should treat it as one.
Where 'they own the code' is genuinely fine
There is a widespread idea that the only acceptable arrangement is owning every line of code. That sounds right and mostly is not, because it ignores what actually happens after launch.
A one-off build you own outright comes with a hidden bill. Somebody has to host it, keep the platform patched, renew certificates, monitor uptime, take backups, and make changes when your hours or prices shift. If your agency's job ended at handover, all of that is now yours. In practice it goes unmaintained, and two years later the site is slow, insecure or quietly broken.
An ongoing arrangement — a build fee plus a monthly plan covering hosting, maintenance and unlimited edits — solves that, and is how we work. The trade is real and should be stated plainly: the platform stays with us. What must not be traded is your domain, your content and your data. Those stay yours in every version of this.
The problem is never the model. It is a model that was never explained, discovered at the worst possible moment.
The questions to ask, verbatim
Ask these before you sign. A straight answer to each is more informative than any portfolio:
- Whose name and email will the domain be registered under? Will I have my own registrar login?
- If I leave, what exactly do I take with me — and can you write that list into the agreement?
- Do I get an export of form submissions, bookings and customer data, in a standard format, on request?
- Is the analytics property in my account, or yours?
- Who controls the DNS records, and can I get access without asking permission?
- If your business closed tomorrow, what happens to my site and my domain?
- Is there a notice period, and is there a fee to leave?
- Are edits included, or billed hourly? What counts as an edit?
Watch the shape of the answers as much as the content. 'We handle all that for you' is not an answer to any of these. 'Nobody has ever asked that' is not either — it means either they are new, or nobody has been paying attention.
Content and photography, specifically
Photography is the sleeper issue. If the agency hired a photographer, the copyright may sit with the photographer, licensed to the agency, licensed onward to you for use on that site. Leave, and the licence may not travel. Stock imagery is worse — those licences are frequently non-transferable by design.
Ask for the licence terms in writing for every image on the site, and prefer photos you took or commissioned directly. There is a side benefit: real photographs of your actual premises, staff and work outperform stock in every context that matters, because customers can tell the difference instantly.
The data question people forget
Three years of enquiries, bookings and reviews is a genuine business asset — arguably worth more than the site around it. Make sure you can get it out, in a format you can open, whenever you want, without a fee attached.
The same goes for anything tied to your Google Business Profile. That profile should be owned by you with the agency added as a manager. Ownership transfers are possible but slow and occasionally painful. Set it up correctly the first time.
What a fair agreement reads like
You own the domain, registered to you. You own your content and your data, exportable on request. The platform arrangement — whether you keep the code or the agency maintains it — is stated in one plain sentence you understood before signing. There is a defined notice period and no exit penalty. Nothing is contingent on staying.
That is not a high bar. But it only gets met if you ask, and the best time to ask is before money changes hands — when the answers are still cheap to get.
If you are weighing up an agency right now, it is also worth knowing the warning signs that show up before the contract does.
