Operations

Your WordPress Developer Is Gone: How to Take Over the Site

What to find, in what order, and what to leave alone until you have a backup.

Quick Answer: Recover the accounts in order: domain registrar, DNS, hosting, then WordPress admin. Take a full backup before you change anything, list the plugins, themes, users and licenses, then change passwords, add MFA and update on a staging copy. Finally, decide who is accountable for the site from now on.

Locked Out or Unsure What You Have?

Tell us about your site and we'll get back to you within one business day.

The developer who built your WordPress site has stopped answering, or the agency closed, or the freelancer moved on. The site still runs, for now, and you are not sure who has the keys. This is more common than it sounds, and the first few days matter. This guide covers what to find, in what order, and what to leave alone until you have a safety net.

Start with the accounts, not the website

A WordPress site depends on several accounts, and the one that is hardest to recover comes first. Work through these in order:

  • Domain registrar. Whoever is listed as the owner of the domain controls everything else. Look the domain up in a WHOIS tool and check the registrar. If the developer registered it in their own name, getting it transferred is the first job. Privacy services can hide the owner, so you may need to contact the registrar.
  • DNS. Find where the domain's nameservers point. That tells you who controls email and where the site is hosted.
  • Hosting. Find out which company hosts the site and whose account it sits under. Their support team can usually tell you what you need to prove ownership.
  • WordPress admin. If you cannot log in, try the lost password link first. If that email goes to the developer, a host or a technical person can reset access through the database or the command line.
  • Email. Check who receives the site's admin and form emails.

Take a backup before you change anything

The moment you have any kind of access, make a full copy of the files and the database. Do not update plugins, delete users or switch themes first. If something goes wrong, that copy is how you get back. Make sure it is stored somewhere other than the server.

Take stock of what is on the site

Write down what you find. You are looking for:

  • The WordPress version, the PHP version, and which plugins and themes are installed, with their versions.
  • Every user with admin access. Remove people you do not recognize only after you are sure they are not the developer or an agency you still depend on.
  • Premium plugins and themes. These often run on a license tied to the developer's account. If the license lapses, updates stop, and the plugin becomes a security risk.
  • Anything custom, such as a child theme or code added by the developer. Find out whether it is documented.

Lock it down in the first week

Once you have a backup, change the passwords on hosting, WordPress, the database and SFTP. Turn on multi-factor authentication for admin accounts. Remove access for people who no longer need it. Then bring core, plugins and themes up to date, ideally on a staging copy first, because a site that has gone unmaintained often breaks when it is updated all at once. If the site looks like it has already been compromised, read what to do first when a WordPress site is hacked.

Decide who owns it from now on

The real problem is usually not the missing developer. It is that nobody was accountable for the site, so the work depended on one person. Before you hire someone new, decide what you need: a developer for changes, or a team responsible for updates, security, backups and response, or both. We cover this in why your WordPress site needs someone accountable and what WordPress website management is.

Whoever you choose, keep a short written record of the accounts, who has access, and where the backups live, and keep it somewhere that does not depend on one person.

If you would rather not do this alone

If you have lost access, are not sure what is on the site, or suspect something is wrong, a free site audit is a safe place to start. It looks at updates, security, backups and performance and tells you what needs attention first. If the site is down or hacked right now, go to emergency support.

Related Guides

Martin Van Den Boogerd
Martin Van Den Boogerd
Founder & Owner, CriticalWP, a WebOps agency for WordPress — background in cybersecurity and municipal government infrastructure
More about Martin →

Common Questions

Work through the accounts in order: the domain registrar, DNS, the hosting account, then WordPress admin. Try the lost password link first. If that email goes to the developer, your host or a technical person can reset access through the database or command line.
It depends on whose name the accounts are in. Check the domain's registrant and the hosting account holder. If the developer registered either in their own name, you will need them or the registrar to transfer it.
Not before you have a backup. Take a full copy of the files and database first, and update on a staging copy where you can, because a site that has not been maintained can break when updated all at once.
Updates can stop when a license lapses, which leaves the plugin unpatched. Find out which premium plugins and themes you have, and move the licenses to an account you control.
Decide who is accountable for the site, keep a written record of accounts and access that does not depend on one person, and use a provider or team responsible for updates, security, backups and response.

Inherited a WordPress site nobody owns?

A free site audit shows what is on it, what is out of date, and what to fix first.