10 articles
Keeping an eye on many WordPress sites at once without drowning in alerts.
Uptime, vulnerabilities, pending updates and alerts across a fleet, and the tooling that keeps it honest. The Fleet Sentinel case study is the worked example.
Not covered yet: alert routing and practical on-call routines for small WordPress teams.
Message
Ask me about your site
Tell me what is wrong or what you need built. I reply by email.
Monitoring9 min read
WooCommerce checkout monitoring without placing live orders
WooCommerce checkout monitoring should run a scheduled browser journey against a staging or sandbox store, using synthetic products, customer details and a test payment method.
Monitoring7 min read
Trace WooCommerce order emails not sending from order to inbox
The phrase "WooCommerce order emails not sending" can describe several different failures. First prove that the expected order event happened, then trace one controlled order through WooCommerce, WordPress, your mail provider, and the destination mailbox.
Monitoring11 min read
Run a WordPress backup restore test and prove recovery works
A WordPress backup restore test should end with a working isolated copy, a timed recovery log, and a pass/fail record for the business tasks that matter. Restore a representative backup away from production, verify the files and database together, run defined checks, and record anything missing or unavailable.
Monitoring7 min read
How to test WordPress plugin updates before they reach production
To test WordPress plugin updates safely, copy production to staging, a private test copy, review what changed, update in controlled batches, and run the site flows that matter before production. Keep a pre-update backup and the previous plugin package or version ready so you can reverse a bad release quickly.
Monitoring7 min read
WordPress cron monitoring: prove scheduled jobs ran
If WordPress cron not running is delaying posts, emails, imports, or backups, first prove whether WP-Cron can spawn and whether events are already overdue. Then move the trigger to a system scheduler when timing matters, and monitor both overdue events and a success heartbeat from the jobs you care about.
Monitoring7 min read
The WordPress debug log: turn it on safely, find it, and read it
To turn on the WordPress debug log, set WP_DEBUG and WP_DEBUG_LOG to true in wp-config.php, then set WP_DEBUG_DISPLAY to false so errors are not printed into pages.
Monitoring8 min read
WordPress plugin vulnerability monitoring: from alert to fix
WordPress vulnerability monitoring works when you keep a current inventory of installed plugins and themes. Compare exact versions with trusted vulnerability data, then record what you did with each match.
Monitoring8 min read
WordPress uptime monitoring: checks that catch site failures
WordPress uptime monitoring should verify that important visitor paths return the right content, not merely an HTTP success status. Check dynamic pages, response time, TLS and domain expiry, then use heartbeats for scheduled work and alert rules that confirm failures before paging someone.
Monitoring7 min read
WordPress visual regression testing before and after updates
WordPress visual regression testing takes reference screenshots of important pages, repeats them after an update, and flags visual differences for review. It catches broken layouts, missing styles, shifted controls, and other front-end regressions that an uptime check can miss.