We host on Hostinger — get up to 20% off your first plan.Get the link →
Referral link · we may earn a commissionReferral link — we may earn a commission at no extra cost to you.Download a working automation JSON
Can AI answer engines cite your site?
Outreach scripts that get replies
Find the 3 workflows costing you sleep
200+ prompts, ready to ship
12-month posting plan in 60 sec
Brand voice doc in 4 steps
Runway / Pika / Sora / Veo formats
Paste a URL and I'll fetch the homepage server-side, then check it for the same nine automation signals I look for on every audit: contact form, chat widget, booking, ad pixels, analytics, schema, email capture, WhatsApp, and click-to-call. Every result is a real match against the actual page — no self-reported checklist.
One URL, one server-side fetch, one score.
Every result is a string match on real HTML.
Form, chat, booking, pixels, schema, and more.
What we check
| Check | Score weight | Detection method |
|---|---|---|
| Contact form | 15 pts | Real HTML string/regex match |
| Live chat / chatbot | 15 pts | Real HTML string/regex match |
| Online booking / scheduling | 12 pts | Real HTML string/regex match |
| Meta (Facebook) pixel | 10 pts | Real HTML string/regex match |
| Analytics (GA4 or Tag Manager) | 10 pts | Real HTML string/regex match |
| Structured data (JSON-LD) | 13 pts | Real HTML string/regex match |
| Email capture (popup / newsletter) | 8 pts | Real HTML string/regex match |
| WhatsApp link | 9 pts | Real HTML string/regex match |
| Click-to-call phone link | 8 pts | Real HTML string/regex match |
How it works
Paste your homepage URL
Enter your domain — https:// is added automatically if you leave it off.
Run the scan
The server fetches your homepage through a hardened proxy (SSRF-guarded, 10s timeout, 2MB cap) and reads the raw HTML.
Read the free preview
See your 0-100 score and the top 3 highest-weighted gaps immediately.
Unlock the full report
Enter your email to see every detected signal, every gap, and what an automation would do to close each one.
I built this scanner from the same nine signals I check on every automation audit I run for service businesses. Most sites lose leads not because their offer is weak, but because the path from "interested visitor" to "captured contact" has silent gaps — no chat widget to catch the visitor who won't fill out a form, no booking link so a phone call has to happen first, no pixel so ad spend can't retarget.
This tool fetches your homepage the same way a bot or a first-time visitor would, checks it against those nine signals, and scores what it finds — nothing more. If a signal loads dynamically after a delay our single fetch doesn't wait for, it can show as a false negative; that limitation is stated plainly above rather than hidden behind a confident-looking score.
Waseem, building from Bali · info@skynetjoe.com
Quick answers
Real scan. The tool fetches your homepage server-side through a hardened proxy and checks the actual returned HTML for real signals — a <form> tag, known chat-widget script sources, booking-widget embeds, pixel snippets, JSON-LD schema, WhatsApp links, and tel: links. Nothing here is self-reported or guessed.
One fetch keeps the tool instant and free, and the homepage is where most of these signals live anyway (chat widgets, pixels, and analytics tags are almost always site-wide includes). If your contact form or booking widget lives on a different page, run the scanner against that page's URL directly.
A positive string/regex match against the fetched HTML — e.g. a script tag pointing at a known chat-widget CDN, or a tel: link in an <a href>. If a tool loads only after a click or a delayed script injection that our single fetch doesn't capture, it can show as a false negative — that's a known limitation of a single-request scan, not a guess dressed up as a fact.
The URL you scan and the resulting score/gaps stay in your browser until you choose to unlock the full report, which asks for an email. That email goes to my CRM so I can follow up. No account, no name, no company required.
No — the proxy only fetches what a normal anonymous visitor (and a search bot) would see. If your homepage requires auth, the scan will fail with a fetch error rather than fake a result.
Updated August 2026