Home

›

The Site Is the Client’s

Pillar

The Site Is the Client’s

The first of my four rules. Why I believe a website should belong to the person who pays for it, and what goes wrong when it does not.

2 articles

Key takeaways

  • A website belongs to its owner when the domain and hosting are in their name, they have full administrator access, and they can move or hand it to someone else without permission from anyone.
  • Many businesses do not meet that test. They rent their site from a platform, an agency or a host, and only discover it when they try to leave.
  • Ownership is the first of my four rules because the other three mean little if someone else holds the keys.

This is the rule I care about most, because I saw it broken more often than any other. When a business owner pays for a website, they assume it is theirs. Very often it is not, and nobody tells them until the day they want to change something, change provider or simply leave.

What owning a website means

I use a simple test. A website belongs to its owner when three things are true:

  1. The domain is registered in their name, with their email as the contact, at a registrar where they can log in.
  2. The hosting account is theirs, billed to them, so the files and the database sit somewhere they control.
  3. They have full administrator access to the site itself, and they could give a new developer access tomorrow without asking anyone.

If any of the three is missing, the owner is renting, not owning. Renting can be a perfectly reasonable choice, as long as it is a choice made with open eyes.

Why it is the first rule

The other three rules, that a site is well built, ready for AI search and kept current, all assume that the owner can act. If someone else holds the domain, the hosting or the admin account, every improvement depends on that person’s goodwill, prices and availability. Ownership comes first because without it the rest is out of the owner’s hands.

The articles in this section

Website Builder Lock-In: Easy to Get In, Hard to Get Out looks at how hosted platforms make the first step effortless and the last step difficult, and what that means for anyone who builds on them.

You Built Your Site With an AI Website Builder. Now Who Can Change It? is about the new wave of sites generated in an afternoon, and the owners who cannot maintain what they were given.

Hostage Hosting: When Your Web Designer Owns Your Domain describes a business model I ran into again and again: selling services nobody asked for to customers who cannot easily leave.

WordPress vs Wix: People Paid to Avoid WordPress Because It Was Hard explains why so many people chose closed builders, and why I decided the answer was to make the open option simpler.

Why Use WordPress? Because Any Developer Can Pick It Up is about choosing a platform that thousands of people know how to work on, so the owner is never tied to one provider.

Website Migration: Why I Stopped Working Inside Other People’s Setups tells how the frustration of migrations turned into a system, and how NoTiesBuilder and FreeYourWeb came out of it.

In this topic