Site Watch’s WordPress/AJAX runtime
- The health callback is callable.
- The admin-AJAX hooks are registered.
- The plugin can prepare a valid internal AJAX health result.
- The result is returned with the protected WordPress health response.
WORDPRESS AJAX MONITORING · APPLICATION-LEVEL CONTEXT
A PAGE CAN BE ONLINE
A PAGE CAN BE ONLINE
WHILE WORDPRESS IS WARNING YOU.
Website Down Watch combines external uptime with a protected WordPress health response that includes the Site Watch plugin’s own internal admin-AJAX runtime result. A successful page load is useful. Application-level context tells you more.
HTTP STATUSWORDPRESS HEALTHINTERNAL AJAX RUNTIMENO ADMIN LOGIN
WORDPRESS MONITORyourwebsite.com/
CHECKINGPublic page200 OK
WordPress healthHEALTHY
Internal WordPress/AJAXCHECK PASSED
PROTECTED HEALTH RESPONSE
Site Watch runtimeWordPress health contextAJAX result available
Plugin runtime validated inside WordPress.WHAT “WORDPRESS AJAX MONITORING”
MEANS HERE.
Website Down Watch checks the Site Watch plugin’s own internal admin-AJAX runtime as part of the protected WordPress health response. It does not pretend to click every button or test every third-party AJAX action installed on your site.
Every AJAX feature on every plugin
- No fake “AI clicks every control” promise.
- No administrator session is created.
- No dashboard scraping.
- No blanket claim that every third-party action was exercised.
HTTP CAN SAY UP.
WORDPRESS CAN STILL SAY WARNING.
The public page result and the internal WordPress/AJAX result are different signals. Keeping both prevents a simple 200 response from becoming the whole story.
OUTSIDEPublic page200 OKThe web server answered.
+
INSIDE WORDPRESSInternal AJAX runtimeCHECK PASSEDPlugin runtime completed successfully.
THE CHECK RUNS INSIDE THE CURRENT WORDPRESS PROCESS.
The current Site Watch plugin validates its admin-AJAX runtime while building the authenticated WordPress health response. No second request to wp-admin is needed for this result.
01Monitoring serviceRequests the private Site Watch health endpoint.
→02WordPress health requestDatabase, maintenance, SSL and runtime context are gathered.
→03Internal AJAX validationSite Watch checks its registered handler and compact payload in-process.
→04Compact resultPass or warning is returned with the protected health response.
NO SECOND WP-ADMIN HTTP REQUESTThe current plugin avoids turning a separate firewall-blocked admin-AJAX request into the internal result.
A FIREWALL SHOULD NOT DEFINE
THE INTERNAL RESULT.
Because the current internal check is completed inside the protected health request, it does not need a second public WordPress route just to prove the plugin runtime exists.
Monitoring serviceSECURE HEALTH REQUESTWordPress
Inside WordPress
AJAX hooks registered✓
Health summary valid✓
Runtime resultPASS
UNNECESSARY SECOND PATH
Separate public AJAX routeNot required for the current internal result
THE CURRENT RESULT IS CARRIED WITH THE PROTECTED WORDPRESS HEALTH RESPONSE.AJAX IS STRONGER WITH
APPLICATION CONTEXT.
The internal runtime result is returned beside other WordPress health signals, so the dashboard can distinguish public availability from what WordPress reports about itself.
DATABASEConnectedHEALTHY
MAINTENANCENormal modeHEALTHY
SSLCertificate stateHEALTHY
INTERNAL AJAXPlugin runtimeCHECK PASSED
PUBLIC PAGEUP+WORDPRESS HEALTHHEALTHY+AJAX RUNTIMEVERIFIED
PASS, WARNING OR NOT CHECKED.
The AJAX runtime result has meaning only when the protected WordPress health request itself is available. Website Down Watch keeps those states distinct instead of turning every missing result into the same red alarm.
The handler and compact result are valid in the current WordPress process.
The public page can still be Up while WordPress reports this warning.
There is no valid internal result to interpret for that check.
SEE AJAX IN THE WORDPRESS HEALTH STORY.
The useful dashboard view is not “AJAX yes/no” in isolation. It shows the public page, WordPress health and internal runtime together so the state is understandable at a glance.
MONITORED WEBSITEyourwebsite.com
HEALTHYPUBLIC PAGE200 OK
RESPONSE TIME184 ms
WORDPRESSHEALTHY
AJAX RUNTIMECHECK PASSED
Database connectionHEALTHY
Maintenance stateHEALTHY
SSL statusHEALTHY
Inside WordPress (AJAX)CHECK PASSED
NO WORDPRESS ADMIN
LOGIN IS REQUIRED.
The monitoring service uses the private Site Watch health endpoint and its generated secret. The AJAX runtime check does not sign in as an administrator or load WordPress dashboard content.
The monitoring service does not need WordPress administrator credentials for this health signal.
The check returns compact health data rather than downloading and analysing wp-admin pages.
The protected Site Watch health namespace still requires the generated private key.
The service receives the monitoring result needed for site health context, not an administrator session.
BUILD A WORDPRESS MONITORING STORY.
Internal AJAX runtime belongs beside uptime, WordPress health, selected pages, public content and protected-page access/content checks. Use the dedicated pages to go deeper into each layer.
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.
ESSENTIAL MONITORING
Basic
Automates one public page plus WordPress, maintenance, AJAX and SSL health with email alerts.
MORE COVERAGE
Plus
Adds three-page coverage, automatic public and signed-in protected-page checks, Telegram and Discord.
FASTEST MONITORING
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.
START WITH THE SIGNALS THAT ACTUALLY MATTER
DON’T WAIT FOR A USER TO TELL YOU
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.
INDEPENDENT EXTERNAL CHECKS
WORDPRESS-AWARE SIGNALS
CONFIRMED DOWNTIME & RECOVERY ALERTS
Website Down Watch
Know when the page answers. Know when WordPress actually works.