It happens more than you’d think. You hired someone to build or maintain your website, and at some point they stopped answering. Now the site is broken, half-finished, or you can’t even log in, and you need someone else to take over.
I see this regularly. Here’s what actually happens when you bring someone in to fix a build the last developer walked away from.
The first step isn’t fixing. It’s looking.
No honest developer can quote a repair on a site they haven’t opened up. So the first thing that happens isn’t a fix. It’s an assessment.
I need to see how the site was built, what’s actually broken, and what shape the code and content underneath are in. Depending on the size of the site, that takes anywhere from a few hours to a day.
This part is worth paying for. It’s the difference between a real plan and a guess.
Access is usually the first obstacle
Before I can look at anything, I have to get in. This is where a lot of abandoned sites get stuck.
The previous developer often holds the keys: the hosting account, the domain name, the admin logins, sometimes all of it. Occasionally those accounts are in their name or paid on their card.
Part of the early work is figuring out who owns what and getting control back to you. Sometimes that means contacting a hosting company directly to prove the site is yours.
What tends to turn up
Once I’m in, the findings are usually some mix of the same things:
- Software that hasn’t been updated in a long time, which is a security risk
- No backups, so there’s no safety net if something goes wrong
- Custom work nobody wrote down, so the only person who understood it is gone
- Plugins or tools that their own makers have stopped supporting
- A site built in a way that only made sense to the person who built it
None of this is unusual. It’s what “abandoned” looks like under the hood.
Fix or rebuild is a real question
Not every broken site is worth saving. Sometimes the repair is quick and cheap. Sometimes the existing build is such a tangle that starting fresh costs less than untangling it.
A straight answer on this is part of what you’re paying for. I’ll tell you which way I’d go, and why, before you commit to the bigger spend.
What you can do to make it faster and cheaper
You can save time and money by gathering whatever you already have before we talk:
- Any login details you have, for hosting, the domain, or the WordPress admin
- Any emails, invoices, or contracts from the previous developer
- The name of the hosting company and domain registrar, if you know them
Even partial information helps. If you have none of it, that’s workable too. It just adds a step.
Keeping this from happening again
Once the site is stable, the goal is making sure you’re never locked out again. That means the accounts are in your name, you hold your own copies of the logins, and how the site works is written down somewhere you can find it.
If a developer disappears on you again, you hand the next person a folder instead of a mystery.
An abandoned website is a common, fixable situation. It’s not a reflection on you, and it’s rarely as bad as it feels when you’re staring at a site you can’t get into.
If that’s where you are right now, this is the kind of work I do. Let’s talk about what you’ve got.
