When the CAPTCHA breaks, it blocks customers, not bots.
An expired site key, a blocked script, a plugin conflict: any of them turns the CAPTCHA into a wall that rejects every real visitor with "verification failed". Formitor monitors forms without disabling the CAPTCHA, and catches the CAPTCHA itself failing.
Other tools ask you to turn the CAPTCHA off. Formitor doesn't.
Disabling spam protection to make monitoring possible trades one risk for another. Formitor keeps the CAPTCHA on and watches it from both sides.
Tests through the CAPTCHA
Formitor's checks work with the CAPTCHA active, using a scoped, auditable bypass that only Formitor's tagged test submissions can use. Real visitors and real bots see the CAPTCHA exactly as before. Spam protection never drops.
Detects the CAPTCHA failing
Around that bypass, Formitor watches for the real outage: the widget not loading, the verification endpoint erroring, real visitors getting "verification failed". A broken CAPTCHA blocks 100% of submissions and looks exactly like a quiet week.
CAPTCHA outages are invisible from the dashboard.
The form renders. The page is up. Every uptime check passes. Meanwhile every real enquiry dies at "verification failed".
- Expired or rotated site keys. The widget loads but every verification is rejected.
- Blocked or broken scripts. A CSP change, a caching plugin, or a CDN rule that stops the CAPTCHA script from loading at all.
- Plugin conflicts after updates. A form-plugin update that breaks the CAPTCHA integration and fails every submit silently.
- Provider-side outages. The verification endpoint degrades and takes your lead flow with it.
- Overzealous spam filtering. CleanTalk or similar starts rejecting legitimate-looking submissions, including your leads.
Works with the CAPTCHAs your clients already run
Keep the CAPTCHA on. Watch it anyway.
Monitoring that works through Turnstile, reCAPTCHA, hCaptcha and CleanTalk, and catches them failing.