Who Actually Owns Your Website? (You Might Be Surprised)
The question usually arrives during a redesign quote. The owner says, "our last developer has everything," and means it as a convenience. It is not a convenience. It is a single point of failure with a phone number.
Your website is three things, not one
The domain, the hosting, and the site itself. The domain is the name, and it is the only one that matters in a dispute: whoever controls the domain can point it anywhere. The hosting is the computer the files live on. The site is the code and content. Each of these can be registered to a different person, and in a surprising number of small businesses, all three are registered to the person who built the site. That is how a routine design relationship quietly becomes an ownership one.
The thirty-minute check
Can you log in to the domain registrar right now? Not "do you have the password somewhere," can you actually log in. Same question for the hosting account. Who receives the renewal emails: an address you will still control in five years, or someone's personal Gmail from 2014? Check the DNS while you are in there. If the nameservers point at your developer's reseller account, you are hosted inside their business, and leaving them means rebuilding your hosting from scratch.
If you do not have your own hosting login, your own domain access, and your own analytics, you do not own the website. You rent it from whoever does, and you will discover this at the worst possible moment, which is when you need to change it.
Do not forget the accounts around it
The website is the center of a small solar system: Google Business Profile, Search Console, analytics, the ad account if you run one. Agencies routinely create these under their own master accounts because it is faster. Ownership means the accounts live under your business's own account, with the agency invited in as a manager. When you part ways, you revoke the invitation. Nothing goes dark, and nobody has to ask permission to keep their own business visible.
If the news is bad
This is recoverable in most cases. Get the domain first. Everything else, the hosting, the files, even the design, can be rebuilt, but the domain is the address your customers know and the only asset that appreciates. A developer who will not transfer a domain the client paid for is a legal problem with a short answer, not a negotiation. And when you set it up right, add the developer as a user on your accounts instead of handing them ownership. They get the access they need. You keep the keys.
This is a standing rule in my own work, and it is non-negotiable: the client owns the code, the domain, the hosting, and the data. If a developer will not agree to that in writing before the project starts, you have learned everything you need to know about the developer.