Who Holds the Keys? A Website Ownership Audit for UK Businesses
Photo: Custom Neon Images, CC BY 2.0, via Wikimedia Commons
Most conversations about website ownership start in the wrong place. They start with blame, or with a contract, or with a story about somebody's cousin who lost a domain in a divorce. That is not the useful angle. The useful angle is continuity: if the person who built your site moved on tomorrow, could you still change your opening hours, renew your domain, fix a broken form and keep the email flowing?
That is not paranoia. It is the same logic as keeping a spare key with a neighbour you trust. You are not expecting the front door to fail. You are just making sure a locked door is not the end of the story.
Here is the handover folder worth assembling, in plain English, for UK businesses that would rather not discover a gap at the worst possible moment.
The domain is the deed, not the door key
For a .co.uk domain, the important record is the registrant contact held by Nominet. For .com and others, it is the registrant record at the registrar. If that record shows your web designer's email address, you do not control the domain in any meaningful sense. You are renting your own front door.
Check who the registrant is, and check that the registrant email is one you control. Then check the registrar login. It should belong to the business, not to a personal account that leaves with someone's notice period. A simple WHOIS lookup will tell you more than most handover meetings.
Hosting, DNS and the things that point at things
Hosting is the server where the site lives. DNS is the address book that tells the internet where to find it. They are often bundled together, which is convenient until they are not.
You need to know who holds the hosting account, who holds the DNS control panel, and what the nameservers are set to. If your email runs through a separate provider, the MX records matter too. A website migration that quietly changes MX records can take down a perfectly healthy inbox, and nobody notices until a customer says they never got a reply.
Ask for the account holder name and the recovery email on both. If the answer is a personal Gmail address belonging to someone who no longer works with you, that is the finding.
Admin, not editor
There is a difference between being able to edit a page and being able to run the site. On most content management systems, you want at least two super administrator accounts, both tied to business email addresses you control. One for the day-to-day, one as a spare.
Editor accounts are fine for staff who write pages. They are not a handover plan. If the only admin account belongs to an agency, you are a guest on your own website.
Analytics, Search Console and the paper trail
Google Analytics, Search Console and Google Business Profile are not just reporting tools. They are records of how people find you. If the properties are owned by an agency account, you may lose historical data, verification and the ability to manage listings when the relationship ends.
You want ownership of the GA4 property, verified access to Search Console, and control of the Business Profile. Ask for an export as well. Data you can read in a spreadsheet is data you can keep.
Email is not a subplot
Website projects often absorb email by accident. The domain is registered, hosting is bought, and email gets set up along the way. That is fine until hosting changes and the mailboxes go with it.
Know where your email is hosted, who pays for it, and who can add or remove a mailbox. If it is part of a hosting package, check what happens to the mailboxes if the website moves. The answer should not be a shrug.
Backups you have actually met
A backup is not a file on a server with a reassuring name. A backup is something you have restored at least once, or watched someone restore, without drama.
Ask where backups are stored, how often they run, and how long they are kept. Then ask for a test restore of a single page or a small database table. If nobody can demonstrate that, you have a schedule, not a safety net.
Licences, fonts and the small print
Premium themes, plugins, stock images and web fonts often carry licences that belong to the person who bought them. Some transfer; some do not. A theme licence tied to an agency account can become a renewal problem later.
Keep a simple list: what was bought, where it came from, which account it sits under, and when it renews. It is dull. It is also the difference between a quiet renewal and a surprise invoice.
The one-page handover note
You do not need a 40-page technical manual. You need one page that a competent person could follow. It should list the domain registrar, hosting provider, DNS provider, CMS admin URL, analytics property, email provider, backup location and the name of the account holder for each.
Store the logins in a business password manager, not in a spreadsheet called 'website stuff'. Give access to at least two people inside the business. Then update the page when something changes. A handover folder that is three years out of date is just archaeology.
The leaving test
Here is the practical check. Can you, without contacting the person who built the site, do all of the following?
- Change the phone number in the header.
- Add a new page and publish it.
- Renew the domain name.
- Access last month's analytics.
- Add a mailbox for a new starter.
- Restore a page from a backup.
If you can do those six things, you own the website in the way that matters. If you cannot, you own the invoice history.
None of this is about expecting the worst from a designer or agency. Most handovers are perfectly civil. But continuity planning is not an accusation. It is just good housekeeping — the digital equivalent of knowing where the stopcock is before the pipe bursts.