// Website Recovery

Your Developer Has Gone Dark. Now What?

The developer isn't responding. The site is still up — for now. This is more common than most business owners realize, and it's fixable.

A Situation We Know Well

A business owner messages us: "My developer stopped responding three months ago. The site is technically still up, but the contact form stopped working and I have no idea if he's even still active."

We get variations of this message regularly. Over the years we've worked with dozens of businesses in exactly this situation. In many cases the hosting was on GoDaddy or A2 Hosting with the account registered in the developer's name. In some cases the domain registrar was Hostinger with the developer as the legal contact.

What's Actually at Stake

Security vulnerabilities: Without someone applying updates, known exploits become open invitations. We've seen this happen within weeks of a known vulnerability being published with no patch in sight.

Hosting-triggered crashes: Hosting providers — GoDaddy, Hostinger, A2 Hosting — automatically upgrade server PHP versions on their own schedule. A Joomla 3 site can silently break overnight. The business owner finds out when a customer calls.

Expired contracts: SSL certificates, domain registrations, hosting renewals — everything has an expiry date. Without someone watching, something lapses.

Outdated information: If nobody can make updates, the website becomes systematically inaccurate — and customers book elsewhere.

First Steps When Your Developer Is Unreachable

Lock down access:

• Do you have login credentials for the hosting control panel?
• Is the domain registered in your name, or your developer's? Check the registrar's WHOIS record.
• Do you have admin credentials for the CMS backend?
• FTP/SFTP credentials are often available in the hosting control panel.

Document current state: Screenshot everything that works and doesn't. Pull Search Console and Analytics data. Save current rankings.

Short-term stabilization: If the system is running and not in immediate danger: don't experiment. No updates without a backup, no plugin changes without someone who knows what they're doing.

Why This Keeps Happening

This isn't a criticism of any particular developer. It's a structural problem in how smaller web projects are typically contracted — no maintenance agreement, no credential handover document, no contingency plan.

What the Alternative Looks Like

The systems we build are designed so the business owner can update content, swap images, and add pages without external dependency. When we take over an existing system, the first step is always a complete inventory: all access credentials documented, all contracts audited, a full backup created before anything is touched. And afterward, the system belongs to you — with plain-language documentation on how to operate it.

Continue reading: Why Joomla Blocks Modern AI Workflows →