Store can still lose the sale
A 200 response says the storefront answered. It does not prove WooCommerce store health.
StoreUptime keeps WooCommerce availability plus eleven-check store health — core, database, products, cart, add to cart, checkout, payments, shipping, order flow, store email and background processing — visible alongside WordPress health.
One homepage is not the store. A store can answer HTTP requests and still be unable to move a customer through the purchase path.
Generic uptime usually stops at reachability. StoreUptime keeps going into the WooCommerce and WordPress signals that explain whether the store is actually ready to sell.
The point is not to create more noise. It is to stop one successful URL check from masking the part of WooCommerce that needs attention.
A 200 response says the storefront answered. It does not prove WooCommerce store health.
WooCommerce product data stays visible as its own commerce signal instead of hiding behind site uptime.
StoreUptime validates the customer-facing add-to-cart path separately, without creating a customer order.
Cart and checkout remain distinct signals so one working page cannot make the whole store look healthy.
Payment and shipping configuration are checked read-only when the store context proves they matter, without processing payment or calculating carrier rates.
Recent failed-order patterns, stale Pending payment orders and transactional-email configuration provide separate operational evidence.
WooCommerce background processing is tracked independently from the public storefront response.
The diagnostic combines a real isolated cart/add-to-cart/checkout flow with read-only checks for payments, shipping, recent order flow, transactional email and background processing. Every result stays readable on its own.
Is WooCommerce loaded and ready for the diagnostic?
Independent resultDoes WooCommerce report a database-update state that needs attention?
Independent resultIs there a safe published simple product or concrete variation the probe can use?
Independent resultCan an isolated in-memory WooCommerce cart initialize and accept the temporary test item?
Independent resultDoes the real customer-facing validation path accept the product?
Independent resultCan WooCommerce initialize the checkout field engine and cart-to-checkout state?
Independent resultWhen the isolated cart needs payment, is at least one WooCommerce payment gateway enabled? No transaction is attempted.
Independent resultWhen an active physical product requires shipping, is an enabled WooCommerce shipping method configured? No carrier rate is calculated.
Independent resultDo recent WooCommerce orders avoid a sustained failed-order spike or a material set of stale Pending payment orders?
Independent resultAre New Order email, recipients and sender configuration valid? No test email is sent.
Independent resultDoes WooCommerce background processing avoid sustained overdue or repeating failures?
Independent resultThe diagnostic builds a temporary in-memory WooCommerce customer, session and cart context, runs the customer-facing add-to-cart validation path, inserts the temporary item, calculates cart totals and initializes the checkout field engine. Separate read-only checks inspect payment and shipping configuration, recent order flow, store email and background work.
When the probe finishes, the original WooCommerce request state is restored.
Available on every plan when WooCommerce is active. Run the eleven-check local WooCommerce Health diagnostic from WordPress whenever you want a fresh store-health result.
Free · Basic · Plus · AdvancedAdvanced repeats the same eleven-check WooCommerce Health diagnostic every 5, 15 or 60 minutes and keeps the latest store-health result alongside your other monitoring signals.
Advanced · 5 / 15 / 60 minStoreUptime keeps advisory Warning states in the dashboard without sending notifications. Automatic WooCommerce Problems use the selected Fast, Balanced or Cautious confirmation before alerting; a true recovery can use the same selected channels.
Pair the store-specific signal with external uptime, WordPress Health, AJAX, selected pages, critical content, signed-in page checks and PHP error context when the active plan and configuration include them.
Explore WordPress uptime monitoringFree includes the full local diagnostic toolkit, including the eleven-check WooCommerce Health diagnostic when WooCommerce is active. Paid plans automate public and WordPress-aware checks; Plus adds automatic public/protected content monitoring and Advanced adds scheduled eleven-check WooCommerce Health.
Reliable local scheduling: a real 1-minute server cron is recommended. 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 →
Compare manual diagnostics, automatic WordPress health, page frequency and coverage, response-time history, protected-page checks, alert routing, incident history and WooCommerce automation in one place.
| 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 the local WordPress check. | Manual | Manual | Manual | Manual |
| Manual AJAX functionality checkRuns the protected internal WordPress AJAX runtime 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 checkThe 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 WooCommerce Health 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. | ✓ | ✓ | ✓ | ✓ |
| PHP error diagnosticsShows a compact local critical-error behavior and request-impact summary when compatible diagnostics are available. Paid monitoring can also route supported new-error and behavior/impact escalation alerts. | Summary | Summary + alerts | Summary + alerts | Summary + alerts |
| Frontend monitoring status badgesTwo optional WordPress 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 StoreUptime can open automatically for one website. | × | 1 | 3 | 5 |
| Automatic public-page frequencyChoose how often StoreUptime 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 WordPress 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 WordPress 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, 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, content checks, WooCommerce Health and PHP error 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 as the selected local Monitoring test user and verifies access. Optional Element ID or required-text rules are 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 StoreUptime. | × | × | 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 on schedule. 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 |
GBP is the billing currency. Any USD amount is an estimate using the latest available daily European Central Bank reference rate.
One monitored public page plus automatic WordPress, maintenance, AJAX and SSL health with email alerts.
Three-page coverage, automatic public content plus Signed-in Page Check from every 5 minutes, Telegram and Discord.
Five-page coverage, one-minute public monitoring and scheduled eleven-check WooCommerce Health.
Billing is annual in GBP. Any available first-year discount is shown on the plan card. Optional USD amounts are estimates only; checkout and billing remain in GBP.
The local eleven-check WooCommerce Health diagnostic covers WooCommerce core, database state, products, cart, add to cart, checkout, payments, shipping, recent order flow, store email and background scheduler. Cart/add-to-cart/checkout exercise an isolated functional path; payment, shipping, order-flow, email and background checks remain read-only or non-transactional as appropriate.
No. The diagnostic never submits checkout, creates an order, processes a payment, contacts a payment processor, calculates a carrier rate, changes stock or sends email. Its temporary cart context is isolated and the original WooCommerce request state is restored afterwards.
No. The probe uses an isolated in-memory WooCommerce session, customer and cart context. It suppresses the normal post-add action for the temporary item so it cannot persist a customer cart or set a cart cookie.
Advanced can run the complete eleven-check WooCommerce Health diagnostic automatically every 5, 15 or 60 minutes. The same eleven checks are available manually on every plan when WooCommerce is active.
Advanced can run the eleven-check WooCommerce Health diagnostic every 5, 15 or 60 minutes. The latest store-health result stays available alongside the website and WordPress monitoring signals.
No. WooCommerce Health remains a separate store signal. Website uptime keeps its own authority, so a store-specific problem does not falsely redefine the whole website as offline.
A confirmed automatic WooCommerce Problem can alert through Email, Discord or Telegram when those channels are available on the plan. A true recovery can use the same selected channels. Warning and warning-recovery states do not send notifications on any channel.
Yes. Depending on the plan and configuration, WordPress-aware monitoring can add external uptime, WordPress Health, AJAX, selected pages, critical content, signed-in page checks and PHP error context alongside the store signal.
Start with uptime. Add the WooCommerce and WordPress signals that match the level of coverage your store needs.