Do you actually own your website? Domains, hosting, and platforms, explained

A lot of small business owners pay for their website every month and assume that means they own it. Usually they own less than they think, and they find out the hard way: when they want to redesign, switch companies, or part ways with whoever set it up, and discover they cannot actually get to their own site.

Owning your website is not one thing. It is really three things, and most people only control one of them. Here is what you actually own, what you are only renting, and why the difference can cost you your address, your email, and your search ranking if you get it wrong.

What are you actually paying for?

When you "have a website," you are really paying for three separate things that often arrive bundled into one monthly bill:

• Your domain name. This is your address, like yourbakery.com. You lease it, usually yearly, through a company called a registrar.
• Your hosting. This is where your website actually lives and runs: the computers that serve your pages to visitors.
• Your platform, or builder. This is the tool you build and edit the site in, like Wix, Squarespace, Shopify, or WordPress.

A website builder rolls all three together and rents them to you from one company. That is convenient, and it is also where the ownership questions begin. When everything comes from one login, it is easy to assume you own all of it. Usually you do not.

So do you own your website, or not?

There are two answers, because there are two different things.

Your content, meaning your words, your photos, your brand, is yours. But the site itself, the thing you built inside a builder, usually cannot leave. A Wix site only runs on Wix. A Squarespace site only runs on Squarespace. You cannot export it and take it to another company. If you leave the builder, you build your site over again from scratch.

Your domain is the part you can truly own and take with you, as long as it is registered in your name. And that "as long as" is the whole game.

Wait, do I even own my domain?

Probably yes. But where it lives matters.

Owning a domain comes down to one thing: whose name and account it is registered under. The official owner is whoever is listed as the "registrant" in the public domain record. ICANN, the organization that coordinates the world's domain names, treats that registrant as the recognized owner.

So if you bought your domain through Wix, you are most likely still the owner. Wix says as much in its own help center: it recognizes the registrant listed in the public record as the domain's owner. What trips people up is that owning it and controlling it are not the same thing. When the domain lives inside your Wix account, Wix manages it by default, and to actually move it you have to go through a transfer process. People feel that friction and assume they do not own it. They do. It is just sitting behind someone else's counter.

One more thing worth knowing if your domain came "free." That free first year usually comes attached to a yearly plan, and after the first year the domain renews at the normal rate. The reassuring part: your site plan and your domain are separate, so you can cancel the website and still keep the domain. The cleaner move, if you want the domain to be fully yours, is to hold it in a registrar account you control.

Why does owning your domain matter so much?

Because your domain is the one piece of your online presence that everything else hangs off of.

• It is your address. Change it, and every business card, every saved link, and every Google listing points to nothing.
• It usually carries your email. Lose control of the domain and you can lose your branded email along with it.
• It holds your search history. The trust you build up with Google lives on your domain. Start over on a new one and you start that climb from the bottom.
• It is the one thing you can take anywhere. If you own your domain in your own account, you can move from a template to a custom site, or from one designer to another, without losing your spot on the internet.

This is the same reason a real website beats renting space on someone else's platform, which I wrote about in whether your small business really needs a website. Your domain is the land you own. Everything else is a building you can put back up.

What if I want to start with a template and go custom later?

This is a smart, common plan, and there is a way to set it up that keeps every door open.

The trick is to not let the builder hold your domain. Buy your domain at an independent registrar that you control, one that gives you full access to your own settings. Then point that domain at your template site now. Later, when you are ready for a custom build, you point the same domain at the new site. The domain itself never moves. There is no transfer, no waiting period, and your email keeps working the whole time.

Most builders support this. Wix, for instance, will let you connect a domain you registered somewhere else, so you are not forced to buy it from them. (Connecting a custom domain does require a paid plan, which is good to know going in.)

Set up this way from day one, going from template to custom later is a quiet afternoon rather than a migration. I compared the two starting points in template or custom: how to choose a website.

How do I move a website without breaking everything?

When the day comes to move, there are two paths, and the safe one is usually simpler than people fear.

• Point it. Leave the domain registered where it is and just change where it points. This is the everyday move. It is reversible, and it avoids the waiting periods that come with transfers.
• Transfer it. Move the domain to a brand-new registrar entirely. You only need this if you are consolidating accounts, and it comes with rules: a domain usually cannot be transferred within 60 days of being registered or moved, so this is not something to start the week before a launch.

The single biggest risk in either case is not the website. It is your email. The settings that route your email live in the same place as the settings that point your website, and a careless move can silently break your inbox. Whoever moves your site for you should be protecting your email before they touch anything. (I will walk through the step-by-step of a clean move in a follow-up post.)

Why does a web studio ask for access to my accounts?

If a designer has ever asked you for logins, this is the part worth understanding, because the right answer should make you feel safer, not less safe.

To build and launch your site, we do need to touch a few specific things: where your domain points, and where the site is hosted. But "we need access" should never mean "give us your password." Every reputable platform lets you grant limited, named access to a helper without handing over the keys to everything:

• You invite us with our own login, never yours.
• We get only the piece we need, not your billing, not your password, not the ability to lock you out.
• You can remove our access the moment the work is done.

Here is how I actually prefer to do it. Whenever possible, I launch your site without taking any access to your accounts at all. You keep your domain exactly where it is, in your name, and you simply point it at the site I built. The keys stay entirely with you. When access is genuinely needed, I ask for the narrowest version of it, and you remain the owner of everything the entire time.

How I think about it

You should own your website the way you own your storefront, not rent it back from whoever built it.

So when I build for a small business, I set it up so you are never locked in. Your domain stays in your name. Your accounts stay yours. I take the smallest amount of access the job requires, and often none at all. If our paths ever part, you can walk away with your address, your email, and your search history intact, because they were yours all along.

If you want a website built so that you actually own it, you can see a few small business sites I have built or start a project.