About this plugin
live24h Website Monitor is a configuration helper, not a monitoring engine. It analyses your WordPress site, suggests the URLs and check types that matter, and creates them in your live24h workspace via API. eu platform.
What gets detected automatically
- Homepage, primary menu entries, important slugs ( /preise, /kontakt, /leistungen, /checkout, …)
- robots.txt and sitemap.xml
- WordPress REST API endpoint ( /wp-json/ )
- WooCommerce shop, cart and checkout pages (if WooCommerce is active)
- SSL certificate and domain expiry candidates
Check types proposed
- HTTP / HTTPS availability (homepage, menu pages, WooCommerce URLs)
- SSL certificate validity
- Domain registration expiry
- WordPress REST API endpoint ( /wp-json/ )
- robots.txt and sitemap reachability (as HTTP checks)
Product Watch for WooCommerce (optional)
If you run WooCommerce, you can additionally hand-pick products or variants and let live24h watch their price and availability. You choose every product yourself; nothing is watched until you do. The plugin reports a change shortly after it happens and sends one daily snapshot per selection, and a delivery view in wp-admin shows whether the last reports went through (with a manual retry if one did not).
See External services below for exactly what leaves your site.
A live24h account and API key are required. eu.
External services
eu. It requires a live24h account and API key. Nothing leaves your site before you, the administrator, act — there is no telemetry and no call the plugin makes on its own.
Two things keep running afterwards, and only because you set them up yourself: the heartbeat pings (if you created a heartbeat check) and the optional Product Watch module (if you connected it and selected products). Both are described below.
What is sent, and when:
- Test Connection (you click the button): your live24h API key is sent in the X-Api-Key request header to verify the key and read your plan capabilities. No site data is sent.
- Scan site (you click the button): the scan itself runs locally on your server. Afterwards your API key is sent to read your plan (allowed check types and free slots) so the suggestions can be shown plan-aware.
- Create checks (you click the button): the check definitions you selected — the public URLs to monitor plus the chosen check type and interval — are sent together with your API key so that live24h can create the monitoring checks.
- Heartbeat pings (only if you created a heartbeat check): applying a heartbeat recommendation stores the ping URL that live24h returned for that check. WP-Cron then calls that URL once an hour, and — if you also created the backup heartbeat and run UpdraftPlus, BackWPup or Duplicator — once after each successful backup. A ping is a plain request to that URL with no payload and no site data attached; what live24h alerts on is the ping missing. Deleting the check in live24h (or clearing the stored URL) stops it.
- Product Watch (optional, WooCommerce only — inactive until you connect the module and select products): after you select products or variants, the plugin sends an observation to the live24h API whenever a selected product’s price or availability changes, plus one daily snapshot per selection. They stop as soon as you clear your selection or disconnect the module. What is sent per observation: the product/variant reference, its public URL, the shop channel, country and locale, the price (amount and currency) and the availability state — together with your API key. The WooCommerce SKU is deliberately never transmitted, and no customer, order or user data is sent.
The plugin transmits only the public URLs you select and your API key. It never sends post content, user data, passwords or database rows beyond what is needed to enumerate the public URLs you choose to monitor. eu if you configure the advanced staging override).
eu). Use of the service is governed by its Terms of Service and Privacy Policy:
- Terms of Service: https://www.live24h.eu/en/legal/agb/
- Privacy Policy: https://www.live24h.eu/en/legal/datenschutz/