How to monitor a website form and catch it when it stops working

A broken enquiry form is the most expensive failure on most websites, because it is invisible from both sides. The visitor sees a thank-you message and assumes you will reply. You see nothing at all - and nothing at all looks exactly like a quiet week.

Start free - add your first site Watch it work (2 min)

Why forms fail so quietly

A form has more moving parts than it looks: the markup, the JavaScript that submits it, the endpoint that receives it, the mail service that delivers it, and the inbox rule that files it. Any one of them can fail alone.

Delivery breaks, submission does not. The form posts successfully and returns the thank-you page. The email never arrives because an API key expired, a sending domain lost its DNS records, or the recipient address bounced.

A plugin update changes the endpoint. The form still renders, but posts somewhere that no longer handles it.

Spam protection turns on the visitor. A stricter captcha or a firewall rule starts refusing genuine submissions - often from one country or one browser.

A required field appears. A field added for internal reasons becomes mandatory without a visible error, so submitting does nothing and the visitor gives up.

The reason it lasts so long

Almost nobody tests their own form. When they do, they test it from their own machine, logged into their own site, from the office IP - the exact conditions least likely to reproduce the failure.

And because the failure mode is silence, there is no moment where anyone thinks to check. Most broken forms are discovered by accident: a customer phones to ask why nobody replied to the message they sent three weeks ago.

How SiteOps handles it

Four steps, none of which involve writing a test script.

Describe the form the way a visitor uses itOpen the contact page, fill in the enquiry form, submit it. That is the whole configuration.

The AI fills and submits it on your real siteIt finds the fields itself and completes them with sensible test values, then submits for real - because a form that is checked but never submitted tells you nothing about whether submitting works.

It watches for what should happen nextThe confirmation, the redirect, the success state. If the page does not do what it did when the journey was recorded, that is the alert.

You get a screenshot of the failureThe page as it appeared at the moment it went wrong, plus a plain-English explanation - a validation error that was not there before, a captcha wall, a submit that did nothing.

What it does and does not do

It submits real form entries. That is the point - a form that is only inspected, never submitted, can be dead and still pass. Entries are clearly identifiable so you can filter them, and you choose the cadence.
It checks the submission, not your inbox. SiteOps confirms your site accepted the form. Whether the email then reached you depends on your mail provider, which SiteOps does not have access to.
Payment and card forms are never submitted. Any form that takes card details is walked to but not fired.

Common questions

Will this fill my inbox with test enquiries?It submits at whatever cadence you choose, and the entries are consistent enough to filter or route into a folder in one rule. Most people run form journeys less often than checkout journeys for exactly this reason.

Can it tell me if the email did not arrive?It confirms your site accepted and processed the submission - the part you control. Confirming delivery to your inbox would mean giving a monitoring tool access to your mail, which is a much larger ask than the problem justifies.

What if my form has a captcha?SiteOps detects captcha and login walls and reports them rather than pretending to pass. If a captcha is blocking legitimate submissions, that is itself something worth knowing.

Does it work with Contact Form 7, Gravity Forms, HubSpot, Typeform?Yes. It drives a real browser and interacts with whatever is rendered, so the plugin or platform behind the form does not matter.

Signup monitoringHow to automatically monitor your website's signup flow Customer journey monitoringHow to automatically test your website's critical customer journeys Checkout monitoringHow to detect a broken checkout before your customers do In the docsUser journeys - how a journey is built and replayed

Find out before your customers do

Add your site, describe one journey, and let it run. Free, no credit card.

Start free