Oxyforge
On This Page
  1. What Should You Check To Monitor WordPress Sites?
  2. How Do You Know A Page Really Loads?
  3. Which Expiry Dates Take A Site Offline?
  4. What Do You Check For Security And Updates?
  5. How Do You Track Page Speed Without Obsessing?
  6. A Worked Example: Eight Sites On A Monday
  7. What Can A Weekly Check Not Tell You?
  8. What To Do Next
  9. FAQ

How To Monitor WordPress Sites: The Weekly Client Check

How To Monitor WordPress Sites: The Weekly Client Check

Ask a freelancer how they know their client sites are fine, and the honest answer is usually that nobody has complained. That works until the week a client’s domain lapses, the site and the email go dark together, and the first you hear of it is a phone call.

Very little of what takes a client site down is sudden. A domain gives a year’s notice. A certificate that won’t renew gives weeks. A plugin with a published hole is on a public list. The information exists. It just isn’t in one place, and nobody is reading it.

To monitor WordPress sites properly you don’t need a wall of graphs. You need seven checks, a warning line for each, and a fixed slot each week when you read them for every site. Acting on what you find is covered in our guide to bulk updating WordPress sites.

Here’s the list, how to do each check by hand, and what a weekly check can’t do, whatever tool or host you use.

Key Takeaways

  • Check seven things weekly: the page really builds, domain expiry, SSL certificate, known vulnerabilities, updates waiting, last backup and phone page speed.
  • Warn at 30 days for a domain and 14 days for a certificate. Treat 7 days on a domain as urgent.
  • A page cache can show you a working copy of a broken site. Check a freshly built page.
  • Watch the speed trend, not the score. A 20-point drop that holds means something was added.
  • A weekly check finds slow problems. It doesn’t replace an uptime monitor for sites that earn money by the hour.

What Should You Check To Monitor WordPress Sites?

Seven things, in the order of how much damage each does when it’s missed.

CheckWarning lineWhy it mattersBy hand
The page really buildsAny error text, a blank page, a server errorThe site is broken for visitors nowLoad the home page uncached and read it
Domain registration30 days to expiry. Urgent at 7Website and email both stopA public RDAP or WHOIS lookup
SSL certificate14 days to expiry, or any browser warningBrowsers show a full-page warningThe certificate details in the browser
Known vulnerabilitiesAny high or critical findingAttackers read the same listsCompare installed versions to a vulnerability database
Updates waitingMore than a week oldFixes not applied, and a bigger jump laterThe Updates screen in each dashboard
Last backupOlder than a dayNothing recent to restoreYour host’s backup list
Page speed, phoneUnder 50, or a drop of 20 pointsSlow pages lose enquiriesGoogle’s PageSpeed Insights

The first three take a site off the air. The last four make next month worse. If you only have five minutes, do the first three.

How Do You Know A Page Really Loads?

You ask for a copy that WordPress has to build fresh, and you read what comes back. Seeing the home page in your own browser proves much less than it seems.

The reason is the page cache. A cache stores a finished copy of each page and hands it to visitors. Many caches go on serving the stored copy while WordPress behind it is failing. You see a perfect home page. A visitor who asks for a page that isn’t stored gets “There has been a critical error on this website.”

What a fresh page check looks for:

  • WordPress’s critical error message, or “Error establishing a database connection”.
  • A PHP error printed into the page, or warnings printed at the top.
  • A server error, or a blank page.
  • “Briefly unavailable for scheduled maintenance”, which means an update is running or got stuck.

Two things aren’t faults: a site that’s password protected on purpose, and a maintenance mode somebody switched on. A good check reports those as what they are.

One more trap. If a domain has been pointed somewhere else, the check reads somebody else’s page and calls it healthy. A check has to prove which server answered. By hand, sign in and load the page, since most caches don’t serve stored pages to signed-in users.

That settles whether the site works today. The next two checks are about next month.

Which Expiry Dates Take A Site Offline?

Which Expiry Dates Take A Site Offline? - Oxyforge

Two: the domain registration and the SSL certificate. They’re renewed by different companies and fail differently.

The domain registration is the yearly fee that keeps the name. When it lapses, the website stops and so does every mailbox on that domain. For domains such as .com, ICANN’s Expired Registration Recovery Policy has the registrar send reminders about a month and a week before the date, but they go to the registrant’s email, and if that address is on the same domain, they stop arriving when they matter most. Warn at 30 days. The hard part is rarely the payment. It’s finding who holds the registrar login.

Watch for one quirk. Some registries move the expiry date forward a year the moment it passes, then take it back if nobody pays. A lookup done the day after can look healthy. The warning before the date is the one that counts.

The SSL certificate is usually renewed by the host or a plugin, typically about 30 days before it runs out. So the useful warning line is 14 days. A certificate with two weeks left is one whose renewal has got stuck, often because the domain’s DNS was changed. Let’s Encrypt stopped sending expiry reminder emails in June 2025, so for many sites nothing else will warn you. Our help article on SSL certificates explains what blocks a renewal.

What Do You Check For Security And Updates?

Known vulnerabilities first, then updates waiting, then the backup. All three ask whether the site carries a risk you could remove today.

  • Known vulnerabilities. A finding means an installed plugin, theme or WordPress version has a published security hole. Read the severity and the version that fixes it. Our guide to WordPress plugin vulnerabilities covers the awkward cases.
  • Updates waiting. Three updates on a site is normal. Twenty means it’s been missed for months and needs catching up in stages.
  • The last backup. Confirm last night’s exists for every site. Once a quarter, restore one to a staging copy to prove it works.

A malware scan is a different check: it looks for a break-in that’s happened, not a door left open. You want both, and the scan should run nightly without you.

How Do You Track Page Speed Without Obsessing?

Record one number per site per week, the phone score from Google’s PageSpeed Insights, and look at the direction.

Google’s test scores each page out of 100: 90 and over is good, 50 to 89 needs improvement, under 50 is poor. Phone scores run lower than desktop scores for the same page, because the test simulates a mid-range phone on a mobile network. The phone score is the one to track.

A single reading is noisy. What means something is a change that holds: a site at 78 for two months that’s now at 55. In our experience it’s usually a slider, a chat widget, a video in the header or a photo uploaded straight from a camera.

The job is to notice the drop in the week it happens, while the client still remembers what they changed. Google explains the measurements behind the score in its guide to Core Web Vitals.

A Worked Example: Eight Sites On A Monday

Say you’re a small web agency with eight client sites and all seven checks in one list. The minutes are illustrative.

  1. Page check, two minutes. Seven build cleanly. A small clinic’s site shows a critical error on the fresh copy, though the cached home page looks fine. A plugin update overnight broke it. Restore the backup, then look for the cause.
  2. Domains, one minute. A florist’s domain has 24 days left. Email the owner now and ask who holds the registrar login.
  3. Certificates, one minute. One has 11 days left. The client moved their DNS last month, so the renewal can’t complete. Write to them with the record to fix.
  4. Vulnerabilities and updates, four minutes. Five findings, four closed by updates already waiting. They go in Thursday’s update run. The fifth has no fix, so it gets a note.
  5. Backups, one minute. Last night’s is there for all eight.
  6. Speed, two minutes. A shop has gone from 71 to 49 on phone. Open it, find the new banner video, write to the owner.
  7. Log it, one minute. Date, what was found, what was sent.

The log matters as much as the check. When a client asks what they pay you for, it’s the answer, and a monthly report built from it is the version they’ll actually read.

What Can A Weekly Check Not Tell You?

It can’t tell you that a site went down at 2am and came back at 3. Outages need a different tool.

Uptime monitoring asks a site every minute or so whether it answers, and alerts you when it doesn’t. If a client loses orders or bookings during an hour of downtime, they need one. On their own sites on 13 November 2026, ManageWP sold an Uptime Monitor add-on that checks every 60 seconds and alerts by email, SMS or Slack, WP Umbrella included uptime monitoring in its per-site price, and MainWP listed uptime monitoring in its free dashboard. Standalone uptime services exist too.

Here’s our own limit, plainly. On Oxyforge, WP Manager puts most of this list in one table for every site on the account: updates, vulnerabilities with the fixed version, SSL and domain expiry, the fresh page check, and phone and desktop speed with history. It doesn’t send alerts or make client reports, uptime monitoring isn’t available in it yet, and it only covers sites hosted with us. If you need your phone to buzz the minute a site drops, add an uptime monitor.

And no check reads the content. Nothing above will notice that the opening hours on the Contact page are wrong. That’s still a person’s job, and it’s on the WordPress maintenance checklist.

What To Do Next

  1. Pick a day and a time. Put the check in the calendar, repeating. How it fits with updates and backups is in our guide to managing multiple WordPress sites.
  2. Run all seven checks by hand once, for every site. It’ll take an afternoon and you’ll find something.
  3. Write every domain’s expiry date and registrar in one sheet. This alone prevents the worst day.
  4. Decide which sites need an uptime monitor: the ones that take money or bookings.
  5. Then stop doing it by hand. If your sites are on one host, ask what it shows across sites. WP Manager is free on every plan on the Oxyforge pricing page.

FAQ

What should I check on a WordPress site every week?

Seven things: whether the home page builds without an error, the domain’s expiry date, the SSL certificate, known vulnerabilities, updates waiting, the last backup, and the phone page speed score against last month’s. With every site in one list, ten sites take a short session rather than a morning.

Is a weekly check enough, or do I need uptime monitoring?

They do different jobs. A weekly check finds slow problems, such as an expiring domain, a stuck certificate renewal or a plugin with a known hole. It won’t tell you a site went down at 2am. If a client loses money when the site is down for an hour, add an uptime monitor with alerts.

Why does my site look fine to me when it’s broken for others?

Usually the page cache, which can go on serving a stored copy while WordPress fails behind it. A visitor who lands on a page that isn’t stored sees the error, so check a freshly built page.

How early should I worry about a domain expiring?

Thirty days before the date. That leaves time to find who holds the registrar login, which is often the hard part, and to renew. Inside seven days treat it as urgent, because a lapsed domain takes down the website and the email together.

What is a good page speed score for a client site?

Google’s test calls 90 and over good, 50 to 89 needs improvement and under 50 poor. The phone score is the stricter and more useful one. When you monitor WordPress sites week to week, the trend matters more than any single number.