When an agency or a freelancer builds your website, it's natural to assume you own it because you paid for it. Often you do. But a website is several things, not one: the domain name, the hosting, the code and design, the content and data, and the logins. Each of them can sit in someone else's name. If you have ever asked "who owns my website?", this guide shows how to check each part, what to ask for, what to put in the contract and which red flags to watch for.
1. The domain name
Your domain, such as yourbusiness.com or yourbusiness.co.uk, is the part you can least afford to lose. Your website address, your email and years of search rankings depend on it. Two things decide who controls it:
- The registrant is the person or business the domain is registered to. It should be your business, not the agency or one of its staff.
- The registrar account is the login at the company the domain is registered through, such as GoDaddy or Namecheap. Whoever holds that login can point the domain elsewhere, move it or let it expire.
Three checks to do today:
- Look it up. Enter your domain at ICANN Lookup, which uses RDAP, the replacement for the old WHOIS search. It works for .com, .co.uk and most other endings, and shows the registrar and the expiry date. The owner's name and email are usually hidden for privacy, so it tells you where the domain is held, not who holds it.
- Log in yourself. In the registrar account, the registrant details should show your business and an email address you read. If you can't log in, someone else controls your domain.
- Check who gets the renewal emails. For .com and similar domains, registrars must email the registrant about a month and a week before the domain expires. If those emails go to the agency, you won't see them. If the domain expires, your website and email can go offline, and if nobody renews it, it can be deleted and registered by someone else.
An agency can still manage the domain for you from inside your account. Some registrars, GoDaddy for one, let you invite someone in without sharing your password.
2. The hosting account
Hosting is the server your website runs on. Many agencies host client sites on their own accounts, which is often sensible: the agency can look after updates, backups and security. What matters is what happens when you leave.
- Hosting in your name: you pay the host and give the agency its own login. If you part ways, nothing has to move.
- Hosting in the agency's name: fine, if the contract gives you a full copy of the site when you leave (files, database and code) within a set number of days, at a cost agreed up front.
Either way, ask where the backups are kept and how quickly you could get one.
3. The code and design
This is the part that surprises people. In both the US and the UK, whoever creates a piece of work usually owns the copyright in it, unless they are your employee. An agency or a freelancer isn't. So unless your contract transfers the rights to you, the code and design can still belong to them after you've paid.
Without a transfer, a court may decide you can use the site for what you paid for, but that right may be limited, and it isn't ownership. In both countries, a transfer of copyright must be in writing and signed by whoever gives up the rights. US contracts often call the work "work made for hire", but for a contractor that only applies in nine specific categories of work, and only with a signed agreement. So a good contract also includes a written transfer, called an assignment.
Third-party parts can't be assigned at all, because the agency never owned them. They are licensed, so what matters is whose name each licence is in:
- Themes and plugins. Premium ones usually come with a licence key for updates and support. If the key sits in the agency's account and lapses, your site can lose both.
- Fonts. Fonts from Google Fonts use open licences, so there's nothing to transfer. Paid fonts can be tied to an account. Adobe, for example, says a client's website must load Adobe Fonts through the client's own Creative Cloud subscription, and the fonts stop working if it's cancelled.
- Photos, video and icons. Ask who bought each stock licence and for the records, so you can show you're allowed to use them.
- Open-source code. Most sites use some, including WordPress itself. That's normal: the licences let you use it.
4. Content, data and marketing accounts
Text and photos you supplied are yours. Anything the agency wrote or shot for you falls under the copyright point above. The data your site collects, and the accounts that measure and promote it, matter just as much:
- Customer data: form entries, orders, customer accounts and mailing lists. Make sure you can export them. In the UK, if the agency stores or handles this personal data for you, UK GDPR requires a written contract, and it must say the agency deletes or returns the data, as you choose, when the work ends.
- Google Analytics: your business should hold the Administrator role, the one that can manage users. The agency gets its own login.
- Google Search Console: you should be an owner of the property. Only owners can add or remove users.
- Google Business Profile: your business should be the primary owner. A profile can have only one, and the agency can work as a manager.
- Ad accounts, such as Google Ads or Meta: they should be in your business's name, with your payment details. In Google Ads, keep Admin access for yourself: it controls who else has access and can unlink an agency's manager account.
If any of these were set up under the agency's own login, ask for owner or administrator access now, while relations are good. Analytics history you lose can't be collected again.
5. Logins and admin access
The quickest ownership test is simple: can you log in to each of these yourself, as an owner or administrator, without asking anyone?
- Domain: the registrar account, and the DNS provider if that's a different company.
- Hosting: the hosting account, or at least a way to download a full backup.
- Website: the admin area. On WordPress, that means a user with the Administrator role.
- Google: Analytics, Search Console and Business Profile.
- Money and email: ad accounts, payment providers such as Stripe or PayPal, and your email service.
- Code: for a custom site, the code repository, for example on GitHub.
Give everyone their own login, never a shared one, so you can remove the agency's access later without changing every password. Use a business email address that isn't tied to one employee, turn on two-step verification and keep the details in a password manager.
Checklist: what to ask for and put in the contract
Ask for these before work starts. It's much easier than asking on your way out.
- Ownership of the custom work: a written assignment of the copyright in the design, code and content made for you, once you've paid in full.
- A licence to the agency's own tools. It's normal for an agency to keep its starter theme or code library, but your licence to use them should never end and should cover any future developer.
- A list of third-party licences (themes, plugins, fonts and images): whose name each one is in, and how it moves to you.
- The domain registered to your business, in a registrar account you own.
- Accounts in your name for analytics, Search Console, Business Profile and ads, with the agency added as a user.
- Admin access to the website for you from launch day.
- Exit terms: a full copy of the files, database, code and design files within a set number of days, at a cost agreed now, and the notice each side must give.
- Data terms: how the agency protects your customers' data, and a promise to delete or return it when the work ends.
This is general information, not legal advice: ask a lawyer to check any contract before you sign it.
If you're still choosing who to hire, our guide on how to choose a custom web development company lists more questions to ask first.
Red flags to watch for
- The domain is in the agency's name or account, and they won't move it to you.
- You have no admin access to your own website: only an editor login, or nothing at all.
- A CMS only the agency can run. If your site is built on the agency's own system, you can't take it to another developer or host. You can only rebuild it.
- The contract says nothing about ownership, or says the agency keeps everything.
- Google and ad accounts under the agency's login, with you added as a viewer or not at all.
- Fees to "release" your domain or files that were never in the contract.
Open platforms avoid the lock-in. WordPress, for example, is open-source software, so you can move a WordPress site to another host and hire any WordPress developer to look after it. If that suits you, see our WordPress development page.
A monthly plan where the agency owns and hosts the site can still be a fair deal for a small business. Just check what you'd keep if you stopped paying: at the very least, your domain, your content and your data.
If you part ways with your agency
A handover goes faster when the contract is clear and the invoices are paid, so start there.
- Read the contract. Check the ownership clause, the notice period and anything still owed. Rights often pass to you only once you've paid in full.
- Ask for everything in one written request: the domain, a full backup (files and database), the code, the design files, licence details and owner access to every account.
- Move the domain. The agency can often move it straight into your own account at the same registrar, or remove the transfer lock and give you the transfer code (often called an auth code) so you can move it to another registrar. For .com and similar domains, that move can be refused within 60 days of registration or a previous move, and a change of registrant can lock the domain for 60 days unless the registrar offers an opt-out. ICANN has approved changes to these rules, and .uk domains follow Nominet's own process, so check with your registrar.
- Test before you switch. Set the site up on the new hosting, check it works, then point the domain at it. Keep the old hosting until you're sure.
- Remove old access last. Once you have everything, remove the agency's users and change any passwords they knew.
If an agency won't hand over a domain registered in its own name, that's a legal question rather than a technical one, and the time to speak to a lawyer.
Talk to Devtings
Devtings builds custom websites, web apps and WordPress sites for small and mid-size businesses in the US and the UK. If you're planning a new site and want ownership clear from day one, or you'd like help working out what you own today, see our custom web development services or get in touch.

