There's a message we see again and again, from very different businesses. A marketing lead at an online shop whose site health warnings have sat open for months while the long-time developer has stopped answering. A small business owner whose web person simply disappeared, along with the admin logins. Someone whose site was hacked and who can't find anyone they trust to look at it. A company that just wants "an agency for maintenance and updates" because the current arrangement has quietly stopped working. And from the other side, freelancers inheriting sites from agencies that wound down, trying to work out what they've actually taken on.
The details differ, but the pattern is the same. Nobody is sure whether it's an emergency, whether they're allowed to ask someone else, or whether asking will blow up a relationship that used to work fine.
We look after other people's sites for a living, and we've been on both ends of this: the second opinion, and the developer being second-guessed. Here are the myths we hear most, and what's usually true.
Myth 1: "If the site is still up, things are fine"
Reality: the most expensive problems are the quiet ones. Pages loading is the last thing to break. Before that, the background jobs go: scheduled tasks that send order emails, process subscription renewals, clear old data or run backups. On a shop, a pile of failed scheduled tasks can mean renewals and receipts haven't gone out for a while, and nobody noticed because the homepage looks normal.
If you can log in, your site's own health screen and its list of scheduled or failed tasks are worth ten minutes of your time. You don't need to understand every line. You need to know whether the warnings are new or have been there for months.
Myth 2: "Asking someone else is a betrayal"
Reality: a second opinion is normal in every other trade. You'd get one for a roof or a medical diagnosis. Good developers know this, and the ones we respect most welcome a written review because it either backs up their plan or catches something they missed.
What damages relationships isn't the review. It's going around someone: changing passwords without telling them, or posting their work publicly with complaints attached. Tell them you're getting an independent check, and ask them for a short written plan in the meantime. Their response tells you a lot.
Myth 3: "We'll just rebuild it from scratch"
Reality: rebuilding feels decisive, but it's often the most expensive way to get an answer you didn't need. A site with years of orders, members, content and search history carries a lot of value that doesn't move cleanly. Some owners who rebuilt after a developer vanished found the new site fine and the old problems gone. Others found they'd swapped one set of unknowns for a brand-new set, with a fresh learning curve and lost history.
A rebuild might be the right call. But make it after someone has looked at what you have, not before.
Myth 4: "Fully updated means we're safe"
Reality: updates matter, but they're one layer. Agencies who keep everything current still see sites flagged as compromised, because the way in was an old admin account, a leaked password, an application password nobody remembered creating, or a file that was planted before the updates happened.
This is also why careful maintenance providers have stopped promising "you'll never be hacked." What a reasonable arrangement can promise is different: backups stored somewhere other than the server, alerts when files change, regular checks of who has admin access, and a clear response window when something does go wrong. If your current arrangement promises prevention but says nothing about response, that's worth noticing.
Myth 5: "I need access to everything before anyone can help"
Reality: helpful, but not required to start. If your developer still holds hosting or domain logins, a second opinion can begin with what you can see: the site's admin area, the health report, the list of plugins and when they last updated, and any warnings from your host or search console.
What you do need, early, is to know where the keys live. Who controls the domain registrar? Whose name is on the hosting account? Where do backups go? If the answer to any of those is "the developer's personal account," that's the first thing to fix, politely and in writing, while the relationship is still working.
Myth 6: "An audit is a sales pitch for a new contract"
Reality: it can be, so ask for the right thing. A useful independent review is short, written and specific: what's urgent, what can wait, what's fine, and roughly what each fix involves. It should make sense even if you hand it straight back to your current developer.
If the review only says "everything is terrible, sign here," get another one. If it says "these three things are urgent and your current person can do them," that's a review you can trust.
A calm order of work
When the replies stop, here's the sequence we suggest:
- Write down what you know. When you last heard from them, what's broken, what's been warned about, and what you pay for.
- Check what you can see yourself. Health screen, failed or pending scheduled tasks, plugin updates, any security or search warnings.
- Find the keys. Domain, hosting, email delivery, payment accounts, backups. Note who owns each one.
- Send one clear message. Ask for a written plan with dates for the urgent items, and mention you're getting an independent check. Give a reasonable deadline.
- Get the second opinion in writing. Short, prioritised, and readable by any competent developer.
- Decide. Stay with a clearer plan, move to someone else with a proper handover, or rebuild, in that order of preference unless the review says otherwise.
Where this tends to go wrong
- Waiting for the perfect moment. Months pass, and the quiet problems compound.
- Changing everything at once. New host, new developer and a redesign in the same month makes it impossible to tell what fixed or broke what.
- No written record. Verbal promises disappear with the person who made them.
- Assuming silence means bad intent. Sometimes the developer is overloaded, unwell, or stuck waiting on their own server provider. A direct question often gets an honest answer.
Your turn
We'd love to hear from both sides of this:
- If you've been the owner in this situation, what was the first sign something was wrong, and how long did you wait before asking someone else?
- If you've been the developer whose work got a second opinion, what made it feel fair rather than hostile?
- What should a maintenance arrangement actually promise, now that nobody can honestly promise "never hacked"?
- Did a rebuild ever turn out to be the right call for you, or did you wish you'd fixed what you had?
Top comments (0)