My web developer disappeared. How do I get my website back?
Your developer stopped answering and you cannot log in. Here is how to find out what you actually own, recover each login, and keep the site running while you do it.
It happens more than you would think. The freelancer took a full-time job. The agency got acquired. The nephew who built it moved away. The site is still up, but nobody can log in, and the person who could is not answering.
Your website is not one thing. It is four or five separate accounts, and each one is recovered differently. Work through them in this order.
1. Find out who holds the domain
The domain is the part you cannot afford to lose. Everything else can be rebuilt; a domain that lapses or sits in someone else’s account is a real problem.
Look it up with a WHOIS or RDAP search (ICANN’s lookup at lookup.icann.org works). Most results hide the owner’s name for privacy, but they always show the registrar, the company it is registered through, and the expiry date.
- If you have ever paid a renewal yourself, check your email for receipts from that registrar. You may already own the account.
- If the developer registered it in their own account, contact the registrar’s support. They can move a domain to its rightful owner with proof of the business, such as a business license, invoices, or old emails showing you paid for it.
- Note the expiry date. If it is close, this is your first job.
2. Find out where the site is hosted
The same lookup shows the nameservers, and a quick search on the site’s IP address usually reveals the host (GoDaddy, Bluehost, SiteGround, WP Engine, and so on).
If the hosting account is in your name or on your card, you can reset the password yourself. If it is in the developer’s name, the host will usually still talk to you, because you are the person paying the bill or you own the domain pointed at it. Ask them for two things: access transferred to you, and a full backup.
3. Get back into WordPress (or whatever runs the site)
If you can reach the hosting account, you can get into the site, even without the developer.
- WordPress: use the host’s file manager or phpMyAdmin to reset the admin password, or create a new admin user. Most managed hosts also have a one-click “log in to WordPress” button.
- Squarespace, Wix, Webflow: these live inside one account. Contact the platform’s support with proof you own the business and the domain.
Once you are in, add yourself as an administrator with your own email, then remove any accounts you do not recognize.
4. Take a backup before you change anything
Before you update a single plugin, take a full backup of the files and the database and store it somewhere you control. A site nobody has touched in a while is fragile, and the first update is the one most likely to break something.
5. Check the things that quietly broke
Developers leave behind connections that were set up in their name:
- Forms. Submit every one and confirm it reaches you. Notification addresses often point to the old developer.
- Business email. If your email runs through the domain, check who controls the DNS records that make it work.
- Google Analytics, Search Console, and Business Profile. Make sure you are an owner, not just a user.
What not to do
- Do not let the domain expire while you wait for a reply.
- Do not “start over” on a new domain to avoid the hassle. You lose every ranking and link the old one earned.
- Do not hand the new developer your only login. Give them their own account so you never end up here again.
When to bring in help
Most owners can do the domain and hosting steps themselves with a few support calls. Where it gets technical is the site itself: an outdated install, unknown custom code, and plugins nobody has updated in two years.
That is the work I do in a website takeover. I start with access, backups, and making sure leads still arrive, then everything else. If you are not sure how bad it is, the free website health check is a good place to start, or tell me what is broken.