Do you own your website if an agency builds it?

You might think that paying thousands for a professional agency to build your website means you own it outright. Actually, that's not always the case.

Plenty of business owners find out years later that they don't have full control over their site, their domain, or even their content. The answer comes down to what's written in your contract.

In many cases, the agency keeps ownership of the code, design assets, or critical access points unless you get explicit transfer of ownership. If the legal terms aren't right, you might only have permission to use the site, not true ownership.

This can become a real headache when you want to switch agencies, make big changes, or bring your website in-house. From domain registration to hosting access, from copyright in the code to third-party accounts, real ownership lets you manage your online presence without being stuck with someone else.

Key takeaways

• Paying an agency doesn't mean you automatically own your website—your contract has to transfer all rights to you
• Real ownership means you control your domain, code, content, hosting, and CMS access, so you can move to another provider whenever you want
• Check your contract before signing; make sure it covers intellectual property assignment, domain registration in your name, and full admin access to everything

Defining website ownership: what does it really mean?

When an agency builds your website, ownership isn't as simple as who paid for it. Ownership is about intellectual property rights, mainly copyright in the design and code.

Access and licensing decide what you can actually do with the site. Website ownership means you hold the copyright to the code, design, and content. That's different from just having access or a licence.

Ownership gives you the legal rights to modify, sell, or transfer the website. You call the shots. Licensing means someone else owns the copyright, but you get to use it under certain terms.

You might be able to run the site but not move it or tweak the code. Access just means you can log in and make changes through the CMS. You could have admin access but not own the code or design files.

Lots of businesses only have access and a licence, not ownership. This causes problems if you want to switch agencies or move to a new hosting provider.

The role of website ownership clauses in contracts

Website ownership clauses in contracts decide who legally owns the finished work after you've paid. Without clear terms, UK law gives the agency copyright ownership of any custom code.

The contract should spell out that after full payment, you own or get a perpetual licence to all code, design assets, and content. Look for language about "finished assembled work" and confirmation you own it after completion.

Some web design contracts keep legal ownership with the agency. This can catch you out if you try to leave and take your site elsewhere.

Key components of website ownership

Website ownership isn't just one thing—it's a bunch of separate parts. Each bit has its own rules about who controls it and what risks you take if you don't own it fully.

Domain name: ownership and risks

The domain name is your website's address. When you register a domain through a registrar like GoDaddy or Bluehost, check who's listed as the registrant.

Some agencies register domains in their own name, so they legally own it. If they do, you could lose your web address if things go sour. Sometimes agencies hold domains as leverage to keep you tied in.

Your business name should appear as the domain owner. You can check this by looking up the WHOIS database for your domain.

Hosting and web server platform control

Your website files live on a web server, and whoever controls the hosting account controls those files. Who manages your hosting decides if you can move your site or make changes yourself.

With managed hosting, the agency usually holds the account credentials. This means you have to go through them for updates or technical issues. If you don't have direct access, you're basically renting your own site from them.

Make sure you have full admin access to the hosting control panel: FTP credentials, database access, and the ability to create backups. If you don't, you can't migrate your site on your own.

Content management system and CMS platform rights

The CMS you use affects how much control you have over your site's code and content. Different platforms have different ownership models that shape your options later.

WordPress is open-source, so you own the core software and can usually take your site anywhere. But if the agency built custom themes or plugins, they might keep ownership of that code.

Wix, Squarespace, and Shopify are proprietary. The service provider owns the underlying code. You can export your content, but you can't take the site design or functionality with you.

If you cancel the subscription, you lose access to the whole site. You might get your content back, but you'd need to rebuild from scratch on a new platform.

Finished assembled work versus underlying code

There's a difference between owning the finished website and owning the code that makes it work. An agency might hand over the completed site but keep rights to reuse the code elsewhere.

The finished work is what you see—design, layout, images, text. The underlying code is the HTML, CSS, JavaScript, and custom programming. Many contracts only give you a licence to use the finished website, not the code itself.

This gets tricky if you want to make big changes or move to another developer. Without owning the code, you might have to rebuild your site if you switch agencies. Ask for explicit transfer of intellectual property rights in your contract, not just delivery of the final product.

Understanding agency agreements and intellectual property

If a web development agency builds your site, UK copyright law gives ownership of the code to the creator unless your contract says otherwise. You need written agreements that transfer intellectual property rights if you want to actually own what you paid for.

Default copyright rules for code and content

UK copyright law is straightforward: the person or agency that creates the work owns it. If you hire a web agency and the contract doesn't mention intellectual property, the agency owns the code. You just get a licence to use it.

This covers both code and content. If the agency writes your website copy, designs graphics, or commissions photography, they own those works by default. You can use them on your site, but the rights stay with the creator.

The problem comes up when you want to leave that agency. Without ownership, you might not be able to modify the code, move to a new developer, or reuse the content elsewhere without permission.

The importance of written ownership transfers

A website ownership clause fixes this by stating what happens to intellectual property when you pay in full. The contract should say that all code, design assets, and content transfer to you after final payment. Or it should grant you a perpetual, irrevocable licence to use, modify, and transfer everything.

Without this, you're exposed. Good agencies include clear ownership and access terms in their contracts. If your agreement is silent on intellectual property, ask for an amendment before signing.

The same goes for third-party work. If the agency hires a copywriter or photographer, the contract needs to assign those rights to you too, so you fully protect your website.

Ensuring full ownership and access

Real ownership means you can move your website to a new developer without asking your current agency. You need full admin access to your website's backend and control of all the accounts your site relies on.

Obtaining full admin access to your website

We need admin-level access to our website's content management system with our own login credentials. This can't be a shared account or a limited "client" account with restricted permissions.

Having full control means we can grant access to anyone we choose. If we can't add new users or give access to a different developer without going through our current agency, we're basically locked in no matter what the contract says.

• We can make urgent updates without waiting for agency approval.
• We can hire new developers or agencies when needed.
• We keep control if our agency relationship ends.
• We avoid being stuck with a single provider.

The fix is usually simple. We should ask for full administrator credentials right away and test them to make sure they work.

A reputable agency will hand these over without fuss.

Controlling third-party service accounts

Most websites rely on external services like email delivery, form handling, analytics, payment processing, and image hosting. Each service sits behind an account that someone controls.

We want all these accounts set up in our business's name, billed to our card, with us as the primary contact. If accounts are in the agency's name, we have to rely on them to keep services running, and we might lose access if the relationship ends.

We should audit every external service our website uses and check who owns each account. Common services to check include Google Analytics, email marketing platforms, payment gateways, CDNs, and form processors.

If any accounts are in the wrong name, we need to transfer them now. This stops service disruptions and means we can change agencies without losing anything important.

Risks and common ownership pitfalls

When a web development agency builds your site, ownership issues often turn up years later when you try to switch providers or take control. The two biggest problems are getting locked into a single vendor and finding out your site depends on accounts spread across different companies.

Vendor lock-in and losing access

Vendor lock-in happens when your agency controls key access points that stop you moving your site elsewhere. The most serious risk comes from domain registration in the wrong name.

If your domain registrar account lists the agency as the owner, you can't transfer your domain without their help. We've seen businesses lose their entire web presence because an agency folded or just refused to release the domain.

Managed hosting can cause similar headaches. Some agencies build sites on their own web server platform using systems that won't work anywhere else. You might pay monthly fees but never see the files needed to move your site.

CMS access is another trap. If you only have limited permissions while the agency holds the admin account, you can't grant access to a new developer.

If you can't hand your entire site to a different developer tomorrow without asking your current agency for anything, you don't really own it.

Split ownership among multiple providers

Modern websites depend on lots of external services. Email delivery, form handlers, payment processors, and analytics all need separate accounts. When these accounts belong to different providers or sit in your agency's name, things get messy fast.

A web development agency might register your domain with one company, host your site with another, and set up email through a third provider. If each account uses the agency's contact details and payment card, you've got no direct control.

Third-party service accounts often get missed during handover. Your site might rely on six different services, but you only have login details for two. The rest stay in the agency's accounts, billed to their cards.

This split causes practical problems. When you need to update payment details, add new users, or check service status, you have to contact the agency. If they're slow to respond or things end badly, your site can break while you wait.

It's smart to audit every service your site uses. Check who owns each account and whose card pays the bills. Any account not in your business name could become a problem later.

How to protect your website and assert ownership

Getting clear ownership terms in writing and keeping control over essential credentials protects your business from vendor lock-in and other surprises. We need to focus on contract language, verification steps, and preparing for future changes.

Best practices in contracts and project setup

Before signing anything with a web agency, we have to clarify website ownership rights in plain terms. The contract should say that we own the finished work, including all custom code, design files, and content made for our project.

We should get written confirmation covering these key areas:

• Domain name registration in our company name and contact details
• Hosting account access with full admin credentials
• Source code ownership for custom development
• Design files and assets in editable formats
• Content management system login credentials

Many agencies include a website ownership clause that gives them control over the code. We need to sort this out before work starts. Ask for the contract to specify transfer of all intellectual property rights once we've paid in full.

It's also worth asking about licensing terms for themes and plugins used in the project. Some parts may stay owned by third parties even if we own the custom work.

Verifying and transferring ownership

Once the project wraps up, we need to check that we actually control our own website. This means testing that we can log into every important system ourselves.

We should confirm access to:

• Domain registrar account with ability to change DNS settings
• Web hosting control panel with full admin rights
• CMS dashboard with owner-level permissions
• Email accounts linked to the domain
• SSL certificates and security credentials

Ask for all login details in a secure format and change the passwords straight away. We shouldn't rely on the agency to keep access for us. If they registered the domain or hosting in their name, we need to transfer ownership properly with updated billing info and contact details.

Download a full backup of all website files, databases, and content. Store these backups in more than one place that we control.

Future-proofing: preparing for changes in providers

We need to keep ownership and access even when switching agencies or developers. It's better to avoid platforms that trap us with systems that can't be exported easily.

Open-source solutions like WordPress, Drupal, or custom code make it easier for any developer to pick up the project. SASS platforms like Wix or Squarespace usually keep control over the code, making migrations tricky or impossible.

Keep a record of how the website works, including:

• Technical specs and architecture notes
• Plugin and theme lists with version numbers
• Descriptions of custom functions and why they exist
• API integrations and third-party services

Review access credentials every few months to make sure they're still valid. Update billing info as soon as payment details change. This stops accidental service lapses that could hand control back to a previous provider.

Frequently asked questions

Most business owners have similar questions about website ownership after hiring an agency. The answers depend on your contract, who controls the accounts, and the platform you use.

How can I check who legally owns my domain name using a WHOIS or ICANN lookup?

We can check domain ownership by using a WHOIS lookup service or the ICANN lookup tool. These databases show the registered owner of any domain name, along with admin contact details.

Type your domain name into the search box. The results will show the registrant name, which should be your business or your own name.

If the agency's name shows as the registrant, they technically own your domain. This needs sorting quickly because losing access to your domain can happen if the agency stops responding or goes out of business.

Some domains use privacy protection that hides owner details. In that case, log into the domain registrar account directly to see who controls it.

What should a web design contract include to confirm ownership of the website, content, and source code?

The contract should say that on full payment, we own or get a perpetual irrevocable licence to all code and design assets created for our project. Without this, the agency keeps copyright ownership of the code under UK law.

We need clear assignment of content ownership too. If the agency wrote copy or commissioned photography for us, the contract must transfer those rights to us after payment.

The contract should specify who will register the domain and in whose name. It must also confirm that we'll get admin-level access to the CMS with our own login credentials.

Third-party service accounts should be set up in our business name. The contract needs to cover what happens to hosting, domain, and all credentials if the relationship ends.

If my site is built on Wix or Squarespace, what parts do I actually own and what remains the platform's property?

We own the content we create, like text, images, and videos we upload to Wix or Squarespace. The platform keeps ownership of the underlying code and technology that runs the site.

Our account stays ours as long as we pay the subscription fees. We control the domain if we registered it through our own registrar, but if we did it through the platform, we're tied to their terms.

We can't export the site's code or design to use elsewhere. If we leave the platform, we can take our content and domain, but we'll need to rebuild the site from scratch somewhere else.

The subscription model means we're basically renting the tools and infrastructure. We don't own the website in the same way we would with a custom-built site.

Who should control the hosting and domain registrar account (for example, GoDaddy) to retain full access and ownership?

We should control both the domain registrar account and the hosting account. These need to be registered in our business name, with our email as the main contact, and billed to our payment method.

If an agency sets up a GoDaddy account for us, we need the login details. We should show as the account owner, not the agency.

Some agencies register domains and hosting in their own accounts, saying it makes things easier. That creates a dependency which can quickly turn into a headache if we want to move or if they stop trading.

We can let an agency manage these accounts for us as part of a maintenance agreement. But we need direct access and the ability to grant access to someone else, without having to ask the agency.

What happens to my website and domain if I stop paying the agency or end the maintenance agreement?

If we stop paying for hosting that's part of an agency maintenance plan, the website will go offline when the hosting runs out. The timing depends on the specific setup, but usually it's within 30 to 90 days.

Our domain will expire too if the agency registered it and we're paying through their fees. There's usually a grace period of a few weeks, then the domain becomes available for anyone to register.

If we own the domain and hosting accounts directly, ending the agency relationship doesn't affect the website's availability. We just need to find someone else to handle updates and maintenance.

How can I transfer a domain and website from an agency to my own accounts without losing email or search visibility?

Start by asking the current registrar for the domain transfer authorisation code. If the agency manages the registrar account, they'll need to unlock the domain and share that code.

Before you begin the transfer, write down all DNS settings, especially MX records for email. If you copy these settings exactly to the new registrar, your email should keep working during the move.

Get a full export of the website files, including code, database, and media. Set up your new hosting environment first, then upload everything before you touch the DNS records.

When the site is ready on the new host, update the DNS nameservers to point over. DNS changes usually take about 24 to 48 hours to reach everywhere.

If you keep the same domain name and URL structure, search visibility should stay steady. Try not to make other big changes at the same time, just to keep things simple.

It's a good idea to leave email running on the old server for a few days after switching DNS. This helps you catch any straggling messages that might show up late.

If you'd like to see how we handle this on our own projects, our process page covers our approach to handover and ownership, and our web design service page sets out what's included in a typical build.