What's changed

A new section in the report: an AI assistant reads only your pages and tells you what it understands about your business and whether it finds what a customer asks (prices, opening hours, contact details…), with the page where it is and what's missing. It's for people who have left their email, and it doesn't count towards the score.

When your /robots.txt answers with an anti-bot challenge or a 429 – or, when your site has shut us out, with another page, a refusal or an error – the bots section, the Googlebot test and the rest of the report now say “not seen” instead of showing the bots as allowed or blocked. The score doesn't change.

The directory has four new bots (Meta-WebIndexer, Meta-ExternalAds, OAI-AdsBot and Diffbot-User), which don't count towards the score, and we've rechecked the descriptions against the operators' official documentation. Bytespider is now listed as a search crawler, as ByteDance documents it, and the log checker now confirms visits from Anthropic's bots by their IP.

A CAPTCHA on the entry page, form fields with labels, hidden text aimed at AI, and trust pages (about, contact, privacy and your business details). They're informational: they don't count towards the score.

Your site and up to three competitors, side by side, showing only the differences we can actually stand behind.

Paste your server log and see which AI bots really visit you: we check each IP against the ranges the operators publish. The file never leaves your browser.

If hidden text with instructions for an assistant turns up on your site, we email you.

Free text from your pages (titles, descriptions, alt text) stays in the report but no longer goes into the prompt you paste into your assistant.

An address that doesn't exist, such as a typo, now shows a warning instead of a report and doesn't count towards the analysis limits. If the site only exists with www, or only without it, we suggest that address.

A check only counts towards the score if we've read the entry page or more than half the pages. A site that shuts us out no longer gets good pillars with almost everything unseen: they show “?”.

Start from scratch or from your own file, with three presets.

A section covering the robots.txt, the response to our request, indexing, the canonical URL and the directives for Google, and how to confirm it all with URL Inspection in Search Console.

See at a glance which assistants can reach your site, jump straight to any section and copy a plain-text summary.

We publish llms.txt and llms-full.txt, serve our pages as Markdown to anyone who asks for it, and have a contact page.

A page that answered 200 with nothing in it came out as “Ready”. It now fails Readability, which caps the score.

We checked every AI bot and its rules against the operator's official documentation.

We now check nosnippet, noarchive, max-snippet and the like.

A page for each bot, in all three languages, with what it does, who runs it and the official documentation.

When you share your report link, the preview shows your site's domain and its score. Your email never appears.

Adding a check that doesn't count towards the score no longer changes the version. No scores change.

Open Graph, author and dates, image alt text and heading hierarchy. They're informational.

One row per check, ready to open in Excel or Google Sheets.

Every report records which version of the rules it was scored with.

Turn it on from your report and we'll email you when your site's score, bot access or problems change.

Built from the pages we analysed, with one section per language on multilingual sites.

When Chrome has data from real visitors to your site (CrUX), the report shows it.

Navigation in the HTML, HTML weight, hreflang tags, entities linked to each other, contradictory entity records, a Markdown version of the page, a commerce manifest (UCP) and actions built as buttons. And a pillar we could barely see shows “?”, not a zero.