Skip to content

Integrations

Read WordPress health findings and mail-send observations

Use the collected WordPress evidence without confusing a reported observation with a complete health or delivery test.

Reviewed

Open the collected evidence

Choose the website, open Monitors and expand Platform Health · WordPress. Check connection status, the last successful collection and whether intelligence is current. Missing or stale evidence is unknown, not healthy.

The environment observations can include WordPress and PHP versions, database response, REST status, overdue cron tasks and cache indicators. A page-cache or object-cache indicator does not test cache effectiveness.

Follow a useful finding

Expand Findings and resolution history. Read the severity, confirmation state, recommendation and first/last observed dates. A component update notice identifies an update reported by WordPress; Regal Pulse does not install it.

For example, a saved WordPress Site Health needs review result directs you to Tools → Site Health in WordPress. It reports WordPress’s last saved native result. The connector does not rerun heavy Site Health checks on every frontend request. Review the native details before choosing a fix.

Interpret mail sending carefully

WordPress email sending shows observed accepted attempts and reported failures for the collection period. Zero reported failures does not prove every intended email was sent or delivered.

Inbox delivery is unverified. Mailers that bypass the observed WordPress hooks and downstream bounces require provider or mailbox evidence. Check the recipient’s mailbox and mail provider before concluding that a contact form delivered successfully.

WordPress Site Health warning

WordPress Site Health needs review, with the saved critical result and the direction to Tools > Site Health.
Recorded on deadsharpmedia.com on 23 October 2026. This example shows a saved native Site Health warning, not a fresh test of your website.

Did this article help?