The person who built our website disappeared. Now what?

A practical recovery checklist for businesses that lost contact with a former developer, employee, agency, or friend who managed the website.

It happens constantly.

A freelancer stops responding. An employee leaves. A marketing company closes. A family friend built the site six years ago and nobody remembers the details.

The website still works—until somebody needs to change something.

Then the business realizes it does not know where anything lives.

Do not panic. Start by separating the pieces.

A website is usually several different accounts

People often talk about “the website” as if it is one thing.

It may involve:

  • the domain registrar,
  • DNS,
  • web hosting,
  • the website platform,
  • a content-management login,
  • business email,
  • analytics,
  • Google Business Profile,
  • form or email services,
  • payment or scheduling tools,
  • plugin or software licenses.

You may control some of these even if another person controls others.

Step 1: Find out who controls the domain

The domain is the address customers know.

Examples are yourbusiness.com or yourbusiness.net.

Figure out which registrar holds it and which account controls that registrar.

If the account belongs to the business and you can log in, that is a strong starting point.

Do not casually transfer the domain or change DNS records while investigating. The same DNS configuration may control both the website and business email.

Step 2: Identify the web host

Hosting is where the website files or application actually run.

Look through:

  • credit-card statements,
  • old invoices,
  • accounting records,
  • password managers,
  • prior vendor emails,
  • browser-saved logins.

Common charges from hosting companies are often the easiest clue.

Step 3: Recover the website login

If the site uses WordPress, Squarespace, Wix, Shopify, Webflow, or another platform, determine whether a business-controlled administrator account already exists.

If it does, create a fresh administrator account for the business and remove access that is no longer appropriate.

Do not share one generic administrator password among everyone forever.

Step 4: Check where forms and notifications go

Even after website access is recovered, contact forms may still send inquiries to the former developer or an old employee.

Test every form.

Verify the destination mailbox and make sure the business controls any third-party service involved in sending those notifications.

Step 5: Inventory connected services

Look for integrations such as:

  • Google Analytics,
  • Search Console,
  • scheduling,
  • payment processing,
  • maps,
  • newsletters,
  • CRM,
  • chat widgets,
  • security tools,
  • backup services.

The goal is to learn what would break if an old account were disabled.

Step 6: Change access carefully

Once you understand the setup, remove accounts that should no longer have access.

Change shared passwords.

Turn on multi-factor authentication.

Move recovery email addresses and phone numbers to business-controlled contacts.

Do this deliberately rather than resetting everything at once.

Step 7: Document the recovered setup

Create a short technology inventory.

For each important service, record:

  • provider,
  • purpose,
  • account owner,
  • administrator contact,
  • renewal method,
  • recovery path.

Passwords themselves belong in a reputable password manager, not in the inventory document.

What if the old provider owns everything?

That situation is harder, but not automatically hopeless.

Gather evidence that the business paid for the domain, website, hosting, or related services.

Save invoices, contracts, email threads, and account records.

Contact the relevant providers through their documented recovery processes.

The exact options depend on how each account was originally registered.

What not to do

Avoid making a brand-new website or buying a second domain simply because access feels confusing.

That can create duplicate systems while the original domain, email, and search presence remain unresolved.

Recover and understand the existing assets first whenever practical.

Prevent the problem from happening again

A business can work with freelancers and agencies without giving up control.

A healthy arrangement usually means:

  • the business owns the domain,
  • the business owns the primary platform accounts,
  • vendors receive appropriate delegated access,
  • at least two trusted people understand the recovery path,
  • recurring charges are visible to the business,
  • and important systems are documented.

The person helping you can still manage everything day to day.

The difference is that they are managing your accounts—not becoming the only person who can access them.

If your current website works but nobody knows who owns it, that is worth fixing while there is no emergency.

Want a second set of eyes on your setup?

We can review your website, business email, domain, or everyday technology and give you a practical next step.