What do I do if my web developer stops responding?

When your developer stops responding, the biggest risk is not the delay. It is losing control of your website. If the developer holds the domain, hosting or admin logins, a silent developer can leave you unable to fix problems or even renew your site.

Here is what to do, in order, to protect your site and move forward.

Step 1: check what you control

Fill in this table today. Anything marked “No” is your priority.

Step 2: secure what you can

• Change passwords on every account you control.
• Create your own administrator account in WordPress.
• Turn on two-factor authentication where available.
• Remove or downgrade the developer’s access once you have your own.

Step 3: take a full backup

Download a copy of your files and database from hosting, or use a backup plugin. If your developer stops responding and later something breaks, a recent backup is your safety net.

Step 4: send one clear message

Write a short, polite message by email. Ask for the missing logins, files and a status update by a specific date, and say you will move the site to someone else if you do not hear back. Keep a copy. Often a clear deadline gets a reply.

Step 5: recover accounts you do not control

If the domain is in the developer’s name, contact the registrar with proof that you paid for it and use the business on it. ICANN publishes the rights of domain owners on its registrant rights page. Hosting companies can often transfer an account if you prove ownership.

Step 6: hand over to a new developer

Once you have access and a backup, a new developer can review the site, update software and take over support. If the project was not finished, read what to do with an unfinished website project.

How to avoid this when your next developer stops responding

• Register the domain and hosting yourself from day one.
• Keep a document with every login, stored safely.
• Choose a team or studio, not a single person, for business-critical sites.
• Agree response times in writing for support work.

When a single developer stops responding, a business with its own logins loses a few days. A business without them can lose its website.

Example: why owning accounts matters

Two businesses had the same problem: their developer stops responding for a month. The first owned the domain, hosting and admin login. It took a backup, hired a new developer and carried on within a week. The second had everything registered by the developer. Its domain renewal failed, the site went offline, and recovering the domain took weeks of emails with the registrar. The only difference was who owned the accounts.

If your developer stops responding today, the steps above will help. If everything is working fine right now, use this moment to move every account into your own name. It is the cheapest insurance you can buy for your website.