What to Do When Your Old Web Guy Disappears

This is the call we get most often: “Our website guy stopped answering. We don’t know where the site is hosted. We don’t even know who registered the domain.” Sometimes the freelancer just stopped responding. Sometimes the local agency closed. Sometimes the family member who built it moved away.

The situation feels worse than it is. Most of these are recoverable. Here’s the playbook.

Step 1: Find the domain registrar

Your domain (yourbusiness.com) is registered with a company — GoDaddy, Namecheap, Cloudflare, Network Solutions, etc. To find out which one, go to lookup.icann.org and look up your domain. The result tells you the registrar.

It will not tell you the registrant’s name in most cases (privacy is on by default now). But you’ll know which company holds the registration.

Step 2: Try to log in or recover the account

Once you know the registrar, try the password-reset flow with every email address your business uses. Old admin email, your personal email, your old web guy’s email if you have it. If a reset link comes through, you’re back in.

If no email works, you’re looking at the registrar’s “account recovery” process. Each registrar has one. They’ll typically ask for:

• Proof of business identity (articles of incorporation, EIN letter)
• A government-issued ID for the person making the claim
• Sometimes a notarized affidavit

It can take 1-3 weeks. It does work. Most reputable registrars have a clear process for recovering a domain that’s rightfully yours.

Step 3: Find the hosting

The website itself is hosted somewhere — possibly the same place as the registrar, possibly elsewhere. To find it:

1. Open whatsmydns.net, enter your domain, select “A” record
2. The IP address that comes back is the server hosting your site
3. Run that IP through bgp.he.net or similar — it’ll tell you which company owns it (AWS, Cloudflare, Bluehost, GoDaddy, DigitalOcean, etc.)

Once you know the hosting company, repeat the password-reset / account-recovery process there.

Step 4: Decide whether to recover the site or just rebuild

Here’s the honest answer most people don’t want to hear: if your site is more than 3 years old, just rebuild.

The recovery effort — logging into hosts you don’t have credentials for, dealing with abandoned WordPress installs, untangling old plugins — usually costs more than just spinning up a new, faster, cleaner site. The only thing worth recovering is:

• The domain (essential)
• The content (text and images, manually)
• The Google Business Profile, Analytics, and Search Console accounts

The actual site code? Almost never worth saving.

Step 5: Recover the Google ecosystem

Three Google products often have your old web guy as the owner:

1. Google Business Profile — go to business.google.com and try to claim it. If the current owner doesn’t respond within 7 days, Google transfers ownership to you.
2. Google Analytics — if you can’t recover access, just create a new property on the new site. You lose historical data, but you keep going forward.
3. Google Search Console — once you have hosting access, you can verify ownership directly via DNS or file upload. Bypasses the old owner entirely.

Step 6: Build the replacement site

This is where we come in. Two paths:

• Coderize Express: $199-$399/month, $99 reservation deposit credited to first month, live in 3-5 days. Best when the old site was simple and you want to be back online fast.
• Custom build: $2,500+ one-time, you own the source. Best when you have multiple service pages, lead routing, custom forms, or commerce needs.

What to do differently this time

• You should be the registrant on the domain. Not your web team. Always.
• You should have admin access to the hosting account. Not just “they’ll handle it.”
• You should have a copy of the source code. If your web shop closes, you’re not stranded.
• Pick a vendor with continuity. If they’re a one-person operation, ask what happens to your site if they get hit by a bus.

Talk to us

Free 15-minute audit. Even if you can’t access anything yet, we can look at what’s publicly visible and tell you what your recovery path looks like. Reach out.

Related: How to Fire Your MSP’s Web Service, Leaving GoDaddy, Signs Your Website Is Costing You Customers.