Know when WordPress is online.
Know when it is healthy.
A successful HTTP response proves that a URL answered. StoreUptime keeps following the WordPress signals behind that response — application health, AJAX, selected pages, required content, protected pages and runtime errors.
Explore the WordPress signalsA website can answer
while WordPress still has a problem.
Availability is the first question, not the last. StoreUptime separates reachability from application, page, content and runtime signals so one green response cannot hide every other layer.
See which layer
actually needs attention.
Each monitoring layer answers a different question, helping you distinguish a full outage from a WordPress application, content or runtime problem.
Can the public site be reached on schedule?
Are the application-level signals answering normally?
Are configured records and important content still present?
Are new runtime errors appearing alongside the monitoring signals?
Seven WordPress signals.
Seven useful answers.
Check availability, application health, AJAX, selected records, required content, protected pages and runtime errors without treating every issue as the same failure.
WordPress Health
Are the core WordPress health signals in a healthy state? Database · maintenance · SSL · page contextAJAX
Can the WordPress application AJAX path complete its check? Application responseSelected Pages
Do the WordPress records you care about still exist and publish correctly? Up to 100 recordsCritical Content
Is required text or an Element ID still present where it matters? Public content monitoringProtected Pages
Can the selected local test user open a protected page and verify its required content? Protected-page checkPHP Errors
Are new runtime problems appearing alongside the monitoring signals? Error contextCheck the application
from the inside.
The on-demand WordPress health view gives you a compact check of the core signals that can explain why a site feels unhealthy even when the public URL still answers.
Database
Surface the current database health state as part of the WordPress health view.
Maintenance mode
See whether WordPress is currently reporting an active maintenance state.
SSL certificate
Check certificate state so an HTTPS problem is visible alongside the application signals.
Selected-page context
Bring the latest selected WordPress page state into the same health view.
Manual WordPress Health is available on every plan.
Check that WordPress can do more than serve a page.
The public-page application check opens the homepage like a normal visitor and confirms that the WordPress AJAX path can complete its application check. This adds an application-level signal to the external HTTP result.
Watch the records
your site depends on.
Select up to 100 WordPress records. StoreUptime checks their existence, publication and permalink state without reading the visible page body.
A page can load
and still be missing what matters.
Check for required text or an Element ID instead of relying on status code alone. Use public monitoring for customer-facing content and the local Monitoring test user for protected pages; real signed-in visits can additionally provide observations.
Required content
Manual page-content testing is available on every plan. Plus can monitor up to 3 public pages automatically; Advanced can monitor up to 5.
Text or Element IDMember-only content
A local Monitoring test user verifies protected-page access and any optional required content. Manual checks work on every plan; Plus can automate up to 3 included protected pages and Advanced up to 5.
No passwords · no login cookies · no page HTML · no screenshotsWait for a real problem
before sending the alert.
Paid monitoring can confirm repeated failures before an incident alert is sent, reducing noise from one temporary failed check.
Basic supports one alert address. Plus and Advanced support up to three.
Add private chat-channel delivery alongside the included monitoring alerts.
Basic 30 days · Plus 30 days · Advanced 90 days.
Add error context
without redefining uptime.
When PHP error diagnostics are available on the monitored WordPress site, StoreUptime can show a compact summary of newly detected runtime problems. Paid plans can also alert on newly detected errors.
Choose the monitoring coverage
that fits your site.
Free 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 →
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 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.
Basic
One monitored public page plus automatic WordPress, maintenance, AJAX and SSL health with email alerts.
Plus
Three-page coverage, automatic public content plus Signed-in Page Check from every 5 minutes, Telegram and Discord.
Advanced
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.
What WordPress monitoring actually covers.
What does WordPress uptime monitoring check?
StoreUptime combines external availability with WordPress-aware signals such as WordPress/database health, maintenance, AJAX, SSL, selected pages, public content, protected-page checks and PHP error context, depending on the active plan and configuration.
Why is a normal HTTP uptime check not enough for WordPress?
A successful HTTP response proves that a URL answered. It does not prove that the WordPress application, AJAX path, selected records, required content or protected pages are healthy. StoreUptime keeps those signals separate so you can see which layer needs attention.
What is included in the manual WordPress health check?
The on-demand WordPress check covers database state, maintenance mode, the internal AJAX runtime, SSL certificate state, selected WordPress pages, saved public/protected content rules and WooCommerce Health when WooCommerce is active. It is available on every plan.
How are selected WordPress pages monitored?
You can select up to 100 WordPress records. The selected-page check verifies existence, publication and permalink state without reading the visible page. Automatic selected-page checks start from hourly on Basic, every 15 minutes on Plus and every 5 minutes on Advanced, with slower intervals available.
Can StoreUptime check that important page content is still present?
Yes. Every plan can save and manually test public or signed-in rules across up to five local page slots. Plus can automate public/protected content on up to 3 included pages and Advanced on up to 5, using optional required text or an Element ID.
Can protected or member-only pages be checked without sharing login details?
Yes. Signed-in Page Check uses a local Monitoring test user whose normal permissions or membership represent the intended visitor. Manual checks work on every plan; Plus and Advanced can repeat included protected-page checks automatically every 5, 15, 30 or 60 minutes even when nobody visits. Passwords, persistent login cookies, private HTML, screenshots and user identity are not sent to StoreUptime.
How does StoreUptime avoid alerting on one temporary website or page failure?
State-based website, WordPress, selected-page, public/protected content and automatic WooCommerce Health Problems use the configured confirmation mode before alerting. Fast confirms after 2 matching failures. Balanced and Cautious require 3, with Cautious waiting longer between checks.
Can StoreUptime show PHP error context?
When PHP error diagnostics are available on the monitored WordPress site, StoreUptime can show a compact error summary. Paid plans can also alert on newly detected errors, while runtime-error context remains separate from the main uptime signal.
Monitor the URL.
Then monitor what WordPress is doing behind it.
Choose the coverage and monitoring frequency that fit your site, from external uptime and WordPress Health through content, protected-page and runtime signals.
