External uptime keeps answering the availability question independently.
YOUR STORE CAN BE ONLINE.
THE BUYING FLOW CAN STILL BE BROKEN.
Website Down Watch can look beyond HTTP 200 and run an eleven-check WooCommerce Health diagnostic inside WordPress. It verifies WooCommerce core, database state, products, an isolated cart, customer-facing add-to-cart validation, checkout initialization, payment configuration, shipping configuration, recent order flow, transactional email and background processing — without creating an order, payment or email.
THE STOREFRONT CAN RETURN 200 OK.
ADD TO CART OR CHECKOUT CAN STILL FAIL.
A successful public request proves that a page answered. It does not prove that WooCommerce will accept a product into a cart, initialize checkout, have usable payment/shipping configuration, show a healthy recent order flow, keep transactional email configured or process background work. WooCommerce Health keeps those signals separate.
The functional probe can be healthy while uptime is healthy — or report a store problem without pretending the entire website is down.
RUN THE BUYING-FLOW ENGINE.
LEAVE THE CUSTOMER AND ORDER SYSTEM ALONE.
The probe executes inside the WordPress installation. It builds an isolated temporary WooCommerce context, uses WooCommerce’s own customer-facing validation and cart engine, then checks checkout readiness before discarding the temporary state. Read-only operational checks then inspect payment, shipping, recent order flow, store email and WooCommerce background work without invoking payment processing, calculating carrier rates or sending email.
Advanced reuses the existing protected health request; manual checks use the same local engine.
No real customer cart, cookie or persistent session is used for the probe.
Customer-facing validation runs and WooCommerce itself must accept the product into the isolated cart.
The checker records a compact result and timestamp without submitting checkout or creating an order.
NOT “WOOCOMMERCE INSTALLED.”
FUNCTIONAL STORE HEALTH.
Each subcheck answers a specific question. A failure points to the part of the WooCommerce stack that needs attention instead of collapsing everything into one vague availability result.
Confirms WooCommerce is active and loaded in the WordPress runtime.
Checks whether WooCommerce reports a pending database update.
Finds a published purchasable product suitable for the isolated purchase-flow probe.
Initializes the WooCommerce cart engine and verifies the configured Cart page.
Runs customer-facing validation and requires WooCommerce to accept the product into the isolated cart.
Initializes checkout fields and cart-to-checkout state without creating an order or payment.
If the isolated cart requires payment, verifies that at least one WooCommerce payment gateway is enabled. No payment transaction or processor request is attempted.
When an active physical product proves shipping is required, checks for an enabled WooCommerce shipping method without calculating a carrier rate.
Looks for a sustained recent failed-order spike or a material group of stale Pending payment orders through WooCommerce’s order API.
Checks New Order email enablement, recipients and the WooCommerce sender address without sending a test email.
Looks for sustained WooCommerce Action Scheduler failure patterns or materially overdue work.
Cart, add to cart and checkout exercise the WooCommerce engine; payment, shipping, order-flow and email checks are read-only operational checks. The complete diagnostic remains deliberately non-transactional.
USE THE REAL WOOCOMMERCE ENGINE.
STOP BEFORE A REAL ORDER EXISTS.
The useful boundary combines a real isolated buying-flow probe with read-only operational diagnostics. Product, cart, add to cart and checkout exercise WooCommerce directly; payment, shipping, order-flow and store-email configuration are inspected without checkout submission, payment processing, carrier-rate calculation, email delivery or customer side effects.
The same customer-facing validation hooks that extensions can reject are exercised by the add-to-cart step.
This is why the check can catch genuine store-function failures without becoming a synthetic purchase bot. It exercises important WooCommerce runtime paths while keeping transactional state out of the monitor.
TEST THE STORE FLOW.
DON’T TOUCH A CUSTOMER OR CREATE A SALE.
The functional probe is isolated from real customer state. It does not need a customer password and it stops before order creation or payment. Payment processors are not contacted, carrier rates are not calculated and the store-email check does not send mail. Only the compact WooCommerce Health result and timing information need to travel with monitoring.
- Change a real customer cart or session
- Create a WooCommerce order
- Attempt a payment or contact a payment processor
- Calculate a carrier shipping rate
- Send a checkout or test email
- Submit a customer checkout
Advanced carries the latest result in the existing protected Site Watch health response; it does not add a separate WooCommerce monitoring request.
RUN ALL ELEVEN CHECKS
EVERY 5, 15 OR 60 MINUTES.
Advanced can run the same eleven-check diagnostic automatically every 5, 15 or 60 minutes. That probe interval is independent from normal public-page frequency, but an automatic WooCommerce Problem uses the same Fast, Balanced or Cautious confirmation choice as the other state-based monitoring signals. Warning states remain visible without notifications.
RUN IT MANUALLY ON ANY PLAN.
LET ADVANCED KEEP RUNNING IT FOR YOU.
WooCommerce Health does not need a separate product or plan. The manual eleven-check WooCommerce Health diagnostic is available when WooCommerce is active; Advanced adds automatic 5, 15 or 60 minute execution.
Run all eleven local WooCommerce Health checks whenever you want to inspect the store.
No automatic WooCommerce scheduleThe same eleven-check diagnostic remains available alongside paid website monitoring.
Plus also supports automatic Signed-in Page Check and Critical Content on eligible protected pages from every 5 minutesRun the complete eleven-check WooCommerce Health diagnostic automatically and keep the latest result visible between probes.
Manual Run WooCommerce check remains available tooSEE WEBSITE UPTIME AND
WOOCOMMERCE HEALTH SIDE BY SIDE.
WooCommerce Health does not pretend that a checkout problem means the entire website is offline. It stays a separate functional signal, with its own eleven-check result and last automatic check time.
THIS IS A FUNCTIONAL STORE PROBE.
IT IS NOT A SYNTHETIC PURCHASE.
Across all eleven checks, Site Watch verifies WooCommerce core and database state, finds a safe product, adds it to an isolated cart, initializes checkout, and reads payment, shipping, recent order-flow, store-email and background-job state. It deliberately does not submit checkout, create an order, process a payment, contact a payment processor, calculate carrier rates, change a real customer cart/session or send email. WooCommerce My Account and other protected-page access/content checks remain available separately through the local Monitoring test user; Plus and Advanced can automate included protected pages.
CHOOSE HOW CLOSELY
YOUR WORDPRESS SITE IS WATCHED.
Free includes the full local diagnostic toolkit. Basic, Plus and Advanced automate public and WordPress-aware checks, while Plus adds automatic public/protected content monitoring and Advanced adds scheduled WooCommerce Health. Every plan still includes the manual eleven-check WooCommerce Health diagnostic when WooCommerce is active. Current GBP pricing and any active first-year discount are loaded from the public pricing service; checkout opens in the Freemius overlay without leaving this page.
Scheduled WordPress-local monitoring: for the most reliable timing, use a real 1-minute server cron. It wakes the scheduler only; Signed-in Page Check and Critical Content still start at 5 minutes, and WooCommerce Health remains 5 / 15 / 60 minutes on Advanced. Read the cron setup guide →
SEE EXACTLY WHAT EACH PLAN INCLUDES.
Compare manual diagnostics, automatic WordPress health, page frequency and coverage, response-time history, protected-page checks, alert routing, incident history and WooCommerce automation.
| Feature | Free | Basic | Plus | Advanced |
|---|---|---|---|---|
| Manual WordPress & database healthRun on demand to verify the live WordPress runtime and database connection without creating an incident or alert. | Manual | Manual | Manual | Manual |
| Manual maintenance-mode checkReports whether WordPress maintenance mode is active as part of Run local WordPress check. | Manual | Manual | Manual | Manual |
| Manual AJAX functionality checkRuns Site Watch’s protected internal WordPress AJAX test on demand. | Manual | Manual | Manual | Manual |
| Manual SSL certificate checkInspects the site’s HTTPS certificate on demand; the local diagnostic may open a short TLS connection to the site. | Manual | Manual | Manual | Manual |
| Selected WordPress Page CheckChecks up to 100 WordPress page records for existence, publication state and a valid permalink; it does not read the visible page. | Up to 100 · manual | Up to 100 · automatic: 1–24 h | Up to 100 · automatic: 15 min–24 h | Up to 100 · automatic: 5 min–24 h |
| Locally saved monitored page slotsKeep the homepage plus four optional same-site pages configured locally. Paid plan limits decide how many are monitored automatically. | Up to 5 | Up to 5 | Up to 5 | Up to 5 |
| Manual public required-content testOpen a saved public page and verify optional required text or an Element ID without creating an incident or alert. | Up to 5 local pages | Up to 5 local pages | Up to 5 local pages | Up to 5 local pages |
| Manual signed-in / member-only access checkRun local WordPress check opens each protected page as the selected local Monitoring test user and verifies access even when no content assertion is configured. | Up to 5 local pages | Up to 5 local pages | Up to 5 local pages | Up to 5 local pages |
| Element ID & required-text assertionsOptional content assertions can be saved for public or signed-in/member-only pages and tested manually on every plan. | Manual | Manual | Manual | Manual |
| Local Monitoring test userChoose the WordPress account whose normal permissions or membership are used for protected-page checks. The user ID stays local and no account password is stored or sent. | Local only | Local only | Local only | Local only |
| Manual eleven-check WooCommerce HealthWhen WooCommerce is active, run all eleven checks: core, database, products, cart, add to cart, checkout, payments, shipping, order flow, store email and background scheduler. No order, payment, email or customer cart/session change is created. | ✓ | ✓ | ✓ | ✓ |
| Titanium Error Intelligence integrationShows the compact local Error Intelligence summary when that plugin is active. Paid monitoring plans can also route supported new-error and behavior/impact escalation alerts. | Summary | Summary + alerts | Summary + alerts | Summary + alerts |
| Frontend Site Watch badge shortcodesTwo optional frontend shortcodes can show the locally synchronized automatic-monitoring state without making a visitor-browser monitoring API request. | 2 shortcodes | 2 shortcodes | 2 shortcodes | 2 shortcodes |
| Automatic checks from outsideChecks continue on schedule when nobody is signed in to WordPress and can still detect when the hosting itself is unavailable. | × | ✓ | ✓ | ✓ |
| Public pages checked automaticallyThe number of saved page addresses the monitoring service can open automatically for one website. | × | 1 | 3 | 5 |
| Automatic public-page frequencyChoose how often the monitoring service opens the included public pages. | × | 15 / 30 / 60 min | 5 / 15 / 30 / 60 min | 1 / 5 / 15 / 30 / 60 min |
| Automatic WordPress / maintenance / AJAX / SSL healthThe protected Site Watch health request checks WordPress/database state, maintenance mode, the internal AJAX runtime and SSL without a WordPress username or password. | × | ✓ | ✓ | ✓ |
| HTTP status & response timeRecords the HTTP result and response time for completed automatic public-page requests. | × | ✓ | ✓ | ✓ |
| Response-time historyThe Dashboard keeps local daily Average, Fastest and Slowest response statistics for every automatically monitored page. | × | 30 days | 30 days | 30 days |
| Fast / Balanced / Cautious confirmationState-based website, WordPress, selected-page, Critical Content and automatic WooCommerce Health Problems use the shared confirmation choice before alerting. | × | 3 choices | 3 choices | 3 choices |
| Per-signal alert routingChoose available channels separately for website availability, WordPress health, AJAX, SSL, selected pages, Critical Content, WooCommerce Health and Error Intelligence events. | × | ✓ | ✓ | ✓ |
| Problem & recovery alertsSends a notification after an eligible monitoring problem is confirmed and can send another after a true recovery is confirmed. | × | ✓ | ✓ | ✓ |
| Email addresses for alertsMaximum email recipients for one monitored website. | × | 1 | 3 | 3 |
| Confirmed incident historyKeeps confirmed problems and recoveries; routine successful checks are not listed. | × | 30 days | 30 days | 90 days |
| Automatic required content on public pagesAutomatically checks saved required text or an Element ID on included public pages every 5, 15, 30 or 60 minutes and can alert after the configured problem confirmation. | × | × | Up to 3 · 5 / 15 / 30 / 60 min | Up to 5 · 5 / 15 / 30 / 60 min |
| Automatic Signed-in Page CheckAutomatically opens an included protected page inside WordPress as the selected local Monitoring test user and verifies access. Optional Element ID or required-text rules are checked separately as Critical Content. The fastest automatic interval is 5 minutes: 5, 15, 30 or 60 minutes. No password, persistent login cookie, protected HTML, user identity or screenshot is sent to Website Down Watch. | × | × | Up to 3 · 5 / 15 / 30 / 60 min | Up to 5 · 5 / 15 / 30 / 60 min |
| Telegram alertsConnect one private Telegram chat for each monitored website and use it in per-signal alert routing. | × | × | ✓ | ✓ |
| Discord alertsConnect one Discord channel for each monitored website using its private incoming-webhook address and use it in per-signal alert routing. | × | × | ✓ | ✓ |
| Automatic eleven-check WooCommerce HealthRepeats the complete eleven-check WooCommerce Health diagnostic inside WordPress every 5, 15 or 60 minutes. Confirmed Problems and true recoveries can use the selected alert channels; Warning states remain visible without notifications, and the store signal never marks the website itself down. | × | × | × | 5 / 15 / 60 min |
Estimated USD prices use the latest daily reference rate from the European Central Bank (ECB). ECB updates its reference rates once each working day. Billing remains in GBP. Click the button to load the latest available rate.
Basic
Automates one public page plus WordPress, maintenance, AJAX and SSL health with email alerts.
Plus
Adds three-page coverage, automatic public and signed-in protected-page checks, Telegram and Discord.
Advanced
Adds five-page coverage, one-minute public monitoring and scheduled eleven-check WooCommerce Health.
Billing is annual and remains in GBP. Current prices are retrieved from the Website Down Watch public pricing service.
DON’T WAIT FOR A USER TO TELL YOU
YOUR WORDPRESS SITE IS BROKEN.
Watch it from outside. Verify WordPress from inside. Use one clear confirmation policy for state-based website, WordPress, page, content and automatic WooCommerce Problems before alerting.