“Do I own my website?” sounds like a yes-or-no question. In practice, a business website is a collection of separate assets and accounts, and each can be controlled by a different person.
You might control the domain but not the hosting. You might have WordPress access but no server access. You may own the copy you wrote but only have a licence to use photography or software supplied by somebody else.
The practical test is simple: if your current web supplier disappeared tomorrow, could your business still renew the domain, access the site, recover the files, see the analytics and appoint somebody else without starting again?
This article is a business handover guide, not legal advice. It focuses on the practical questions UK businesses should resolve in writing before a website project ends or a supplier changes.
Website ownership is really three different questions
It helps to separate three ideas that are often mixed together.
| Question | What it means |
|---|---|
| Who owns it? | Who holds the legal rights to a particular asset, such as original copy, photography or design work. |
| Who controls it? | Who has the account, login or authority needed to manage the domain, hosting or platform. |
| Who is licensed to use it? | Who has permission to use software, images, fonts, themes or other material owned by somebody else. |
A healthy website arrangement can involve all three. The problem starts when nobody knows which applies.
The website asset map: what should you check?
| Asset | What to confirm | Why it matters |
|---|---|---|
| Domain name | Your business can renew, transfer and update it. | Losing domain control can affect both the website and email. |
| DNS | You know where DNS is managed and who can change records. | DNS controls where web and email services point. |
| Hosting | You know the provider, account arrangement and exit process. | You need a route to migrate or recover the site. |
| CMS admin | Your business has suitable administrator access. | Editor-only access may not be enough to move or maintain a site. |
| Files and database | A current backup can be exported and restored. | A login is not a replacement for a recoverable copy. |
| Copy and photography | Rights and licences are documented. | Paying for creative work does not automatically answer copyright ownership. |
| Theme, plugins and software | You know which licences are yours and which belong to an agency. | Updates or premium features may change when a supplier leaves. |
| Analytics and Search Console | Your company has its own access. | Historic performance data should not disappear with an agency login. |
| Email and forms | You control the mailboxes, sending service and destination addresses. | Leads can be lost if old supplier accounts remain in the chain. |
| Payment and booking accounts | Business-critical integrations sit under appropriate company control. | Customer and revenue systems should not depend on one freelancer’s login. |
1. Start with the domain name
Your domain is the web address customers know. It may also be connected to business email, verification records and other services.
The important question is not only “Who paid for the domain?” Ask:
- Which registrar holds it?
- Which account manages it?
- Which email receives renewal and security notices?
- Can the business authorise a transfer?
- Is automatic renewal configured appropriately?
For .uk domains, registry rules are designed around a registrant being able to move between registrars. In practice, that process is much easier when the business knows which account and contact details are attached to the domain.
A web designer managing the domain for you is not automatically a problem. The risk is having no documented route to take control later.
2. Domain control and DNS control are not always the same thing
The domain may be registered with one company while DNS is managed somewhere else, such as a hosting provider or CDN.
That matters because DNS can control:
- where the website points;
- where business email is delivered;
- verification records;
- subdomains;
- some security and CDN settings.
If a business only knows the domain registrar login but has no idea where DNS is managed, a future migration can become unnecessarily stressful.
3. Hosting does not always need to be in your own account
There are two reasonable models.
Client-owned hosting: the hosting account is in the business’s name and the developer is given access.
Managed agency hosting: the supplier hosts several client websites under an agency account and bills the business for hosting and support.
Either model can work. The questions are:
- Can the site be exported?
- Are backups available?
- What notice is required to leave?
- Are there migration charges?
- What happens if the supplier stops trading?
If you are changing providers, our website maintenance takeover checklist covers the operational side of moving responsibility safely.
4. WordPress administrator access is different from editor access
A WordPress user can have different roles. An editor can manage content but may not be able to install plugins, manage users or control wider site settings.
For a business that expects to appoint another developer later, it is sensible to know whether the company has appropriate administrator access and whether there is more than one safe route into the site.
Do not share one permanent administrator password between several people. Use individual accounts, strong passwords and appropriate access levels.
5. A WordPress login is not the same as having the website
If the site is business-critical, make sure a complete backup can be produced.
A recoverable WordPress site generally depends on both:
- the website files;
- the database.
Media files, plugin settings, users, orders, form data and content may be split across those components. A backup is only useful if it can actually be restored.
This becomes especially important before a major migration. The website migration SEO checklist covers what should be protected when URLs, platforms or hosting change.
6. Paying a freelancer does not automatically answer the copyright question
This is where practical control and legal ownership diverge.
UK Intellectual Property Office guidance explains that the creator of commissioned copyright work is generally the first copyright owner unless ownership is agreed otherwise. That means paying for a design, piece of copy or photograph does not by itself answer every rights question.
A sensible contract should therefore state what happens to:
- original website design work;
- custom illustrations;
- copywriting;
- photography;
- bespoke code;
- brand assets;
- source files.
Some suppliers transfer relevant rights after final payment. Others provide a licence to use the work. Either model can be legitimate when it is clear and agreed in advance.
7. Content you supplied is easier to understand
If your business wrote the copy and supplied photographs it already owns, the ownership position is usually clearer.
But be careful when assets come from:
- freelance photographers;
- copywriters;
- stock libraries;
- AI image services;
- manufacturers;
- third-party catalogues;
- design marketplaces.
Those assets may be governed by licences rather than outright ownership. Keep records of where important commercial assets came from.
8. WordPress itself is open-source, but not every website cost disappears with it
WordPress is distributed under the GPL. That does not mean every service, premium plugin, font, image, hosted tool or external integration used on a WordPress site becomes your property.
A website can include:
- open-source WordPress software;
- premium plugin subscriptions;
- agency licences;
- third-party fonts;
- stock photography;
- external SaaS tools;
- paid APIs.
Ask for a simple licence list at handover so you know what renews, when it renews and what happens if it is not renewed.
9. Agency licences are not automatically a red flag
Many web agencies use developer or agency licences for tools they use across client sites.
That can reduce the client’s immediate cost. The important question is what happens when the service relationship ends.
For each important licence, ask:
- Will the feature continue working?
- Will updates stop?
- Can I buy my own licence?
- Will any content or functionality become inaccessible?
A transparent supplier should be able to answer without drama.
10. Website builders change what “ownership” means
A WordPress website that can be exported is not the same as a hosted website-builder account.
Platforms such as Wix and Shopify provide hosted systems under their own platform terms. You may own your business content and data while using software you do not own and cannot simply copy onto another server.
That does not make those platforms bad. It means portability is part of the buying decision.
Our guide to WordPress vs Wix for a small business explains the broader trade-offs between a hosted builder and a more portable WordPress setup.
11. Analytics should belong to the business relationship, not one person’s inbox
Historic analytics can be valuable because it shows which pages attracted traffic, which campaigns worked and how user behaviour changed over time.
Make sure the business has appropriate access to:
- Google Analytics;
- Google Search Console;
- tag management where used;
- advertising conversion accounts;
- call tracking where used.
A supplier can be added as a user. The company should not have to rebuild its measurement history merely because an agency relationship ends.
12. The same principle applies to forms, email and customer data
Find out where website enquiries actually go.
A form may send through:
- your hosting mail system;
- SMTP;
- a transactional email provider;
- a CRM;
- an automation platform;
- the website database.
Businesses often discover hidden dependency only after a supplier’s account is cancelled and form notifications stop arriving.
Document the important services and make sure the organisation knows which accounts keep customer journeys working.
13. Payment gateways and ecommerce accounts need special care
For ecommerce, the website itself is only part of the operational stack.
Stripe, PayPal, shipping providers, tax tools, stock systems and marketplaces may all have separate accounts.
Those accounts should be tied to the appropriate business entity and business-controlled contact details. A developer may need technical access, but the commercial relationship should not depend on a developer’s personal payment account.
14. Ask what happens to the website if you stop paying monthly
This question matters particularly with website-as-a-service, rental or bundled subscription models.
Ask directly:
- Does the website remain online?
- Can I export it?
- Do I receive a copy of the files and data?
- Can another supplier take over?
- Are there transfer or buyout fees?
- Does the domain stay with my business?
A monthly website can be a sensible way to spread cost. What matters is understanding whether you are paying for maintenance, hosting, a licence to use the site, finance on the build, or a mixture of all four.
15. Put ownership and handover into the quote before the project starts
The easiest time to resolve website ownership is before anyone builds anything.
When reviewing a supplier proposal, ask for ownership and handover to be stated alongside scope, price and support.
Our new web design quote checklist gives you the wider set of questions to compare before signing a project.
A practical website handover pack
At the end of a project, a small business should be able to assemble a simple record like this:
| Item | Record |
|---|---|
| Domain | Registrar, account owner, renewal date, authorised contact |
| DNS | Provider and account access route |
| Hosting | Provider, package, renewal, support contact |
| Website | CMS URL, administrator accounts, backup location |
| Licences | Plugin/theme/tool, owner, expiry or renewal |
| Analytics | Analytics, Search Console and tag-management access |
| Email/forms | Sending provider, destination, form storage |
| Integrations | CRM, booking, payment, newsletter and API accounts |
| Creative assets | Logo files, images, copy, design/source files and rights notes |
You do not need to print passwords into a spreadsheet. Use a password manager and document where access is held.
The “supplier disappeared tomorrow” test
Use this once a year.
- Can someone in the business access the domain?
- Can someone identify where DNS is managed?
- Can the website be backed up?
- Does the business have appropriate CMS access?
- Can analytics and Search Console be accessed?
- Do you know which software licences are agency-owned?
- Do you know where enquiries and customer data go?
- Could another competent supplier take over without rebuilding everything?
If the answer to several questions is no, fix the documentation while the current relationship is healthy.
What if your designer currently controls everything?
Do not assume the worst. Many arrangements begin informally because it was convenient when the site was first created.
Start by asking for a calm written inventory:
- domain registrar and registrant details;
- DNS provider;
- hosting arrangement;
- CMS access;
- backup/export options;
- analytics access;
- licence list;
- handover process.
Once you know the facts, you can decide what genuinely needs transferring and what can sensibly remain managed by the supplier.
What should you own, and what only needs to be portable?
The goal is not necessarily to force every service into a company-owned account.
A practical setup normally prioritises:
- business control of the domain;
- documented access to critical systems;
- recoverable website data;
- clear rights to business-critical creative work;
- portable analytics and customer data;
- a known exit process.
A supplier can still manage hosting, licences and maintenance on your behalf. Good management reduces work for the business. Dependency becomes a problem only when the company cannot leave without losing important assets or starting again.
What to ask before choosing a web designer
Before appointing anyone, ask one simple question:
“If we stop working together in two years, what exactly can I take with me, and what would I need to replace?”
The answer often tells you more about the supplier relationship than a long sales presentation.
If you are comparing providers, our web design service explains how Core Web UK approaches business websites, while this ownership checklist can be used with any agency or freelancer.
Website ownership FAQs
Do I automatically own a website because I paid for it?
Not necessarily. Payment, copyright ownership, account control and software licensing are separate issues. The contract should explain what rights transfer and what remains licensed or supplier-managed.
Should my domain name be in my company’s account?
For most businesses, direct control of the domain is the cleanest arrangement. If a supplier manages it, make sure the registrant, renewal and transfer process are documented.
Is it bad if my web designer hosts my website?
No. Managed hosting can be convenient. The important questions are whether backups are available, the site can be moved and the exit process is clear.
Do I need my own premium plugin licences?
Not always. Agencies commonly use multi-site licences. You should know which features depend on those licences and what happens to updates or support if you leave.
Can I move a WordPress website to another host?
Usually, yes, provided you have the necessary files, database and access. Custom integrations, proprietary plugins or contractual restrictions can make a migration more involved.
