Description
Crash alerts
When WordPress crashes, visitors see “There has been a critical error on this website.” The real error is hidden, so you don’t know which plugin or theme caused it.
With crash alerts on (1 Preventionlabs credit a day), you get an email when your site crashes. It says:
- Which plugin or theme broke the site, by name (for out-of-memory and time-limit crashes: which one was running).
- What went wrong. For example: it ran out of memory, a file has broken code, or it needs code that isn’t on your site.
- Whether that plugin was updated or turned on shortly before the crash, with the version and how long before.
- How to fix it, including what to do if you can’t log in.
A real alert, from a test site:
Acme Shop crashed your site.
The plugin Acme Shop tried to use a piece of code (acme_missing_helper) that isn’t on your site. This usually means it needs another plugin that is turned off or missing, or it doesn’t match your WordPress or PHP version. It was updated to version 2.0.0, 1 minute before the crash, so the update is the most likely cause.
How to fix it: Turn off Acme Shop. In your dashboard, go to Plugins and click Deactivate under it. If you can’t log in, open your host’s file manager and rename the folder wp-content/plugins/acme-shop to acme-shop-off. If Acme Shop caused the crash, that brings your site back.
How it works:
- It uses WordPress’s own crash handler (the wp-content/fatal-error-handler.php drop-in), which loads before any plugin. So it also catches crashes in plugins that load before this one. If another plugin already uses that file, or WordPress can’t write to wp-content, it catches crashes after plugins load, and the plugin’s page tells you so.
- Every 10 minutes it checks your PHP error logs for new crashes and database errors. WordPress runs scheduled tasks when someone visits the site, so on a quiet site the check waits for the next visit.
- The same crash is emailed at most once every 6 hours, not once per visitor.
- WordPress’s own error page and recovery email work as before. Sending the report can delay the error page by up to 3 seconds, at most once per crash every 5 minutes.
What it can’t catch:
- Anything that stops WordPress before it loads: a broken wp-config.php, a database that’s down, or a server that’s down. For those, the uptime check covers you: once this site is verified, Preventionlabs checks it every 5 minutes, and emails you if the site fails two checks in a row (1 credit a day).
- A crash on a site where alerts were off. The plugin has to be on before the crash.
- A crash on a host that blocks outgoing connections. The error can’t be sent.
- Multisite networks. Crash alerts can’t be turned on there yet, because every site in a network shares the same crash handler and error logs.
Full report
One click checks your site from the outside, the way visitors, Google and email providers see it. It takes 15 seconds to about a minute and lists what’s broken, where, and what to do.
It checks:
- Pages: errors, slow pages, redirects, pages hidden from Google, broken links, JavaScript errors.
- Security: leaked files such as .env, .git and backups, outdated scripts with known security holes, security headers.
- Uptime and speed: HTTPS, redirects, page weight, caching.
- Search: noindex tags, robots.txt blocks, sitemap pages that fail.
- Email: SPF, DKIM and DMARC, which decide whether your emails land in spam.
- Domain and DNS: DNSSEC, nameservers, records pointing at services that no longer exist.
- WordPress: versions and plugins visible from outside.
Every check is read-only: the checks can’t change your site, DNS, code or settings. (Crash alerts, if you turn them on, add one file to your site; see below.) Reports are made by code from what was checked, not by AI. You can copy a report into an AI assistant or send it to your developer.
Only a site’s owner can check it. The plugin proves the site is yours in one click, with no DNS changes.
Website: https://preventionlabs.com.au. Everything a report checks: https://preventionlabs.com.au/checks.
External services
This plugin connects to the Preventionlabs service at app.preventionlabs.com.au. Reports and crash explanations are made on Preventionlabs’ servers, not on your site.
- Reports: your Preventionlabs API key, this site’s address (when you click Verify this site), and the ID of the site you choose to check. Sent when an administrator clicks Connect, Verify this site or Run full check, and each time the Tools > Preventionlabs page is opened (to list your sites).
- Uptime check: once this site is verified, Preventionlabs requests its home page every 5 minutes, as any visitor would, and emails you if it fails two checks in a row (1 credit a day). Turn these emails off on the Health page in your Preventionlabs dashboard.
- The proof: when you click Verify this site, the plugin publishes a random token at /?rest_route=/preventionlabs/v1/proof. Preventionlabs reads it to confirm the site is yours, when you verify and before each report. It only proves this site to your account. It is removed when you delete the plugin.
- Crash alerts, only after an administrator clicks Turn on crash alerts: when the site crashes, the error message, file and line, the page address without its query string, and the names and versions of the active plugins and theme. Every 10 minutes, new crash and database error lines from the PHP error logs WordPress can read. Before sending, folder paths on your server are replaced with wp-content/…, values passed to functions are removed from stack traces, and database queries are removed from database errors. Nothing else from the logs is sent. Errors are sent with a token made for this site, which can only send errors for it. Each error is kept until 30 days after it was last seen, and emailed to your Preventionlabs account’s email address.
- The crash catcher: turning crash alerts on adds the file wp-content/fatal-error-handler.php. Turning them off, or deactivating or deleting the plugin, removes it. If another plugin already uses that file, it is left alone.
- Terms: https://preventionlabs.com.au/terms. Privacy policy: https://preventionlabs.com.au/privacy.
A Preventionlabs account is required. Price:
- Free to sign up, with 2 free full reports on each domain.
- US$28 a month for 1,500 credits a month (they reset each month). Cancel any time.
- A full report is 1 credit. Crash alerts and uptime checks are 1 credit a day each, per site. Reading reports is free.
- Subscribers can buy more credits at 10 US cents each, from US$20. Bought credits never expire.
- When credits run out, alerts pause until credits come back. You get an email at 25 credits left.
Installation
- Install and activate the plugin.
- Sign up at https://app.preventionlabs.com.au.
- In your Preventionlabs dashboard, open Integrations, then AI agents, and click Create API key.
- In WordPress, open Tools > Preventionlabs, paste the key and click Connect.
- Click Verify this site.
- Click Turn on crash alerts, then Send a test email to check alerts reach you.
- Click Run full check.
FAQ
My site shows “There has been a critical error”. Can this tell me why?
Only if crash alerts were on before the crash. If your site is down now and you can’t log in: open your host’s file manager, go to wp-content/plugins, and rename one plugin folder at a time (for example, add -off to the end) until the site comes back. The last one you renamed is the cause. Then turn on crash alerts, so next time you get the answer by email.
Does it slow down my site?
It adds nothing to your pages. The crash catcher only runs when the site crashes; sending the report then can delay the error page by up to 3 seconds, at most once per crash every 5 minutes. The log check runs every 10 minutes in the background and reads only the lines added since the last check.
Will it change how my site handles a crash?
Only by a moment. It sends the error first (taking up to 3 seconds, at most once per crash every 5 minutes), then WordPress handles the crash as usual: the same error page for visitors, and the same recovery email to your admin address.
Why didn’t I get an email?
Click Send a test email on the plugin’s page. If the test doesn’t arrive, check spam or junk, and add alerts@preventionlabs.com.au to your contacts. If the test arrives but crashes don’t, check the Crash alerts panel: it says whether the crash catcher is installed and which logs it can read.
Can someone use my key to check other people’s sites?
No. A key can only run reports on sites in your account that you’ve proven are yours. It can’t change anything on any site.
Why does verifying fail?
The message says why. The usual causes: a security plugin or firewall blocks the WordPress REST API for visitors (allow /?rest_route=/preventionlabs/v1/proof), the site redirects to another address (check Settings > General), or WordPress runs in a folder such as example.com/blog, which can’t prove the whole domain. In those cases, add the DNS record from your Preventionlabs dashboard instead.
What happens when I delete the plugin?
It removes the crash catcher file, the stored key, the proof, the crash alert settings and the last report. Without the proof, the site stops counting as verified at its next report. If you no longer need the key, delete it in your Preventionlabs dashboard too.
Screenshots
Changelog
1.2.2
- Price wording for Preventionlabs credits: crash alerts use 1 credit a day per site, and the plugin’s page says when they’re paused for lack of credits.
1.2.1
- Says plainly that crash alerts are part of the Preventionlabs subscription (US$28 a month), and warns on the plugin’s page when the account doesn’t have it.
1.2.0
- New: crash alerts. When your site crashes, you get an email naming the plugin or theme that broke it, why, and how to fix it.
- Crashes are caught through WordPress’s own crash handler, and the PHP error logs are checked every 10 minutes.
1.1.5
- Copyright: Preventionlabs.
1.1.4
- The description says a report takes 15 seconds to about a minute, as the plugin itself does.
1.1.3
- Setup steps say each domain’s first 2 full reports are free (new pricing).
1.1.2
- The dashboard page is now called Integrations; instructions updated.
- Copyright notice added.
1.1.1
- Author is now Preventionlabs.
1.1.0
- Verify this site in one click, with no DNS changes.
1.0.0
- First release: connect with an API key, run a full report, copy it.


