colb.dev

Writing · Owning your site

Who owns your website, your domain and your code

Four accounts decide whether you can leave. Here is how to check which ones are actually yours.

Most people find out they do not own their website at the worst possible moment, which is when they want to change developer. It is worth checking before then, and it takes about ten minutes.

There are four things, and they are separate. You can own some and not others.

The domain

Your web address, registered at a company like Namecheap, GoDaddy or Cloudflare. This is the one that matters most, because it is the only piece that cannot be rebuilt. Everything else can be made again. Your domain is where your customers, your email and ten years of Google rankings all point.

Look it up on a WHOIS service and see whose name and email are on it. If it is your developer's, you do not own your domain. You are renting your own address from them.

The hosting

Where the site actually runs. You want an account in your name that you can log into, even if you never do. The common arrangement where a developer hosts dozens of client sites under one account they control is fine right up until the relationship ends.

The code

The files that make up the site. You should be able to ask for a copy and receive one. If the answer is that it lives on a proprietary platform and cannot be exported, then you are not buying a website, you are renting access to one, and the price of leaving is starting over.

The logins

Google Business Profile, Search Console, Analytics, your email provider, the DNS records. These accumulate quietly over a project and get forgotten. They are also the ones most likely to still be in someone else's name a year later.

How to check all four

Send one email and ask for the registrar login, the hosting login, a copy of the code, and a list of every account created for you with the login for each. A developer who has done this properly will send it over. It is not a difficult request and it is not an accusation.

If the reply is vague, that is the answer.

How I do it

The domain goes in your name from the start, usually on your own registrar account. You get the code. Every login is handed over in writing when the project ends, whether you plan to use them or not. If you want to take the site to another developer two years from now, nothing of mine is in the way.

Related

Start a project

Tell me what you need built

A few sentences is enough: what the site or tool has to do, and roughly when you need it. You'll get a reply from me, the person who writes the code, usually the same business day, with a couple of questions and a rough range.

What do you need help with?

So I can reply. Nothing else goes to it.

The business, the problem, and anything that already exists: a current site, a deadline, a budget range.