This guide applies to Drupal 10 or 11 and PHP 8.1 to 8.3. You need a live24h account, a workspace and an API key with write permission – see the shared steps .
Install
Composer installation and activation:
composer require live24h/drupal-adapter
drush en live24h_health_center
Alternatively, enable the live24h Health Center module from the module list in the back end. Then, under Configuration → Services → live24h Health Center, enter the api_key and – unless support specifies a different environment – the api_base_url (https://api.live24h.eu). The module is available now as a direct download from live24h; a listing on drupal.org will follow.
Step by step
The illustrated flow (API key, scan, Health Score, recommendations, create) is shown step by step in the overview . In Drupal it works like this:
- In the back end, open Reports → live24h Health Center.
- Under Configuration → Services → live24h Health Center, check the API key and use “Test connection”.
- Start the analysis of the site (scan).
- Review the Website Health Score and the recommendations.
- Select the checks – locked suggestions stay visible and are marked “From Pro”.
- Create the checks in live24h with one click.
The Health Center checks pages/SEO (homepage, robots.txt, sitemap.xml, indexability and canonical per surface), SSL and domain expiry as well as DNS per productive domain, the mail deliverability (MX, SPF, DKIM, DMARC) and – where present – cron hooks and queue workers as a heartbeat.
Troubleshooting and tips
The Health Center is missing from the back end.
Check whether the module is enabled (drush en live24h_health_center or via the module list), and clear the cache with drush cr. The Health Center lives under Reports, the settings under Configuration → Services → live24h Health Center.
“Test connection” fails.
Check the api_key (write permission required), the api_base_url (https://api.live24h.eu) and whether the server is allowed to connect outbound. Hosting firewalls occasionally block outgoing requests.
The wrong domain is being checked. SSL, domain and DNS checks refer to the productive domains of the site. If the base URL is ambiguous, set the correct productive domain in the module configuration.
Mail checks (SPF/DKIM/DMARC) report gaps. This is often the feedback you want: missing SPF, DKIM or DMARC records lower deliverability. Add the DNS records at your DNS provider and scan again.
A heartbeat check stays on “Waiting”. This is normal and not an error: a heartbeat waits for the first signal from the monitored job (the ping to the heartbeat URL). As long as the cron run or queue worker has not reported in yet, the check stays on “Waiting” – not on “Down”. With the first run, the status switches to “Operational”.
No commerce area visible. This is intentional. Drupal core is a CMS without a shop, so the commerce area is hidden and not shown as a locked suggestion.
A suggestion is marked “From Pro”. The check type is not included in your plan. You can deselect it or upgrade your plan .
Frequently asked questions
Why a dedicated Drupal module? Drupal sites often have multiple productive domains, editorial responsibilities and active cron/queue processes. A guided flow fits better than manual one-off checks.
Which check types are created? http (homepage, robots.txt, sitemap.xml), ssl, domainexpiry, seo (directive per surface) and heartbeat (cron/queue) – depending on the scan result and the plan you booked.
Does the module run the checks itself? No. It only creates the configuration. The running checks are executed by live24h from several regions.