live24h.eu<\/a>.<\/p>\n\nExternal services<\/h3>\n\n
This plugin is a configuration helper for the live24h<\/strong> uptime-monitoring service and communicates with the live24h API at https:\/\/api.live24h.eu<\/code>. It requires a live24h account and API key. Nothing leaves your site before you, the administrator, act \u2014 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.<\/p>\n\nWhat is sent, and when:<\/p>\n\n
\n- Test Connection<\/strong> (you click the button): your live24h API key is sent in the
X-Api-Key<\/code> request header to verify the key and read your plan capabilities. No site data is sent.<\/li>\n- Scan site<\/strong> (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.<\/li>\n
- Create checks<\/strong> (you click the button): the check definitions you selected \u2014 the public URLs to monitor plus the chosen check type and interval \u2014 are sent together with your API key so that live24h can create the monitoring checks.<\/li>\n
- Heartbeat pings<\/strong> (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 \u2014 if you also created the backup heartbeat and run UpdraftPlus, BackWPup or Duplicator \u2014 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<\/em>. Deleting the check in live24h (or clearing the stored URL) stops it.<\/li>\n
- Product Watch<\/strong> (optional, WooCommerce only \u2014 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 \u2014 together with your API key. The WooCommerce SKU is deliberately never transmitted, and no customer, order or user data is sent.<\/li>\n<\/ul>\n\n
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. The API key is only ever sent to api.live24h.eu<\/code> (or staging-api.live24h.eu<\/code> if you configure the advanced staging override).<\/p>\n\nThe live24h service is operated by Marcel Grunert (live24h.eu). Use of the service is governed by its Terms of Service and Privacy Policy:<\/p>\n\n
\n- Terms of Service: https:\/\/www.live24h.eu\/en\/legal\/agb\/<\/li>\n
- Privacy Policy: https:\/\/www.live24h.eu\/en\/legal\/datenschutz\/<\/li>\n<\/ul>\n\n\n
\n- Upload the plugin to
\/wp-content\/plugins\/live24h-website-monitor\/<\/code> or install via the WordPress plugin uploader.<\/li>\n- Activate the plugin through the Plugins<\/em> menu.<\/li>\n
- In your live24h dashboard, go to Settings \u2192 API Keys \u2192 Create Key<\/em> and select the
Write<\/code> permission<\/strong> (not Read<\/code> \u2014 a Read key can connect but cannot create checks).<\/li>\n- Copy the generated key (it starts with
lv24_<\/code>).<\/li>\n- Go to Tools \u2192 live24h Website Monitor<\/em>, paste the key, and click Test Connection<\/em>.<\/li>\n
- Click Scan site<\/em>, review the suggestions, and click Create checks<\/em>.<\/li>\n<\/ol>\n\n
Note: each API key is bound to exactly one workspace. To monitor multiple workspaces, set up the plugin separately for each (one WordPress install = one key = one workspace).<\/p>\n\n\n
\nWhich API key permission do I need?<\/h3><\/dt>\nWrite. Only a key with the Write<\/code> permission can create checks. A Read<\/code> key authenticates (the connection test will pass) but every check creation returns a 403 error. Admin<\/code> also works but is broader than necessary.<\/p><\/dd>\nDoes this plugin run monitoring on my server?<\/h3><\/dt>\nNo. All checks are executed by live24h's globally distributed worker network. The plugin only configures them.<\/p><\/dd>\n
Do I need a paid plan?<\/h3><\/dt>\nNo. The free tier of live24h includes 15 checks, which is enough for a typical WordPress site.<\/p><\/dd>\n
Does this plugin send sensitive data?<\/h3><\/dt>\nThe plugin sends only your selected URL list, detected page types, and your API key (to authenticate). It never reads post content, user data or database rows beyond what is needed to enumerate public URLs.<\/p><\/dd>\n\n<\/dl>\n\n\n
0.7.1<\/h4>\n\n\n- WooCommerce shops: the Product Watch delivery job is now registered the way WooCommerce expects it. On sites running WooCommerce this removes debug notices on every page load \u2014 and makes sure the job is actually queued, so pending product reports leave your site reliably.<\/li>\n
- The robots.txt preview and the admin requests now resolve your real admin URL instead of assuming the default one, so installations with a relocated wp-admin are handled correctly.<\/li>\n<\/ul>\n\n
0.7.0<\/h4>\n\n\n- Product Watch for WooCommerce (optional): hand-pick the products or variants that matter and live24h watches their price and availability \u2014 a report goes out when something changes, plus one daily snapshot per selection. A delivery view in wp-admin shows whether the reports arrived, and a single click retries one that did not. Your SKUs stay on your server, and nothing is watched until you select it.<\/li>\n
- Tested against WordPress 7.1.<\/li>\n
- Clearer documentation of what the plugin talks to: the heartbeat pings and the Product Watch deliveries are now spelled out field by field in External services<\/em>.<\/li>\n
- Site scan: the page lookup no longer suppresses query filters, so multilingual setups keep their language context.<\/li>\n
- Packaging: the release archive now ships the composer manifest for the bundled live24h library, so its origin is visible at a glance.<\/li>\n<\/ul>\n\n
0.6.0<\/h4>\n\n\n- Policy presets: roll out monitoring in one decision \u2014 choose \"Essential\", \"Recommended\" or \"Everything\", preview exactly what would be created (and what is skipped and why: already created, plan-locked, unavailable), then apply. The preview and the apply always agree, applying never creates files on your site, and anything the plugin cannot verify is skipped instead of duplicated.<\/li>\n
- Enterprise hardening across the plugin family: deeper test coverage, a shared CI gate for all nine adapters and per-adapter changelogs.<\/li>\n<\/ul>\n\n
0.5.6<\/h4>\n\n\n- Maintenance release of the plugin line: the Shopware and TYPO3 plugins now ship the same health-center UX as WordPress 0.5.x (severity-first ordering, status chips, settled \"Created\" recommendations, the two-chip \"file still missing\" rule). No functional changes inside the WordPress plugin itself.<\/li>\n<\/ul>\n\n
0.5.5<\/h4>\n\n\n- Two chips, two statements \u2014 a created file-shaped recommendation (robots.txt\/sitemap) whose FILE is still missing now shows the amber \"File still missing\" badge next to the green \"Created\" one, with an amber (not green) row stripe. A row only reads fully green once nothing is left open.<\/li>\n<\/ul>\n\n
0.5.4<\/h4>\n\n\n- Recommendations know what exists \u2014 recommendations whose monitoring check is already created now render settled (green \"Created\" badge, disabled and unchecked checkbox, excluded from \"create all recommended\"), exactly like the Scan tab. Their details \u2014 including the \"how to get the file\" guidance for robots.txt\/sitemap \u2014 stay available, because \"the check exists\" and \"the file is still missing\" are two different statements. The overview summary no longer advertises already-created recommendations.<\/li>\n<\/ul>\n\n
0.5.3<\/h4>\n\n\n- Settings sub-tabs \u2014 the settings page now uses real sub-tabs (Connection \/ Privacy & Telemetry \/ AI access \/ Setup Wizard) in the native WordPress tab look, exactly like the Health Center. Deep links (e.g. from the AI access card) open the right tab; without JavaScript all groups stay visible.<\/li>\n
- Scan tab clarity \u2014 suggestions that are already created are no longer pre-selected or selectable; the selection only ever contains checks that are still missing.<\/li>\n<\/ul>\n\n
0.5.2<\/h4>\n\n\n- Dashboard tile \u2014 a live24h status widget on the WordPress dashboard: cached availability pass count, last scan time and a one-click \"Open Health Center\" link. It never runs score modules, a scan or an HTTP call.<\/li>\n
- Clear apply semantics \u2014 the Recommendations tab now states explicitly that applying creates monitoring checks in live24h and never creates files; the robots.txt\/sitemap recommendations carry a remediation note explaining how WordPress serves those files natively, with a deep link to Settings \u2192 Reading.<\/li>\n
- llms.txt deep link \u2014 the AI access card in the SEO area now links straight to the llms.txt controls on the settings tab.<\/li>\n
- Structured settings \u2014 the settings page is grouped into anchored topic cards (Connection \/ Privacy & Telemetry \/ AI access \/ Setup Wizard) with a jump navigation on top.<\/li>\n<\/ul>\n\n
0.5.1<\/h4>\n\n\n- Recommendations tab now speaks the Health Center design language \u2014 card rows with a severity stripe, a clean severity chip on the right and quiet expandable details (severity no longer glued to the title).<\/li>\n
- Overview: failed availability rows now use their negative wording (\"Homepage not reachable\") so a red PROBLEM badge never sits next to a positive check name.<\/li>\n
- Overview: every recommendation summary row carries a right-aligned \"View recommendations\" deep link, matching the \"Go to problem\" links above.<\/li>\n<\/ul>\n\n
0.5.0<\/h4>\n\n\n- Problems first \u2014 every Health Center area now sorts its facts and cards by severity (problem \u2192 needs attention \u2192 healthy), so anything that needs action is the first thing on screen and a healthy area opens green.<\/li>\n
- Clear monitoring state \u2014 every card carries an explicit chip (\"Monitored\" \/ \"Not monitored\" \/ \"Problem\" \/ \"Warning\"); an already-monitored recommendation no longer shows a contradictory empty checkbox next to an \"Already monitored\" note.<\/li>\n
- Overview polish \u2014 the score breakdown is now cleanly aligned (label left, value right), and every critical problem line carries a \"Go to problem\" link that jumps straight to the affected area.<\/li>\n
- Cron jobs \u2014 a failing WP-Cron fact links directly to the setup guide, and the apply summary now says WHY entries were skipped (e.g. \"already monitored\").<\/li>\n
- Recommendation reasons \u2014 the WP-Cron heartbeat recommendation now resolves its localized why\/what-to-do copy from the shared catalogue instead of falling back to the raw English rationale.<\/li>\n<\/ul>\n\n
0.4.1<\/h4>\n\n\n- Fixed plugin links \u2014 the \"Visit plugin site\" and author links in the WordPress plugin list now point to https:\/\/www.live24h.eu. The previous non-www address is served by a redirect endpoint whose HTTPS handshake modern browsers reject, so the links failed with a security error.<\/li>\n<\/ul>\n\n
0.4.0<\/h4>\n\n\n- AI access card + llms.txt generator \u2014 the SEO tab reports whether llms.txt is served and evaluates the REF-aligned shortlist of visibility-critical AI crawlers, including whether each provider documents robots.txt compliance. One click serves a spec-conform
\/llms.txt<\/code> with an H1, description blockquote and at most 30 curated links; no file or llms-full.txt<\/code> is written, and physical files, foreign routes and existing responders are never overridden. llms.txt does not guarantee an SEO or AI-search boost; its effect remains unproven, while robots.txt access is the decisive lever.<\/li>\n<\/ul>\n\n0.3.0<\/h4>\n\n\n- SEO cards now create checks \u2014 every actionable card in the SEO tab (sitemap, homepage reachability, indexability, per-page checks) carries a checkbox and a \"Monitor selected\" button that creates the monitoring checks directly via the live24h API, with per-row feedback (created \/ skipped \/ failed). Discovered URLs are shown as plain text and are never turned into links.<\/li>\n
- WP-Cron activation guide \u2014 when WP-Cron is disabled (DISABLE_WP_CRON), the Cron jobs tab now shows a step-by-step guide with copy-ready crontab examples using your real site URL, hosting-panel pointers (cPanel\/Plesk), the ALTERNATE_WP_CRON alternative, and how to verify the cron is really running via the heartbeat.<\/li>\n
- Complete German translation \u2014 every string in the plugin is now translated (including the SEO card actions), and a build gate keeps source strings, translation template and German translation in sync.<\/li>\n
- Recommendation checkboxes in all discovery tabs (SEO, Cron jobs, SSL & Domain, WooCommerce, Mail) are now wired to the same one-click apply flow as the Recommendations Center.<\/li>\n<\/ul>\n\n
0.2.0<\/h4>\n\n\n- Health Center \u2014 the scan\/wizard screen is now an eight-area Health Center (Overview, SEO, Cron jobs, SSL & Domain, WooCommerce, Mail, Recommendations, Settings). Areas only show when they apply to your site (a non-WooCommerce site no longer shows a WooCommerce tab).<\/li>\n
- Recommendations Center \u2014 grouped bulk review (critical \/ recommended \/ optional \/ locked) with one-click \"create all recommended\"; plan-locked checks are shown but never pre-selected.<\/li>\n
- Wider discovery \u2014 per-domain SSL certificate expiry + DNS, mail authentication (SPF \/ DKIM \/ DMARC \/ MX), WooCommerce storefront objects, and background-job heartbeats are detected during the scan and turned into monitoring recommendations.<\/li>\n
- Security hardening \u2014 central secret redaction guarantees no API key \/ token \/ webhook secret \/ certificate detail ever appears in a card, log or error, at any depth.<\/li>\n
- Built on the shared live24h CMS SDK so WordPress, Shopware and TYPO3 produce identical scores, suggestions and recommendations from the same facts.<\/li>\n<\/ul>\n\n
0.1.0<\/h4>\n\n\n- Initial release \u2014 scan your WordPress site and create monitoring checks in live24h with one click: HTTP \/ HTTPS \/ SSL \/ domain-expiry, plus WordPress REST API, robots.txt and sitemap as HTTP checks.<\/li>\n
- Plan-aware suggestions \u2014 check types your live24h plan does not include are shown but not pre-selected (with an upgrade hint); your free check slots are displayed after a scan.<\/li>\n
- Hardening \u2014 the API key is preserved when you save settings without re-typing it; per-check errors from bulk creation are shown individually; the scanner follows only same-host redirects (never internal\/loopback hosts); the API key is only ever sent to api.live24h.eu.<\/li>\n
- Full German translation included.<\/li>\n<\/ul>","raw_excerpt":"Scan your WordPress site and create 24\/7 monitoring checks in live24h with one click \u2014 HTTP, SSL, domain and WooCommerce.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/322460","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=322460"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/live24heu"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=322460"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=322460"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=322460"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=322460"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=322460"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=322460"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}