The emails bounce. The phone goes to voicemail. The "I'll get to it this weekend" texts stopped three weekends ago. Somewhere between annoyed and alarmed, it sinks in: your developer is gone, and they were the only person who knew how your website works.
First, breathe. We've helped a lot of owners through exactly this, and here's the truth up front: this is almost always recoverable. Sometimes it's an afternoon of password resets. Sometimes it's a rebuild. It is very rarely a catastrophe, unless you panic and do things out of order.
So this is the order. Domain first. Hosting second. Content salvage third. Rebuild decisions last. Work the list.
Before anything: figure out what kind of "disappeared" this is
Not every silence is abandonment. Before you start filing disputes and transferring domains, spend one day ruling out the boring explanations:
- Send one clear, kind email with a specific ask and a date: "I need admin access to my domain registrar and hosting by Friday. If something's going on, no judgment, just let me know how to get access." Developers are human. People get sick, burned out, divorced, deployed.
- Check whether the business still exists. A dissolved LLC, a dead website, a disconnected number, those change your approach.
- Check your own inbox history. Search for old emails from them. You're looking for receipts, login credentials they sent years ago, invoices naming a hosting company, anything. This archaeology will matter in every step below.
If a week passes with no response, stop waiting and start recovering. You can do all of the following without their cooperation. It's just slower.
Step 1: Secure the domain (do this first, always)
Your domain is the only part of your web presence that's genuinely hard to replace. Hosting can be repurchased. A site can be rebuilt. But yourbusiness.com, the address on your trucks and your Google listing and ten years of customer bookmarks, exists exactly once. Everything starts here.
Find out where it's registered. Use the public lookup tool from ICANN, the organization that coordinates the domain system, to look up your domain. You'll see the registrar (the company it's registered through) and the expiration date.
Check that expiration date right now. If the domain expires soon and nobody's paying the renewal, this graduates from project to emergency. Expired domains go through a grace period and then can be released or auctioned, and getting one back after that ranges from expensive to impossible.
Try to get into the registrar account. Attempt a password reset using every email address your business has ever used. If the account was created with your email, you're nearly done: reset, get in, update the contact info, turn on auto-renew with your own card, and exhale.
If the account is in the developer's name, contact the registrar's support directly. Explain the situation: you're the business owner, your vendor is unreachable, and you need to recover or transfer the domain. Registrars deal with this regularly and most have a process, but be ready to prove you're you. Useful evidence includes business registration documents, invoices showing you paid for the domain or the website, the trademark or business name matching the domain, and a government ID. The more your paper trail shows you paid for and used this domain, the smoother this goes. This is also the moment many owners learn why those invoices were worth keeping.
One honest caveat: if the domain was legitimately registered by the developer, in their name, paid with their card, and your contract said nothing about it, recovery can get genuinely hard, and in contested cases owners sometimes end up negotiating or consulting an attorney. We're not lawyers and this isn't legal advice; it's a reason to escalate politely and persistently, in writing, and to read our piece on hostage situations on the blog if the silence starts feeling strategic.
Step 2: Get control of hosting (or decide you don't need to)
While the domain work is in motion, turn to hosting, which is where your site actually lives.
Follow the money. Check your bank and card statements for hosting charges: GoDaddy, Bluehost, SiteGround, WP Engine, Wix, Squarespace, and similar names. If you find a charge, you have an account, and you can password-reset your way in.
If the developer paid for hosting as part of your monthly fee, assume the clock is ticking. When their card fails or they cancel their account, your site goes offline with no warning. This is why content salvage (step 3) shouldn't wait for steps 1 and 2 to finish.
Decide whether the hosting is even worth recovering. Here's a secret that takes the pressure off: you often don't need the old hosting account at all. Hosting is a commodity. If you control the domain and you have your content, you can point the domain at brand-new hosting and never think about the old account again. Fight hard for the domain. Fight only as hard as it's worth for the hosting.
Step 3: Salvage your content while the site is still up
If your site is currently online, treat that as a gift with an expiration date. Today, while it's live, capture everything:
- Copy the text of every page into a document. Services, about page, FAQs, the wording you spent hours getting right. All of it.
- Save every image you care about, especially photos of your actual work, team, and location. Right-click and save, page by page. Tedious, but an hour of tedium beats losing five years of job photos.
- Screenshot every page top to bottom, so a rebuild can match the layout.
- Export anything exportable. If you have any level of admin access to the site platform, look for export or backup functions and use them now.
- Lock down the accounts adjacent to the site. Make sure you have owner access to your Google Business Profile, since marketers and developers often set these up under their own accounts, and claim your site in Search Console if you can, so your search data and history stay with you.
If the site is already offline, all is not lost. Public web archives often hold old snapshots of small business sites, your own email outbox is full of text you wrote, and your phone's camera roll has more usable photos than you think. Rebuilding from fragments is normal. We do it weekly.
Step 4: Decide, rebuild or revive
With the domain secured and content in hand, you're out of emergency mode and into a business decision. Two paths:
- Revive: you got full access to the old hosting and site, it works, and you just need someone new to maintain it. Fine, as long as someone you trust reviews it for outdated software and leftover vendor access.
- Rebuild: access never came through, or the old site was held together with duct tape anyway. Honestly, most owners in this spot end up happier rebuilding. The disappearance forced an audit they'd never have done voluntarily, and the new site goes up with clean ownership from day one.
Either way, the meaningful loss in most disappearance stories isn't the website. It's the weeks of downtime and missed calls while the owner figured out steps 1 through 3. Which brings us to the part that protects you next time.
The prevention checklist
Whoever builds your next site, set it up so that no single person's disappearance can ever take you down again:
- Domain registered in an account you own, with your business email, your card on auto-renew, and the renewal date on your calendar.
- Hosting billed to you, or at minimum, admin credentials in your hands, tested once a year.
- A written answer to "what do I walk away with if we part ways," before any work starts.
- Copies of your content (photos, copy, logo files) stored in your own cloud drive, refreshed whenever the site changes.
- Owner access to Google Business Profile, Search Console, and analytics under a Google account your business controls.
- More than one human with access. You plus a spouse, partner, or bookkeeper. Buses come for all of us.
The Small Business Administration's guidance on managing your business includes a recurring theme that applies perfectly here: keep your critical records and accounts in the business's name, not an individual's. The SBA wasn't writing about websites specifically, but the principle is the same one that saves owners in every story above.
If you'd rather never do this again
This recovery playbook is yours either way, use it with any developer you like. But if you want the rebuild done fast and owned right, that's literally our specialty.
We're a veteran-owned shop in Wilmington, NC. We build done-with-you websites live on a call with you, first draft in 24 hours, live in 7 days, guaranteed. You own your domain and your site, period, in accounts under your name, so this guide becomes something you never need twice. We've built 1,500+ small business sites in the last 90 days, with tiers from $500 and pay-in-4 or Klarna available, and our website and SEO service handles the ongoing care without holding your keys.
Book a call, bring your salvage folder, and let's get you back online.