Why This Happens More Than You'd Think
A freelance developer goes quiet mid-project. A "web guy" who built the site years ago stops answering calls. An agency shuts down without notice. Whatever the version, the result is the same: a business owner left holding a website they can't access, can't update, and sometimes can't even identify who built it or where it's hosted.
This is more common than most business owners expect, and it's rarely anyone's fault in the moment — it just means someone now needs to do forensic work before any actual improvements can happen.
Cost by Handoff Scenario
| Scenario | Typical Cost | What's Involved |
|---|---|---|
| You have all logins, site is running fine | $300–$800 | Security audit, plugin/theme updates, ownership transfer of hosting/domain |
| Missing some credentials, site has minor issues | $800–$1,800 | Password resets via host/registrar, fixing broken functionality, cleanup |
| No credentials, unclear hosting, site partially broken | $1,800–$3,500 | Full access recovery process, rebuilding broken sections, security hardening |
| Site down entirely, domain/hosting expiring | $1,000–$4,000+ | Emergency recovery, possible rebuild from backup or from scratch if no backup exists |
What to Do First
- Check your email for original setup messages. Hosting welcome emails, domain registrar confirmations, and the original project agreement often contain account details you forgot you had.
- Check who owns the domain. A WHOIS lookup shows the registrar; if you're not listed as the owner, this needs fixing first, before anything else.
- Don't panic-cancel hosting or make guesses at passwords. Repeated failed login attempts or account changes can sometimes trigger security lockouts that make recovery harder.
- Gather anything you do have. Old invoices, emails, screenshots of the admin dashboard — anything helps a developer reconstruct what's actually going on faster (and cheaper).
What Drives the Recovery Cost
- How much access you already have. This is the single biggest factor — every missing credential adds real hours of detective work.
- Hosting situation. Shared hosting with an unresponsive host is harder than a well-documented managed WordPress host.
- Whether backups exist. A recent backup can turn a rebuild into a restore.
- Code quality left behind. Custom, undocumented code takes longer to safely understand and maintain than a standard WordPress/WooCommerce setup.
- Urgency. A site that's actively down and losing sales costs more to fix on a rushed timeline than a stable-but-inaccessible site.
Real Case Study
Small e-commerce business, developer went unresponsive for 3 months — $1,450 total.
The business owner had WordPress admin login but no hosting account access, no idea which company hosted the site, and an SSL certificate about to expire. Recovery involved: tracing the hosting provider through DNS records, working with the registrar to regain domain control, resetting hosting access, renewing the SSL, and a full security audit since the account had been dormant. Total time: 8 days from first contact to full access restored, plus 2 weeks of plugin/theme updates and testing afterward.
How to Avoid This Next Time
- Always keep your own copy of hosting, domain registrar, and admin credentials — never rely solely on a developer's records
- Register domains under your own name/account, not the developer's
- Ask for a written handoff document at project completion, even if you plan to keep the same developer
- Keep at least one recent backup stored somewhere you control
Frequently Asked Questions
What if I don't know who hosts my site?
A developer can trace this through DNS and WHOIS records in most cases, even without your original login information.
Can the site be recovered if I have zero login information?
Usually yes, though it takes longer and costs more — recovery paths exist through domain registrars and hosting providers even without saved passwords.
What if my old developer registered the domain in their own name?
This is a legal transfer situation, not just a technical one — it requires cooperation from the registrar and sometimes documentation proving you're the rightful business owner.
How long does recovery usually take?
A straightforward case with existing access can be stabilized in 2-3 days. A messy handoff with missing credentials can take 1-3 weeks.
Is it cheaper to just rebuild from scratch?
Only if the existing site has serious underlying issues or no meaningful content/SEO value to preserve. If the site has been ranking in search or has real content, recovery is almost always cheaper than a full rebuild.
Developer gone quiet and you're stuck?
I help business owners recover access to abandoned WordPress and WooCommerce sites, audit what's been left behind, and get things stable again.
Get Help NowRelated reading: Cost to Fix a Hacked WordPress Site | WordPress Site Hacked Recovery | WordPress Maintenance Cost | Website Redesign Cost | Hire a WordPress Developer
