Only what a bot sees
We read the site from the outside, like an AI crawler: robots.txt, HTML, markup, server responses. No access to your admin or analytics is needed.
What we check, how the score out of 100 is built and why. The formula is public: one site — one score.
We read the site from the outside, like an AI crawler: robots.txt, HTML, markup, server responses. No access to your admin or analytics is needed.
The formula is public and the same for everyone: the same site gets the same score. Your site's text is not sent to language models.
A robots.txt line, a server response, a page address — you can see where each conclusion came from. In the full audit — for every fix.
Every item says what is there now, what to do and how to verify. Fixes are ordered by impact / effort.
Readiness score = 100 × points earned / maximum of the items checked. An item we could not check drops out of both. If fewer than 60 of the possible 100 points were checked, we don't give a score, so as not to mislead.
Content items are counted across all pages read: the result is the average.
Six areas, 25 items. An area's weight is how much it contributes out of 100.
robots.txt and the server's answer to ChatGPT, Claude, Perplexity, Gemini and Alice bots.
| Item | Points |
|---|---|
| robots.txt is open to AI search and user-request bots (OAI-SearchBot, ChatGPT-User, PerplexityBot…) | 10 |
| robots.txt is open to model-training bots (GPTBot, ClaudeBot, Google-Extended…) — blocking them is legitimate, the penalty is mild | 3 |
| The server returns the home page to AI bots, not a 403, captcha or firewall page | 5 |
| No noindex, noai or noimageai in meta robots or X-Robots-Tag | 2 |
Whether page text is visible without JavaScript: most AI bots don't run it.
| Item | Points |
|---|---|
| Share of the home page text visible without JavaScript | 10 |
| The raw HTML has the title, H1, main text and contacts | 5 |
llms.txt and llms-full.txt — a site map and the full text for AI agents.
| Item | Points |
|---|---|
| /llms.txt opens and is text, not an HTML placeholder | 4 |
| llms.txt structure: heading, description, sections with links | 3 |
| llms.txt links point to your site, work, and are not template placeholders | 3 |
| /llms-full.txt — the full site text for AI agents | advice |
Organization markup, contacts, profiles — how AI understands whose site it is.
| Item | Points |
|---|---|
| Organization or LocalBusiness markup on the home page: name, address, logo, contacts | 6 |
| sameAs links to company profiles (2GIS, Instagram, LinkedIn…) | 3 |
| Page type markup: product, service, article, FAQ, breadcrumbs | 5 |
| canonical and Open Graph (og:title, og:description, og:image) | 3 |
| There are “About” and “Contacts” pages | 3 |
An answer in the first paragraph, numbers, tables, FAQ — what AI quotes.
| Item | Points |
|---|---|
| Answer first: a 20–90-word paragraph with specifics at the top of the page | 7 |
| Headings: one H1, at least three H2, no skipped levels | 4 |
| Tables and lists — facts that are easy to extract | 4 |
| A question-and-answer block | 4 |
| At least 300 words and numbers in the text | 3 |
| Links to sources and attributed quotes | 3 |
Dates, authors, sources and a fresh sitemap.
| Item | Points |
|---|---|
| Publication and update dates on articles | 3 |
| Authors on articles | 2 |
| sitemap.xml exists, is listed in robots.txt, with recent dates | 3 |
| HTTPS with a valid certificate, http redirects to https | 2 |
Calculated from the same pages, 0 to 100, and not part of AI readiness: good SEO does not guarantee AI will quote you.
| Item | Points |
|---|---|
| title of 10 to 70 characters | 15 |
| description of 50 to 170 characters | 10 |
| One H1 per page | 15 |
| canonical is set | 10 |
| og:title is set | 5 |
| The page is indexable and returns 200 | 20 |
| The language is set in <html lang> | 10 |
| hreflang for language versions | 5 |
| Server response under 1.5 s | 5 |
| Page HTML under 2 MB | 5 |
The same formula, but bot access (robots.txt and server response) is counted only for that engine's bots. So a site can be open to ChatGPT and closed to Alice.
These items are not part of the score: we show them with evidence and fixes. They will join the next methodology version, based on real checks.
Free check: the home page and up to 9 more pages from the sitemap, of different types (catalogue, service, article, contacts). No sitemap — we take links from the home page.
Full audit: 30 pages; you can buy more or name your own — but no more than the site has.
We open pages with JavaScript in a browser and compare with what is visible without it: the home page in the free check, the home page and one more in the full audit.
AiseenBot does the reading: it respects robots.txt and does not overload the server. How AiseenBot works
We look not only at robots.txt but at what the server actually returns to AI bots, and what is visible without JavaScript. A site with an open robots.txt but a firewall that blocks bots scores lower with us.
No. The score is about readiness: AI can read and understand the site. Whether it appears in answers also depends on demand, competitors and the site's authority.
Below the report there is “Score wrong?”: pick the item and describe what is wrong. If we made a mistake, we fix the check for everyone.
Yes, as AI search changes its rules. A new version gets a new number; old reports are shown by their own version, so before/after comparisons stay fair.
Not in this methodology: it is about whether the site is ready. Checking AI answers will come in the extended audit.
15 seconds — and you'll know whether ChatGPT, Claude and Alice can see your site.
Check a site