Website Ownership: Who Controls Your Domain, Hosting, Code and Accounts?
Your business should control every part of its website. The domain should be registered in the company's name, the hosting account should be yours or reachable by you at any time, you should have owner-level access to accounts such as Google Search Console and Google Analytics, and your contract should state what rights you have to the code and content. Agencies and freelancers can – and often should – manage these things for you. The difference that matters is between someone managing your assets and someone holding them. What follows is practical guidance, not legal advice.
The domain: the asset you cannot replace
Design, hosting and even content can be rebuilt. The domain carries your email addresses, links from other sites, your search visibility and the address customers remember. Losing control of it is the most expensive ownership problem.
Three roles are involved: the registry that runs the extension (for example .bg or .com), the registrar or reseller through which the domain is registered, and the registrant – the person or company that holds the registration. ICANN, which coordinates generic domains such as .com, says registrants assume sole responsibility for the registration and use of their domain name, must provide accurate contact information, and are entitled to know who their registrar is and how renewal, transfer and restoration work.
What to check:
- the registrant is your company – not the agency, a former employee or a freelancer personally;
- the contact email is a company address that will still work when a person leaves, not someone's private mailbox;
- you have your own login at the registrar, or at least a written commitment that the transfer code will be provided on request;
- automatic renewal is switched on and the payment card on file is valid;
- you know who manages the DNS records – they decide where the website and the email point.
Under ICANN's transfer policy for generic domains, only the registered name holder (or someone they have explicitly authorised) can start a transfer to another registrar, and the transfer needs an authorisation code, which the registrar either lets you generate yourself or must provide within five calendar days of a request. Country-code domains such as .bg and .eu follow their own registry rules, but the principle is the same: the registrant decides.
Hosting: whose account, and can you leave?
It is common and perfectly reasonable for an agency to host the sites it builds, or to manage a hosting account on your behalf. What matters is that you can leave. Ask:
- Is the hosting account in your name or the agency's? If it is the agency's, what exactly do you receive if you move – files, database, configuration, email?
- Can you get a full, recent backup on request, in a standard format?
- Where is your email hosted? Moving a website is easy compared with moving years of mailboxes.
- Who receives the invoices and renewal notices?
Hosting also means data. If your site collects enquiries, orders or customer accounts, the hosting provider – and any agency with access – processes personal data on your behalf. As the European Commission explains the GDPR, the controller decides why and how personal data is processed, the processor processes it only on the controller's behalf, and the processor's duties must be set out in a contract or other binding legal act. Make sure that contract exists.
Code and content: who holds the rights?
This is the part most often assumed and least often written down. Paying for a website does not automatically mean you hold every right in it. The EU Software Directive (2009/24/EC) says that when a computer program is created by an employee in the execution of their duties or following the employer's instructions, the employer alone is entitled to exercise the economic rights – unless a contract provides otherwise. An agency or a freelancer is not your employee, so the contract, together with national copyright law, decides. If the project matters to your business, have the contract checked by a lawyer.
Points to settle in writing:
- Custom code: are the rights transferred to you, or do you receive a licence to use and modify it? Either can be fair, as long as it is clear and covers what you will need – for example, hiring another developer for changes.
- The developer's reusable components: a licence to use them in your site is normal; check that it continues if you stop working together.
- Third-party parts: themes, plugins, fonts, stock photos and map services come with their own licences, often per site and often with yearly renewal. In whose name are they bought?
- Open-source components: fine to use, but their licences have conditions a professional developer should know.
- Content and design: texts, photos and graphics created for you – can you reuse them elsewhere, for example in print or in an app?
- Access to the code: a copy of the source code or access to the repository, plus enough documentation for another developer to set the site up.
We write our own code rather than relying on heavy templates, which is exactly why it matters to state clearly in the contract what the client receives. Ask the same of anyone who builds your site, whatever technology they use.
Accounts: the part that grows quietly
A typical business website is connected to many accounts: Google Search Console, Google Analytics, Tag Manager, Google Business Profile, advertising accounts, social media profiles, the cookie consent tool, the payment provider, the email-sending service. Each should have your company as owner, with others given only the access they need.
- Google Search Console has owners, full users and restricted users, and only owners can add or remove others. A verified owner is tied to a verification token – for example an HTML file, a meta tag or a DNS record. When someone leaves, Google advises removing both their access and all of their verification tokens, because otherwise they can verify ownership again.
- Google Analytics has roles from Viewer to Administrator, and only an Administrator can manage users. Make sure someone inside your company holds that role.
- For everything else the rule is the same: the company owns the account, people get access, and logins live in a company password manager, not in one person's head or inbox.
Who should own what – a summary
| Asset | Who should own it | What the agency typically gets |
|---|---|---|
| Domain | Your company, as registrant | Access to DNS or the registrar account, if needed |
| Hosting | You, or the agency with a clear, written exit | Technical access to deploy and maintain |
| Code | Rights or licence defined in the contract | Right to reuse its own generic components, if agreed |
| Content and design | You, as agreed in the contract | Permission to show the project in its portfolio, if you agree |
| Search Console, Analytics, Tag Manager | Your company, as owner or administrator | User access at the level needed |
| Licences – themes, plugins, fonts, photos | Bought in your name where possible | Information about renewals |
An access audit you can do this week
- List every account and service connected to your website. Our company website checklist can remind you of the usual ones.
- For each one, write down who the owner is, which email address is used and whether you can log in yourself.
- Check the domain registrant and the expiry date.
- Ask for a current backup of the site and check that it opens.
- Remove people who no longer work with you, including their old verification tokens in Search Console.
- Store the result in a company password manager that more than one person can reach.
When you change developers
Changing who looks after your site goes smoothly when ownership was clear from the start: the new team gets access, the previous one hands over code, backups and documentation. Warning signs are a domain in the developer's name, no logins at all, or a platform from which content cannot be exported. If you are preparing a new project, put these points in your brief – see how to write a website brief that gets comparable quotes – and if the platform will change, plan redirects carefully, as described in our guide to redesigning without losing Google rankings.
Whoever builds your next website or web-based software – including us – should be able to answer these questions in writing before work starts: who owns the domain and accounts, what rights you receive to the code and content, and what you get if you move. Contact us to discuss your project.
Sources
- Registrants' Benefits and Responsibilities – ICANN
- 5 Things Every Domain Name Registrant Should Know About ICANN's Transfer Policy – ICANN
- Managing owners, users, and permissions – Search Console Help
- Access and data-restriction management – Google Analytics Help
- Directive 2009/24/EC on the legal protection of computer programs, Article 2 – legislation.gov.uk
- What is a data controller or a data processor? – European Commission