A surprising number of business owners do not own their own websites. They find out at the worst possible moment: the developer stops answering, the monthly fee jumps, or the business tries to switch providers and discovers the domain is registered to someone else. The site they paid for turns out to have been a rental.
None of this requires bad intent. Most of it happens through defaults: the developer registers the domain under their own account because it is faster, hosts everything under their own login, and nobody writes down who owns what. The arrangement works fine until it doesn’t.
Here is what to settle, in writing, before any work begins.
1. The domain
The domain name is the single most important asset. If you lose everything else, a domain you control means you can rebuild and your customers can still find you. Ask directly: whose account holds the registration, and whose name is on it? The only correct answer is yours. A developer can manage it for you, but the registrar account should belong to the business, with your email on file and your card paying for it.
2. The content
The words, the photos, the logo files. If a builder writes your pages, confirm the copyright transfers to you on payment. If a photographer shoots your shop, confirm the license covers your use everywhere, forever. You should be able to take every word and image to a new provider without asking permission.
3. The site itself
Ask what happens to the design and code if you part ways. Some platforms simply do not allow export: the site exists only inside their system, and leaving means starting over. Some developers license rather than sell their work. Neither is automatically wrong, but you deserve to know which deal you are signing. The strongest position: the files are yours, hosted in an account you can access.
4. The accounts around the site
Google Business Profile, analytics, search console, email. These accumulate value over years and are painful to rebuild. Each should be created under the business’s ownership with the developer added as a manager, never the other way around. A Google Business Profile owned by a former developer is one of the most common and most expensive messes a small business can inherit.
5. The exit, in writing
One paragraph in the agreement settles everything: on full payment, the client owns the domain, the content, the site files, and all associated accounts, and the developer will provide reasonable transfer assistance if the relationship ends. A professional will not hesitate to sign that. Hesitation is information.
How TenGlade handles ownership
TenGlade’s answer to “do I own my site” is one word: yes. Domain, content, site, accounts, all registered and built in your name from day one, not held by the studio. If you ever leave, everything goes with you. This is published policy, stated on the site and in the agreement, because ownership should never depend on goodwill.
The optional care plan exists for owners who want the site managed, monitored, and updated without thinking about it. It is a service, not a hostage arrangement. The difference matters.
The five-minute check you can run today
Look up your domain with any public WHOIS tool. If you see a privacy notice instead of a name, the real question is whose registrar account the domain sits in, so log in or ask your developer directly which account holds it. Log into your Google Business Profile and check who holds the “owner” role. If either answer surprises you, fix it now, while relations are good and nothing is urgent. Transfers are simple when nobody is angry.
Unsure what you actually own? Bring the question to a fifteen-minute call and get a straight answer, including the steps to fix it, whether or not TenGlade does the work. Book a 15-minute call.