Contact form visibility, submit, action-target, and required-label signals
Free tool
Check whether a public page exposes form and CTA signals.
SiteLeak looks for public contact-form and call-to-action signals, then pairs those findings with broken links, mobile screenshot evidence, and browser errors. It does not submit forms, collect visitor data, or create fake leads.
Customer-path evidence this page checks
Phone, email, booking, quote, order, and contact CTA signals
Console errors that may interfere with visitor actions
Broken links and mobile evidence around the public page
First-screen mobile CTA evidence when browser checks are available
A safe form signal check
The check looks for form and CTA evidence without submitting lead forms or entering personal data.
Useful before campaigns
Run the checker before paid traffic or seasonal promotions so obvious public-page issues can be fixed first.
What paid evidence adds
The full report includes the affected URL, issue severity, source evidence, screenshot context where available, and a fix checklist that can be handed to a site maintainer.
What this page helps you decide
Use this page when you need to know whether a public page gives visitors a working path to call, contact, book, request, order, or buy.
Practical fixes after the scan
Add a visible submit action and clear labels for required contact fields.
Make phone numbers and email addresses clickable where visitors are expected to use them.
Move the primary customer action higher on mobile pages if first-screen evidence is weak.
Check third-party form, chat, booking, and tracking scripts after updates because they can change public behavior.
Evidence examples
conversion.form_submit_disabledhigh
Contact form submit action appears disabled
Static form evidence or browser evidence indicates a disabled submit action near the contact path.
Fix: Review form state logic, required fields, and widget scripts, then retest without submitting user data.
conversion.phone_number_not_clickablehigh
Phone number is visible but not clickable
The public page shows a phone number in text but the scan does not find a matching tel: link.
Fix: Wrap the phone number in a tap-to-call link and confirm it appears where mobile visitors need it.
conversion.no_above_fold_ctamedium
No customer action is visible in the first mobile screen
Browser evidence does not find a visible call, contact, booking, order, quote, or checkout action above the mobile fold.
Fix: Move the primary action into the first mobile screen and retest the page with browser checks enabled.
Questions this scan can answer
Will the checker submit my form?
No. It detects public form and CTA signals but does not submit forms or create leads.
Can it detect every embedded widget problem?
No. It reports visible public evidence such as console errors, mobile screenshot state, and missing CTA signals.
Will it store customer submissions?
No. The scanner does not submit lead forms, place orders, or create customer records.