Titanium Site Watch can schedule WordPress Health, Signed-in Page Check, Critical Content, Selected WordPress Pages and WooCommerce Health from inside WordPress. For those scheduled local checks, the most reliable setup is a real hosting/server cron that wakes WordPress once per minute.
wp-cron.php every 1 minute. This wakes the lightweight Site Watch scheduler; it does not run every Site Watch check every minute.WordPress normally checks scheduled tasks when a request reaches WordPress. On a low-traffic website there may be no request at the time a check is due. On heavily cached or CDN-served sites, many visitor requests may never load WordPress at all.
That means a task scheduled for 10:00 can start later than 10:00. Site Watch cannot make WordPress execute a local check until WordPress itself gets a chance to run its scheduler.
If WordPress wakes late, WordPress-local results can be late too. Status timestamps may trail behind the configured cadence, a problem may be detected later, and a short-lived failure can be missed between delayed runs.
A real one-minute cron gives the scheduler a frequent, predictable opportunity to start whichever Site Watch job is actually due.
The one-minute cron is only the scheduler heartbeat. When it runs, Site Watch checks the authoritative schedule and starts only the local check families whose configured slot is due.
Site Watch knows which local check family is due and which cadence applies.
A one-minute runner gives WordPress a chance to process that due slot without waiting for a visitor.
Expensive page, protected-page and WooCommerce diagnostics are not repeated every minute just because cron wakes every minute.
Scheduled local monitoring normally sends the due PASS, FAIL or INCONCLUSIVE result outbound. A bounded server fallback can request only a missing predefined result if the due push does not arrive.
First create and verify a real cron job with your hosting provider or server scheduler. Configure it to invoke WordPress cron once per minute. After you have confirmed that the real cron is running successfully, set DISABLE_WP_CRON to true in wp-config.php so page views do not also trigger the normal visitor-based scheduler.
Hosting panels vary. A common HTTP-style job requests https://example.com/wp-cron.php?doing_wp_cron. Servers with WP-CLI can use a local command such as wp cron event run --due-now. Use the method supported by your host and make sure it targets the correct WordPress installation.
Website Down Watch's outside monitoring runs from the monitoring service and does not depend on your WordPress cron. If the hosting is completely unavailable, external monitoring can still observe that outage.
WordPress Health, Signed-in Page Check, Critical Content, Selected Pages and WooCommerce Health execute inside the monitored WordPress installation. Their scheduled execution therefore needs a healthy WordPress scheduler.
DISABLE_WP_CRON=true is used only after the replacement cron is verified.