What happens if your web designer disappears?

People become unreachable for ordinary reasons: illness, a change of career, a business closing, an inbox nobody checks any more. Most freelancers and small agencies do good work. The difficulty arises when the business depended on one person for access it never held itself, and nobody wrote down what that person held.

Before you start, try every route to the original provider: email, phone, any company address, and mutual contacts. A short, polite request for the domain, the files and a list of accounts is often all it takes. If that fails, work through the steps below in order.

Step 1. Find out who controls the domain

Look up your domain. For .uk domains, Nominet's WHOIS lookup shows the registrar; for most other endings, ICANN's lookup service does the same. Personal details are often hidden, but you will usually see the registrar, the nameservers and the expiry date.

Note the expiry date first. If it is close, renewing it is the most urgent job in this list.

Step 2. Get into the registrar account

If the domain is in an account you set up, sign in, check the recovery details belong to the business, and turn on multi-factor authentication.

If you cannot sign in, contact the registrar's support team and use its account recovery process. Have proof of your business identity ready. If the domain was registered in the provider's own account or name, recovery is harder and may need their cooperation; ask the registrar what it requires in that situation before assuming the worst.

Step 3. Find out where the DNS is hosted

The nameservers from step 1 tell you which company hosts your DNS. It may be the registrar, the hosting company or a service such as Cloudflare. Find out whose account it is in.

Then take a full copy of every DNS record, using a DNS lookup tool if you cannot reach the account. This copy matters more than anything else in this guide. Your email depends on records such as MX, SPF, DKIM and DMARC, and they are easy to lose when DNS is moved.

Do not change the nameservers until you have that copy and a new DNS provider holds every record. If the domain uses DNSSEC, the DS record at the registrar has to be removed, and its time to live allowed to pass, before the nameservers change. Doing it in the wrong order can make the domain stop resolving.

Step 4. Identify the hosting or platform

The DNS records show where the website is served from. Lookup tools that show a site's technology can usually tell you the platform, for example a website builder, WordPress or a static host. Check your bank statements for hosting charges, which often name the company.

If the hosting is in the provider's account and still paid, the site may keep running for some time. If it is in your account but you cannot sign in, use that company's recovery process as in step 2.

Step 5. Find the site files or backups

Look for anything the provider sent you at launch: a zip file, a link to a code repository, a backup, a handover document. Check old emails and shared folders. If the site runs on a platform you can sign in to, look for an export option.

If there is nothing, the live website itself is the last resort. The text and images can be collected from it, and a simple site can be rebuilt from them. That is more work than a handover, but it is rarely a dead end.

Step 6. Recover analytics and search properties

For Google Search Console, once you control the DNS you can verify ownership yourself by adding a DNS record, then remove owners who should no longer be there. For Google Business Profile, Google has a process to request ownership of a profile someone else manages.

Google Analytics is harder. If nobody with administrator access can be reached, you may need to set up a new property and accept the loss of past data. Do that sooner rather than later, so new data starts collecting.

Step 7. List the third-party services

Work out what else the website depends on: the contact form and where enquiries go, booking or ordering systems, payment providers, maps, chat tools, email sending services. For each, find whose account it is. A contact form quietly sending enquiries to a former provider's inbox is more common than it sounds; test yours.

Step 8. Reset and revoke access

Once the business can sign in to each account, remove the old provider's access: their user accounts, any shared passwords they knew, API keys and access tokens. Check the recovery email and phone on every account. Do this after you have secured access, not before, so you do not lock yourself out.

Step 9. Write down what you now hold

Record every account, who has access, the recovery details and the renewal dates, and keep the DNS copy with it. This record is what stops the same thing happening again. Our website access checklist gives a structure for it.

Step 10. Decide who is responsible from now on

Whatever you choose, make the arrangement explicit. If you look after the site yourself, decide who in the business owns each task. If you appoint a new provider, agree in writing what they hold, in whose name, what they are responsible for, and what you receive if you part ways. Our guide to who owns your business website lists what that agreement should cover, and our comparison of freelancers, agencies and managed services can help you choose.

• Moving the nameservers before copying the DNS records. This is the most common way to break business email during a recovery.
• Letting the domain expire while waiting for the old provider to reply.
• Rebuilding first and sorting access later. A new website you cannot point the domain at helps nobody.
• Sharing one new password with the next provider instead of giving them their own account with only the access they need.

The fix is the same whoever builds your next website: keep the domain in the business's own registrar account, keep a current copy of the DNS records, hold a copy of the site files, make sure a business account owns analytics and Search Console, and keep a short written record of who has access to what. None of this needs technical skill, and it turns a crisis into an inconvenience.

Will my website go offline if my web designer disappears?
Not necessarily. If the hosting is paid and nothing breaks, it can keep running for months. The risk is what happens at the next renewal, the next problem or the next change you need, when nobody with access can act.

Can I get my domain back if it is registered in their name?
Often, but it takes longer. Start with the registrar's support team and ask what evidence it needs. Keep records showing the domain has been used by your business, such as invoices and correspondence.

Do I need to rebuild the website?
Not always. If you can recover the files or the hosting account, the existing site can usually be moved. If you cannot, a simple site can be rebuilt from the content on the live pages.

• Who actually owns your business website?
• What website access should a business owner keep?
• How to move your website to a new provider

All resources