GUEST REQUEST200 OK
/account/
Please sign in to continue
The server answered. Traditional uptime can stop here.
WORDPRESS MEMBERSHIP PAGE MONITORING · LOCAL TEST USER + AUTOMATIC CHECKS
MONITOR THE PAGE
MONITOR THE PAGE
YOUR MEMBERS ACTUALLY SEE.
A protected account page can look perfect to a guest while the signed-in experience is missing something important. Select a local Monitoring test user and Website Down Watch can verify protected access plus optional text or an Element ID; Plus and Advanced can run the check automatically even when no member is online.
LOCAL TEST USERTEXT OR ELEMENT IDNO LOGIN CREDENTIALSPLUS / ADVANCED
PROTECTED PAGE CHECKyourwebsite.com/account/
TEST USER READYM
WORDPRESS USERLocal test user · access allowed
PROTECTED PAGEAccount dashboard renderedResponse generated in the selected user context
SAVED RULE#account-dashboardRequired Element ID
COMPACT RESULTVERIFIEDNo page HTML sent
THE BLIND SPOTTHE PUBLIC PAGE CAN BE FINE.
THE PUBLIC PAGE CAN BE FINE.
THE MEMBER EXPERIENCE CAN STILL BE WRONG.
A normal uptime check sees what an unauthenticated request can reach. Membership problems often live behind the login wall, where access rules, conditional content and account interfaces change what the user actually receives.
WORDPRESS TEST USERVERIFYING
/account/
Membership activeAccount dashboard present
Site Watch can validate access and configured content in the page WordPress returns for the selected local test user.
HOW THE CHECK HAPPENSNO PASSWORD IS SHARED WITH THE SERVICE.
NO PASSWORD IS SHARED WITH THE SERVICE.
WORDPRESS OPENS THE PAGE AS YOUR LOCAL TEST USER.
Choose a local Monitoring test user whose permissions or membership represent the intended visitor. Site Watch establishes that WordPress current-user context, your existing membership/access rules decide whether the account is allowed through, and the protected page is then verified.
The WordPress user ID stays on your site; no account password is stored or sent.
Your existing membership, role or access plugin still decides whether that account can view the page.
Access can be verified by itself, with required text or an Element ID as optional extra assertions.
Only the compact result is used for monitoring; private HTML, screenshots and user identity are not sent.
READY FOR PROTECTED-PAGE CHECK
VERIFY WHAT MATTERSCHECK FOR THE SIGNAL THAT PROVES
CHECK FOR THE SIGNAL THAT PROVES
THE MEMBER PAGE REALLY RENDERED.
Save a small, deterministic rule instead of trying to understand every pixel. Site Watch supports required text or an Element ID, so the check can focus on the part of the protected page that matters.
CONFIGURED TARGET
Element ID#account-dashboard
✓
Small rule, small result. The monitor does not need the full private page to know whether this configured signal was present.
Account Dashboard
Membership activeYour member content is available.
RULE RESULTFOUND
YOUR ACCESS RULES STAY YOURSNOT LOCKED TO ONE
NOT LOCKED TO ONE
WORDPRESS MEMBERSHIP PLUGIN.
Site Watch does not need a special API integration with your membership plugin. If WordPress accepts the locally selected Monitoring test user and your existing access rules allow that account to open the configured page, the protected-page check can run manually on every plan and automatically on included Plus/Advanced pages.
YOUR WORDPRESS SITEMembership / access rules
ANY ACCESS PLUGINPMPro EXAMPLECUSTOM ROLE LOGIC
The access system decides whether this user can view the page.
ACCESS ALLOWED
SITE WATCHVerify the delivered page
Logged inYES
Configured page receivedYES
Required signalCHECK
Paid Memberships Pro is a useful example, not a dependency. The same principle works with other WordPress access systems that use the normal WordPress current-user context for protected-page access.
PRIVATE BY DESIGNVERIFY THE RESULT.
VERIFY THE RESULT.
DON’T SHIP THE PRIVATE PAGE.
Signed-in monitoring should not require handing a remote service the credentials or private content it is trying to protect. Site Watch keeps the verification result compact.
NEVER NEEDED FOR THE CHECK
- Member username
- Password
- Login cookie
- Private page HTML
- Screenshot
COMPACT VERIFICATION SIGNAL
Checked pageAccount area
Verification ruleRequired page signal found
ResultFound
The illustration shows the principle: a compact result, not the member’s private page.
DON’T ALERT ON ONE ODD CHECKA MISSING SIGNAL BECOMES AN INCIDENT
A MISSING SIGNAL BECOMES AN INCIDENT
ONLY AFTER CONFIRMATION.
A single failed protected-page result is not enough. The same Fast, Balanced or Cautious confirmation choice applies here, so a temporary access/content problem does not immediately become an alert.
MEMBER PAGE · /account/OBSERVING
1 / 3Waiting for another matching failed check
MANUAL WHEN YOU NEED IT · AUTOMATIC ON PLUS & ADVANCEDSTART WITH A MANUAL CHECK.
START WITH A MANUAL CHECK.
AUTOMATE THE MEMBER-PAGE ALERTS WHEN IT MATTERS.
Protected-page access and optional text/Element ID assertions can be tested manually on every plan with the local Monitoring test user. Plus can automate up to 3 included protected pages and Advanced up to 5.
Open up to five locally saved protected pages as the selected Monitoring test user and verify access plus any optional text or Element ID without creating an automatic alert.
Automatic signed-in required-content alerts: not includedAutomatic Signed-in Page Check opens included protected pages as the selected local Monitoring test user every 5, 15, 30 or 60 minutes, with confirmation before an incident is opened.
Email + Telegram + Discord options available on the planThe same Signed-in Page Check model with up to five protected pages and 5, 15, 30 or 60 minute automatic intervals.
Email + Telegram + Discord options available on the planCONTENT-CHECKED PAGE CAPACITY
PLUS · up to 3 pages
MEMBER-PAGE SIGNALS IN CONTEXTSEE WHICH PROTECTED PAGE WAS VERIFIED —
SEE WHICH PROTECTED PAGE WAS VERIFIED —
AND WHAT THE LATEST PROTECTED-PAGE CHECK REPORTED.
A useful dashboard keeps scheduled external uptime separate from protected-page access/content results. Plus and Advanced can update the protected-page signal on schedule with the local Monitoring test user, while real signed-in visits can add observations.
WEBSITE DOWN WATCHyourwebsite.com
● MONITORING ACTIVEPUBLIC UPTIMEHEALTHY
WORDPRESS HEALTHHEALTHY
MEMBER PAGES3 CONFIGURED
OPEN INCIDENTS0
SIGNED-IN / MEMBER-ONLY PAGE SIGNALS
/account/Element ID · #account-dashboard
AUTOMATICVERIFIED/downloads/Required text · Download Library
AUTOMATICVERIFIED/member-profile/Element ID · #membership-profile
WAITINGNO NEW CHECKONE PROTECTED SIGNAL · PART OF THE BIGGER PICTUREMEMBER-PAGE MONITORING MAKES MORE SENSE
MEMBER-PAGE MONITORING MAKES MORE SENSE
WHEN UPTIME AND WORDPRESS HEALTH ARE BESIDE IT.
A protected page is one layer of the WordPress experience. Website Down Watch can combine its access/content result with external uptime and WordPress-aware signals so the dashboard has context when something changes.
01WordPress UptimeDid the public site answer?02WordPress MonitoringWhat does WordPress report?
03Member PagesDid the signed-in page contain the required signal?
04AJAX RuntimeIs the internal AJAX runtime healthy?Monitor the public edge. Understand WordPress. Verify the protected experience.CHOOSE A MONITORING PLAN →
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.