Website Health Monitoring Tool: 3 Layers Agencies Need

A website health monitoring tool checks a site on a schedule and tells you when something gets worse: whether the site is up, how fast it loads (Lighthouse scores and Core Web Vitals), and whether search engines can still read and index it. No single tool covers all three layers well, so the setup that works for agencies is an uptime monitor for outages, a weekly performance scan for speed, and Google Search Console for indexing. DFY Hub covers the middle layer. Every plan, including the free Starter tier, gets a weekly scan of the homepage, early Saturday UTC, with Lighthouse scores, lab Core Web Vitals (Largest Contentful Paint and Cumulative Layout Shift), on-page warnings and tech stack detection.

Last updated: October 2026

The old early-warning system is the client's phone

Ask an agency how they found out a client's site broke last time. Odds are the client told them. The phones went quiet, a customer mentioned the booking form wouldn't load, or the owner's nephew noticed the homepage looked strange on his phone.

That's been the default for years, and I think it's running out of road. My bet is that clients will judge agencies less on the monthly report and more on one question: did you notice before I did? I can't put a number on that shift. But every time a client finds a problem first, they quietly ask what they're paying for.

Monitoring is how you get there first. The trick is knowing which layer catches which problem.

The three layers of website health

Layer	What it catches	How often to check	What usually does it
Availability	Site down, expired SSL certificate, lapsed domain	Every few minutes	A dedicated uptime monitor
Performance	Slower load times and Core Web Vitals failures after plugin, theme or image changes	Weekly	A scheduled Lighthouse scan, such as DFY Hub's Saturday scan
Search health	Pages dropped from Google's index, an accidental noindex, crawl errors	Weekly to monthly	Google Search Console

Most agencies have one of these covered and assume it covers the other two. It doesn't, and no wonder problems slip through. An uptime monitor will happily report "up" on a site that takes eight seconds to load. A speed scan won't notice that a developer set half the site to noindex. Search Console won't page anyone at 2 a.m. when the server dies.

What "healthy" means for performance

Google publishes the thresholds, so you don't need to invent your own. A page passes Core Web Vitals when:

• Largest Contentful Paint (how fast the main content shows) is 2.5 seconds or less
• Interaction to Next Paint (how fast the page responds to a tap or click) is 200 milliseconds or less
• Cumulative Layout Shift (how much the page jumps around while loading) is 0.1 or less

Lighthouse adds a 0 to 100 performance score on top. Treat that score as a trend line, not a verdict. It moves a few points between runs even when nothing changed, which Lighthouse's own documentation acknowledges. A drop that holds for two weekly scans is worth a look. A one-week dip of a few points usually isn't.

What DFY Hub's weekly scan does, and what it doesn't

Here's the honest version, because a monitoring tool you misunderstand is worse than none.

What it does: every Saturday at 2 a.m. UTC (Friday evening in the US), DFY Hub scans the client's homepage and records Lighthouse scores, lab Core Web Vitals (Largest Contentful Paint and Cumulative Layout Shift), on-page warnings and the detected tech stack. A lab test can't measure Interaction to Next Paint, which needs real visitors; Search Console's Core Web Vitals report covers that one. It runs on every plan, including Starter. If you opt into the Monday digest email, the website health grade shows up there, so the result lands in your inbox at the start of the week.

What it doesn't do:

• It doesn't check uptime. If the site goes down on Tuesday, the scan won't tell you.
• It doesn't send alerts. You see a worse score by looking, not by being paged.
• It doesn't show history. The dashboard shows the latest scan only, so the week-over-week comparison is yours to make. Last week's digest email works as the record.
• It doesn't crawl the whole site. Inner pages, like the service pages that actually take bookings, aren't part of the weekly scan.

That last one matters most for local service clients. The homepage is often fine while a heavy service-area page drags. For those pages, DFY Hub's SEO MCP can run an on-page analysis or a full Lighthouse audit on any URL from inside an assistant like Claude, billed in credits. The MCP SEO Tools for Claude: An Agency Playbook post covers how agencies budget those checks across a roster.

The tech stack detection is more useful than it sounds. When a score drops, the first question is "what changed?", and a new plugin or a theme switch showing up in the detected stack often answers it before anyone opens a ticket.

A triage routine that doesn't eat your week

For a roster of 5 to 50 clients, the goal isn't to stare at dashboards. It's to look at the right ones once.

Monday morning. Read the digest, compare each client's grade with last week's digest, and write down the ones that got worse. Ignore anyone who held steady.

Same day, for the drops. Check the detected tech stack for a change, ask the client whether anyone touched the site, and run an on-page check on the key service pages through the SEO MCP.

Monthly. Open each client's Search Console and look at indexing. This is the layer weekly speed scans can't see, and it's where the expensive surprises hide.

Always. A person decides what gets fixed and who fixes it. A scan can tell you the homepage's Largest Contentful Paint got worse. It can't tell you the client just uploaded twelve uncompressed photos of their new truck, or that they'd rather live with a slower page than lose the photo gallery.

If you're deciding which other checks deserve a schedule beyond site health, SEO Audit Automation: What to Automate, What Not To covers rankings, reviews and citations.

Monitoring vs reporting

Monitoring is for your team. It runs constantly, it's noisy, and most weeks nothing happens. Reporting is for the client. It should be calm, short and explain what changed and what you did about it.

Mixing them up is a common mistake. Forward raw monitoring data to a client and they'll see a 3-point Lighthouse dip as a crisis. How to turn the monitoring data into something a client reads is its own topic, covered in the automated SEO health report tool post.

Site health is also only half of what a client's customers see online. The other half is reputation, and the brand monitoring guide walks through checking that with the SEO MCP. For the local side (listings, map-pack position and reviews), see Local SEO Audit Tool: The 3 Checks That Matter.

Frequently asked questions

What does a website health monitoring tool check?

It depends on the tool, but website health has three layers. Availability covers whether the site is up and its SSL certificate is valid. Performance covers Lighthouse scores and Core Web Vitals. Search health covers whether Google can still index the pages. Most tools cover one layer well, so agencies usually combine an uptime monitor, a weekly performance scan and Google Search Console.

How often should website health be monitored?

Uptime should be checked every few minutes, because an outage costs calls immediately. Performance changes more slowly, so a weekly scan catches problems from plugin, theme or image changes without creating noise. Indexing problems build over weeks, so a monthly Search Console review works for most local service clients. Check more often around a redesign or a hosting move.

Does DFY Hub alert me when a client's site goes down?

No. DFY Hub doesn't monitor uptime and doesn't send alerts. Its weekly scan runs early every Saturday (UTC) on the homepage and records Lighthouse scores, lab Core Web Vitals, on-page warnings and the tech stack. You see the latest result on the dashboard or in the opt-in Monday digest email. Pair it with a dedicated uptime monitor if outages are a concern for a client.

Is DFY Hub's website scan free?

Yes, for one business. The weekly website scan is part of every plan, including the free Starter tier, which needs no credit card. Agencies running several client sites will be on a paid plan, and paid plans are billed per client, starting at $99/mo per client on Local Dominator. Each client added is billed at the same plan price.