What do I do if my website developer disappears?

You need one change on the website, but the person who built it no longer replies. The site is still live. You aren't sure where it is hosted, which account renews the domain or whether the files you received are enough for someone else to work on it.

The first job is to understand what access and material already exist. That lets a replacement assess the work without making a live-site problem worse.

This is general information, not legal advice. Rules change and vary by country. Check with a qualified professional before acting on it.

What should you collect before changing anything?

Build a factual record of the website and its accounts.

When a developer disappears, list the accounts, source files, editable content and outside services you can access. Separate what is confirmed from what is missing before authorising repairs or a move.

Find the project emails, invoices, onboarding documents and any handover links. Record the public website address and the contact methods visitors currently use.

Check whether you have invitations to the domain registrar, hosting, code repository, CMS or form service. An invitation email isn't proof that access still works, so sign in through the provider's official website and verify it.

Don't put passwords, recovery codes or secret keys into a document sent around to possible suppliers. Describe the account and your current access first, then agree how access will be granted safely.

Which missing access matters most?

Prioritise continuity of the existing website and enquiries.

Use a short inventory rather than collecting files at random.

Area	What to establish	Why it matters
Domain	Provider, authorised account access and renewal information	The public address must remain available
Hosting	Where the live site runs and who administers it	Someone needs to inspect and deploy changes
Source code	Repository or usable project files	A custom site needs editable source for ongoing work
CMS	A working login and the content it controls	You may already be able to make the required edit
Forms and booking	Receiving account and connected services	Enquiries must keep reaching the business

Mark each row as confirmed, uncertain or missing. The distinction helps a replacement ask the next useful question.

A screenshot of an account panel or a ZIP file isn't necessarily a complete handover. Our handover checklist explains what usable access and project material look like.

Can the website provider help recover an account?

Use the provider's official recovery process when you are authorised to manage the account.

Requirements depend on the provider and the account arrangement. Gather the records that identify the business and service, then ask official support what evidence they need. Don't assume a payment receipt or the public website alone is sufficient.

Avoid creating duplicate accounts and changing domain or hosting settings on a guess. You can interrupt the working site or its email before the replacement is ready.

Also separate account access from a disagreement about deliverables or ownership. A technical supplier cannot settle that disagreement simply by rebuilding the page. If it becomes a contractual dispute, get appropriate professional advice about your agreement.

What can a replacement assess without full access?

A public review can identify symptoms, but it cannot reveal every part of the setup.

Show the replacement what you want changed and what currently fails. Include the exact page, device, steps and expected result. Use dummy information when demonstrating a form.

They can inspect the public design and behaviour, but a reliable repair quote may need source and hosting access. Ask them to explain what they can establish now and what remains uncertain.

Don't commission a complete rebuild simply because nobody has yet found the repository. Equally, don't assume a visible website can be maintained from screenshots alone.

The recurring-breakage guide gives you a simple way to document faults that a new person can reproduce.

If you're left with a website and no responsive developer, we can discuss what it would take to take the work forward. We repair custom-coded sites once the relevant code and setup can be assessed. Framer repairs are possible with a recommendation to move to custom code; other builders and AI-built marketing sites are rebuild conversations. Start with a free intro call, or describe the access you have at hi@aruno.studio, WhatsApp or Telegram @mihaipostelnicu.

Should you repair, rebuild or use the existing editor?

Choose the smallest route that can meet the actual need reliably.

If the task is a content change and you have a suitable editor, you may be able to complete it already. The guide to safe website editing helps distinguish a content field from a design change.

A repair makes sense when the source is available and the problem is bounded. A rebuild may be more sensible when the marketing site needs a different structure and design, or the current setup cannot support the intended work reasonably.

Ask for an explanation of the tradeoff. "This is easier for us" doesn't tell you what happens to your content, page addresses, forms or accounts.

Keep the current site working until the replacement route has been tested. Plan any move with the people managing the domain, hosting and email.

What should the next agreement make clear?

Resolve the handover questions before depending on another person.

Agree where the accounts and source will live, how access is granted, who handles renewals and how the work can be transferred. Record what you can edit and what needs a developer.

Also agree what support includes after delivery. Our maintenance-cost guide distinguishes upkeep from new design or feature work; don't assume they are the same service.

Test the handover while everyone is still available. A new document is useful only when its accounts, files and instructions can actually be used.

Frequently asked questions

Can someone maintain the site without its original developer? Often, if the necessary source, accounts and documentation are available. The replacement needs to assess the specific setup before promising a repair.

Can I copy the public page and move it elsewhere? A public page doesn't necessarily include the source, backend or rights needed for a move. Treat a move as a scoped project, not a guarantee based on what appears in the browser.

Should I remove the old developer's access immediately? Consider continuity and the account arrangement before changing access. Ensure the business has working administrative access and a tested transition plan; handle disputed access through the appropriate provider or professional process.

What if I only need a phone number changed? Check the CMS first. If the text is hard-coded, it still requires a code change and deployment, even though the visible edit is small.

How much does taking over an existing website cost? The quote depends on the access available, the condition of the source and the work you need. Ask the replacement to separate assessment, the immediate change and any wider rebuild rather than pricing everything as one unknown task.

How long does it take to replace a missing developer? A small change with working access is different from recovering accounts or rebuilding missing source. Establish those dependencies first, then ask for a timeline tied to what the replacement can actually inspect.

Turn the unanswered emails into an access inventory and one clear task. A replacement can work from facts much more usefully than from guesses.