Do you actually own your website? Five things to check

Most people find out they do not own their website at the worst possible moment: when the person who built it stops replying.
It is rarely malice. Developers move on, change careers, get busy. The problem is structural. If everything sits in their account, your business depends on their goodwill indefinitely.
Five things decide whether you own your site. Check them today; it takes about twenty minutes.
1. The domain
This is the one that matters most, because it is the only thing online that is genuinely yours. Everything else can be rebuilt. A domain someone else controls cannot be taken back without their cooperation.
Go to a WHOIS lookup and search your domain. If the registrant is your business, good. If it is your developer or their agency, that needs fixing now, not eventually.
Better still, log in to the registrar yourself. If you cannot, you do not control it.
2. The hosting account
Hosting is where the site lives. If it is on your developer's reseller account, your site exists at their discretion and you likely cannot move it without them.
You should have a login to the hosting provider directly, with billing in your name. Paying your developer who pays the host is not the same thing.
3. The code
Ask where the code lives and whether you can get a copy. The answer should be a repository you can access, or at minimum a copy of the files handed over.
If the site runs on a platform with no export, understand that before you build on it, not after.
4. The email
If your business email runs through an account you cannot administer, you can be locked out of every password reset you own. Email is the master key to everything else.
You should be the administrator of your email domain. Not a user on it. The administrator.
5. The analytics and the business listings
These accumulate quietly. Analytics, Search Console, your Google Business Profile, your advertising accounts. Each one should list you as an owner, not just as a user someone granted access to.
A business listing in someone else's account is particularly painful, because it carries your reviews.
What good looks like
You can be entirely happy with your developer and still hold every key. Those are not in conflict, and a good developer will not mind. The usual arrangement is that you own the accounts and grant them access, rather than the other way round.
If someone resists this, that is the answer to a question you should have asked earlier.
How to fix it without a fight
Ask plainly, in writing, for ownership of the domain, hosting, code and email. Most developers will transfer them the same week.
If they do not respond, a domain can usually be recovered through the registrar with proof of business identity, which is slow but works. Hosting and code are harder, and sometimes the honest answer is to rebuild on accounts you control and treat it as the cost of learning.
Either way, do it while the relationship is still good. Nobody has ever regretted holding the keys to their own business.
Keep reading
Domains & HostingBusiness email vs a Gmail address: what it really costs youWhy a quote sent from a Gmail address competes with a stranger's, what a domain email proves, and how to switch in about twenty minutes.
Digital ProductsHow to price a digital productWhy cost-based pricing fails for files, how to price against the outcome instead, and what to do when nobody is buying at any price.
Digital ProductsWhat you need in place before selling digital productsThe practical checklist before your first sale: delivery, refunds, tax, licensing and the file itself, and which parts genuinely matter at the start.
Comments