$0
Free scan
See the score and top customer-path issues before creating an account or paying.
Evergreen guide
Your website can be online and still losing customers.
Most lead leaks do not announce themselves. The homepage loads, the brand looks credible, and analytics may still show visits, but the paths customers use to call, contact, book, request, order, or buy can quietly fail. SiteLeak checks those public paths and turns the evidence into a free preview, a paid repair packet, and optional monitoring.
After the scan
Free preview first. Pay only when the evidence is useful.
Each page routes into the same self-serve path: scan the public site, review the strongest signals, then unlock the full repair packet or monitor the same paths.
$9 once
Full report
Unlock every affected URL, severity, evidence summary, fix note, and PDF-ready handoff.
$19/mo
Weekly monitoring
Rerun checks automatically and get alerted when forms, links, CTAs, or paths get worse.
Customer-path evidence this page checks
Broken forms, disabled submit actions, missing contact fields, and weak public form signals
Dead booking, appointment, quote, order, cart, checkout, menu, and service links
Phone numbers and email addresses that appear but are not clickable where expected
Mobile first-screen CTA evidence for the customer action the page depends on
Recurring monitoring evidence when customer paths change after site updates
What makes this different
This is not a broad score page. It is an evidence page for the specific moments where a visitor tries to take action and the site gives them a dead link, hidden CTA, broken form, or unreachable contact path.
Best first use case
Run it before a campaign, seasonal push, website relaunch, new booking provider, menu update, or landing-page change. Those are the moments when customer paths often break without looking broken.
How the money path is protected
Free finds the first signals. The $9 full report gives the repair handoff. The $19 weekly monitor watches for new or returning blockers so the owner does not need to manually check the site every week.
What this page helps you decide
Use this page when the buyer thinks the site looks fine but inquiries, bookings, calls, or purchases may be blocked by public customer-path issues.
Practical fixes after the scan
Fix high-severity blockers tied to contact, booking, quote, order, cart, checkout, or phone paths before lower-risk cleanup.
Send the full report to the person who edits the site because it includes affected URLs and copy-ready fix notes.
Rerun the scan after publishing so the evidence shows what changed.
Turn on weekly monitoring after the first repair if the site changes through plugins, page builders, booking providers, or campaigns.
Evidence examples
conversion.phone_number_not_clickablehigh
Phone number is visible but not tappable
The public page shows a phone number in text but does not expose a matching tap-to-call link for mobile visitors.
Fix: Wrap the number in a tel: link and retest the page on the public mobile path.
checkout.broken_booking_linkhigh
Booking button leads to a dead destination
The public booking CTA resolves to an error response instead of a live appointment or reservation path.
Fix: Replace the destination with the current booking URL or add a redirect from the old path.
conversion.form_submit_disabledhigh
Lead form appears present but cannot be submitted
Form evidence indicates a disabled submit action or missing submit path near the customer inquiry form.
Fix: Repair the form state or widget script and retest without submitting private customer information.
Questions this scan can answer
Does SiteLeak prove my website is losing money?
No. It reports public website evidence that can block customer paths. It does not estimate revenue impact or promise outcomes.
What counts as a lead leak?
A lead leak is a public issue that can interrupt contact, booking, call, quote, order, cart, checkout, email, menu, service, or request paths.
Why pay after a free scan?
Pay only when the preview finds useful evidence and you need the complete issue list, affected URLs, severity, repair notes, PDF-ready report, and retest steps.