KNOW WHEN YOUR WEBSITE
STOPS ANSWERING.
Website Down Watch monitors public URLs on connected WordPress websites from outside the hosting, records HTTP status and response time, confirms persistent failures before opening an incident, and keeps watching until the site recovers.
YOUR WEBSITE CANNOT
DEPEND ON ITSELF TO REPORT DOWNTIME.
The public uptime request runs outside the connected WordPress hosting. If the site, PHP process or hosting platform stops answering, the external monitoring path remains available to observe the failure, confirm it and later detect recovery.
The service requests the public page from outside the monitored hosting.
Availability, returned HTTP status and response time come from that external check.
If the website disappears, the monitoring path can still confirm downtime and keep checking for recovery.
FROM EVERY HOUR
DOWN TO EVERY MINUTE.
The fastest available public-page interval depends on the connected plan. You can still choose a slower cadence when one-minute monitoring would be unnecessary for that website.
Fastest Basic public URL check.
Faster automatic website monitoring.
Fastest available public URL monitoring.
The animation compresses time. The real schedule follows the interval saved for the connected plan.
DON’T SETTLE FOR
A SINGLE GREEN DOT.
Each external public-page check records whether the URL answered, the HTTP status returned by the website and the response time used in the uptime view.
CONFIRM THE FAILURE
BEFORE THE ALERT FIRES.
Fast, Balanced and Cautious confirmation let the monitor require matching failed checks before a temporary problem becomes a confirmed website incident.
Matching failures at least 1 minute apart.
FASTEST CONFIRMATIONMatching failures at least 1 minute apart.
RECOMMENDEDMatching failures at least 2 minutes apart.
MORE PATIENTHEAR ABOUT THE OUTAGE.
HEAR WHEN IT IS OVER.
After downtime is confirmed, Site Watch can notify the configured recipients. Monitoring continues during the incident, and a later healthy result records recovery and can send the recovery message.
Downtime and recovery messages can go to the configured email recipients.
Connect one private Telegram chat for monitoring notifications.
Connect one Discord channel through its private incoming webhook.
MONITOR THE PUBLIC PAGES
YOUR VISITORS ACTUALLY NEED.
The connected plan determines how many public URLs can be watched automatically: one with Basic, up to three with Plus and up to five with Advanced.
SEE WHEN DOWNTIME STARTED.
SEE WHEN THE WEBSITE RECOVERED.
Confirmed problems and recoveries are retained for the plan period so the uptime history focuses on the events that mattered instead of listing every normal successful check.
CURRENT STATE, IMPORTANT URLS
AND RECENT INCIDENT CONTEXT.
The uptime view brings the latest public result, monitored URLs, 30 days of local daily Average/Fastest/Slowest response history and incident state together so the health of the website is immediately understandable.
WHEN THE SERVER ANSWERS,
WORDPRESS CAN STILL NEED ATTENTION.
Website uptime monitoring answers whether the public URL responded. Because Website Down Watch is built for connected WordPress websites, you can go deeper with automatic WordPress/database, maintenance, AJAX and SSL health, selected-page checks, public content and protected-page access/content signals.
The public URL answered from outside the hosting. That is the essential first layer.
Additional WordPress signals can explain cases where the website answers but something important inside the application is wrong.
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.
Basic
Automates one public page plus WordPress, maintenance, AJAX and SSL health with email alerts.
Plus
Adds three-page coverage, automatic public and signed-in protected-page checks, Telegram and Discord.
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.
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.