Feature

Website form monitoring

Form monitoring is the part of LeadGuard Pathway Monitoring that applies to submission forms. It combines source-page load, form presence, visibility, destination behaviour and outcome verification into a single continuous check, and it does not rely on sending test submissions.

By LeadGuard Product Team · Published 15 July 2026 · Editorial policy

A working contact form is a stack of separate things that must all keep working: the page has to load, the form has to render, the fields have to be usable, the submit action has to reach its endpoint, and a success indication has to appear so the visitor knows their enquiry went through. Form monitoring is the discipline of checking every layer, not just the outermost one.

LeadGuard treats form monitoring as a specialisation of Pathway Monitoring. The check families are the same; the practical checks and safety rules are the ones described below.

Five layers of form health

LayerWhat LeadGuard checksCommon failure it catches
Page uptimeThe source page URL returns a successful response within a reasonable time.Server errors, cache poisoning, DNS misconfiguration.
Form presenceAfter the page renders, the specific form element still exists in the DOM and matches the canonical pathway.A plugin update that removes the form, a theme change that swaps the shortcode, a conditional render that hides the form on the wrong page variant.
Form visibilityThe form is not hidden, disabled or covered by an overlay at the viewport widths that matter, particularly mobile.Cookie banners or promo modals sitting over the form, a responsive breakpoint that collapses fields off-screen, disabled submit buttons after a JavaScript error.
Destination healthThe action URL or handler the form submits to is reachable and does not appear to return an error.A rename or move of the form processor, an expired third-party integration, a CDN rule that blocks the endpoint.
Outcome verificationA confirmation page or learned inline success message is reachable in principle, so a real submission can be verified.A missing or moved thank-you page, a success message removed in a redesign, a redirect chain that never resolves.

Why page uptime is not enough

A traditional uptime monitor tells you the URL responded. That is a useful signal, but it is not what a lead needs. The page can return HTTP 200 while the form element inside it is missing, hidden, disabled or pointed at a broken endpoint. LeadGuard treats page uptime as the first of five layers, not the answer.

Monitoring without test submissions

LeadGuard does not submit real forms. The active checks look at the page and its behaviour: does the form render, are the fields interactive, is the submit action wired up, does the action URL respond, is an outcome source still reachable. Real submission evidence comes from the passive event stream generated by real visitors, not from synthetic tests.

Form availability is not email delivery

It is important to be honest about the boundary here. LeadGuard can verify that a form is available, reachable and confirmed on the customer's site. It cannot, by itself, verify that the resulting enquiry email arrived in a specific inbox on the other side. Email delivery depends on the customer's mail flow, spam-filter behaviour and any downstream automation. This gap is a common source of confusion and is called out on the Form Monitoring dashboard as well.

What form monitoring covers and does not cover

Covers

  • Native HTML forms rendered by the site itself.
  • Forms rendered by common form-builder plugins where the resulting DOM is inspectable.
  • Embedded provider forms whose elements are exposed to the parent document.
  • Multi-step forms, provided each visible step is reachable in a normal browser render.

Does not cover

  • Actual email delivery from the customer's server or provider to a specific inbox.
  • Judgement of whether an enquiry is a good lead.
  • Deep introspection of iframes whose parent document is denied access by the provider.
  • Behaviour that only reproduces under load or region-specific network conditions LeadGuard does not currently simulate.

How to start

Run the free protection check on a page that contains one of the forms you care about. LeadGuard will list the pathways it finds and show how each one currently performs across the five layers.

FAQs

Will LeadGuard send test enquiries to my inbox?
No. LeadGuard does not submit forms. Active checks observe the page and its behaviour. Real submission evidence comes from real visitors.
Can LeadGuard prove my enquiry emails are arriving?
Not on its own. Form monitoring proves the form is available, reachable and confirmed on the site. Downstream email delivery depends on your mail flow and is a separate check to perform.
What if my form is inside an iframe I do not control?
LeadGuard can still monitor the source page, the visibility of the iframe container and the destination URL. If the iframe denies access to its content, deeper introspection is limited.
How does this differ from a general uptime check?
Uptime checks confirm the URL responded. Form monitoring additionally checks that the specific form still exists on the page, is visible, has a working destination and a reachable outcome source.

Related content