It happens more than you would think. The freelancer who built your site years ago stops answering emails. The small agency closes. The friend-of-a-friend who “does websites” moves abroad. Everything works until it does not, and then you discover you have no idea where the website lives, who controls your domain or how to change a single word.
If your web designer has disappeared, this guide walks through what to do, in order of urgency. Most situations can be recovered, but the sooner you start, the more options you have. It also covers how to take over a website from an old developer in a calmer situation, when they are still around but you want to move on.
First, work out what is at risk
| Account | What it controls | Risk if you cannot access it | Urgency |
|---|---|---|---|
| Domain registrar | Your web address and where it points, including email | Domain expires or cannot be moved; website and email stop | Highest |
| DNS settings | Where website and email traffic go | Cannot move the site or fix email | High |
| Hosting | The server the website lives on | Site goes offline if unpaid; cannot get files | High |
| Email service | Your business mailboxes | Lost messages, locked out of other accounts | High |
| Website admin login | Editing content | Cannot make changes | Medium |
| Google Search Console, analytics, Business Profile | Search data and listings | Lose history and control of listings | Medium |
Step 1: secure the domain
Your domain is the most valuable piece, because it carries your website address, your email and every link to you. Start by finding out who it is registered with. For .com and other generic domains, use the ICANN registration data lookup. For .uk and .co.uk, use the WHOIS lookup on Nominet’s website. The results show the registrar, the expiry date and sometimes the registrant, although personal details are often hidden.
Check the expiry date immediately. If it is close, that is your first priority. Contact the registrar, explain the situation and ask how to prove you are the rightful registrant. If the domain was registered in your name or your company’s name, the registrar has processes to help you recover access, usually involving identity documents or company records. If it was registered in the designer’s own name, recovery is harder but often still possible; for .uk domains, Nominet has processes for registrant disputes and transfers.
Step 2: find the hosting and get a copy of the site
Next, find where the website is hosted. A web developer can usually tell from the site’s DNS records and server responses within minutes. Once you know the host, contact them with proof of ownership of the business and domain. Many hosts will help the site owner regain access to an account, especially if you can show invoices or that the site is yours.
If you cannot get into the hosting, do not panic. A great deal can be rescued from the live site: text, images and structure can be copied, and the Internet Archive’s Wayback Machine may hold older versions. That is enough for a new developer to rebuild quickly, even if the original files are lost.
Step 3: protect your email
Business email often depends on the same domain and DNS settings as the website. If the designer set it up, the mailboxes might be on the same hosting account. Before anything moves, find out where your email is hosted and make sure you have admin access. A careless move can cut off email for days, which for many businesses is worse than the website going down.
Step 4: reset access and move to accounts you control
- Put the domain in your business’s name, with an email address you control, and turn on two-step verification and registrar lock.
- Change every password: registrar, hosting, website admin, email, Search Console and analytics.
- Remove the old developer’s admin accounts once you have your own.
- Add yourself as owner of Google Search Console and analytics properties, and of your Google Business Profile if the designer managed it.
- Take a full backup of the site and store it somewhere you control.
- Write down, in one place, which company holds each account and how to log in.
Step 5: decide whether to keep, move or rebuild
Once you have control, look at the site honestly. If it is on a current platform, works well and you simply need someone new to look after it, a new developer can take it over. If it is old, insecure, hard to edit or built in a way only the original developer understood, a rebuild may be cheaper than patching it.
Whichever you choose, protect what works. Keep the same domain, keep or redirect existing page addresses so you do not lose Google rankings, and keep any content that brings in visitors.
Taking over from an old developer who is still around
If your developer is reachable but you want to move on, the process is calmer but similar. Ask them, in writing, for the items below. Check your original contract for what you own. Many agreements say the client owns the content and domain, but some licence the design or keep the code. Being polite and specific usually gets the best result, and most developers would rather hand over cleanly than be chased.
- Transfer of the domain into your name, or the authorisation code to move it to a registrar of your choice.
- Admin access to the hosting, or a full copy of the site files and database.
- Admin access to the website, Search Console, analytics and any connected services.
- A list of plug-ins, licences and third-party services the site depends on, and who pays for them.
- Any design files, logos and photos they hold for you.
How to stop it happening again
At Nerdsharks, the domain stays registered in the client’s name and anyone who leaves gets their content, photos and enquiry records, because a website you cannot take with you is a risk to your business. If you are dealing with a vanished designer right now and need help recovering the site, the steps above are where we would start too.
- Register your domain in your own business name, with your own email, whoever manages it.
- Keep a written record of every account related to your website, stored securely.
- Make sure you always have your own admin access, even if someone else does the work.
- Get the ownership terms in writing: who owns the domain, content, design and code, and what happens if you leave.
- Prefer providers who document how to leave, not just how to join.
- Keep your own copy of content and photos.