Website leak check
33 checks on what keeps costing owner-run businesses customers, run on your own site, with the fix for each and a basics score.
What we'll read
Each page and file shows up here as we read it, and the six areas fill in as their checks finish.
How to use it
We read your homepage and the pages it links to, and run 33 checks across six areas: getting found, AI search, phones, getting in touch, trust and speed. You get the fixes ranked by how many customers each one costs, a basics score, and a report you can keep.
- 1
Put in your website
Just the address. We read what's already public: the page's own text, links and code.
- 2
We run the 33 checks
Your homepage and the pages it links to, read for getting found, AI search, phones, getting in touch, trust and speed. You watch each area fill as it's read.
- 3
Read what to fix
The fixes ranked by how many customers each one costs, the tool that does it where one applies, and a basics score out of 100. Save it as a PDF.
What you get
33 checks on what keeps costing owner-run businesses customers, run on your own site: the fixes ranked, a basics score, and a report you can keep.
The card is the tool’s own output for a sample input, worked out by the same code that runs the form above.
Sample output
For www.example-cafe.example: 10 to fix first, basics score 27/100
01. Built for phones
Fix thisNo viewport tag: phones show a shrunken desktop page.
02. Tap to call
Fix thisThe homepage shows 204-555-0142, but it isn't a tap-to-call link.
03. Booking and contact buttons that go nowhere
Fix thisFollowed 1 booking or contact link: "Book Now" points at "#booking", which isn't on the page.
04. Email links that don't work
Fix thisa mailto link goes to info@yourdomain.com, a template placeholder.
05. Page title and description
Fix thisThe homepage title is just "Home".
06. Business details Google can read
Fix thisNo LocalBusiness structured data (JSON-LD) on the pages we read.
07. An always-open promise with a slow way in
Fix thisThe homepage says "24/7", but the only way in is slow: no tap-to-call, text, chat or booking.
08. About and contact pages with real content
Fix thisNo about or contact page with real content linked from the homepage.
09. Stale dates and notices
Fix thisThe footer's copyright year reads 2019.
10. Link previews look right
Fix thisNo preview title or image for shared links: a texted link shows up bare.
11. Phone and address on the site
Worth a lookFound a phone number, but no postal address (with a postal or ZIP code).
12. Readable without JavaScript
Worth a lookBefore any script runs, the homepage has only 170 characters of text. Many AI crawlers read only that.
Plus 21 more of the 33, passed or not tested: this sample is one page, so robots.txt, the sitemap and Google’s speed test aren’t in it.
The method
Why each rule is there, and how to do the job well with or without the tool. Open any card for the full reasoning.
Why a small thing on your homepage costs you a real customer
A stranger looks for one thing: a way to book, ask or buy. If it's broken, they leave.
Read the reasoning
Someone finds your site, decides in a few seconds whether to trust it, and looks for one thing: a way to book, ask or buy. If that one thing is broken, they don't email to tell you. They leave and call the next name on the list.
We read the homepages of businesses like yours by hand, looking for exactly this kind of thing, as part of our own research before we reach out to anyone. The same handful of problems kept turning up: a booking button that leads nowhere, an email link that goes to the wrong address, a page that still says it's 2019. None of them take long to fix. Most of them take longer to notice, because you don't read your own site the way a stranger does.
What we check, and how
Your homepage and the pages it links to, read as they actually are: no sign-in, no JavaScript run.
Read the reasoning
Put in your website address and we read your homepage, plus up to fourteen pages it links to, contact, booking, services and about first. We also read your robots.txt and sitemap, ask for a page that doesn't exist, and try the http and www versions of your address. We read what's actually there: the page's own text and code, where the links say they go, and what happens when you follow them. No sign-in, nothing typed into a form, no JavaScript run. Google's PageSpeed test measures how fast the page loads on a phone.
33 checks run on what we read, in six areas:
- Getting found on Google: whether Google may show the page, its title, a description on each page, a sitemap, business details Google can read, your phone, address and hours.
- Showing up in AI search: whether ChatGPT, Claude and Perplexity's search bots are let in, whether the page reads without JavaScript, bot walls, missing pages, and buttons with no name.
- First impression on a phone: fits the screen, page weight, oversized images and template leftovers.
- Getting in touch: tap-to-call, booking and email links that go nowhere, whether the dates in your booking form can still be booked, whether Book now leads to a real booking, promises you can't back up, and a privacy note on your form.
- Trust: https, insecure pieces on a secure page, about and contact pages, broken links, stale dates and link previews.
- Speed: how fast the main content shows, whether the page jumps, and how quickly the server answers.
Eight of the checks are ideas drawn from Is Agentic, Vercel and Ora's AI-readiness scanner: readable without JavaScript, real missing pages, business details, about and contact pages, bot walls, a sitemap, and named buttons and fields. When Is Agentic already has a public report for your site, we link it; we never start one for you, since every scan it runs is published.
What counts as a pass, and what we won't guess
Every result says exactly what we found. Nothing is invented, and nothing is guessed.
Read the reasoning
Every result says exactly what we found on your pages, nothing more. A check failed on something we can point to, passed, is worth a look (a smaller problem), or wasn't tested, which means there was nothing on your site for it to test or the measurement didn't happen this time. The fails are ranked by how directly each one loses you a customer. Your basics score out of 100 counts only what was tested, and it covers what can be read from outside the site: a high one means the basics are in place, not that nothing is costing you customers.
We never invent a problem to make the list longer, and we never guess at something we didn't actually read. If your site makes no always-open promise, that check has nothing to test, and it says so instead of failing you for a promise you never made.
Email links that quietly bounce
The address shown as text and the one the link actually opens don't always match.
Read the reasoning
An email address shown as text and an email link that goes somewhere else. A mailto link still pointing at the template's placeholder address from whoever built the site. Tap it on a phone, and the message goes nowhere, or nowhere useful, and you never see it.
We compare the address a link actually opens against the address shown next to it, and flag the ones that don't match or that still carry a placeholder domain.
A promise you can't back up after hours
"Open 24/7" with no instant way in after hours is an expensive promise to break.
Read the reasoning
"Open 24/7", "same day service", "no call goes unanswered". Good promises, and expensive ones if the only way in in the evening is a form that says "we'll reply within two business days." A customer who needed you at 9pm on a Saturday just learned your 24/7 means office hours.
We check whether an always-open or emergency promise on your site is backed by an instant way in: a tap-to-call link, a chat widget, a text link or a booking widget, not just a form that waits for business hours.
Placeholder text and old dates
Leftover template text and dates that have passed, both read as nobody's minding the site.
Read the reasoning
"Lorem ipsum", "Your Company", "Just another WordPress site": the text the site builder left behind, still live because nobody went back and replaced it. A copyright year still reading three seasons ago. A COVID-era notice nobody took down. Each one is a small, honest signal that nobody's minding the site, and a visitor reads it in about one second.
We check the page's visible text for the common leftovers, the footer's copyright year, the dates still on offer in your booking forms, and words that usually mean an old notice is still up, and we say which one specifically, so it's a two-minute fix, not a search.
What still needs you
This reads your site once, when you ask. It doesn't fix anything by itself.
Read the reasoning
This tool reads what's public on your site once, when you ask it to. It doesn't watch your site over time, and it doesn't fix anything by itself: every result is a fix in plain words, and where a tool we've reviewed does the job, we link to it and what it costs.
If you'd rather talk the result through with someone, talk to us: in the free 15-minute call we go over what the check found, what you run, and whether we're the right people for it.
Questions
Is the website leak check free?
Yes. It asks for an email before showing the results, and that address joins our weekly newsletter, which you can leave from any issue. There's no account, and you can run it as often as you like; to keep it available for everyone, only a few checks run from one address in a short time.
Is my website's address or content sent anywhere?
The address you type is sent to our server once, to fetch your public pages and run the check; that's the one free tool here that has to work this way, since a browser alone can't safely fetch another site. From our server, the page address we landed on goes to Google's PageSpeed test, to measure speed (when that test is available), and your site's address goes to Is Agentic, to look up a report it may already have; each of them handles it under its own privacy policy. We don't store it ourselves: it's used for that one check. The one place it lingers is the request log of Vercel, our host, which lists the pages our server fetched and clears within 30 days.
Does it use AI to check my site?
No. The 33 checks are fixed rules run against what's actually on your pages: links, text, code and Google's speed measurements. Nothing is sent to an AI model, and nothing is guessed.
Can it check a site with a login, or one that isn't live yet?
No. It only reads public pages, the same as a customer would, and never submits a form or signs in. A staging site behind a password or a local address can't be checked.
Why these 33 checks?
Six are the leaks that kept costing real businesses customers when we read their sites by hand. The rest come from what Google, the AI search companies and the web's own standards say about being found, trusted and reached, each one something an owner can act on. Two look at booking itself: whether the dates on offer can still be booked, and whether Book now leads to a real booking. We cut anything we couldn't measure reliably from public pages. It's not everything wrong a site could have; it's the list worth checking first.
Want us to fix these?
In the free 15-minute call, we talk through what the check found, what you run, and whether we're the right people for it.
Want to read about the audit first? See how it works.