Guide

Your web developer disappeared. Here's what to do.

It happens more than anyone admits. The person who built your website moved on, stopped answering, or went out of business, and now nobody knows how the site works. Here's how to get back in control.

At a glance

Covers
Domains, hosting, logins, and whether to rebuild
You'll need
Any invoices, emails or documentation from your old developer

By Jeremy Gimbel, founder of Conflux Group · Last reviewed

First: is this actually an emergency?

Two very different situations get described the same way. Work out which one you're in before you do anything else.

It's urgent if:

  • Your site is down, showing errors, or redirecting somewhere strange
  • You're getting warnings that your domain or hosting is about to expire
  • Your site has been hacked, or Google is showing a security warning

It can wait a week if:

  • The site works fine, you just can't edit it
  • You want changes made and there's no one to make them
  • You're worried about what happens if something breaks

If you're in the first group, start with the domain and hosting sections below today. If you're in the second, you have time to do this properly. That's the better position, and it's worth using.

Secure the three things that let you stay in control

Everything else about a website can be rebuilt. These three can't, or can only be rebuilt at real cost.

What Why it matters Where to look
Your domain name It's your address. Lose it and your site and your email go with it. A registrar such as GoDaddy, Namecheap, Squarespace Domains, Cloudflare or Network Solutions. Check old invoices and card statements for annual renewals.
Your hosting account It's where the site's files and database actually live. A host such as WP Engine, SiteGround, Bluehost, DigitalOcean or AWS. Look for monthly or annual charges.
An admin login to the site It's how you, or a new developer, get into the content management system. Usually /wp-admin for WordPress, /admin for Craft, /user/login for Drupal. Check your password manager and old onboarding emails.

Once you've found them, put every account in your organization's name, with an email address your organization controls ([email protected] rather than a personal or developer address), and store the credentials in a shared password manager.

Lock out old access, but don't delete it. For any company or person who used to work on the site, deactivate their accounts or change their passwords instead of deleting them. On many platforms, deleting a user account also deletes the content that account created.

How to find out who owns your domain

Look your domain up with a registration lookup tool, such as the one at lookup.icann.org. It will tell you which registrar holds it and when it expires, though personal details are usually hidden for privacy.

If the domain was registered in your developer's name rather than your organization's, contact the registrar directly. Registrars have processes for proving you're the rightful owner. Have your organization's documents, any invoices showing you paid for the domain, and evidence that you've used it for your business ready.

Check the expiry date now. An expired domain can be bought by someone else after a grace period, and getting it back is far harder than renewing it.

What if you can't get into anything?

It's more common than you'd think, and it's recoverable.

  • Hosting: contact the host's support team. Like registrars, they can transfer an account to its rightful owner with proof.
  • The site itself: whoever controls the hosting can create a new admin login, so recovering hosting usually recovers the site.
  • Code and backups: ask the host whether they keep automatic backups. Many do, even if nobody set any up.
  • The worst case: if the hosting is truly gone, your site's public pages can often be recovered from search engine caches and web archives as a starting point for a rebuild. It's not ideal, but it's not nothing.

Get an independent assessment before anyone quotes a rebuild

Once you have access, someone experienced should look at what you actually have. A good assessment answers:

  • What is it built on, and which version? An outdated version isn't automatically a problem, but an unsupported one is.
  • Is it secure? When were the software and plugins last updated? Are there signs of compromise?
  • How much is custom? Custom code is where an unfamiliar developer needs the most time.
  • Are there backups, and has anyone ever tested restoring one?
  • What licences does it depend on? Paid themes, plugins and some CMSs (Craft and ExpressionEngine among them) have licences that should be in your name too.
  • What would it take to keep it healthy? This is often much less than people fear.

Be wary of anyone who recommends a full rebuild before they've looked at the site. Sometimes a rebuild is the right answer, but it should be a conclusion, not an opening offer.

Should you rebuild or keep what you have?

Keeping it probably makes sense if… A rebuild is worth considering if…
The platform is still supported, even if your version is old The platform has reached end of life with no upgrade path
The site does what you need and you mainly want it maintained Your organization has changed and the site no longer reflects it
The custom code is reasonably organized Nobody can safely change anything without breaking something else
Your budget this year is for stability, not a project You were planning a redesign anyway

There's often a middle path: stabilize and maintain the site you have now, then plan a rebuild on your own timeline instead of in a crisis.

How to make sure this never happens again

  • Every account in your organization's name, with an organizational email address.
  • More than one person with admin access, including at least one staff member, not only the developer.
  • A shared password manager your organization owns.
  • A one-page handover document: where the site is hosted, what it's built on, where the backups are, who to call.
  • A maintenance agreement that includes an exit. Any good developer should be happy to commit, in writing, to handing over everything if you part ways.

Questions

Common questions

Can a new developer work on a site someone else built?

Yes, on most platforms. An experienced developer can pick up a WordPress, Craft, Drupal or ExpressionEngine site built by someone else. The first few hours go into understanding how it was put together, and the quality of the original work decides how many hours that takes.

Do I own my website's code?

It depends on your agreement with the original developer, so check your contract. In practice, if you have the hosting account, you have the files. If ownership is genuinely in question, that's one for a lawyer, not a developer.

How long does a takeover take?

Getting access is usually the slowest part, and it depends on registrars and hosts rather than on any developer. Once access is in hand, an initial assessment of a typical small-organization site takes days, not weeks.

Is it expensive to switch developers?

The assessment is a small, fixed piece of work. After that, maintaining an existing site almost always costs less than rebuilding it. Our guide to what website maintenance costs covers typical ranges.

Get started

Need someone to take it over?

We maintain and support sites other people built, on WordPress, Craft CMS, ExpressionEngine and more. Tell us what you've got and we'll tell you honestly what it needs, which is sometimes less than you'd expect.