DEV Community

Cover image for Who Actually Owns the Website — and Why Clients Never Ask Until They Want to Leave
аЛЕКС ЛИР
аЛЕКС ЛИР

Posted on

Who Actually Owns the Website — and Why Clients Never Ask Until They Want to Leave

I run a small WordPress studio — webmaster.co.ua, 18 years, 235+ projects. Ownership never comes up during a happy project. It only comes up when a client wants to switch developers, and suddenly discovers the domain, hosting account, or a key plugin license isn't actually theirs.

Registering the domain under your own account feels efficient, and it's the single worst thing you can do to a client. Early on, we'd register domains for clients because it was faster than walking them through it. Years later, some of those clients wanted to move to another developer and couldn't, because the domain lived in our account, under our payment method. Nothing malicious — just an ownership gap nobody noticed until it mattered. We now register everything directly under the client's own account, even when it's slower for us upfront.

Premium plugin licenses are often tied to the developer, not the site. A lot of premium WordPress plugins license per-account, not per-domain. If a developer built a site using their own plugin license, the client's site can silently lose functionality the moment that developer stops renewing it — sometimes years after the relationship ended, with no warning. We now document every paid plugin and whose license it's under, as a deliverable, not an afterthought.

Hosting accounts create the same trap in reverse. A client who never sees their own hosting login has no real ownership, even if their name is on the invoice. If the developer disappears, so does access to the actual site. We hand over hosting credentials at project completion by default now, not on request — because "on request" assumes the client knows to ask, and most don't.

None of this shows up as a problem until someone tries to leave. A functioning relationship never surfaces an ownership gap. It only surfaces during a transition — which is exactly the worst time to discover it, because it's also the moment of least trust and least patience for a technical explanation.

If you build client sites, it's worth auditing what's actually in the client's name versus yours — not because anyone's acting in bad faith, but because ownership gaps are invisible right up until someone needs the exit door.

Top comments (0)