Store uptime
ExternalScheduled availability keeps running from outside WordPress.
TrackedKnow when the site is reachable, then keep following WooCommerce core/database, products, cart and add to cart, checkout, payments, shipping, recent order flow, store email, background processing and WordPress health. One green homepage no longer gets the final word.
A successful homepage response answers one question. It does not tell you whether WooCommerce core/database, product state, cart/add-to-cart, checkout, payment/shipping configuration, recent order flow, store email or background work are healthy.
Instead of hiding everything behind one generic status, StoreUptime gives every important part of the store its own question and its own result.
Scheduled availability keeps running from outside WordPress.
TrackedDatabase, maintenance mode, internal AJAX and SSL health stay visible separately from public uptime.
TrackedThe local diagnostic first proves the WooCommerce runtime itself is available.
TrackedDatabase-version state stays separate from general WordPress database connectivity.
TrackedThe diagnostic finds a safe published simple product or concrete variation before the functional flow starts.
TrackedThe temporary WooCommerce cart is isolated from real customer state.
TrackedCustomer-facing validation and real WC_Cart insertion must accept the temporary product.
TrackedCheckout fields and cart-to-checkout state are initialized without submitting an order.
TrackedThe read-only check verifies that an enabled gateway exists when payment is required; it never attempts a transaction or contacts a payment processor.
TrackedA bounded read-only check looks for an enabled WooCommerce shipping method without calculating carrier rates.
TrackedRecent failed-order ratios and materially stale Pending payment orders provide an operational signal without creating or changing orders.
TrackedThe check validates enablement, recipients and sender configuration without sending a test email.
TrackedSustained overdue or repeating WooCommerce Action Scheduler failures remain visible separately from storefront uptime.
TrackedChoose what matters and let scheduled checks run in the background. Website, page and content failures are confirmed before alerting; automatic WooCommerce Health Problems use the same Fast, Balanced or Cautious confirmation choice as the other state-based monitoring signals.
Connect your WordPress site and choose the public pages, store checks and alert destinations you want to monitor.
StoreUptime keeps checking availability and the WordPress or WooCommerce signals included in your plan.
For state-based website, WordPress, page, content and automatic WooCommerce Health Problems, Fast confirms after 2 matching failures; Balanced and Cautious after 3, with Cautious waiting longer between attempts.
Confirmed state-based monitoring Problems and configured error events can trigger alerts; true recoveries close the relevant incident.
Traditional uptime sees this clearly. StoreUptime keeps that signal separate and authoritative for website availability.
Product, add-to-cart, cart, checkout, payment or shipping trouble can need a store-aware signal even while a public URL still answers.
Recent order flow, transactional-email configuration and background processing can fail away from the visible storefront, so they stay visible as separate WooCommerce Health evidence.
Current state, response time, 30 days of daily Average/Fastest/Slowest response history, WordPress health and WooCommerce signals stay together so you can move from alert to diagnosis faster.
Explore WordPress-aware monitoringWebsite, WordPress, selected-page, content and automatic WooCommerce Health Problems use Fast, Balanced or Cautious confirmation. Warning states remain visible and never send notifications.
Confirmed state-based monitoring Problems, configured PHP error alerts and true recoveries can use Email when enabled.
Plus and Advanced can route eligible actionable events to one private Discord channel for each website.
Plus and Advanced can route eligible actionable events to one private Telegram chat for each website.
Add WordPress health, AJAX, selected pages, required content, member-page checks and PHP error context alongside store uptime and WooCommerce health.
See 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.
No. External uptime remains a separate signal, while StoreUptime can also surface WordPress and WooCommerce health signals so a successful homepage response does not hide a broken store function.
No. The eleven-check WooCommerce Health diagnostic combines an isolated cart/add-to-cart/checkout probe with read-only payment, shipping, order-flow, store-email and background-work checks. It does not create an order, payment, email or customer cart/session change, contact payment processors or calculate carrier rates.
Advanced. It can run the complete eleven-check WooCommerce Health diagnostic automatically every 5, 15 or 60 minutes. The same eleven checks remain available manually on every plan when WooCommerce is active.
Public-page, selected-page and required-content monitoring use the confirmation mode: Fast confirms after 2 matching failures, while Balanced and Cautious require 3. Automatic WooCommerce Health Problems use the same Fast, Balanced or Cautious confirmation choice as the other state-based monitoring Problems.
Plus and Advanced include Discord and Telegram. Confirmed state-based monitoring Problems, true recoveries and configured PHP error alerts can use those channels. Warning states stay visible without sending a notification.
Yes. StoreUptime can pair external uptime with WordPress Health, AJAX, Selected WordPress Pages, Critical Content, Signed-in Page Check and PHP error context depending on the configured plan and features.
WordPress WP-Cron is request-triggered and can run late on quiet or heavily cached sites. A real server cron that wakes WordPress once per minute gives scheduled WordPress-local checks a reliable execution opportunity. It does not run every check every minute: Signed-in Page Check and Critical Content start at 5 minutes, Selected Pages use plan-specific intervals, and automatic WooCommerce Health uses 5, 15 or 60 minutes on Advanced.
Combine uptime, WordPress health and WooCommerce checks at the level of coverage your store needs.