After talking to dozens of freelance developers, the same mistakes come up again and again when it comes to monitoring client sites. Most of them aren't technical failures — they're process failures that are easy to fix once you see them.
Here are the seven most common ones.
Mistake 1: Not Monitoring at All
The most common mistake, especially for newer freelancers: assuming that if nothing is obviously broken, everything is fine. Sites go down for many reasons — hosting issues, memory limits, plugin conflicts, bad deployments, DDoS, expired SSL — and most of these don't generate any notification you'll see unless you're monitoring.
The fix: Add even a basic free monitor for every client site. ndelog's free Spark plan covers 15 HTTP monitors. There's no reason not to.
Mistake 2: Only Monitoring the Homepage
Your homepage can return 200 OK while the checkout page, login flow, or contact form is completely broken. A 500 error on /checkout or /api/orders won't show up in a monitor pointed at your homepage.
The fix: Add a second monitor for your most revenue-critical page. For a WooCommerce site, that's /shop or /cart. For a SaaS, it's /login or /api/health. One extra monitor, same alert channel.
Mistake 3: Using Email as the Only Alert Channel
Email notifications sit in your inbox and compete with everything else. An alert sent at 2 AM might be read at 8 AM. For a client whose business depends on their site being up, that 6-hour gap is professionally damaging.
The fix: Add WhatsApp as an alert channel. Messages interrupt. Emails don't. Even on ndelog's free Spark plan, you get 5 WhatsApp alerts per month — enough to know what it feels like. On Watchman ($2/mo), you get unlimited WhatsApp alerts.
Mistake 4: Not Monitoring SSL Certificates
SSL certificate expiry is one of the most embarrassing — and most preventable — causes of downtime. When a certificate expires, browsers show a full-screen security warning that drives away 90% of visitors immediately.
The worst part: the client sees it, their customers see it, and you find out last.
The fix: Add an SSL certificate monitor for every client domain. ndelog's Spark plan includes 1 SSL monitor; Watchman includes 5. Set it to alert you 30+ days before expiry so you have time for a calm renewal, not a panic call.
Mistake 5: Not Monitoring Domain Expiry
Domains expire. Renewal emails go to client addresses (not yours), get marked as spam, or get ignored. A lapsed domain takes a site completely offline and requires a painful recovery process — sometimes including ransom pricing from domain resellers if someone snaps it up first.
The fix: Add a domain expiry monitor for every client domain. ndelog alerts you 30+ days before expiry. You remind the client, they renew, disaster avoided.
Mistake 6: Monitoring But Never Checking the History
Having monitoring active is necessary but not sufficient. The historical uptime data tells you if a client's site has a recurring issue at certain times (shared hosting memory limits at peak traffic, cron jobs conflicting with visitor load) that might not look like an emergency in any single alert.
The fix: Once a month, review the uptime history for each client. Look for patterns: repeated short outages at the same time, slow response times on specific days, degraded performance you can correlate with deployments.
Mistake 7: Not Including Monitoring in Your Client Handoff
Many freelancers do the monitoring themselves without ever discussing it with the client. This means no credit for the value you're providing, and no documented process for when the engagement ends.
The fix: Include uptime monitoring as a line item in your service proposal or retainer agreement. "Monthly website monitoring and uptime reporting" — even a basic monthly summary from your ndelog dashboard — is a tangible deliverable clients understand. It also justifies your retainer fee in a way that "keeping an eye on things" doesn't.