Who actually owns your website?

It is not one thing

The first useful move is to stop saying "the website" and start listing what it is made of, because these can and do end up in different hands.

• The domain name. Rented from a registrar, annually. Whoever the registrant is, controls it.
• The source code. What the site is actually built from.
• The design files. The layouts, the components, the assets in editable form.
• The hosting. Where it runs, and whose account pays for it.
• The content. Text, images, documents, and whatever database sits behind them.
• The measurement. Analytics, Search Console, tag manager. Years of history, attached to whoever created the property.

A client who was told they own their website and later discovers the domain is registered to a former supplier owns five of these six things and cannot use any of them.

The domain, which is the one that actually holds you hostage

Of the six, this is the one worth checking today rather than at the next project.

Domains are rented, not bought, and the record shows a registrant. If that registrant is an agency, a freelancer, or somebody's personal email from 2017, then your address on the internet, your email, and everything anyone has ever linked to depends on a relationship you may no longer have.

It is checkable in about a minute. Public WHOIS lookups will show the registrant and the expiry date, though many are behind privacy services now, in which case the faster route is to log into the registrar account and see whose name is on it. If you cannot log in, you have your answer.

A sense of how often the address is the thing people end up fighting over: there is an international arbitration procedure that exists solely for domain disputes, and in 2025 the World Intellectual Property Organization handled 6,282 cases through it, the highest number since the procedure was created more than twenty-five years ago. Most of those are trademark squatting rather than clients versus suppliers. The point is the pattern underneath: of everything a website is made of, the address is the piece with its own court.

What you want: the domain registered to your company, with billing on a company card and renewal notices going to an address more than one person can read. Suppliers can have administrative access. They should not be the owner.

The source files, and the phrase that decides it

For custom work, the question is whether you get the code and the editable design files, or only the finished result.

Both are legitimate arrangements and they are priced differently. What is not legitimate is leaving it undefined and finding out later.

The clause to look for is about transfer on final payment. Under most legal systems the person who creates something holds the rights unless they are assigned in writing, so silence in a contract usually favours the supplier, not you. It rarely comes up while everyone is getting along.

And ownership on paper is not the same as usable in practice. Code you own but cannot build, because the process lives on one person's laptop, is a legal fact and a practical dead end. Ask what a new supplier would need to run the project, and ask for it to be written down.

The trap that is not about ownership at all

You can own every one of the six things and still be stuck, and this is the version people do not see coming.

If changing a price on your own website means emailing somebody and waiting, you have not been given a website. You have been given a dependency. It does not matter whose name is on the code.

The related version: a site built on a platform whose subscription is in the supplier's account. You own the content, in the same way you own the furniture in a flat you are being evicted from.

So the question to ask alongside ownership is a practical one. What can somebody on my team change without asking anyone? Text, images, prices, posts, should all be on that list. Structure and layout usually should not, and that is normal rather than a restriction.

The measurement, which people forget entirely

Analytics and Search Console properties are owned by whoever set them up, and years of history live inside them.

This is the one that quietly disappears. A supplier changes, the new one creates fresh properties because it is faster than chasing access, and three years of history is gone. Not deleted, just unreachable, which for practical purposes is the same thing.

It is also the cheapest to fix: it is an admin permission, and it takes a minute while the relationship is good.

What to ask for, and when

At the start of a project, in writing, before signing. All of it is reasonable and none of it should cause friction.

• The domain is registered to us, and we hold the registrar login.
• Hosting is in an account we control, or we can be given control on request.
• On final payment, the source code and editable design files transfer to us.
• A handover document listing what exists, where it runs, and what a new supplier would need.
• Admin access on analytics and Search Console properties from day one.
• A named list of what we can edit ourselves without asking.

A studio that has done this before will recognise the list and answer in a sentence each. Hesitation on any single item is worth understanding before you sign rather than after.

If you are reading this because it has already gone wrong

The order to work in, most recoverable first.

Content is almost always recoverable, even in the worst case, because it is published and can be copied back off the live site.

The domain is the urgent one. If it is registered to somebody else and renewal is approaching, that is the item with a deadline attached. Registrars have transfer processes, and a company that can document its own trading name has a stronger position than it usually assumes.

Source and design files are the hardest, because if the contract is silent you may be negotiating rather than requesting. Sometimes the honest answer is that rebuilding costs less than recovering, which is unpleasant but worth calculating before spending months on it.

This is where a lawyer earns their fee rather than a studio, and we would tell you that rather than take the project.