WordPress health, downtime and WooCommerce monitoring in one place.
Titanium Site Watch gives WordPress administrators local health diagnostics, protected-page checks and a dedicated 11-check WooCommerce Health system. Local checks work without a paid plan. Connect Website Down Watch only when you want scheduled monitoring, external uptime checks and alerts.
- Local checks without a paid plan
- 11-check WooCommerce Health
- Protected-page monitoring
- Email, Telegram & Discord alerts when connected
Checks performed inside this WordPress installation
These cards always use the newest WordPress-side result. Scheduled automatic monitoring updates the checks it performs, and Run local WordPress check can refresh the same local signals on demand.
WordPress can use the current database connection.
WordPress maintenance mode is not active.
The plugin's internal AJAX check ran successfully.
Certificate and HTTPS checks are healthy.
Selected page records and permalinks are available.
No active warning is affecting the current site state.
Error behavior and impact
Grouped critical errors are analysed for spikes, recurrence, bursts, persistence, request impact and source-version lifecycle.
Latest homepage external check
Latest automatic check
Most recent failed observation in local history
No current dashboard signal is reporting a problem.
11 store checks with a separate store state
Store health stays independent from website uptime. During the animation, an isolated WooCommerce issue appears and then recovers without falsely taking the whole website down.
Warnings can become confirmed Problems — and recoveries close them
The animation demonstrates the difference between a warning, a confirmed incident and a recovery while the selected notification channels remain separate from the Dashboard display.
The WordPress plugin is the starting point.
Install Titanium Site Watch from WordPress.org and use the local diagnostics immediately. You do not need to buy a monitoring plan just to run the plugin's local health checks.
Useful checks inside WordPress before you add external monitoring.
Site Watch combines basic WordPress health checks with content verification, protected-page checks and store-specific diagnostics so you can see more than a simple “site up / site down” result.
WordPress core health
Check the database connection, maintenance mode, AJAX/runtime behaviour and HTTPS/SSL status from the WordPress dashboard.
Selected WordPress Pages
Select important pages for verification instead of relying only on the homepage as a signal that the whole site is healthy.
Critical content checks
Require specific text or an Element ID so a page can fail even when it still returns a technically successful HTTP response.
Signed-in page checks
Use a local Monitoring test user to verify member-only or signed-in content without sending credentials or private HTML to the monitoring service.
External availability monitoring
When connected, Website Down Watch can monitor public availability, HTTP status and response time independently of the WordPress dashboard.
State-based alerts
Fast, Balanced and Cautious confirmation modes help avoid treating a single failed request as a confirmed incident.
Email, Telegram & Discord
Connected monitoring can send configured downtime and eligible WooCommerce Health Problem alerts with recovery handling.
Error Intelligence integration
If Titanium Error Intelligence is active, Site Watch can show its compact summary and use privacy-safe critical-error event data for configured alerts.
Go beyond “the shop page still loads.”
When WooCommerce is active, Titanium Site Watch can run an eleven-check local store diagnostic. WooCommerce state stays separate from website uptime, so a store-health problem does not falsely mark the complete website as down.
Use it locally, then connect monitoring when you need automation.
The WordPress plugin and the Website Down Watch service have different jobs. Local tools stay useful even without a monitoring subscription.
Local Site Watch tools
Run diagnostics manually from your own WordPress installation without requiring an account for the local checks.
- Database, maintenance, AJAX/runtime and SSL checks
- Selected WordPress Pages
- Required text and Element ID checks
- Signed-in/member-only checks with a local test user
- 11-check WooCommerce Health diagnostic
- Optional Titanium Error Intelligence summary
Website Down Watch automation
Connect the optional service when you want checks to continue on a schedule and alerts to arrive without opening WordPress.
- External public availability monitoring
- HTTP status and response-time monitoring
- Scheduled supported local checks
- Downtime incident confirmation modes
- Eligible WooCommerce Health Problem alerts
- Email, Telegram and Discord notification channels
Protected checks without exporting private page content.
Signed-in monitoring is designed so the private material used to verify a protected WordPress page stays on the WordPress site.
Privacy-safe protected-page verification
You choose a local Monitoring test user. Site Watch performs a short-lived internal WordPress loopback and returns only the compact check result required for monitoring.
- WordPress user credentials are not sent to the monitoring service.
- Persistent login cookies are not sent.
- Private HTML and screenshots are not sent.
- WordPress user identity is not sent as part of the protected-page result.
Required text and Element ID checks help detect pages that technically respond but no longer contain the expected application content.
A WooCommerce Health Problem can be visible and alertable without incorrectly turning the entire website uptime state into a downtime incident.
Site Watch does not add advertising, behavioural tracking or automatic public credits. Optional status badges appear only when you place them.
Frequently asked questions
Quick answers about the WordPress plugin, WooCommerce Health and optional Website Down Watch monitoring.
Do local checks require a Website Down Watch account?
No. The local WordPress and WooCommerce diagnostics work without an account or paid monitoring plan. You connect Website Down Watch only for supported scheduled monitoring and external alerts.
What does WooCommerce Health check?
WooCommerce core, database, products, cart, add to cart, checkout, payments, shipping, order flow, store email and the background scheduler.
Does the WooCommerce diagnostic create a test order?
No. It does not submit checkout or create an order, payment or email, and it does not change stock or contact payment processors.
Can Site Watch monitor member-only pages?
Yes. You can select a local Monitoring test user for protected-page checks. The short-lived internal check keeps credentials, login cookies and protected HTML on WordPress.
Can a page be checked for specific content?
Yes. You can require specific text or an Element ID, which can detect a broken page even when the web server still responds successfully.
Does one failed request immediately trigger a downtime alert?
No. Connected state-based monitoring uses Fast, Balanced or Cautious confirmation modes before opening a Problem incident. Warning states remain visible without being treated as confirmed downtime.
Which alert channels are available when monitoring is connected?
Configured alerts can use email and, on supported monitoring plans, Telegram or Discord. Recovery handling follows successful checks after an incident.
Does Site Watch replace Website Down Watch?
No. Site Watch is the WordPress plugin and local diagnostic layer. Website Down Watch is the optional external monitoring service that schedules checks and delivers configured alerts.
Does disconnecting the plugin cancel a subscription?
No. Disconnecting or uninstalling the WordPress plugin is separate from subscription cancellation. Subscription management is handled on Website Down Watch.
Does Site Watch add ads or public credits to my website?
No. It does not add advertising, behavioural tracking or automatic public credits. Optional Site Watch status badges appear only if you explicitly place them.
Start with the WordPress plugin.
Install Titanium Site Watch, run the local WordPress and WooCommerce diagnostics, and connect Website Down Watch later only if you want scheduled monitoring and alerts.
Download Titanium Site Watch23 practical tutorials for WordPress, WooCommerce and downtime monitoring.
Start with the free local WordPress and WooCommerce diagnostics, then move through selected pages, Critical Content, signed-in/member-only checks, optional Website Down Watch automation, alert routing, monitoring history and frontend status badges.
- Free local diagnostics first
- 11-check WooCommerce Health
- Protected/member-only page checks
- Automatic alerts when connected
Step-by-step Titanium Site Watch tutorials.
Every item below is a practical task you can perform in Titanium Site Watch: configure it, run it, test it or read a monitoring result.
Install Titanium Site Watch and run your first local WordPress check
Start with the plugin itself. The core local diagnostics work without a Website Down Watch account or paid monitoring plan, so you can verify WordPress before connecting any external service.
Step by step
- Install and activate Titanium Site Watch from WordPress.org.
- Open Site Watch → Dashboard in WordPress admin.
- Press Run local WordPress check.
- Wait for the local check batches to complete instead of refreshing the page during the run.
- Review Database, Maintenance Mode, AJAX Functionality, SSL Certificate, Selected WordPress Pages and Error Intelligence.
- If WooCommerce is active, also run the separate WooCommerce Health diagnostic.
- Fix any local issue first, then repeat the manual check to confirm the new state.
Read the local health cards on the Dashboard
The top health area is designed to answer whether WordPress itself can operate correctly, not merely whether the homepage returns an HTTP response.
Step by step
- Open Site Watch → Dashboard.
- Check Database for a usable current WordPress database connection.
- Check Maintenance Mode to make sure WordPress is not unexpectedly in maintenance.
- Check AJAX Functionality for the plugin's internal WordPress AJAX runtime result.
- Check SSL Certificate for the local HTTPS/certificate diagnostic.
- Check Selected WordPress Pages for saved-page record problems.
- Check Error Intelligence for active, inactive or not-installed integration state.
Select up to 100 WordPress Pages for record-level verification
Selected WordPress Pages is intentionally different from browser/content monitoring. It verifies that WordPress still has each saved Page, that it is published and that it still has a permalink.
Step by step
- Open Site Watch → Pages & Checks.
- Find Selected WordPress pages.
- Search by page title, or leave the search field empty and press Search to show pages.
- Select the Pages you want Site Watch to verify.
- Use Selected only when you want to review the current saved list.
- Use Select all on this result page when appropriate.
- Press Save selected pages.
Add a public monitored page before adding content rules
A monitored page can be used for normal public availability first. Element ID and required-text assertions are optional layers on top of that page.
Step by step
- Open Site Watch → Pages & Checks.
- Find Monitored pages and required content.
- Choose an unused monitored-page slot.
- Set the page mode to Public page.
- Select or enter the public page URL.
- Leave Element ID and required text empty if you only want the page itself configured.
- Save monitored pages and content rules.
Require a specific Element ID on a monitored page
An Element ID assertion helps detect pages that still return successfully but have lost a critical form, application container or other expected interface element.
Step by step
- Open the monitored page slot in Site Watch → Pages & Checks.
- Make sure the correct page URL is already selected.
- Enter the HTML Element ID only, without a # prefix.
- Use a simple ID containing letters, numbers, hyphens or underscores.
- Save the rule so Site Watch can verify the configured value.
- Use Open page and test or Run local WordPress check to repeat the local verification.
- Confirm the field shows Verified when the element is found.
Require text that must appear on a monitored page
Required text is useful when the page structure may change but one important phrase, state message or application label must still be present.
Step by step
- Open the required monitored-page slot.
- Enter the text that must appear in Text that must appear (optional).
- Keep the expected text concise and specific.
- Save monitored pages and content rules.
- Run the local verification.
- Review Required content found or Required content missing.
- Update the rule when the site's real visitor-facing text intentionally changes.
Configure a signed-in or member-only monitored page
Use Signed-in/member-only page when the real page must be opened inside WordPress with a specific local account rather than checked as an anonymous visitor.
Step by step
- Open Site Watch → Pages & Checks.
- Choose a monitored-page slot and set it to Signed-in/member-only page.
- Select the real protected URL.
- Choose a Monitoring test user in the signed-in page checks panel.
- Optionally add an Element ID or required text for the protected page.
- Save monitored pages and content rules.
- Review the immediate test-user verification, then use Run local WordPress check whenever you want to repeat it.
Choose a Monitoring test user that represents real member access
The quality of a protected-page check depends on the permissions of the local account used to open that page.
Step by step
- Create or identify a dedicated WordPress account for monitoring.
- Give it the same role, membership or access level as the users whose experience you want to verify.
- Avoid using an Administrator account when the protected page has membership or role restrictions.
- In Site Watch → Pages & Checks, search for the user by name or username.
- Select the account and save the monitored-page settings.
- Confirm the Test user result says the page can be opened correctly.
- Re-test after changing membership, access-control or role plugins.
Run an immediate local protected-page or required-content test
Manual tests are setup and diagnostic tools. They let you prove the saved page/access/content rule without waiting for an automatic monitoring cycle.
Step by step
- Save the page mode, URL, test user and any required-content fields first.
- Use Open page and test for the configured slot when available.
- For public required content, use Check content locally now when the control is available.
- Or return to the Dashboard and press Run local WordPress check to execute the local checks in a batch.
- Review the local access and content outcomes separately.
- Fix the page or rule, then repeat the manual check.
- Use automatic monitoring later only when you want scheduled incidents and alerts.
Run the complete 11-check WooCommerce Health diagnostic manually
When WooCommerce is active, Site Watch can test store health locally even without a monitoring subscription.
Step by step
- Open Site Watch → Dashboard.
- Find the WooCommerce Health panel.
- Press the WooCommerce Health check button.
- Wait for the complete store diagnostic to finish.
- Review the overall store state and each check result.
- Fix the affected WooCommerce area rather than treating the result as general website downtime.
- Run the diagnostic again after the store change.
Add Titanium Error Intelligence to the Site Watch Dashboard
Site Watch detects whether Titanium Error Intelligence is active, installed but inactive, or not installed, and changes the Dashboard action accordingly.
Step by step
- Open Site Watch → Dashboard and find the Error Intelligence card.
- If it says Not installed, use Download Error Intelligence to open its WordPress.org plugin page.
- Install the plugin through WordPress as usual.
- If Site Watch shows Inactive, press Activate Error Intelligence.
- When active, return to the Dashboard and review the compact error behavior/impact summary.
- If a paid monitoring plan is connected, configure New Critical Error and Behavior / impact escalation routing under Alerts.
- Use Error Intelligence itself for detailed local error analysis.
Connect a Website Down Watch monitoring plan
Connection turns on external automatic monitoring. The public website is checked from outside while authenticated Site Watch requests can trigger the predefined WordPress-local checks.
Step by step
- Open Site Watch → Connection.
- Enter the Website Down Watch license key.
- Enter the first email address to use for alerts.
- Review the connection notice explaining what is sent.
- Press Connect monitoring plan.
- Confirm the page shows Connection active and the connected plan.
- Save Pages & Checks monitoring frequencies and alert routing after the connection is active.
Allow Site Watch through a firewall or security plugin
A security layer can allow the public page while blocking the protected WordPress REST path that Site Watch needs for WordPress-side monitoring.
Step by step
- Open Site Watch → Connection and read the firewall compatibility notice.
- Identify the WordPress REST API path containing titanium-site-watch.
- In the firewall, WAF or security plugin, allow public network access to that path.
- Do not remove Site Watch's own private authentication requirement.
- Reconnect or refresh the monitoring state.
- Run a manual local check and wait for the next automatic cycle.
- Confirm the service can now see both outside availability and WordPress-local health.
Choose the Outside Monitoring interval
Outside Monitoring is the independent availability and response-time check. It can run more frequently than heavy WordPress-local probes when the connected plan supports it.
Step by step
- Open Site Watch → Pages & Checks.
- Find Automatic monitoring → Check intervals.
- Locate Outside Monitoring.
- Choose one of the intervals available on the connected plan.
- Use a faster interval for business-critical public availability when appropriate.
- Press Save monitoring settings.
- Return to the Dashboard after new checks arrive to confirm the cadence and response data.
Set separate automatic intervals for each WordPress-side check
Site Watch does not force every automatic feature onto one frequency. Each heavy local check can use a cadence appropriate to its cost and importance.
Step by step
- Open Site Watch → Pages & Checks → Check intervals.
- Set Logged-in Page Access when the connected plan supports protected-page automation.
- Set Critical Content for automatic Element ID/text verification.
- Set Selected WordPress Pages for record-level scheduled checks.
- If Advanced and WooCommerce are active, set WooCommerce Health to 5, 15 or 60 minutes.
- Leave unavailable controls unchanged instead of trying to force a locked interval.
- Press Save monitoring settings.
Choose Fast, Balanced or Cautious problem confirmation
The confirmation mode controls how many matching failed automatic checks are required before a temporary problem becomes a confirmed Problem incident.
Step by step
- Open Site Watch → Pages & Checks.
- Find Website / page alert confirmation.
- Choose Fast when rapid confirmation matters most.
- Choose Balanced for the recommended default.
- Choose Cautious when reducing false alarms matters more than speed.
- Press Save monitoring settings.
- Remember that once the state is confirmed, Site Watch hands the notification to the selected channels immediately.
Save email alert recipients
Email is the base automatic notification channel once a paid monitoring connection is active, and the same recipient list can be routed independently by alert type.
Step by step
- Open Site Watch → Alerts.
- Find Email alerts.
- Enter the primary Alert recipient 1 address.
- Add additional recipient fields when the connected plan allows them.
- Press Save email recipients.
- In Notification routing, enable Email for the alert types that should use it.
- Keep at least one available channel enabled for Website down + recovery.
Connect a private Telegram chat for alerts
On supported plans, Site Watch can connect one private Telegram chat through the Titanium Site Watch bot.
Step by step
- Open Site Watch → Alerts and find Telegram alerts.
- Press Connect Telegram.
- Create the temporary connection link.
- Open the Telegram app or Telegram Web.
- If Telegram does not insert it automatically, copy and send the exact /start command shown by Site Watch.
- Return to WordPress and press Check connection if needed.
- After Connected appears, press Send test and then enable Telegram for the desired alert types in Notification routing.
Connect a Discord incoming webhook
Discord uses the private incoming-webhook URL created for the channel where you want Site Watch notifications to appear.
Step by step
- Create an incoming webhook in the required Discord channel.
- Copy the webhook URL.
- Open Site Watch → Alerts → Discord alerts.
- Paste the URL into Discord webhook URL.
- Press Save and test webhook.
- Confirm the test message appears in Discord.
- Enable Discord for the desired alert types in Notification routing.
Choose channels separately for every alert type
Notification routing lets you decide whether each monitoring signal should use Email, Discord, Telegram or a combination of currently available channels.
Step by step
- Open Site Watch → Alerts → Notification routing.
- Review which channel columns are Available or Unavailable.
- Choose channels for Website down + recovery.
- Configure WordPress health, AJAX and SSL separately.
- Configure Selected Pages and Critical Content separately.
- Configure WooCommerce Health problem + recovery separately.
- Configure New Critical Error and Behavior / impact escalation when Error Intelligence is active.
- Press Save alert routing.
Read the 30-day response-time chart for all monitored pages
Connected public monitoring feeds a compact local 30-day history so you can compare how quickly each monitored page responded over time.
Step by step
- Connect Website Down Watch and allow automatic public checks to run.
- Open Site Watch → Dashboard.
- Find Response time history.
- Use the legend to identify each monitored page.
- Review Average, Fastest and Slowest statistics across all monitored pages.
- Hover or focus a date to compare the page values for that day.
- Use long-term changes as a performance signal, not just the latest single response.
Use Incident History to review confirmed automatic problems
Incident History stores confirmed automatic monitoring incidents rather than every successful check or manual diagnostic run.
Step by step
- Open Site Watch → Incident History.
- If the website is not connected, connect Website Down Watch first.
- Review the newest confirmed incidents.
- Use Type to distinguish Website, Selected WordPress pages and public or signed-in Critical Content incidents.
- Review Started, Recovered and Duration.
- Read Reason for the stored failure explanation or HTTP status.
- Use Refresh history when you want the latest service state.
Add an optional Site Watch status badge with a shortcode
Site Watch never adds public branding automatically. You can deliberately place one of two linked status shortcodes where you want it.
Step by step
- Choose the page, footer or widget area where you want the status badge.
- Insert
for the full badge. - Or insert
TitaniumMonitoring warningfor the logo-style badge. - Publish or update the WordPress content.
- View the public page while logged out.
- When automatic monitoring is connected, confirm the LED reflects the latest synchronized monitoring state.
- Remove the shortcode whenever you no longer want a public badge.
Ready to start with the WordPress plugin?
Install Titanium Site Watch from WordPress.org, run the local diagnostics, configure the checks that matter to your site, and connect Website Down Watch later only if you want automatic monitoring and alerts.
Download Titanium Site Watch