Do You Own Your Own Website?
The question most owners can't answer: who actually controls your domain, hosting, email, and accounts? The five-minute ownership audit, and the hostage problem it prevents.
A veterinary clinic decides it's time for a new website. The old one was built seven years ago by a freelancer who was great back then and has since drifted — slow to reply, then very slow, then nothing. Fine, thinks the practice manager. We'll just take our site to someone new.
Except there is no "our." The domain — the clinic's name, the address on its signage, the ending of every staff email — was registered under the freelancer's personal account. The hosting is his. The login for the Google profile is an email address only he can open. The clinic doesn't own its website; it has been borrowing it for seven years from someone who has stopped answering the phone. When the domain's renewal fails eleven months later on his lapsed credit card, the website disappears, and the email goes with it — mid-week, mid-everything.
Nobody stole anything. That's what makes this story so common: it's not a crime, it's a default. Ownership goes to whoever happened to click "register," and nobody thought about it again for seven years.
The Foundations
Constraint check
Is This Your Constraint?
If your web person vanished today, you couldn't get into your own site? This is probably your constraint.
Five minutes · tells you what to fix first
Cluster tool
The Foundations Audit
Whether you truly control your domain, email, and site, scored with fixes ranked.
Shows what isn't actually yours
The stage underneath the stage
Every other cluster in this library builds something: visibility, trust, conversion, cash flow, relationships. This one protects all of it. The foundations aren't a step in the customer's journey — they're the ground the journey happens on: the domain, the hosting, the email, the handful of accounts that everything upstream quietly depends on. Nothing here wins you a single customer. Losing it can cost you all of them at once.
The five-minute ownership audit. Can you answer these, today, without asking anyone?
- The domain: whose name is on the registration, and who gets the renewal emails?
- The hosting: whose account does your website live in, and could you log in right now?
- The site itself: if you left your current provider, does the site come with you?
- The email: does it run on a domain you control, and who controls the settings behind it?
- The accounts: Google Business Profile, analytics, socials — do you hold working logins, or does someone hold them for you?
Every "I'd have to ask" is a dependency you didn't know you had.
The right answer to all five has the same shape: accounts in the business's name, billed to the business's card, with helpers invited in as users — never the other way around. Good web people work happily inside that structure; it's the ones who resist it you learn something about.
This is not about trust
The objection arrives immediately: my web person is honest. Almost certainly true — the hostage problem is rarely villainy. People retire, burn out, move countries, close businesses, lose interest, and die. Ownership isn't an accusation; it's structure that keeps their bad year from becoming your outage. The same goes for the quieter failures this cluster covers: the renewal on an expired card, the email that lands in spam because nobody set up the records that vouch for it, the plugin that gets hacked because nothing was updating it, the backup that turns out to be a hope rather than a file.
None of it is glamorous. All of it is cheap to fix on a calm Tuesday and expensive to fix during a fire.
What's in this cluster
Domains in plain language — what a domain actually is, the renewal games registrars play, and how to never lose yours.
Hosting in plain language — what a practice site really needs, and the overpaying patterns to recognise.
Business email that lands — an address on your own domain, and the invisible records that decide whether your messages reach inboxes.
Backups and what breaks — the short list of what actually goes wrong, and the minimal safety net for each.
Switching providers cleanly — leaving an agency or freelancer without losing your domain, site, email, or history.
Hiring web help without getting burned — fair price ranges, red flags, and the ownership questions to settle before any work starts.
Your next step
Run question one of the audit right now: try to log in to wherever your domain is registered. Not your website — the registration. If you don't know where that is, or the login lives with someone else, that's the first thing to fix this week — it's the deed to everything else.
Questions practices actually ask
My web person set everything up years ago and it all works. Why touch it? Because "it works" and "you control it" are different facts, and only one of them is tested by things going wrong. The audit costs five minutes; discovering the answers during an outage costs weeks.
What does healthy ownership actually look like? The business owns the registrar, hosting, and email accounts; renewals bill to the business's card; the web person has their own invited login that you can revoke. Handing over that structure is a ten-minute job for any competent provider.
Is my free Gmail address really a problem? For receiving, no. For being taken seriously and for owning your identity, yes: the practice's email should live on the practice's domain, so it moves when you move and vouches for you when you write to strangers.
Isn't switching providers a nightmare? It's a checklist, not a nightmare — but only if you own the foundations. Everything hard about switching comes from untangling ownership after the relationship has already soured. That's exactly what this cluster exists to prevent.