Website ownership is one of those things most UK business owners assume they have until the day they need it. The domain was registered by a freelancer in 2017, the hosting sits on an agency reseller account, Google Analytics lives under someone’s personal Gmail and the only person who knows the DNS login left the company two years ago. Everything works — right up until a renewal email bounces, a supplier relationship sours or you want to move to a new developer and discover that you do not actually control any of the pieces your website is built from.
This guide is a practical how-to for taking back control. You will learn what “owning” a website really means under UK law and in practice, which accounts and assets need to be in your organisation’s name, how to run a clean website handover from an agency or developer, what it typically costs, and the mistakes that leave businesses locked out of their own domain name. It is written for owners, operations leads and finance directors at UK SMEs — no developer background required.
What does website ownership actually mean?
A business website is not one thing. It is a stack of separate assets, each with its own account, its own login and, crucially, its own legal owner. At minimum there is the domain name (registered with a registrar such as Nominet-accredited resellers for .co.uk, or ICANN-accredited registrars for .com), the DNS that points that domain at services, the hosting account where the site runs, the code and design itself, the content (copy, photography, video), the data collected through forms and checkouts, and a ring of third-party accounts — Google Analytics, Search Console, Google Business Profile, Google Ads, Meta Business Suite, email delivery services, payment gateways, cookie consent platforms and so on.
Owning your website means three things for every one of those assets. First, legal title: the contract, registration record or licence names your company as owner or licensee. Second, administrative control: someone employed by your business holds the top-level admin login, protected with multi-factor authentication, and can add or remove other users — including your suppliers. Third, portability: you can export or move the asset to a different provider without asking permission or paying a ransom-style “release fee”.
The legal side matters more than most people expect. Under the Copyright, Designs and Patents Act 1988, copyright in work created by an employee in the course of employment belongs to the employer, but copyright in commissioned work — a site built by an external agency or freelancer — stays with the person who created it unless it is assigned to you in writing, signed by the assignor. Paying the invoice does not, on its own, transfer copyright. In many cases a court would imply a licence to use what you paid for, but an implied licence is a thin foundation if you later want to move the site, modify it substantially or sell the business. If you are weighing up who should build your next site, our guide on choosing a web development company in the UK covers the contract questions to ask up front.
Run a simple test today: without contacting any supplier, can someone on your payroll log in to the domain registrar, the DNS provider, the hosting control panel and Google Analytics as an administrator? If the answer to any of those is “no” or “not sure”, you have an ownership gap — and the time to close it is while relationships are good, not during a dispute.
Website ownership risk scoring — where most UK SMEs sit
Before you start fixing anything, it helps to know which gaps are genuinely dangerous and which are merely untidy. We group website assets into three risk tiers. The high badge means losing control could take your website and email offline or make it impossible to move supplier. Mid means painful and expensive to rebuild, but survivable. Low means an inconvenience you should still tidy up.
The pattern we see most often in small and mid-sized organisations is that the expensive, visible part — the design and build — got careful attention during procurement, while the cheap, invisible parts — a £12-a-year domain, a free DNS account, a Search Console verification — were set up by whoever happened to be at the keyboard. Those cheap parts are exactly what an outgoing supplier can hold on to.
Notice that most of the high-risk rows are infrastructure, not design. A dated design can be replaced in weeks; a domain registered to someone else can take months to recover and, in a hostile dispute, may require Nominet’s Dispute Resolution Service or legal action. That is why the how-to that follows starts with the domain and works outwards.
Website ownership by the numbers — the rules that set the clock
A handful of fixed rules shape how quickly you can move each asset. None of them are negotiable with a supplier, so it pays to know them before you plan a handover.
.com after registration or a registrar transfer.uk or .co.uk domain with NominetThe 60-day lock catches people out more than any other rule. If a supplier transferred your .com to their preferred registrar last month, you generally cannot move it again until the lock expires — but you can ask the current registrar to update the registrant details to your company immediately, which is the step that actually matters. For .uk domains the mechanism is different: there is no auth-code transfer, instead the current registrar changes the domain’s IPS tag to point at your chosen registrar, and a separate registrant transfer changes the legal owner recorded by Nominet.
The UK GDPR point is easy to overlook because it feels unrelated to “the website”. Yet if your contact forms, quote requests or online orders are stored in a database your agency hosts, that agency is acting as a data processor on your behalf. You, as controller, need a written contract covering what they do with the data, security measures, sub-processors and — directly relevant here — what happens to the data when the contract ends. The ICO’s guidance on controllers and processors is the reference point.
Agency-held accounts vs business-held accounts
There are two broad models for running a website with outside help. In the first, the agency or developer sets up and holds every account, bills you a single monthly fee and gives you access on request. In the second, your business holds every account at the top level and grants the supplier delegated access — a named user, an API key, a role in Google Analytics — that can be revoked in minutes. Both can work day to day. Only one of them makes it easy to change supplier.
Agency-held
Supplier owns the accounts, you get access on request
Business-held
You own every account, supplier gets delegated access
The business-held model is not about distrust. Good agencies actively prefer it, because it removes them from awkward conversations about renewals and payment cards, and it makes their own offboarding simple. Where an agency resists putting accounts in your name, ask why. There are occasionally legitimate reasons — a managed hosting platform where the agency carries the server contract, for example — but in those cases the contract should still guarantee a full export of files and database, and the domain and DNS should still be yours.
A useful middle ground for very small businesses is a shared role mailbox such as web-admin@yourcompany.co.uk, owned by your Microsoft 365 or Google Workspace tenant, used as the login for registrar, hosting and analytics accounts. When a staff member leaves, the mailbox stays. When a supplier changes, you remove their delegated access without touching the root account. This mirrors the joiner–mover–leaver discipline we describe in our guide to new-starter IT onboarding.
Which lost assets hurt most — relative impact scores
Not every asset is equally painful to lose. The chart below shows Cloudswitched’s relative impact scoring for each asset, out of 100, combining how long recovery typically takes, how much of the business stops while it is missing, and whether a supplier can legitimately refuse to hand it over. These are our working weights for prioritising a handover, not survey results — but they reflect a consistent pattern in recovery projects.
The domain and DNS sit at the top because they underpin far more than the website. Your email, Microsoft 365 or Google Workspace verification, SPF, DKIM and DMARC records, any VoIP or SIP services, and often your remote-access endpoints all depend on DNS records under that domain. Losing control of DNS is effectively losing control of your company’s identity on the internet. If you rely on fixed endpoints, our explainer on static IP addresses for business broadband shows how many services quietly hang off DNS records.
Analytics history sits mid-table because it is irreplaceable rather than operationally critical. If a former employee owns the Google Analytics account and refuses or simply never responds, you can create a new property tomorrow — but years of trend data for SEO and advertising decisions are gone. Likewise, a Google Ads account held under an agency’s manager account can usually be unlinked, but if the agency owns the account itself you may lose conversion history and the learning that bidding strategies rely on. Ownership of advertising accounts also matters for consent configuration; see our guide to Google Ads Consent Mode v2 and enhanced conversions.
How much of a handover is accounts rather than code?
People picture a website handover as “getting the code”. In practice, the code is a small part of the job. Our standard handover checklist has 24 line items. Seventeen of them are account ownership, access or billing changes; only seven concern files, code, licences or documentation.
That ratio has a practical consequence. The person running the handover on your side does not need to be a developer. They need to be organised, have authority to sign contracts and change payment details, and have access to the company’s role mailbox and authenticator app. A developer or IT partner is useful for verifying that what you have received actually works — that the database export restores, that the repository builds — but the bulk of the hours are administrative.
It also explains why handovers stall. Each account has a slightly different transfer mechanism: an IPS tag change here, a primary-owner role there, a billing profile change in a third place, a two-step verification prompt sent to a phone number nobody recognises. A checklist with a named owner and a due date for each line is what gets it finished.
How to take back control: a six-week website handover plan
The sequence below works whether you are moving to a new agency, bringing the site in-house or simply tidying up with your current supplier. The order matters: you secure the assets that underpin everything else before you touch anything that could break the live site.
web-admin@) in your own Microsoft 365 or Google Workspace tenant. List every asset: domains, DNS, hosting, CMS, repositories, analytics, ads, social, email-sending services, payment gateways, plugins and licences. Run a WHOIS or Nominet lookup on each domain and note the registrar and expiry date..com, IPS tag change for .uk). Turn on registrar lock and auto-renew.Six weeks is a comfortable pace for a cooperative supplier and a typical SME site. A single-domain brochure site with a helpful agency can be done in a fortnight. A multi-domain e-commerce estate, or a supplier who is slow to respond, can stretch to three months — mostly spent waiting on transfer locks and email replies. The live website should not go offline at any point; if a step risks downtime, schedule it out of hours and keep the old provider running until the new one is verified.
Website ownership readiness — scoring your own position
To decide how urgent your handover is, score yourself against the weighted controls in the progress section further down this guide. Each control carries a weight; add up the weights for every control you can evidence today — not “I think the agency did that”, but a login you have tested or a document you can find. A score under 50 means at least one high-risk asset is outside your control. Between 50 and 80 you are in reasonable shape with gaps to close. Above 80 you could change supplier in a few days.
The worked example above is typical of a business whose site was built well, by a competent agency, several years ago. The website itself was fine. What dragged the score down was that the domain registrant, the registrar login and the DNS account all sat with the agency, the Google Ads account ran under the agency’s billing, and there was neither a copyright assignment nor an asset register. Those six gaps carry 62 of the 100 points. None of that was malicious; it was simply the default when the site was commissioned. The point of scoring is to turn a vague worry into a short, prioritised list.
Repeat the score once a year, ideally alongside your wider IT and SaaS review. Website accounts are a classic source of forgotten subscriptions and orphaned logins — exactly the sprawl covered in our SaaS spend audit guide.
What a website handover costs in the UK
The direct costs of taking ownership are modest compared with the cost of a rebuild forced by a lost domain or an unrecoverable site. Typical ranges, excluding VAT, are below. Your actual figures depend on the number of domains, how the site is built and how cooperative the outgoing supplier is.
| Item | Typical UK cost | Notes |
|---|---|---|
| Domain transfer and renewal | £5–£20 per domain per year | .com transfers usually include a year’s renewal; .uk IPS tag changes are normally free |
| Business-controlled DNS | £0–£20 per month | Many registrars and CDN providers include DNS; premium DNS adds features rather than ownership |
| Independent handover verification | £400–£1,500 one-off | A developer restores the backup to staging, checks the repository builds and audits plugins |
| Hosting migration (if moving) | £300–£2,500 one-off | Brochure sites at the low end; WooCommerce, Magento or custom apps at the high end |
| Legal review and IP assignment | £300–£1,200 one-off | Solicitor review of the original contract and a short deed of assignment |
Watch for exit or “release” fees. Some contracts include a reasonable charge for the agency’s time preparing exports and documentation, and that is fair — handovers take real hours. What is not reasonable is a fee that only exists to make leaving expensive, or a refusal to release a domain until an unrelated invoice is paid. If you are in that position, take advice before escalating; for .uk domains, Nominet’s Dispute Resolution Service exists for exactly these cases, and for generic domains ICANN’s UDRP is the equivalent route.
It is also worth separating the handover cost from the ongoing run cost. Once accounts are in your name, you will see itemised bills for hosting, domains, licences and add-ons that were previously bundled. That transparency is useful: it is often the first time a business can see what its website actually costs to run, and it feeds directly into the wider true cost of a business website calculation.
Website ownership controls benchmark — the weighting behind the score
These are the controls behind the readiness score, with their weights. The weights add up to 100. They reflect the relative impact scoring earlier in the guide: infrastructure first, data protection second, marketing history third.
Cloudswitched website ownership controls (weight out of 100)
A few notes on evidence. “Domain registrant is your company” means the registry record names your limited company exactly as it appears at Companies House — not a director personally, not a trading name, and not the agency. For .uk domains you can check this through Nominet’s WHOIS (some details are redacted for privacy, but the registrar and status are visible) or by asking your registrar for the registrant record. “Tested backup” means someone has actually restored it somewhere in the last 12 months. And “processor contract” means a signed agreement that meets UK GDPR Article 28, not a line in an email.
The asset register carries the lowest weight but makes everything else sustainable. A simple spreadsheet listing each asset, provider, account owner, login mailbox, renewal date, cost and the supplier with delegated access is enough. Store it somewhere with access control, and never put passwords in it — those belong in a business password manager.
Common website ownership mistakes to avoid
Most ownership problems come from small decisions made quickly at the start of a project. These are the ones we see repeatedly.
- Registering the domain in a director’s personal name. It feels harmless when the company is one person, but it creates problems on sale, on a director’s departure and in probate. Use the limited company as registrant.
- Using a personal Gmail or Hotmail as the registrar login. If the person leaves or loses access to that inbox, renewal notices and transfer approvals go nowhere. Use a role mailbox in your own tenant.
- Letting the agency “just handle” DNS. DNS controls your email and Microsoft 365 as well as the website. If it sits in the agency’s account, a dispute over web work can disrupt your email.
- Assuming payment means ownership. Under the 1988 Act, copyright in commissioned work stays with its author unless assigned in writing. Ask for the assignment at contract stage, when it costs nothing.
- Removing the old owner before adding the new one. In Google Analytics, Search Console and Business Profile, always add your business owner first, confirm it works, then remove the old account.
- Letting the domain auto-renew on a card that is about to expire. Expired domains enter grace and redemption periods; recovery fees can be substantial and, after that, the name can be released for anyone to register.
- Accepting a backup you have never restored. A zip file is not a handover. Until a developer has rebuilt the site from it on a staging server, you do not know whether it is complete.
- Forgetting the data. Enquiry forms, newsletter lists and order histories are personal data under UK GDPR. Agree how the outgoing supplier returns and deletes them.
Never share a single admin password with a supplier by email or chat. Give them their own named user account with only the permissions they need, so you can revoke it cleanly when the work ends. Shared passwords are also a Cyber Essentials concern: the scheme expects user accounts to be individual and admin rights to be controlled.
Website handover checklist — the 12-point essentials
Use this as the minimum standard for any website handover, whether you are leaving an agency, onboarding a new one or auditing what you already have. Each item should end with evidence you can file: a screenshot, a signed document or a tested login.
- Asset inventory — every domain, subdomain, hosting account, CMS, repository, plugin licence and third-party service listed in one register with owner and renewal date.
- Domain registrant — registry record shows your limited company’s exact Companies House name; contact email is a business role mailbox.
- Registrar account — held by your business, protected by MFA, with registrar lock and auto-renew on and a valid company card on file.
- DNS zone — full zone exported, hosted on an account you control, with email authentication records (SPF, DKIM, DMARC) verified after any change.
- Hosting — contract in your name, or a written right to a full export of files and database on request within a defined number of days.
- Backup — complete files and database copy stored outside the hosting provider and successfully restored to staging by someone other than the outgoing supplier.
- Source code — for custom builds, the Git repository with full history transferred to an organisation account you own, plus build and deployment notes.
- Licences — premium themes, plugins, fonts and stock images either re-registered to your business or replaced; licence keys recorded in your password manager.
- Analytics and search — your business is Administrator on Google Analytics, verified Owner in Search Console and Bing Webmaster Tools, and Primary Owner of Google Business Profile.
- Advertising and social — Google Ads, Meta Business Suite and LinkedIn pages owned by your business; agencies linked through manager or partner access, not ownership.
- Data and processor terms — UK GDPR Article 28 contract in place for any supplier handling site data; return and deletion confirmed in writing at exit.
- Intellectual property — signed assignment of copyright in the design, code and content you commissioned, or a clearly documented perpetual licence where the supplier reuses its own framework.
Item 12 does not mean an agency must hand over its entire in-house framework. Many developers build on reusable components they also use for other clients. A fair arrangement assigns you the bespoke work and grants a perpetual, transferable licence to the reusable parts — enough that you, or any future developer, can maintain and modify the site freely.
If your site is being rebuilt as part of the handover, add two extra checks: a redirect map from every old URL to its new equivalent, and a post-launch review of Search Console coverage. Ownership changes and redesigns often happen together, and lost redirects are the most common way a handover quietly damages search visibility — see our guide to website migration without breaking links.
Real-world example: a 45-person firm takes back its website
A Leeds-based professional-services firm with around 45 staff had used the same small agency for seven years. The site was well designed and reliable, and the relationship was friendly. The trigger for change was ordinary: the agency’s founder was retiring and the business was being wound down, with clients given three months’ notice.
When the firm’s operations manager started listing assets, the readiness score came out at 38 out of 100. The domain, registered in 2016, named the agency as registrant. DNS ran inside the agency’s registrar account, which also held the firm’s Microsoft 365 verification and email records. The Google Ads account sat under the agency’s billing. There was no copyright assignment, and no asset register. On the positive side, the hosting contract included an export clause, the agency took monthly off-site backups, there was a data processing agreement covering enquiry forms, and the firm’s marketing lead had set up Google Analytics on a company mailbox from the start.
The firm followed the six-week plan almost exactly. Week one created a web-admin@ mailbox and a register. Week two updated the .co.uk registrant to the limited company and changed the IPS tag to a registrar the firm controlled; the agency completed both on the same day once asked. DNS moved in week three, after the full zone was exported and email records were double-checked with the firm’s IT support provider. Google Ads was moved to a company billing profile with the new agency linked through its manager account. The backup was restored to a staging server by an independent developer, who found two premium plugins licensed to the agency; the firm bought its own licences for under £150 a year. A solicitor drafted a two-page assignment, which the retiring founder signed in week six.
“The website was never the problem. The problem was that every account it depended on had someone else’s name on it. Once we listed everything on one page, it was a month of admin rather than a crisis — and the next time we change supplier it will take a day.” — Operations manager, Leeds professional-services firm
Total direct cost came to a little over £1,800 including legal fees and independent verification. The firm’s score after the project was 100. The more important outcome was the asset register: renewal dates now sit in the finance calendar, and new suppliers receive delegated access from day one rather than ownership.
Website ownership at a glance
| Question | Short answer |
|---|---|
| Who should be the domain registrant? | Your limited company, exactly as named at Companies House |
| Who should hold the registrar login? | A business role mailbox in your own tenant, with MFA |
| Where should DNS live? | An account your business controls — it carries your email too |
| Does paying for a site give you copyright? | Not automatically; commissioned work needs a written assignment |
How do .uk domains move registrar? | IPS tag change by the current registrar, not an auth code |
How do .com domains move registrar? | Auth (EPP) code, subject to a 60-day lock after recent changes |
| What counts as a real backup? | Files and database held off-host and restored successfully to staging |
| Should agencies own Google Analytics or Ads? | No — they should have delegated access to accounts you own |
| Is site form data covered by UK GDPR? | Yes; suppliers storing it need an Article 28 processor contract |
| Typical handover timescale | Two to six weeks for an SME site with a cooperative supplier |
| Typical direct cost | Roughly £700–£5,000 depending on migration and legal work |
| How often to review? | Annually, and whenever a supplier or key staff member changes |
How Cloudswitched helps with website ownership and handovers
Cloudswitched’s web development team builds and maintains business websites on the business-held model by default: domains, DNS, hosting and analytics sit in accounts our clients own, and we work through delegated access. We also run handover projects for businesses moving away from another supplier — inventory, domain and DNS moves, backup verification and documentation — working alongside your existing IT support so email and Microsoft 365 records are protected throughout.
Want to know who really owns your website?
We can audit your domains, DNS, hosting and accounts and give you a prioritised plan to bring them under your control.
Talk to us about Web DevelopmentFrequently Asked Questions
Who legally owns my business website in the UK?
It depends on each part. The domain belongs to whoever is recorded as registrant with the registry, which for .uk names is Nominet. Copyright in the design and code belongs to its author unless assigned: if staff built it in the course of employment, your company owns it; if an agency or freelancer built it, they own the copyright unless your contract or a separate document assigns it to you in writing. Content you wrote yourself is yours. Hosting is a service contract, so ownership there means having the contract or at least a right to export everything. Check each layer separately rather than assuming one answer covers the whole website.
How do I find out who owns my domain name?
Run a WHOIS lookup. For .uk domains, Nominet’s WHOIS shows the registrar, registration and expiry dates and status; registrant personal details are often redacted for privacy, but your registrar can confirm the registrant name on request. For .com and other generic domains, use an ICANN lookup service. If the registrar is not one your business has an account with, the domain is almost certainly being managed by a supplier, and you should ask them to confirm the registrant and give you access.
My web developer registered the domain in their name. What should I do?
Ask them, in writing, to change the registrant to your limited company and either transfer the domain to a registrar account you control or give you admin access to theirs. Most developers do this without fuss — they registered it for convenience, not as leverage. If they refuse, check your contract, keep records of your payments for the domain and take legal advice. For .uk domains Nominet runs a Dispute Resolution Service; for generic domains the UDRP process applies. Do not let the domain lapse in the hope of re-registering it yourself, as expired names can be picked up by others.
Does paying for a website mean I own the copyright?
Not automatically. Under the Copyright, Designs and Patents Act 1988, copyright in commissioned work stays with the creator unless it is assigned in a signed written document. Courts will often imply a licence allowing you to use what you paid for, but the scope of an implied licence can be narrow and uncertain — it may not clearly cover modification, transfer to a new developer or sale of the business. The simple fix is to include an assignment clause in your web development contract, or ask for a short deed of assignment at handover.
What should a website handover include?
At minimum: control of the domain registrant and registrar account, the DNS zone, hosting or a full export of files and database, source code with history for custom builds, theme and plugin licences, admin access to the CMS, ownership of Google Analytics, Search Console, Google Business Profile and advertising accounts, design source files, documentation of how the site is deployed, return or deletion of personal data, and a written copyright assignment or licence. Our 12-point checklist above is a good starting template for your website handover checklist.
How long does it take to transfer a website to a new provider?
For a typical SME brochure site with a cooperative outgoing supplier, two to four weeks is realistic, and a six-week plan gives comfortable margin. Domain transfers themselves are usually quick — a .uk IPS tag change can complete the same day, and .com transfers normally take up to five days — but transfer locks, slow email replies and verification of backups add time. E-commerce or multi-domain estates can take two to three months. The site should stay online throughout.
Can my agency keep my website if I stop paying them?
If invoices are genuinely unpaid, a supplier may be entitled to suspend services they provide, such as hosting, under the terms of your contract. They are on much weaker ground holding on to a domain registered for your business or data that belongs to your customers, which they process on your behalf under UK GDPR. Disputes are best avoided by keeping domains, DNS and key accounts in your own name from the start, so the commercial relationship and your online identity are never tied together.
Should my business or my agency own Google Analytics and Google Ads?
Your business. Create the Google Analytics account, Google Ads account and Business Profile using a business-owned Google account or role mailbox, then grant your agency access — for Ads, by linking the agency’s manager account. This keeps historical data and conversion learning with you if you change agency, and lets you revoke access instantly. Agencies that insist on owning these accounts make switching harder and are worth questioning.
What is an IPS tag and why does it matter?
An IPS tag identifies which Nominet-accredited registrar manages a .uk domain. To move a .uk domain to a new registrar, the current registrar changes the IPS tag to the new one’s tag — there is no authorisation code as there is for .com. Separately, the registrant (legal owner) can be changed through a registrant transfer. Knowing which registrar holds the tag tells you who to ask, and holding your own registrar account means you can move the domain without depending on a supplier.
Do I need a data processing agreement with my web developer?
If your developer or host stores or can access personal data collected through your website — enquiry forms, newsletter sign-ups, customer accounts or orders — then yes. UK GDPR Article 28 requires a written contract between a controller and any processor, covering the nature of the processing, security, use of sub-processors and the return or deletion of data at the end of the contract. Many agencies have a standard agreement; ask for it if you have not signed one.
Related reading
If you are tidying up website ownership, these guides cover the connected areas of IT, data and marketing accounts:
- SaaS Spend Audit for UK SMEs - A Virtual CIO’s 30-Day Method to Tame Software Sprawl
- New Starter IT Onboarding Checklist UK - Autopilot, Entra ID and a Ready Day One
- Static IP Addresses for Business Broadband: A UK Guide to Costs, IPv4 Scarcity and IPv6 Readiness in 2026
- Google Consent Mode v2 and Enhanced Conversions - A UK How-To Guide for Accurate Google Ads Tracking
- Data Quality for Business Reporting - A UK Guide to Fixing Bad Data Before It Reaches Your Dashboards
Build your next website on foundations you own
Cloudswitched designs, builds and maintains business websites with domains, hosting and analytics held in your name — and handles the handover if you are moving from another supplier.
Explore our Web Development service








