Is your website ready to be recommended by AI?

It fetches your homepage, your robots.txt, your sitemap and your llms.txt, then runs around 25 checks across five areas: whether AI crawlers are allowed in, whether your business identity is machine-readable, whether the page structure can be parsed, whether your content is written in a quotable way, and whether it looks current. Every result you see reflects something genuinely found on your site — not a guess. One detail worth stating plainly: a browser cannot read another website's files directly, so those requests travel through a third-party relay service. We only ever request pages that are already public, and we never send anything about you to it.

No, and be sceptical of any free tool that claims it does. Asking six AI engines dozens of real customer questions, repeatedly, can't happen from a web page — it takes actual prompt runs against each engine. That's the free audit. This checker measures your readiness: the conditions that have to be true before a recommendation is even possible.

Because those live on other people's websites. Your Google reviews, directory listings, press mentions and forum discussions are the strongest signals in AI recommendations — research puts brand mentions at roughly three times the influence of backlinks — but they can't be read from your homepage. That gap is why the score above is about readiness rather than visibility.

Your page's content isn't stored — it's analysed in your browser and discarded when you close the tab. We do record two things in our analytics: the domain you checked and the score it got, so we can see which kinds of sites the tool is used on and improve it. Your name and email are only ever sent if you choose to request the report. Because browsers can't read other websites directly, page content is relayed through a public proxy service to reach your site — the same way a link preview works, and only for pages that are already public.

Usually one of three things: the site is behind a login or password, it's protected by a firewall that blocks automated requests (Cloudflare "under attack" mode does this), or the public relay we use is temporarily rate-limited. Worth noting: if a bot-blocker is stopping this check, it may well be stopping AI crawlers too — which is itself a finding worth investigating.