Your website, as AI actually reads it.
Your buyers ask ChatGPT before they ask you. If those answers never mention you, this tells you why. Paste your URL and see your homepage the way a machine sees it.
17 checks. Most finish in under ten seconds. You keep the results.
Free, no account. 17 checks across four gates.
You can be invisible to AI with nothing on your site looking broken.
Your homepage loads fine. It looks finished. That tells you nothing about what a machine gets when it comes to read you, and the machine is what your buyers are asking.
Two things go wrong most often. Your pages build themselves in the browser, so a crawler receives an empty shell instead of your pitch. Or a security setting somebody switched on months ago quietly turns the crawlers away at the door, while your robots.txt still reads perfectly clean.
Other tools count how often AI mentions your brand. They cannot tell you why the number is zero. This check can, because it looks at the four things that have to work in order. Reach, read, understand, quote. It names the first one you fail and stops there, since that is the only one worth your afternoon.
What it checks
Four things, in the order they have to work. Nothing here is a guess or an opinion from a model, so every finding comes with the fact behind it and you can check any of them yourself in a browser tab. Take the list to a developer and it reads as a work order.
Reach
If they cannot get in, nothing else on this page matters. Sites get locked out by a security setting somebody switched on months ago and forgot about. Your robots.txt can look perfect while it is happening, which is why we knock on the door as a bot and see what comes back.
- ·robots.txt rules for GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, PerplexityBot, Google-Extended, CCBot, Applebot-Extended and three more
- ·A live fetch of your homepage wearing the GPTBot user agent, compared against the same fetch as a browser
- ·noindex directives in meta tags and x-robots-tag headers
- ·Sitemap reachable and parseable
Read
Most AI crawlers do not run JavaScript. If your page builds itself in the browser, they get the empty shell and leave. Your site looks finished to you and blank to them. This is the most common failure we see, and the one owners suspect last.
- ·Word count of the text in the served HTML, with no JavaScript run, reported next to the text-to-markup ratio
- ·Title tag present and descriptive
- ·Exactly one H1
- ·Meta description present and long enough to be useful
Understand
A machine can read every word on your homepage and still not know what you sell. Clever headlines do not survive the trip. One plain sentence saying what this is and who it is for does more here than a rewrite of everything else.
- ·A plain sentence of 8 to 40 words stating what this is and who it is for
- ·JSON-LD present, valid, and typed
- ·Organization and Product or Service schema
- ·Headings phrased as questions, answered directly underneath
- ·llms.txt present
Cite
AI repeats sentences that carry a fact. Pages full of adjectives get read and skipped. "Fast" is not quotable. "Ships in 72 hours" is. This gate asks whether anything you wrote is worth repeating.
- ·Machine-readable dates (schema dateModified, time elements, article:modified_time)
- ·Canonical URL
- ·Density of specific quantified claims in the page text
- ·Open Graph tags
Five verdicts
AI crawlers cannot reach this site.
Crawlers reach this page and receive almost no text.
The page reads fine. It does not give a machine enough to identify what this company is.
Reachable, readable, clear. Nothing on the page is shaped like a quote.
AI can reach this site, read it, and quote it.
Questions
Is this actually free?+
Yes, and it stays free. The scan uses no AI models and no paid services, so it costs us nothing to run. You get your score and verdict straight away. The full report, every finding with its evidence and what to change, comes by email.
What do I actually walk away with?+
A score, the one thing to fix first, and a plain-language instruction for each problem found. Most people forward the email straight to whoever owns the website. Nothing in it needs us to explain it.
How is this different from an SEO audit tool?+
SEO tools grade you against ranking best practices. AI visibility trackers count how often you get mentioned. This sits underneath both, because a mention count of zero tells you nothing about the cause. If a crawler only ever received 40 words from your homepage, that is the cause.
Can I check a site I do not own?+
Yes. Everything here reads files that are already public: your HTML, robots.txt, sitemap.xml, llms.txt. It is what any crawler fetches anyway, so competitors work fine.
What if my score comes back high?+
Then stop working on this and go look somewhere else. Findability is not your problem. Traffic that shows up and does not buy is a positioning problem or a product problem, and both cost you more than this one.
Do you store my results?+
A scan is cached for six hours so running the same URL again is instant, then it expires. We do not publish scans and there is no public list of scanned sites.
Why does it not just ask ChatGPT about my brand?+
Because that costs money every time someone runs it, and a tool with a bill attached has to either charge you or throttle you. We would rather keep this one free. Reply to the report email and we will ask by hand and send you the screenshot.
Findability is one of three layers we fix. The other two are positioning and product. How we work on findability.
A score is a symptom. The audit names the cause.
This check reads four gates on one page. The Broken-Layer Audit reads the whole business and says which of the three layers is costing you growth: positioning, product, or findability. 72 hours, written verdict, fix plan. Credited in full toward any sprint.
Nothing materially broken, no charge. Full audit details → · Sprint pricing →