My web developer disappeared: get your WordPress site back under your control

The short answer
When your web developer disappears, you get your WordPress site back by taking control of the accounts it runs on, in order: the domain registrar first, then the hosting, then the WordPress admin, which you can usually recover through the hosting account. Then take a full backup of the database and the uploads folder before you change anything else, and write down every plugin, license and form, so the site never again depends on one person's memory.
Work through it in this order. Each step makes the next one easier.
- Find out who holds each login. Domain registrar, DNS, hosting and WordPress are four separate accounts, and the developer may hold any of them.
- Secure the domain. It is the one piece you cannot rebuild.
- Get into the hosting account. The site's files and database live there.
- Recover the WordPress admin. Through the password reset, or through the hosting account.
- Take a full backup. The database plus the uploads folder, stored away from the server. An export is not a backup.
- List every plugin, theme and license. Including whose account paid for each one.
- Document every form and where it sends. Then send a test from each.
- Check you hold every key. One table tells you when you are done.
You need your own email address, an hour or two, and paperwork that ties you to the site: invoices from the developer, receipts or card statements for the domain and hosting, and your business registration. Don't cancel, delete or rebuild anything while you work. If the site is up today, it can keep running while you take back the keys.
1. Find out who holds each login
A WordPress site runs on four accounts, often at four different companies: the domain registrar, where the name is registered; DNS, which points the name at a server and routes your email; hosting, where the files and database live; and the WordPress admin itself. Find out which company holds each one and whose name is on it before you contact anyone.
Piece | What it controls | How to find out who holds it |
|---|---|---|
Domain registrar | Who owns the name, and when it expires | Search your domain at ICANN Lookup. It shows the registrar's name and the expiry date. Owner contact details are often hidden for privacy |
DNS | Where the domain points, including your email | The same lookup lists the nameservers. A name like ns1.yourhost.com or one ending in ns.cloudflare.com tells you which company runs your DNS |
Hosting | The site's files and database | Search your card statements and inbox for hosting charges or renewal notices. The DNS records show the server address your domain points to, and that address belongs to the host |
WordPress admin | Editing the site, its users, plugins and settings | The login page is usually yourdomain.com/wp-admin/. If you have never had a login, the developer holds the only one |
While you look, note every other account the site depends on: Google Analytics, Google Search Console, Google Business Profile, a mailing-list service, paid plugins. Write down who signed up for each. They matter less than the four above, but they are easier to sort out now than in a hurry later.
Keep all of it in one place: the company, the account name, whose email it uses, who pays, and the renewal date. That one sheet is what was missing.
2. Secure the domain first
Check when the domain expires and whose name it is registered in before you do anything else. Everything else hangs off the name: the site, your email and the search history your pages have built. A domain that lapses can be lost to someone else, so if the expiry date is close, renewing it is the most urgent task on this list.
Then get the registrar account into your hands:
- If the account is yours (it uses your email or your card), reset the password, turn on two-step sign-in and switch on auto-renew.
- If the developer registered it, contact the registrar's support. The legal holder of a domain is the registrant, which ICANN also calls the "registered name holder" (ICANN). Ask how they move an account or a registration to its rightful owner. Expect to show invoices, payment records and business documents.
- Once you are the registrant, you can move the domain to a registrar account you control. ICANN's rules say "Your registrar must provide you with the AuthInfo code within five (5) calendar days of your request" (ICANN). The AuthInfo code is the domain's transfer password.
Do not change the nameservers yet. They decide where your website and your email go, and changing them before you know every DNS record can take both offline. Once you can sign in to the DNS account, save a copy or screenshots of every record and keep them with your sheet.
A registrar generally follows its own records. If the developer registered the domain in their own name and will not hand it over, that is the point to talk to a lawyer, with your invoices in hand.
3. Get into the hosting account
The hosting account holds the site's files and its database, so it is the key to every step after this one. If the hosting is billed to your card, you are probably the account holder: reset the password through the host's login page and turn on two-step sign-in. If the developer pays for it, the site lives inside their account, and you need the host's help.
Contact the host's support with the domain name and your proof of ownership, and ask how they handle an account whose holder cannot be reached. Policies differ from host to host, so ask in writing and keep the replies. Two things work in your favor:
- The site is still running. While it is up, nothing is lost yet, and there is no reason to rush a rebuild.
- A narrow request is easier to grant. If the developer still reads email, "please add me as a user on the hosting account" is easier to say yes to than "give me everything".
If the hosting account cannot be recovered at all, a site you can still sign in to can be copied out with a backup plugin (step 5) and restored to a new hosting account in your name. That is more work, so it is the fallback, not the plan.
4. Recover the WordPress admin
Go to yourdomain.com/wp-login.php and use "Lost your password?" with your email or username. WordPress's own documentation calls that link "normally, the easiest way" to reset a password (WordPress.org). It only works if the account's email address is one you can read, and on a site the developer set up, it may well be theirs.
If the reset email goes to the developer, recover the admin through the hosting account instead. If your host offers a one-click backup, run it first.
- Ask the host's support to create a new administrator account for you, or to reset the password on an existing one. Hosting support teams can often do this for the account holder.
- Or reset it yourself in phpMyAdmin, the database tool in most hosting control panels. WordPress documents the steps under "Through phpMyAdmin", with a warning worth taking seriously: "use phpMyAdmin at your own risk. If you doubt your ability to use it, seek further advice" (WordPress.org).
Once you are in, make the site yours:
- Create your own administrator with your own email address, and sign in with it from now on.
- Change the Administration Email Address under Settings, then General, to an address you read. WordPress sends a confirmation to the new address before it switches.
- Review every user. Under Users, list each administrator. Lower the developer's account to a smaller role, or delete it once your backup exists. When you delete a user, WordPress asks what to do with their content: attribute it to your account, or their pages and posts are deleted with them.
5. Take a full backup: the database plus the uploads folder
A full WordPress backup has two parts, the database and the files, and you need both. WordPress's own guide says "There are two parts to backing up your WordPress site: Database and Files" (WordPress developer docs). The database holds your pages, posts, users and settings. The files include the wp-content/uploads folder, where every image and document you have uploaded lives.
An export is not a backup. The file you get from Tools, then Export, lists your content, but EmDash's migration guide notes that it "points to media on the WordPress origin; it does not contain the attachment bytes" (EmDash docs). It carries no images, no theme and no plugins. If the server goes, an export cannot bring the site back.
Three ways to take a full backup, easiest first:
Method | What you do | Watch for |
|---|---|---|
Your host's backup tool | Run a full backup in the hosting control panel, then download it | A backup that only lives on the same server goes down with it |
A backup plugin | Install one from the WordPress plugin directory and back up the database and the files | Database-only backups miss your images. Send the backup to cloud storage or download it |
By hand | Export the database in phpMyAdmin, and download the wp-content folder by SFTP or the host's file manager | Slowest, but nothing new gets installed on the site |
Then check what you have. Open the archive: there should be a .sql file, which is the database, and a wp-content folder with an uploads folder inside, sorted into year and month folders. Keep more than one copy. WordPress recommends you "keep at least three backups on file, just in case one is corrupted or lost, and store them in different places" (WordPress developer docs).
6. List every plugin, theme and license
Open Plugins in the WordPress dashboard and write down every plugin, active or not, with its version, then do the same for the theme under Appearance, then Themes. For each paid plugin or theme, find out whose account bought it. Paid licenses are often registered to the developer's email, and a lapsed license usually means the product stops getting updates.
Write down | Why |
|---|---|
Name and version | Shows what the site depends on, and how far behind it is |
Active or inactive | Inactive plugins still sit on the server. Remove the ones nobody needs, after the backup |
Free or paid | Paid ones carry a license key and a renewal date |
Whose account holds the license | If it is the developer's, buy your own or ask them to transfer it |
Renewal date and price | So nothing expires without anyone noticing |
Don't press "update all" while you do this. Updates are worth doing, one at a time, after the backup in step 5, with a look at the site after each one. Plugins are where most WordPress security trouble starts: Patchstack counted 11,334 new WordPress vulnerabilities in 2025, 91% of them in plugins (Patchstack).
7. Document every form and where it sends
For each form on the site, write down the page it is on, the plugin that runs it, and every address or service its messages go to, then send a test from each one. Developers often set the notification address to their own inbox during the build, or connect a form to a mail or CRM account in their name, so leads can go to someone who no longer reads them.
Check each form for:
- The "To" address and any CC or BCC. Change every address that is not yours.
- Connected services. The mailing lists, CRMs and spreadsheets the form feeds, and whose account each one is.
- How the site sends mail. If an SMTP plugin sends through an email account, find out whose account that is.
- Saved entries. Some form plugins keep a copy of every message in the dashboard. Look there for leads you never received.
Then fill in each form yourself from a logged-out browser, using an address outside your domain. If messages don't arrive, our guide to a WordPress contact form that stopped sending email walks through the fix.
8. Check you hold every key
You are back in control when every line below is true. Keep this table with your sheet and re-check it once a year.
Account | Done when |
|---|---|
Domain registrar | You are the registrant, auto-renew is on, and two-step sign-in is on |
DNS | You can sign in, and you have a copy of every record |
Hosting | The account is in your name, or you have your own login to it |
WordPress | You have your own administrator account, and the Administration Email Address is yours |
Backup | Full, checked, and stored in at least two places away from the server |
Plugins and licenses | Listed, with whose account each license is on and when it renews |
Forms | Every form sent a test message that you received |
Why it happened, and how to stop it happening again
The developer did not take your site. The site was set up so that only one person understood it: accounts in their name, licenses on their email, forms sending to their inbox, and the knowledge of how the pieces fit kept in their head. Any site set up that way stalls when that person moves on, whether they vanish, retire or just get busy.
That is the real problem: a site only one person understands. WordPress makes it easy to end up there, because a WordPress site is many separate parts (a registrar, DNS, hosting, WordPress itself, a theme, a dozen plugins, a form plugin and a mail setup), and each one has its own login, its own updates and its own renewal date.
The process fix is the sheet you just built, kept current:
- You hold the accounts. Registrar, DNS and hosting in your name, on your card, with your email. Anyone who works on the site gets their own login, which you can remove.
- Two people can get in. You and one person you trust, so access never lives in a single head.
- Backups leave the server. Automatic, full, and opened to check a few times a year.
- A short monthly test. Sign in to each account, send each form, and look at the renewal dates.
If the site works now that you hold the keys, staying on WordPress is a fine answer. Hire a new developer or buy a care plan with the sheet in hand; our guide to WordPress care plans covers what $50 to $250 a month buys, and what it doesn't. Stay on WordPress too if your site is a store, has members or courses, or is built around one plugin feature. Those sites need WordPress, and a missing developer is a problem you have now solved.
When moving is the better fix
If your site is mostly pages and posts, and you would rather not keep a dozen moving parts patched and paid for, a site with fewer parts is the lasting fix. EmDash, the open-source CMS from Cloudflare that its makers call "the spiritual successor to WordPress" (emdashcms.com), is built on Astro. Once a whole site has moved to it, there is no WordPress core, theme or plugin left to patch, and plugins from its registry are sandboxed and permission-gated. Our EmDash vs WordPress comparison covers what changes for an owner and what gets harder.
It does not remove the need for someone to look after the site. EmDash's documentation says running it yourself "adds operational work: the team is responsible for the database, media storage, backups, upgrades" (EmDash docs). What changes is who carries that work, and whether the accounts stay in your name while they do.
A move is also where a site that only one person understood shows its gaps: forms nobody listed, redirects nobody wrote, pages nobody knew existed. The sheet and the backup you just made are the first steps of any safe move. Before anything else, five questions tell you whether your site should move at all; if it should, our website migration SEO checklist lists what to check next, with the proof to ask for at each step.
Bring your WordPress site into the AI era on EmDash and Astro. We check every URL, redirect, form and search detail against your live site before anything changes, and switch only after you approve the preview, with the rollback written down. After launch we host the site and email you a monthly certificate listing the checks we ran and what changed, and if you ever cancel, you download your site and take it with you. Moving costs from $790 for up to 25 pages to $1,990 for up to 250 (pricing). A free, read-only check of your public pages shows whether your site is a good fit and the exact price before you ask.
Want to know where your site stands? Check your site for free.
Frequently asked questions
What should I do first if my web developer disappeared?
Check when your domain expires and who it is registered to, using ICANN's free lookup tool. The domain is the one piece you cannot rebuild, so secure it first. Then get into the hosting account, recover the WordPress admin through it, and take a full backup before you change anything else.
How do I find out who my domain registrar is?
Search your domain name in ICANN's free lookup tool. The result names the registrar and shows the expiry date and nameservers. Owner contact details are often hidden for privacy, so if you need to prove the domain is yours, contact the registrar's support with your invoices and business documents.
How do I find out who hosts my website?
Start with your own records: search card statements and email for hosting charges or renewal notices. The domain's nameservers often name the host. If DNS runs through a separate service such as Cloudflare, the DNS records show the server address your domain points to, and that address belongs to the host.
Can I get into my WordPress site without the developer's password?
Usually, yes, if you can reach the hosting account. Try the "Lost your password?" link first. If the reset email goes to the developer, ask the host's support to create an administrator account for you, or reset the password in phpMyAdmin using the steps WordPress documents.
Is a WordPress export the same as a backup?
No. The file from Tools, then Export, lists your posts and pages and links to your images, but it does not contain the image files, the theme or the plugins. A real backup has two parts: the full database, and the files, including the wp-content/uploads folder.
Who owns my website if a developer built it for me?
The domain is controlled by whoever is listed as its registrant, and the hosting by whoever holds the account. Your agreement with the developer covers the rest, such as the design and code. If the developer registered accounts in their own name and will not hand them over, keep your invoices and talk to a lawyer.