Do you actually own your website?

Ask a small-business owner if they own their website and almost all of them say yes. Then ask where the domain is registered, who holds the hosting login, and whether they could move the whole thing to a new developer next week. That's when it gets quiet.

Website ownership comes down to four things. Each one is easy to check, and easy to give away without noticing.

What owning your website actually means

Four things make a website yours.

The code. The actual files your site is built from. If they live only inside a builder like Wix or Squarespace, you can't take them anywhere. Those platforms don't hand you a copy you can move to another host. You rent the building and you never get the blueprints.

The domain. Your web address, registered in your name or your business's name, on an account you control. This one gets taken from owners all the time. A developer registers it under their own account to “make setup easier,” and now your address is theirs.

The accounts. Hosting, analytics, the dashboard where everything's managed, the email tied to it. All in your name, with logins you hold.

The content. Your words, your photos, your customer data. Yours to export and walk out with.

Own all four and you can pick up your website and move it to anyone. Miss one and you're stuck, usually at the worst possible time.

Where people find out they don't

Two ways this usually goes.

The platform. Wix and Squarespace are fine for getting started, and plenty of businesses run on them for years. The catch shows up the day you want to leave. You can't take a Wix site with you, and Squarespace only lets you export part of one. Your design, your pages, the work you put in, most of it stays on their platform. Leaving means rebuilding from scratch, and they know it. So the monthly price climbs and you pay it.

The handshake deal. A local developer or agency builds your site and quietly keeps the keys. The domain sits on their account. The hosting is in their name. The code never gets handed over. As long as you're happy, none of it comes up. The day you want to switch, you learn that “your” website was theirs with your logo on it.

The one test that settles it

One question settles ownership, and I'd ask it of anyone I hired to build my site.

Can I fire this person tomorrow, take the code and the domain to a new developer, and have my website keep running without them?

If yes, you own it. If the honest answer is “I'd have to start over,” you don't, whatever the contract says.

What it costs you when it goes wrong

Lock-in costs you at the exact moment you can least afford it.

The platform raises its monthly price. You do the math on leaving, realize it means rebuilding everything, and you stay and keep paying. The pricing works precisely because leaving is expensive.

Your business grows and the template can't keep up. So you rebuild anyway, except you start from nothing, because you never had the code to build on.

You and your developer part ways. The site goes stale or goes down and you can't get in to fix it, because the accounts were never in your name.

Every one of these ends the same place: paying for your website twice. A cheap site that locks you in costs more than the one you'd have owned outright.

How I do it

When I build you a site, you own the parts that make it yours to keep: the code, the domain, and the content. The domain and your accounts are registered in your name. I host it on my own Cloudflare setup and keep it running, but that's not a leash — the code and domain are yours, so you can take them to another host any time, or have me hand everything off. The day you don't want me, I do exactly that, with nothing locked and nothing missing.

If you ever fire me, you lose nothing but me.

That's the whole promise, and it's why I do this the way I do. I'd rather earn the work every month than trap you into it.

What to ask before you sign with anyone

You don't have to hire me to get this. You have to ask the right questions of whoever you do hire. Four of them:

1. Will the domain be registered in my name, on an account I control?
2. Do I get the actual code, in a form I can move to another host?
3. Are the hosting and analytics accounts in my name, with my logins?
4. If you and I stop working together, what exactly do I keep, and how do you hand it over?

A builder who owns their work answers all four without flinching. If the answers turn vague, keep looking.

You can skip the quiet moment

Back to that quiet moment, the one where someone realizes they can't move their own website.

You can skip it. Own the code, the domain, the accounts, and your content, and your website is yours to keep and yours to move. You can walk anytime. You probably never will, and that's the point.

If you want a site built that way, tell me what you need. And if you're not sure what you've got right now, send me your domain and I'll tell you who actually owns it.