Inherited a Website From an Old Developer Who Disappeared? Here's What to Do

It’s a more common situation than it sounds. A business owner has a working website, but the freelancer or agency who built it is nowhere to be found anymore, moved on, stopped answering, or just vanished entirely without a word of warning. Nobody currently has the access needed to change a single thing on the site. If this is you, the good news is it’s almost always fixable. The steps just aren’t obvious if you’ve never had to do this before in your life.

Start with what you can actually log into right now

Check your domain registrar first, wherever the domain itself is registered under whichever account. Look through your email for any registration or renewal receipts from years back. The “from” address usually reveals which registrar you’re dealing with, even if you’ve forgotten the details entirely. Check hosting too, wherever the site’s files actually live day to day. Sometimes it’s the same account as the domain, sometimes it’s completely separate and harder to track down. Check the site’s admin panel, if it runs on WordPress or something similar, usually sitting at yoursite.com slash wp-admin or close to it in most standard setups.

If you already have login access to all three, you’re in a much better position than you probably think sitting there worried. A new developer can work with what’s already there without starting completely from zero.

Check who actually owns the domain

This is the single most important thing to verify before anything else gets addressed. Look up your domain’s registration details, a WHOIS lookup, or directly inside your registrar account, to see whose name and contact information is actually listed as the owner on record. If it’s the old developer’s name and not yours, this needs sorting before anything else moves forward at all. Without it, you don’t fully control your own website’s address, no matter what else you manage to recover from the old setup.

Get an honest audit before you decide anything

A new developer can usually look at what exists, the platform, the code if it’s custom, the overall condition of things behind the scenes, and give you a straight answer. Is this worth continuing to build on, or is a rebuild actually the more practical option given the state of things? This isn’t something to guess at on your own without technical background. It takes someone who can actually read what’s sitting there and assess it honestly.

Deciding between a rescue and a rebuild

Rescue makes sense when the site is reasonably well-built, mostly just needs updates, fixes, or new features added, and you have, or can recover, the access needed to work on it going forward without a major fight. Rebuild makes more sense when access can’t be recovered at all despite real effort, the underlying code is genuinely in rough shape once someone looks under the hood, or the site’s old enough that starting fresh costs about the same as untangling what’s already there.

What this experience teaches about choosing your next developer

Photographers and business owners who’ve been through this once tend to ask very different questions the second time around, specifically about ownership and access, before signing anything with a new developer. That hard-earned caution is reasonable and worth carrying forward, even though it can feel a bit exhausting to have to ask upfront questions that shouldn’t have been necessary in the first place.

What to insist on this time around

Whoever takes over, whether it’s a rescue or a full rebuild, get the domain transferred fully into your name without delay. Get real access to hosting and any admin accounts under your own credentials. Get the source code, or a documented account of the full setup if there isn’t clean code to hand over. This is the moment to actually fix the ownership gap that caused the whole problem the first time through.

Why acting sooner rather than later matters here

The longer a site sits with unclear ownership, the more likely small problems compound, a domain renewal quietly missed, hosting that lapses without anyone noticing, security patches that never get applied because nobody has access to apply them. Addressing this as soon as you notice the gap, rather than putting it off because the site still technically works for now, prevents a manageable problem from turning into a genuine emergency down the line when you least expect it.

What a smooth transition actually looks like once sorted

Once ownership and access are properly resolved, moving forward with a new developer should feel like a completely normal project, not a recovery mission anymore. Files transfer over, a plan gets made for what needs updating or rebuilding, and work proceeds on a regular timeline just like any other website project would. The messy part is almost always the untangling at the very start, not the actual rebuilding work that follows once things are sorted out properly, which is genuinely reassuring to hear if you’re currently in the middle of the stressful part and wondering how long this will drag on.

What documentation to keep once everything’s resolved

Once ownership and access are sorted, write down the key details somewhere safe, the registrar login, the hosting account, who to contact for support, and when key renewals are due. This single step is what prevents the exact same situation from happening again in a few years under a different developer, and it takes only a few minutes compared to the days or weeks a full recovery process can otherwise take.

Don’t let embarrassment slow down the fix

Some business owners feel a bit embarrassed admitting they don’t know who owns their own website, as though it reflects poorly on how they’ve run their business. It doesn’t. This situation is common enough that any experienced developer has seen it many times before and won’t think twice about it. The only real mistake is letting that discomfort delay fixing something that only gets harder to untangle the longer it sits unresolved, so reaching out sooner rather than later is always the better move.

Have a site with an access problem, or an old developer who’s gone quiet on you? Send over what you have and get an honest read on whether it’s worth saving or better off rebuilt.