How the Jrooky AI readiness score works

A Jrooky scan runs a set of checks on your site and turns them into one number from 0 to 100. This post explains exactly how that number is calculated, so you can see why your site scored what it did and which fix will move it the most.
The short version
- Each check is worth a set number of points, based on how much it matters to AI tools.
- Your score is the points you earned divided by the points available, as a percentage.
- Some checks give partial credit instead of all or nothing.
- A few serious problems cap your score, no matter how well everything else does.
llms.txtis shown in your results but never counts toward the score.
What each check is worth
Checks are weighted high, medium or low. A high check is worth three times a low one, and a medium check twice as much.
| Check | Weight |
|---|---|
robots.txt rules for AI crawlers | High |
| Server-side rendering | High |
| HTTPS / SSL | High |
| HTTP Status (do your sitemap's pages load?) | Medium |
| Sitemap | Medium |
noindex and canonical tags | Medium |
| Snippet controls | Medium |
| Core Web Vitals | Medium |
| Schema markup | Low |
| Markdown negotiation | Low |
| Content freshness | Low |
| Server response time (TTFB) | Low |
| Page size | Low |
llms.txt | Not scored |
The high-weight checks decide whether AI crawlers can get to your content at all. If a crawler is blocked, sees an empty page or can't open a secure connection, nothing else on the list matters much. The low-weight checks help AI tools understand and trust your pages, but a site can still be read and cited without them. For what each check looks for, see What does "AI-ready" actually mean?
Here's how that plays out. With every check passing you score 100. If only server-side rendering fails, you lose its 3 points out of 24, and the score drops to 88. If only page size fails, you lose 1 point and land on 96.
Partial credit
Some checks aren't simply pass or fail, so they earn a share of their points:
robots.txtearns credit for each of the five AI search and browsing agents it allows (ChatGPT search, ChatGPT browsing, Claude search, Claude browsing and Perplexity). Blocking training-only crawlers likeGPTBotorClaudeBotcosts nothing. That's a business decision, and it doesn't stop AI search from citing you.- HTTP Status earns credit for the share of checked pages that return a normal
200response. If 58 of 60 pages load, it earns 58/60 of its points. - HTTPS earns half its points when your certificate is valid but plain
http://addresses don't redirect tohttps://. - Core Web Vitals averages its three measures: full credit for each one rated good, half for "needs improvement" and none for poor. The thresholds come from Google.
When your score gets capped
Three problems are serious enough that a high score would be misleading. If one of them shows up, your score can't go above a set limit, even if every other check passes:
| Problem | Maximum score |
|---|---|
robots.txt blocks every AI search and browsing agent | 40 |
| No server-rendered content on your homepage | 50 |
| HTTPS is missing or the certificate is invalid | 50 |
"No server-rendered content" means AI crawlers that don't run JavaScript see an empty or nearly empty page. A page that's mostly rendered in the browser but still has some text in the HTML fails the check without triggering the cap.
When a cap applies, your report says so and shows what the score would have been without it. If more than one cap applies, the lowest one wins.
Why llms.txt doesn't count
llms.txt is a proposed file, not a formal standard, and
Google says
you don't need it to appear in AI Overviews or AI Mode. It can still help AI agents find
your key pages, so Jrooky reports whether you have one, marked with an info icon. Having
it or not never changes your score or your section scores.
What the bands mean
| Score | Band | What it means |
|---|---|---|
| 90–100 | Good | AI tools can reach, read and cite your site. Only small gaps remain |
| 50–89 | Needs work | AI tools can use your site, but some fixes would help noticeably |
| 0–49 | Poor | Something is likely stopping AI tools from reading your site |
Each section of the report (AI Accessibility, Indexing & Citation, Content Signal and Performance) also gets its own score from 0 to 100, worked out the same way using only the checks in that section. Caps only apply to the overall score.
Where to start fixing
Under your score, the report lists your top fixes: the failed checks that cost the most points, with any check causing a cap first. Each one shows how many points fixing it would add back, so start at the top of that list.
Score versions
The scoring rules have a version number, shown at the bottom of every report. This post describes version 1.0. If the weights, caps or bands change, the version changes too, so two scores are only directly comparable when they share a version.
Run a free scan to see your score and your top fixes.