Most business owners assume they own their website because they paid for it. It feels like a safe assumption until the moment it is tested: a falling-out with the agency, a sale, a rebrand, or a developer who stops answering emails.
At that point the question stops being philosophical. For a surprising number of SMEs, the honest answer is that they own an invoice and a set of screenshots, and somebody else owns everything that matters.
Your website is really five things, and each of them has an owner. You should know who owns all five while the relationship is fine, because that is precisely when nobody checks.
The domain name
The domain is the single most important item on the list, and it is the one owners think about least. Your email runs on it, your search presence is attached to it, and every business card and invoice you have ever printed points at it. Whoever controls the registrar account controls your digital identity, and everything else on this list can be rebuilt except this.
A website can be redesigned in months. A lost domain can mean a new name, in the eyes of the internet, forever.
Checking is straightforward. Run a WHOIS-style lookup on your domain and see what comes back. Privacy services mask many records, so the more reliable test is direct: ask your agency which registrar holds the domain, and ask for your own login to that account. Being listed as a contact on someone else’s account is not ownership. The account itself, in your name, is.
If the answer is vague, or the domain turns out to be registered to the agency, treat it as urgent even if everything else is rosy.
The hosting account
Hosting is where the website physically lives. If the account belongs to your agency, your site is in practical terms a tenant in their building, and moving out requires their cooperation.
Agency-owned hosting is not automatically bad. Managed hosting is a legitimate service, and most SMEs have no desire to administer servers. The question that matters is what happens if you part ways. Ask where the site is hosted, whose account it is, and what the documented handover process would be. A good partner has an answer written down.
The source code
The code is the thing you actually paid to have built. Ask one plain question: where does the code repository live, and who has admin access to it?
Any professionally built site lives in a version-controlled repository, usually on a platform like GitHub. You do not need to read code to hold it. You should either own the repository or have permanent access to it, so that any future developer can pick the project up without asking your old one for permission.
While you are asking, check the contract too. Under UK law, the copyright in commissioned code generally stays with the party that wrote it unless the contract assigns it, which startles many owners. Look at what your agreement says about intellectual property, and if there is no written agreement at all, that is your answer.
The CMS and the content
Then there is everything inside the site: the pages, the products, the images, the enquiries, the customer data. Ask who holds the CMS admin login, whether you can add and remove users yourself, and whether the content and data can be exported in a usable format.
Content is easy to overlook because you can see it in a browser and it feels like yours. Seeing it is not the same as being able to take it with you. If the only admin account belongs to the agency, your years of content exist at their discretion.
The third-party accounts
Finally, the constellation of services around the site: analytics, the email service behind your forms and newsletters, the payment processor, ad accounts. Each is an account with an owner, and agencies routinely set them up under their own logins because it is quicker.
Losing analytics history is painful. Losing access to the payment processor that takes your customers’ money is a different order of problem. List the services your site depends on and ask, for each one, whose account it is and whether you can be made an owner-level user today.
Why good agencies end up owning everything
It is worth saying plainly: most agencies that hold all five of these are not villains. Bundled ownership usually happens through convenience, not malice. Registering the domain themselves got the project moving, and their hosting account was already open. Each choice was reasonable in the moment, and each one shifted a little more of your business into someone else’s name.
The trouble is that motive does not change outcome. When you want to leave, convenient bundling and deliberate lock-in feel exactly the same.
A professional partner should be able to answer “how would we leave you?” without flinching.
That question is the whole test, so ask it directly. A confident partner will walk you through the handover, from the domain transfer to the repository to roughly what the migration would cost. A partner who bristles or stalls has just told you something important, and it is better to learn it now.
What good looks like
Here is the arrangement we consider the professional baseline.
The domain is registered in the client’s name, in the client’s registrar account, always, with no exceptions. The code lives in a repository the client can access at any time. Hosting is either in the client’s name or, where the partner manages it, covered by a documented handover path that both sides have seen. The CMS has an owner-level login held by the client, and the data can be exported. Third-party services are on the client’s accounts wherever the platform allows it.
Under that arrangement, leaving your supplier costs a conversation and a modest amount of transition work. Under the alternative, it can cost a legal letter, a ransom-shaped final invoice, or a new domain name. The measure of a good setup is that the exit is boring.
What to do about it
Set aside an hour this week and audit the five items. Run the domain lookup, then ask where the registrar account, the repository, the hosting, the CMS admin and each third-party account sit, and who would control them if the relationship ended tomorrow. Write the answers down and keep them with your company records.
Where something sits in the agency’s name, ask for it to be transferred or for you to be added at owner level, starting with the domain. Frame it as housekeeping, and a good partner will treat it that way. Where there is resistance, you have learned something valuable while you still have room to act.
If you are commissioning a new site, put ownership in the contract before work starts. It is a paragraph, and the cheapest insurance you will buy this year.
The question a buyer will ask anyway
If you ever sell the business, due diligence will demand exactly this list: proof that the company owns its domain, its code, its data and its accounts. Gaps found at that stage cost real money, because the other side’s lawyers find them on a deadline with a purchase price in play.
Ownership of your website is not an IT preference. It is part of the value of the company, and worth an hour of your time long before anyone else asks.
Flux Dynamics builds, hosts and manages software on a no lock-in principle: clients own their domain, their code and their data from day one, and the exit is always documented. Start a conversation if you want a partner who can answer the leaving question without flinching.