Website monitoring that understands WordPress — checking uptime, WordPress health, WooCommerce store functionality, AJAX, selected pages and critical content from inside and outside your site.
A server can answer perfectly while the WordPress experience behind it has already failed. Website Down Watch checks beyond the page load.
The server returned a successful response, so the monitor stays green.
Uptime matters. So does everything that can fail after the server has already answered. Website Down Watch combines external monitoring with WordPress-aware checks from inside the site.
External checks confirm whether the website answers, the HTTP result it returns and how quickly it starts responding.
Plugin-side checks can report the live database connection, maintenance mode, SSL status and other WordPress-side health signals.
A page can return 200 while dynamic WordPress functionality has already failed. The internal AJAX check confirms WordPress can still execute its own runtime check.
Verify that important WordPress page records still exist, remain published and still have a usable permalink.
Receiving a page is not enough. Website Down Watch can verify configured text or an Element ID so important content is actually present.
Functional checks exercise WooCommerce core, products, an isolated cart, real add-to-cart validation, checkout initialization and background jobs without creating an order or payment.
Choose one local Monitoring test user whose normal WordPress permissions or membership represent the visitor you want to verify. Run local WordPress check opens the protected page as that account on every plan; Plus and Advanced can repeat the same access check automatically on schedule even when nobody visits.
The check verifies protected-page access even without a content rule, then evaluates optional required text or an Element ID. The selected user ID stays local; Website Down Watch does not receive the password, persistent login cookie, private page HTML, WordPress identity or screenshot.
#account-dashboardWebsite Down Watch does not need a special integration with Paid Memberships Pro or another membership plugin when access is based on the normal WordPress current-user context. The locally selected Monitoring test user is established inside WordPress first, then your membership/access rules decide whether that account can open the configured page.
That lets Site Watch distinguish a valid protected page from a login redirect or denied-access response, then check optional required content. Real signed-in visits can additionally contribute observations, but scheduled Plus/Advanced monitoring does not depend on a member being online.
When the same configured content check keeps failing, Website Down Watch confirms the problem according to your alert mode. If the page becomes healthy again before confirmation completes, no incident is opened.
Website Down Watch combines independent external checks with protected signals produced by the Site Watch plugin inside WordPress. One view tells you what the internet received. The other tells you whether WordPress itself actually ran as expected.
Many of the things your visitors actually use are dynamic. Account panels, member interactions, filtering, refresh actions and background requests can fail even when the page itself still answers with HTTP 200. Website Down Watch treats AJAX functionality as a first-class signal.
If a button, filter, account widget or protected action depends on an AJAX call, the page can still load while the real experience is already broken.
The Site Watch plugin contributes an internal AJAX health result from inside WordPress. That means the system can distinguish “the page answered” from “the WordPress functionality behind it actually worked.”
Site Watch can test WooCommerce from inside WordPress instead of treating a successful storefront request as proof that the buying flow works. The eleven-check diagnostic combines an isolated cart, add-to-cart and checkout probe with read-only payment, shipping, recent order-flow and transactional-email checks, without creating an order, payment, email or customer-session change.
Website Down Watch separates a single failed observation from a confirmed Problem. The selected Fast, Balanced or Cautious mode applies to state-based website, WordPress, selected-page, public/protected content and automatic WooCommerce Health Problems. Warning states stay visible without notifications.
The monitoring job checks the enabled website signals that are due at that moment.
SCHEDULEDHTTP response, WordPress health, AJAX and configured page/content evidence are evaluated by the relevant monitor.
RESULT RECEIVEDFor website, selected-page and required-content checks, Fast, Balanced or Cautious rules decide when repeated failures become a real incident.
WAITING FOR EVIDENCENotification delivery begins as soon as the configured confirmation threshold is met. Automatic WooCommerce Health Problems use the same confirmation choice; there is no separate first-failure bypass.
NOT YET TRIGGEREDThe monitor keeps checking the affected signal. When its recovery rule is satisfied, the incident is resolved.
MONITORING CONTINUESA monitoring alert is more useful when it has context. This example follows one AJAX failure through observation, confirmation, incident creation, notification and recovery — while the public page continues to answer with HTTP 200.
HTTP 200 is healthy, but the expected WordPress AJAX result is not.
The matching failure is recorded again after the Balanced confirmation interval.
The same problem has now satisfied the configured confirmation rule.
The confirmed incident enters the notification path instead of alerting on the first failed load.
Website Down Watch keeps monitoring until the recovery rule is satisfied and the incident can close.
Website Down Watch combines website uptime monitoring with WordPress-aware health, AJAX, selected-page, protected-page, critical-content and eleven-check WooCommerce Health checks when WooCommerce is active. The goal is simple: detect when the site is reachable but the WordPress experience your visitors rely on is not working correctly.
Traditional website uptime monitoring answers a valuable question: did the server respond? Website Down Watch adds application-level evidence from WordPress so you can also see problems that a simple external request may miss.
Independent external checks keep watching even if WordPress itself becomes unreachable.
Protected health signals add application context from inside the WordPress installation.
Dynamic functionality gets its own signal instead of being hidden behind a successful page load.
Selected public pages can be checked for the content that is expected to be there.
Signed-in Page Check uses the local Monitoring test user for protected pages; Plus and Advanced can automate included pages every 5, 15, 30 or 60 minutes.
Detect when an important page answers successfully but the required content is missing.
Every plan can run the eleven-check local WooCommerce Health diagnostic; Advanced can repeat it automatically every 5, 15 or 60 minutes.
Uptime is only one part of the picture. Website Down Watch brings the important external and WordPress-aware signals together so you can see what is healthy, what changed and where attention is needed.
If WordPress, PHP or the hosting platform becomes unreachable, a monitor running inside that same website cannot be the only source of truth. Website Down Watch keeps the external monitoring path outside the monitored site, while WordPress-aware signals add deeper context whenever the application is available.
Normal state: external checks and inside-WordPress evidence are both available.
WordPress is reachable, inside signals are available and external monitoring continues normally.
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 →
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.
Automates one public page plus WordPress, maintenance, AJAX and SSL health with email alerts.
Adds three-page coverage, automatic public and signed-in protected-page checks, Telegram and Discord.
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.
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.