A form can pass every server-side check and still be impossible for a real visitor to submit. A required field hidden by conditional logic. A submit button broken by a theme update. A JavaScript error that only happens in a browser.
Server-side testing never sees any of that, because it never renders the page. So Formitor now does what your visitor does.
What shipped
Render checks open each form in a real browser and flag any form that can’t actually be submitted, naming exactly which forms are affected instead of just showing a count.
Deep checks (Tier 3) go further: a headless browser loads the page, fills the form field by field, and clicks Submit, every week, per form. Enable it with the 🤖 On/Off toggle in the form row. Available to all Pro subscribers.
Screenshot on failure. When a deep check fails, click the “✕ deep check failed” badge and see the screenshot taken at the moment it got stuck. Debugging starts with evidence: you see the validation error, the hidden field, or the broken layout exactly as the visitor did.
Why it matters for agencies
The worst support conversation is “the form works when we test it.” A form that submits fine via the API but blocks real visitors produces exactly that conversation, plus weeks of silently lost leads before anyone connects the dots.
Three tiers now cover the whole path: delivery checks verify the email lands in a real inbox, render checks verify the form exists in the browser, deep checks verify a human could actually submit it. The full story is on the delivery verification page.