What to Do When Your Web Developer Disappears

You've sent three emails. Left two voicemails. Checked LinkedIn to see if they're still alive. Nothing. Your web developer has vanished, and your website is either broken, half-finished, or completely inaccessible.

Take a breath. You're not alone—this happens far more often than you'd think, and there's a clear path forward.

Splendid Web rescues abandoned websites so if you're in crisis mode right now and need immediate help, we'll get you back online. But whether you call us or not, this guide will walk you through exactly what to do when your web developer disappears.

Don't Panic: Why This Happens (And It's Not Always Malicious)

Before we dive into solutions, it helps to understand why developers disappear. Rarely is it outright fraud—though that does happen. More commonly:

Health or personal crisis. Freelancers and small agencies are often one-person operations. Illness, family emergencies, or mental health struggles can take someone offline without warning.

Overcommitment. They took on too many projects, fell behind, and now they're avoiding difficult conversations rather than facing them.

Business closure. Small web development businesses fail like any other. If they've gone bust, they may have moved on to employment and simply stopped responding.

Skills mismatch. They realised they couldn't deliver what they promised and didn't know how to tell you.

Communications issue. Email and phone services can have problems, especially if working whilst travelling. Equally, phones/laptops can be lost or stolen.

None of this excuses abandoning a client. But understanding the "why" can help you approach recovery with clear thinking rather than anger. Now, let's fix your situation.

Immediate Steps When Your Web Developer Disappears

Document Everything

Before you do anything else, gather every piece of information you have:

• All emails, contracts, and invoices
• Any login credentials they shared (hosting, domain, CMS)
• Screenshots of your website as it currently exists
• Records of payments made
• Their business name, address, phone number, and company registration if they're a limited company

This documentation matters if you need to pursue legal action, but more importantly, it helps whoever rescues your website to understand what they're working with.

Attempt Contact Through Multiple Channels

Your developer may be avoiding email but still active elsewhere. Try:

• Phone calls at different times of day
• LinkedIn messages
• Their business social media accounts
• A physical letter to their registered address (especially for UK limited companies—you can find this on Companies House)

Send a final "intent to take action" email. Something like: "I haven't heard from you in [X weeks]. If I don't receive a response by [date], I'll be engaging another developer and pursuing recovery of my domain and hosting access." Sometimes this prompts a response when nothing else has.

Review Your Contract

Dig out whatever agreement you signed. Look for:

• Who owns the domain name and hosting?
• Who owns the website code and content?
• Are there any handover clauses?
• What are the payment terms and refund conditions?

If you never signed a contract—and many small business website projects operate on handshake agreements—you still have rights, but recovery becomes more complicated.

Secure What You Can Access

If you have any logins, use them now:

• Domain registrar (GoDaddy, Namecheap, 123-reg, etc.)—log in and verify your contact details are correct
• Hosting control panel (cPanel, Plesk, or similar)—download a backup of your website files if possible
• CMS admin (WordPress, Craft, Squarespace)—export your content
• Email hosting—ensure you can still access your business email

Change passwords on anything you can access. Your developer may still have credentials, and if the relationship has soured, you don't want them making changes.

How to Recover Your Website: Step-by-Step UK Guide

Finding Your Domain Registration Details

Your domain name (yourcompany.co.uk) is often the most critical asset. If you're not sure who registered it or where it's hosted, use a WHOIS lookup tool like who.is to find the registrar.

For .uk domains, you can also check directly with Nominet, the official UK domain registry.

Critical question: Is the domain registered in YOUR name or your developer's name? If it's in their name, recovery becomes more complex.

UK Domain Recovery via Nominet

If your .uk domain is registered to your developer but you can prove it relates to your business, you have options:

Contact the registrar directly. Explain the situation. Some registrars will help facilitate transfer if you can prove the domain relates to your trading name or registered company.

Nominet dispute resolution. For more serious disputes, Nominet offers a dispute resolution service. A summary decision costs £200+VAT, but can force transfer of a domain that rightfully relates to your business.

Legal action. For high-value domains or clear-cut cases, a solicitor's letter sometimes prompts cooperation.

The key evidence Nominet looks for: Does the domain match your company name, trading name, or trademark? Can you prove you commissioned and paid for the website? These strengthen your case considerably.

Recovering Hosting Access

Hosting is trickier than domains. If your developer set up hosting in their name, you typically can't just claim it—you'll need to either:

1. Get credentials from them (unlikely if they've ghosted you)
2. Start fresh with new hosting and migrate your site

If you have FTP or cPanel access, download everything immediately—all files, databases, and email data. Even if you can't use these files directly, a competent developer can work with them.

Using Web Archive to Recover Content

If you've lost everything—no access to hosting, no backups—there's still hope. The Wayback Machine archives websites periodically. Search for your domain to see historical snapshots.

You won't get your exact files back, but you can often recover:

• Text content from your pages
• The general structure and layout
• Images (sometimes)

This gives a new developer something to work from rather than starting completely from scratch.

When to Cut Your Losses and Start Fresh

Sometimes recovery costs more than rebuilding. Consider starting fresh if:

• Your website was built on a platform you can't maintain (custom code with no documentation)
• The design was outdated anyway
• Recovery would cost more than a new build
• You want to move away from the platform that caused these problems

A broken WordPress site that relied on 15 plugins from a vanished developer might not be worth rescuing. Sometimes the kindest thing for your business is a clean slate.

The WordPress Problem: Why Plugin-Dependent Sites Are Particularly Vulnerable

Here's something most guides won't tell you: WordPress sites are especially vulnerable to developer abandonment.

Why? Because most WordPress websites are held together by plugins—third-party code that handles everything from contact forms to security to SEO. When your developer disappears:

• You don't know which plugins are critical
• Plugins need regular updates (security patches, compatibility fixes)
• Outdated plugins break or become security risks
• Custom code often isn't documented

WordPress powers over 43% of all websites, according to W3Techs. It's popular because it's cheap and fast to build with. But that same flexibility creates fragility—especially when the person who understood how it all fits together vanishes.

This is why so many businesses find themselves on a "rebuild every three years" treadmill. Their cheap WordPress site works for a while, then breaks, then needs expensive rescue or replacement.

If this sounds familiar, you're not alone. We've written extensively about the hidden costs of WordPress that only become apparent after the initial build.

How to Prevent This Happening Again

Own Your Domain (Always)

Never let a developer register your domain in their name. Ever.

Your domain should be registered to your business, with your email address as the contact. Your developer can manage it for you, but ownership must be yours.

Choose a Platform That Doesn't Rely on Third Party Dependencies

The WordPress model—cheap initial build, ongoing plugin maintenance, eventual breakdown—isn't the only option. Platforms exist that don't rely on loads of third-party plugins for core functionality.

When the people who built your site control the entire codebase, there are no mysterious plugins to fail, no third-party dependencies to update, and no surprise compatibility issues. If you do rely on plugins make sure they are created by reputable developers and that you have a support or maintenance package to keep them updated or replaced if they cease to be supported.

Look for Long-Term Partnership, Not Project-Based Work

The "pay once and walk away" model creates misaligned incentives. Your developer gets paid whether your site works in two years or not.

A better model: ongoing partnership where your developer has skin in the game. If they're responsible for maintaining your site long-term, they're incentivised to build it sustainably.

This is exactly why pay-monthly website packages work well for small businesses. When your web partner's business depends on your site continuing to work, they build it properly from the start.

Verify Business Stability

Before hiring any developer:

• Check Companies House if they're a limited company
• Look for an actual business address (not just a PO Box)
• Verify they've been trading for more than a year
• Ask for references from long-term clients, not just recent ones
• Confirm their support arrangements—what happens after launch?

How to Choose a Reliable Web Developer: Red Flags and Green Flags

Red Flags

• Unusually cheap quotes. If it seems too good to be true, it often is. Ask for more costing detail if you’re concerned.
• No physical address. Legitimate businesses have real locations.
• Promises of delivery in days for complex projects. Quality takes time.
• Won't explain what platform they'll use or why. Transparency matters.
• No maintenance plan. A site without ongoing support is a site waiting to break.

Green Flags

• Transparent pricing with no hidden fees
• Explains technical choices in language you understand
• Offers ongoing support as part of the package, not as an afterthought
• Has been in business for years with verifiable client relationships
• Owns their codebase—not heavily dependent on themes or plugins they didn't build

We've covered this in more detail in our guide on how to choose a web developer.

Frequently Asked Questions