Who actually owns your website?

Ask a business owner whether they own their website and most will say yes, of course. Then something goes wrong — the person who built it stops replying, a renewal notice arrives for an account nobody recognises, a move to a new firm turns out to be impossible without starting from scratch — and it becomes clear that "owning" a website isn't one thing. It's several, and you can hold some of them without the others.

It's worth understanding the parts before you need to, because the moment you need to is usually a bad moment to find out.

The domain

Your domain name — the address people type to reach you — is the single most important thing to own outright, and the one most often quietly held by someone else. It should be registered in your name, on an account you control, with a login you have. If it was registered by a contractor "to keep things simple," it stays simple right up until you part ways, at which point your address can walk out the door with them.

You don't need to manage the domain day to day. You do need to own the account it lives in. Ask where your domain is registered and whose name is on it. There's only one right answer.

The code and the content

The site itself — the pages, the design, the words and images — should be yours once the work is paid for. This sounds obvious and often isn't. Some arrangements license you the use of a site without handing over the thing itself, so that leaving means rebuilding. Others are built on a platform you can't export from, which comes to the same lock-in by a quieter route.

The test is simple: if you decided to work with someone else next year, could you take your site with you? A firm confident in its work has no reason to trap you, and no trouble answering the question.

The accounts

A working website sits on a small stack of accounts — hosting, the domain registrar, analytics, whatever handles your forms or email. Over a project's life these get created quickly, sometimes under a developer's own login "for now." Years later, nobody's quite sure who holds what.

The healthy arrangement is that every account is in your business's name, and your suppliers are given access to them — not the other way round. You lend the keys; you don't hand over the house.

Why this matters even when nothing is wrong

Most of the time, none of this surfaces. The site works, the renewals get paid, everyone's friendly. Ownership matters precisely because of the day that isn't like that — a supplier who becomes unreachable, a relationship that ends, a decision to move on. On that day, owning your domain, your code, and your accounts is the difference between an inconvenience and being held hostage.

The good news: it costs nothing to get right, and it's easiest to arrange at the start. When you commission a site, say plainly that you expect to own the domain, the code, and every account in your name, with your suppliers given access. Anyone who builds honestly will treat that as completely normal — because it is.