Website uptime monitoring that watches after the audit ends
Uptime probes with an incident log, SSL and domain expiry alerts, broken-link and mixed-content sweeps, Core Web Vitals tracking and change detection — with alerts to email, Slack, Telegram or a webhook the moment something breaks.
A site audit tells you the condition of a website at the moment you ran it. It says nothing about the certificate that expires next Tuesday, the domain renewal someone forgot to set to auto-renew, or the page that started returning an error three days after the audit finished. Websites don't stay broken or stay healthy — they change, silently, between the times anyone thinks to check. Monitoring is what watches during the gap.
Uptime probes with an incident log
WDIBoard checks that your site responds and keeps a running incident log of what it finds — when a check failed, when it recovered, and how long the site was down. That log is the record you don't have if you only find out about downtime from a customer complaint: the next time someone asks "was the site actually down, and for how long," you have an answer instead of a guess.
The probe is single-origin: checks run from one location, not spread across a network of regional probes. That's a straightforward way to catch the thing that matters most — is the site reachable and responding — without the site owner needing to reason about which region's result to trust.
SSL and domain expiry alerts
Certificates and domain registrations both expire on fixed dates that are easy to forget, because nothing about the site changes until the exact day they do. WDIBoard tracks both and alerts ahead of the expiry date, so a renewal becomes a calendar task instead of an emergency. The expiry problem is common enough, and painful enough, that it gets its own section below.
Broken-link and mixed-content sweeps
WDIBoard sweeps your site for broken links — internal and outbound — and for mixed content, where an otherwise secure HTTPS page loads an image, script or stylesheet over plain HTTP. Both are the kind of problem that accumulates quietly: a page gets linked to, then removed, and nobody notices the link is now dead until a visitor hits it. A sweep finds these before a visitor does.
Core Web Vitals tracking
Core Web Vitals — the loading, interactivity and visual-stability measurements that describe real page performance — are tracked over time rather than as a single snapshot. That makes a regression visible as a trend: a page that was fine last month and has been quietly getting slower with every deploy, long before anyone notices it "feels slow."
Change detection
Pages you care about — a pricing page, a legal page, a client's homepage — can change without anyone deciding to change them: a plugin update, a theme edit, a hosting migration. Change detection flags when a monitored page's content changes, so an unexpected edit gets noticed on its own instead of being discovered by accident weeks later.
Alerts to email, Slack, Telegram or a webhook
Every check — uptime, expiry, broken links, Core Web Vitals, change detection — can alert to email, Slack, Telegram or a generic webhook, with a test-alert action so you can confirm a destination actually works before you need it to. That means monitoring fits into whatever channel your team or your client already watches, instead of adding one more dashboard nobody opens.
The expiry problem: why advance warning matters
Of everything monitoring catches, certificate and domain expiry deserve the most attention, because the failure mode is unusually harsh. An SSL certificate that lapses doesn't degrade a site gracefully — it takes it down in every modern browser, immediately, with a hard warning page that most visitors will not click through. It doesn't matter if the rest of the site is perfect. And it tends to happen at the worst possible time: certificates are typically issued for a fixed term, the renewal date drifts to a weekend as months pass, and nobody's watching a Saturday.
A lapsed domain registration is worse. The site, the email addresses on that domain, and anything else built on it all stop working at once, and recovering a domain after it lapses can be far slower and less certain than renewing a certificate.
Both are entirely preventable, and both fail for the same underlying reason: the renewal date isn't on anyone's calendar until it's already too late. Staged advance alerts fix that by turning a silent deadline into a scheduled reminder with enough runway to act — checked automatically, not dependent on someone remembering to look.
Why the incident log matters beyond the moment
The alert prevents the outage. The incident log is what you have afterward. When a client — or your own team — asks "what happened last month, and for how long were we down," a log with real timestamps is the difference between a confident answer and a reconstruction from memory. For an agency running monitoring across several client sites, that log is also what turns "we monitor your site" from a claim into something you can actually show a client on request.
None of this is framed as a guarantee about how much uptime a site will get. It's a record of what a single-origin probe observed, and an alert system built to catch the two failures — expiring credentials and unnoticed downtime — that are easiest to prevent and most damaging to miss.
The continuous counterpart to the free audit
WDIBoard's free site audit is a snapshot: run it once, get a scored report on performance, SEO, security headers, accessibility and content, right now. Monitoring is what happens after that snapshot — the same categories of problem, watched continuously instead of checked once. An audit tells you the site is healthy today. Monitoring is what tells you the moment that stops being true.
That distinction is the commercial hook for agencies specifically: a free audit is a one-time conversation starter, but nobody pays monthly for a report they already have. Monitoring is the part that turns into a recurring line item — a "website care plan" that an agency sells alongside hosting or retainer work, billed every month, built on watching for the things a client will never notice until they break. It's a genuinely recurring-revenue product, not a repackaged one-off audit.
Who this is for
Agencies building a care plan
Monitoring across every client site, with an incident log to back up what you tell them, is the backbone of a recurring website care plan — see how agencies use WDIBoard.
Site owners who've been burned by an expired cert
If a certificate or domain has ever lapsed without warning, staged expiry alerts are the single feature that prevents it from happening again.
Developers tracking performance over time
Core Web Vitals tracked as a trend catches a slow regression from a deploy long before "the site feels slow" turns into a support ticket.
Frequently asked questions
Does WDIBoard monitor from multiple regions?
No. Checks run from a single origin. That's enough to catch whether your site is reachable and responding, without asking you to interpret results from several probe locations at once.
How far in advance does SSL and domain expiry alerting warn me?
Alerts are staged in advance of the expiry date, giving you enough runway to renew before a certificate or domain actually lapses, rather than a single warning on the day it happens.
What does the broken-link and mixed-content sweep check?
It checks for broken internal and outbound links across your site, and for mixed content — secure HTTPS pages that load an image, script or stylesheet over plain HTTP.
How is monitoring different from the free site audit?
The audit is a one-time snapshot you run on demand. Monitoring checks the same kinds of issues continuously — uptime, expiry, broken links, Core Web Vitals, content changes — and alerts you the moment something changes, instead of waiting for you to run another audit.
Where can alerts be sent?
Email, Slack, Telegram or a generic webhook, with a send-test-alert action so you can confirm a destination works before an incident happens.
Can an agency use this to monitor client sites and bill for it monthly?
Yes — that's the intended use for agencies. Monitoring across every client site, with an incident log per site, is the kind of ongoing work that supports a recurring website care plan rather than a one-off project fee.
Does WDIBoard guarantee a specific uptime percentage?
No. Monitoring reports what the probe observes and alerts you to it — it isn't sold against an uptime guarantee or service-level percentage.
Start watching, not just checking
Run a free audit first, then turn on monitoring so the next problem gets caught before a visitor — or a client — finds it.
Get early access