Your web designer has gone silent - what to do now
The pattern before the silence starts
Three emails sit in your sent folder, all unanswered, and the domain renewal is due next week. Before it gets to that point, there's usually a pattern. Replies that once arrived same-day start taking days. Then a week. Then longer than that.
Excuses show up along the way, too. A family emergency. A server migration that's taking longer than planned. A big client eating all the hours this month. Then, eventually, nothing at all — no reply, no explanation, no acknowledgment that the emails even arrived in the first place.
Sometimes the first sign isn't silence at all. It's a reply that answers a different question than the one you asked, or a vague promise to "get to it soon" that never turns into anything concrete.
Watch for the shift from specific answers to general ones, too. A designer who used to name exact dates and exact files, and now only offers reassurance without either, is telling you something even while still replying.
None of these signs alone means abandonment. People get sick. They take leave. They get swamped by one genuinely bad stretch. What matters is the trend across several contacts over several weeks, not any single slow reply on its own.
The accounts worth checking while you still can
The moment you notice the pattern, check what you can actually log into right now. Hosting account. Domain registrar. CMS admin panel. Any third-party tools tied to the site, like a booking widget or an email service. Confirm you have working credentials for each one today, while the designer might still answer a password-reset request.
Do this quietly and calmly. You're not accusing anyone of anything yet. You're just making sure you're not locked out later, once the answers stop coming entirely.
Write the logins down somewhere safe as you confirm each one. A password manager works. So does a single note kept somewhere other than an inbox tied to the same account you're worried about.
Waiting until contact has fully stopped to discover you never had your own login is the single most common way this turns into a real emergency instead of an inconvenience. The access and contract terms that keep this from becoming urgent in the first place are worth reading before you're in this spot, not during it.
Why "unlimited revisions" doesn't cover this
A contract promising unlimited revisions is about design changes during an active build — tweaking a layout, swapping a color, adjusting copy. It says nothing at all about what happens if the person doing the work simply stops responding.
Revisions language and responsiveness are two separate promises. Most contracts only spell out the first one. The second one, how fast someone answers and what happens if they stop, rarely gets written down at all.
That gap isn't unusual. It's just easy to miss when you're focused on getting the build itself right, before you've ever needed to think about what happens if it stalls.
If your agreement doesn't say anything about response times, escalation, or what counts as abandonment, that's a gap worth naming now, in your own notes, even if you can't fix the contract after the fact.
It also explains why pointing back at the contract rarely gets you anywhere in the moment. There's often nothing in it that speaks to this specific situation, no matter how carefully it was written for everything else.
Draft the handoff request before you're desperate for it
Write a short, specific email now. List the accounts and files you need. Set a deadline for a response. State plainly that you'll need to move the project if you don't hear back by then.
Send it even if you expect no reply. It puts a clear, dated record on file of what you asked for and when you asked for it.
Keep a copy somewhere outside your regular inbox, too, in case access to that inbox is ever tied up in the same mess.
That record matters later if you need to lean on a registrar, a host, or who actually owns the site once it's finished to get your own material back. A dated request shows good faith. It also shows you tried before you acted.
How long is long enough before you call it abandoned
There's no single answer that fits every project. But a pattern of unanswered messages across multiple attempts, spread over multiple weeks, with no explanation offered anywhere, is a reasonable point to stop waiting and start planning a move.
Don't wait for a dramatic confirmation that isn't coming. It won't arrive. Sustained silence past a reasonable point is the confirmation, and treating it as one is not overreacting on your part.
If a deadline is genuinely close, like a domain renewal or an upcoming launch, that changes the math. Waiting the same length of time makes less sense when something concrete is about to lapse.
Treat that deadline as the real clock, not the calendar date you'd otherwise pick. A renewal that lapses because nobody was watching is a harder problem to undo than a project that simply changes hands a little early.
Finding someone to finish the build
Once you've decided to move on, untangling the site from a designer who's gone quiet is its own project — a different situation from choosing to switch designers while a project is still moving along, where you're the one ending things rather than chasing someone who already stopped answering. It takes a bit of digging. It's worth doing properly rather than rushing it.
The actual steps for moving a site away from a designer who's disappeared cover what to gather and how a new person picks it up cleanly, without starting the whole build over from nothing.
A new designer picking up someone else's unfinished work is not a mark against you. Plenty of freelancers and small agencies have a standard process for exactly this kind of handoff.
This kind of gap is also just one version of a wider problem. How ongoing upkeep is supposed to work once a site is live is worth understanding so a single unresponsive contact never becomes the only path your site has to get fixed.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go