Check if lead forms are visible on your website

A contact form is the most trusted element on most lead-gen pages, because it is the most visible. The fields render, the submit button is styled, and clicking it shows a thank-you message — so everything looks like it works. But whether the form looks right and whether a submission actually lands in the inbox or CRM are two separate questions, and only the first one is visible from the page.

Forms fail quietly in ways a visitor never sees. A recipient address gets removed in a redesign, an SMTP or CRM integration expires, a required field or spam filter silently blocks the send, or the thank-you page shows while the submission goes nowhere. The page still behaves normally, so nothing looks broken — while every lead that should have arrived is lost. On a page running paid traffic, that gap sits invisibly behind a live campaign.

This is what the free check surfaces: not whether the submission succeeds end to end, but whether a real form and lead path appear present on the public page, so you know where a manual submission test is worth running before more budget goes through it.

Measuring a form as a lead usually means firing an event when the form is submitted — a GA4 event, a Meta custom event, or a Google Ads conversion, most often wired through GTM on the submit or on the thank-you page view. That event is what lets a form show up as a conversion in reporting. Without it, the form can work perfectly for the visitor and stay completely invisible in the numbers.

Two failure shapes are common, and they pull in opposite directions. Some forms have no submit event at all, so real leads are never counted. Others fire the event on page load or button click rather than on a confirmed submission, so every visit or every misclick inflates the lead count. A visible form is not the same as a measured submission, and the difference is exactly what makes a form-led campaign's reporting drift away from what actually happened.

The free check works at the visible layer: it looks for whether a form and its lead path appear present on the public page and flags it for review. It does not submit the form, prove the submission succeeds, verify CRM delivery, or confirm an event fires — those need manual testing and account access. Naming that limit honestly is the point: the scan tells you where to test, not that the pipeline is fine.

The usual way to test a form is to fill it in and submit — which means a debug tool that pushes test data into a live CRM, mixing fake leads into real ones, and only checks one form on one page at a time from the machine it runs on. For an agency reviewing a client's site, that is both slow and messy: someone has to manufacture a submission on every page just to see whether the lead path is even there.

TrackCanary takes the opposite approach for the first look. Paste a public URL — no login, no install, no test submission — and the check reviews the page for visible forms and lead paths alongside calls, WhatsApp, pixels, GA4, GTM, and Google Ads signals, all in one pass. It is the fast preflight you can run on any page, including a client's, before more budget goes through it, without putting a single fake lead into anyone's inbox.

It does not replace a real end-to-end submission test — that still confirms the inbox, the CRM, and the event downstream. TrackCanary is the step before that: a quick, honest read of what appears visible from the public page, and a way to keep watching it so a form that breaks after launch does not run unnoticed.