Your web developer has disappeared: what to do next

Key takeaways

If your web developer stops responding, secure what you can control today: the domain, hosting, email and analytics. Find out who each is registered to, recover access through the provider if needed, and take a full backup. Then decide whether a new developer can take over the site or whether it is safer to rebuild.

• Find out who is the registrant of the domain first.
• Check who holds the hosting account and the renewal dates.
• Take a full backup as soon as you have access.
• Take over if the platform is standard; rebuild if it is not.

What should you do first?

Find out what you control. Look up the domain registrant, check which accounts renewals are billed to, and list every login you have: hosting, CMS, email, analytics, Search Console and Google Business Profile. The domain matters most, because losing it takes your email and search history with it.

• Signs your business needs a new website
• Who owns your website, domain and content?

How do you recover access?

Through the providers. Registrars and hosts have processes for account owners who can prove identity and payment.

• Domain: contact the registrar with proof the domain is used by your business.
• Hosting: if the account is in your name, reset the password.
• CMS: with hosting access, a new admin user can be created.
• Analytics and Search Console: verify ownership again with your own account.
• Business Profile: request ownership through Google's process.

What if the developer holds the domain?

Write to them formally asking for the domain to be transferred, keep records of your invoices and any contract terms on ownership, and give a deadline. If they do not respond, the registrar's dispute processes and, as a last resort, legal advice are the routes. Start before the renewal date.

Should a new developer take over or rebuild?

Take over if the site runs on a mainstream, supported platform with no heavy custom code: a new developer can audit, update and maintain it. Rebuild if it is proprietary, unsupported, undocumented custom code, or already compromised.

• Website technical debt: when to stop patching
• Unsupported CMS: what to do when support ends

How do you stop this happening again?

Hold every account in the business's name, with at least two people having access, and keep the logins in a password manager. Put ownership of the domain, files and content in writing with any new supplier, and ask for documentation of how the site is built.

• Questions to ask a web design agency before signing

When should you wait?

Rarely, if the domain renewal is close or the site is insecure. If renewal is a year away and the site is stable, a polite fortnight of chasing may resolve it. Take a backup in the meantime if you have any access.

What should a new developer check first?

The basics that decide whether the site can be taken over: which platform and versions it runs, whether updates are possible, what custom code exists, whether backups exist and work, and whether there are signs of compromise. That audit usually takes a few hours for a small business site.

Ask for a short written report with a recommendation: take over and maintain, fix specific problems then maintain, or rebuild. It gives you something concrete to compare if you ask more than one developer, and a record for the future.

• Platform, versions and update status.
• Custom code and undocumented changes.
• Backups and whether they restore.
• Signs of compromise or malware.
• A written recommendation.

What does this look like in practice?

A pattern in UK SMEs: a freelance developer who built the site years ago stops answering, and the domain renewal notice goes to their email. Contacting the registrar with invoices and business records, then moving the domain into the business's account, secures it before it lapses. The site itself is then audited and taken over.

• See client work
• Website Design & Development for UK businesses

Recovery checklist

Work through these this week.

• Look up the domain registrant and renewal date.
• List every account and who holds it.
• Recover hosting and CMS access through providers.
• Take a full backup.
• Re-verify analytics and Search Console.
• Decide: take over or rebuild.

Next step

If your developer has disappeared, we will help you work through recovery in a 30-minute call and assess whether the site can be taken over.