Fazley RabbiYou should own, or at least fully control, four things: the domain name, the hosting and other service accounts, the content, and the code (or a clear licence to use it). Paying for a website does not make these yours automatically. What counts is whose name the accounts are registered in, who holds the logins, and what your written agreement says. The time to sort this out is before a problem, not during one.
The four things you need to control
1. The domain name
Your domain (yourbusiness.com or yourbusiness.com.bd) is your address on the internet and usually your email address too. Whoever is listed as the registrant, and whoever controls the registrar account and its email, effectively controls the domain. If that is a former developer or an employee who has left, renewing or moving it needs their cooperation. Domain, hosting, SSL and DNS explained covers how these pieces fit together.
2. Hosting and other service accounts
A website depends on more accounts than most owners realise:
- Hosting or cloud account
- Business email
- Google Search Console, Google Analytics and Google Business Profile
- Meta Business account, Facebook page and Instagram
- Payment gateway and any plugin or theme licences
- DNS and security services
Each should be in the business's name, with the business owner as the main administrator. Developers and agencies can be added as separate users and removed when the work ends.
3. The content
Your text, photos, logo, product descriptions and videos. If you supplied them, they are generally yours, but check that the developer did not fill gaps with images or text copied from elsewhere. Stock photos come with licences; keep a record of where each one came from.
4. The code
Custom code written for you, and the themes, plugins or libraries it is built on. Third-party parts come with their own licences. Who owns the custom part depends on your agreement and the law that applies to it, so this is the point where a lawyer's review is worth having. At a minimum, you should receive a full copy of the source code and the right to use, change and move it.
How to check what you control today
- Look up who the domain registrant is, and confirm you can log in to the registrar account yourself.
- Try logging in to your hosting, email and Google accounts with your own credentials, not the developer's.
- List every account the website touches, using the list above as a starting point.
- For each one, note who the owner or main admin is and which email receives password resets.
- Ask your developer for a full backup of the site and database, and confirm you can open it.
If any of these steps fails, you have found a gap to close.
Common situations that cause trouble
| Situation | Risk | What to do |
|---|---|---|
| Domain registered in the developer's name | You cannot renew or move it without them | Ask for it to be transferred to the business |
| Hosting on the agency's own account | Leaving the agency means rebuilding or migrating | Move to an account in your name, or agree in writing how you can leave |
| Facebook page admin is a former staff member | Lost access to page and ads | Keep at least two trusted admins from the business |
| Renewal reminders go to a personal email | Domain or SSL expires unnoticed | Use a shared business address for all account emails |
| "Free" website where you never receive the code | Locked in if you want to change | Ask before you start what you will receive at the end |
What to put in writing
Before a project starts, the agreement or a written email exchange should cover:
- Who owns the custom code and design once you have paid
- Which third-party themes, plugins and licences are included, and in whose name
- That all accounts will be created in the business's name
- Handover of all logins, source code, database and setup notes at the end
- What happens if payments stop part way, for either side
- Whether the developer may show the work in their portfolio
- Support, maintenance and response times after launch, if any
Contract and copyright rules vary, so ask a lawyer to review anything important. I prefer to agree these points before writing any code, because they are easy to settle when everyone is still on good terms.
Common questions
Is it fine for my developer to keep admin access? Yes, as a separate user you can remove later. The problem is when they hold the only owner account.
What if my website runs on a subscription platform? You usually own your content, but the platform owns the software. Check what you can export if you leave.
I'm planning to change developers. Where do I start? Secure the domain and accounts first, then take a full backup. If you are moving host as well, read moving to a new website or host without losing rankings.
A good final step is a written handover; the website handover checklist lists what to collect. If you want help untangling ownership of an existing site, see software and website development or get in touch.