Your web designer has stopped answering emails. Maybe you need to change your business hours, fix a broken contact form, or update a service page before a busy season. The website still loads, but nobody seems available to maintain it.
The immediate question is not whether you need a new website. It is what you can still control. A small cleaning company, landscaping business, or home repair contractor may be able to hire a replacement developer and continue using the existing site. Another business may discover that its domain registration, hosting account, and website files are all managed through someone else's accounts.
Those situations require different responses. Before canceling services or changing technical settings, establish what is working, what access you have, and what evidence you can gather.
First, determine whether the website is actually at risk
An unresponsive designer does not necessarily mean a website is about to disappear. The designer may no longer be providing maintenance while hosting and domain renewals continue separately. But the fact that the site is online today does not prove that the business controls the accounts required to keep it online tomorrow.
Start with three questions:
- Is the website functioning? Open it on a phone and desktop. Test the main pages and send a test inquiry through the contact form, making sure it reaches the intended inbox.
- Are renewals covered? Find recent domain, hosting, maintenance, and email invoices. Note expiration or billing dates where available.
- Is anything changing without your approval? Look for unexpected page edits, redirects, password-reset notices, or unfamiliar account users. Treat signs of unauthorized access as a security issue rather than an ordinary communication delay.
Save screenshots of important pages and record current issues. Do not assume that a screenshot is a usable website backup; it documents what a visitor sees, not the underlying files or database.
Identify the four things your business needs to control
A website involves several accounts and assets that may be held by different providers. Recovering one does not automatically recover the others.
1. The domain registration
The domain is the address customers recognize. Find the registrar, the account holder or registrant information, the renewal arrangement, and the login or recovery method. The person who designed the website might have registered the domain on the business's behalf, but that arrangement does not guarantee the business can manage it directly.
ICANN's domain registration guidance specifically addresses situations in which a developer registered a domain and later became unreachable. Its advice is to contact the registrar promptly about updating the registration contact details and access. The registrar will need to follow its own verification and applicable procedures; recovery is not automatic.
2. Hosting and DNS
Hosting is where the website operates. DNS records direct visitors—and often business email—to the appropriate services. They may be controlled in the same account as the domain or somewhere else entirely.
Find out who pays for hosting, which provider operates it, who can sign in, and where DNS records are managed. Do not change nameservers or DNS records simply to see whether you can take control. A poorly planned change can interrupt the website or email.
3. The website itself
Ask whether you have access to the content management system, site files, database, uploaded images, theme or design assets, and any software licenses required to run it. The assets you are entitled to receive will depend in part on your agreement and the platform used.
A content export is not always a complete website copy. For example, Learn WordPress explains that a standard WordPress export can move content but does not include the site's design, themes, or plugin files. A working recovery may need more than posts and page text.
4. Services connected to the website
Check the business email, contact-form delivery, analytics, Search Console, online booking, payment services, and third-party integrations. Some accounts may be owned by the business; others may belong to the designer or agency.
Make a simple account inventory: provider, account email, billing owner, current access, renewal date, and what would stop working if the service were disconnected. Record credentials in a secure password manager, not in an unprotected spreadsheet shared by email.
Try a documented handoff before rebuilding anything
Send one clear, written request to the designer or agency. Identify the business and website, describe the maintenance or access problem, and request the specific items you need: account access or transfer procedures, a current website backup where applicable, information about active subscriptions, and a list of systems they manage.
Include a reasonable response date and keep copies of the request, your contract, invoices, and prior correspondence. A professional handoff can resolve a communication breakdown without forcing a migration.
Avoid sending a message demanding every password in one email. Account transfers, individual user invitations, or secure credential-sharing methods are generally safer than circulating shared administrator credentials. The right method depends on each platform.
If the provider remains unreachable, contact the companies that operate the services directly. A domain registrar can discuss domain-account recovery. A hosting provider can explain its verification and support procedures. Neither should be expected to bypass account-security checks simply because you explain that the designer is missing.
If ownership is disputed, the contract is unclear, or a provider refuses to release assets, consider qualified legal advice before taking irreversible action. Paying for website work does not, by itself, establish every contractual or intellectual-property right.
Choose a recovery path based on the access you actually have
You control the domain and hosting
This is usually the most flexible situation. A replacement professional can review existing access, preserve a backup, correct urgent problems, and decide whether the current site can be maintained. You may not need a redesign at all.
Before granting access, create a separate account for the new provider where the platform allows it, use multifactor authentication, and limit permissions to what the work requires. Review old access after a verified handoff rather than abruptly removing the only person who can still operate an essential service.
You control the domain but not the hosting
You may be able to rebuild or migrate to a new host, assuming you have the necessary content and rights. First determine whether you can obtain a complete backup from the old environment. If not, inventory the pages, images, files, and functions that must be recreated, and confirm which materials you are permitted to reuse.
Google's guidance on changing hosting recommends preparing and testing the new environment before changing DNS, monitoring both environments during the move, and retiring the old hosting only after traffic has shifted. Keep the same public URLs where practical; if URLs must change, plan redirects rather than treating the move as a simple hosting switch.
You can access the website editor but not the domain account
Make a safe copy of content and document the website's existing configuration. Then prioritize domain-account recovery with the registrar. Administrative access to a website editor does not necessarily grant the authority to change domain registration or DNS.
You cannot access any of the accounts
This is the hardest situation, and there may be no clean technical shortcut. Collect contracts, payment records, registration notices, and business-identification information. Contact the registrar and other known providers using their official support channels. Ask what verification they require, what services are affected, and which recovery options are actually available.
If recovery fails, a new website or domain may become necessary. That is a business-continuity decision, not a guaranteed recovery of the old website. A new domain does not automatically retain the old site's links, search visibility, or customer recognition.
Don't accidentally break email or customer inquiries during a move
A website move involves more than making the homepage appear on a new server. Before changing DNS, identify any records used for email and other business systems. Keep a copy of the current DNS settings where you have authorized access.
In a private testing environment, check the pages that produce business inquiries: phone links, quote forms, booking buttons, mobile navigation, and confirmation messages. Confirm that submissions arrive in the intended inbox. Review tracking and verification tools so that the new site does not silently lose measurement or search reporting.
If the public URLs change, Google's site-move documentation explains the need to map old addresses to new ones, implement appropriate redirects, and monitor performance. A change of hosting with unchanged URLs has a different procedure. Neither process guarantees identical search performance immediately after the move.
What should your next website agreement prevent?
Once the immediate situation is stable, review how the business will avoid the same dependency again. A useful website care agreement should make clear:
- Which accounts are registered to the business and which are managed by the provider.
- Who pays for the domain, hosting, software subscriptions, and renewals.
- What access the business will retain during the relationship.
- What is included in backups, how often they occur, and how restoration is tested.
- How urgent incidents, normal update requests, and end-of-contract handoffs are handled.
- What files, content, data, and licenses can be transferred, and whether handoff work has a separate fee.
These terms do not have to be complicated, but they should be written down before there is a problem. The goal is not to eliminate the need for a web professional. It is to make sure the business can replace a professional without losing control of its customer-facing website.
The practical next step
If your designer is unresponsive, do not start by ordering a replacement website. First establish domain control, hosting access, backup availability, and the systems connected to the site. Then choose the least disruptive recovery path that your actual accounts and agreements support.
A working website is valuable. A working website that your business can maintain, recover, and transfer is much more resilient.
Sources and Further Reading
Related service: Explore services
