Lead Form Signal Checker

It finds crawled pages whose title, description, or text matches selected form-related phrases. On those pages, it looks for email, phone, name, submit, placeholder, privacy, reassurance, incentive, CAPTCHA, and related wording, plus the page protocol.

No. The field count is an estimate from distinct words such as email, phone, name, company, message, address, and website. The checker does not inspect input elements, required states, labels, autocomplete attributes, or the form action.

No. It does not interact with a form or inspect its control-to-label relationships, keyboard behavior, validation, error messages, success state, responsive layout, virtual-keyboard hints, or submission. Test those directly in the rendered experience.

Only if their surrounding crawl-visible text matches the phrase rules. It does not open modals, advance steps, execute embeds, or inspect dynamically rendered controls, so these forms can be missed or misclassified.

There is no universal ideal count. Ask for the information required to complete the current task, clearly distinguish optional fields, and consider the audience, commitment, risk, and follow-up process. Verify the real controls because this tool reports only an estimated cue count.

Check its purpose, labels, instructions, required fields, autocomplete and input types, keyboard flow, validation, clear error recovery, success confirmation, privacy context, spam controls, responsive layout, and successful delivery. Use analytics and user research to understand abandonment.