Free tools / ai-readiness-score
AI Readiness Score
free · no signupOne run over the technical checks AI engines depend on — crawler access, no-JavaScript rendering, schema, answer structure — reported as a score you can take apart.
Run the check
What the score is made of
Six checks, fixed weights, 100 points when all six run. A check that does not run is excluded from the total — never scored zero.
100points, all six checks running. Page speed and Core Web Vitals are deliberately not among them.
readiness-report
example result · not your site—
/ 100
Fix list — ordered by points recoverable
This check runs on our server, and it has to: every input to it — your robots.txt, your raw HTML, your JSON-LD — lives on your domain, and a browser cannot read another domain’s files. No signup, nothing stored beyond the run.
What it measures
Whether engines can read your site — not whether they will mention you
This score answers one question: can an AI engine reach your pages, read them without running JavaScript, and work out what they say? That is a technical question with technical answers, which is why it can carry a number at all.
It does not answer whether an engine will mention you. Nothing on this page measures that. Being readable is a precondition for being quoted — a page an engine cannot fetch or parse is not in the running — but plenty of perfectly readable pages go unmentioned, because a competitor answered the question better, or because the model was working from memory and never fetched anyone.
Can read and will mention are two different claims, and only the first one is measurable here. The second needs a different instrument: asking the engines real buyer questions, repeatedly, and counting what comes back. That is the visibility check, and it is a separate tool for the honest reason that it is a separate measurement.
Where the points usually go
Four failures account for most of the missing points, and none of them is exotic.
01
The content only exists after JavaScript runs
Text that appears when a framework hydrates is text several AI agents never see — they do not execute it. Not a speed problem; the words are simply absent from what they read.
02
A robots.txt group quietly replaced the general one
A crawler obeys the most specific group naming it and ignores User-agent: * entirely once it has one. A group added for a crawl-delay line can remove every Allow rule you wrote.
03
robots.txt says yes and the edge says 403
Your CDN or WAF sits above the file and answers first. This is why the live fetch is a separate check with its own weight — sent with each bot’s user-agent, from our IP, not theirs.
04
Nothing on the page says who you are
No Organization markup, no consistent name, no about page a parser can resolve. An engine that cannot pin your identity has trouble attributing anything it reads to you.
Reading your report
The score is the points earned divided by the points that could be measured, not by 100. Each row shows what its check looked at and what it contributed out of its own weight, so a 70 is always traceable to the 30 points that went missing and where.
If a row reads not measured, that check produced no result — our fetch timed out, the page returned an error, or the API gave back nothing usable. Its weight leaves the denominator with it, and the report says by how much. Re-run later; if it persists, the reason line tells you whether the obstacle is on your side or ours.
The fix list is ordered by points recoverable, which is only a meaningful ordering because the weights are on the page. Excluded checks never appear in it — we do not recommend fixing something we failed to look at.
A check that did not run is not a zero
Our fetch can time out. A CDN can rate-limit us. A page can return a 504 on both attempts. In each case the honest output is not measured, with the reason attached, and the check’s weight comes out of the denominator entirely. Scoring an unrun check as zero punishes a healthy site for our own network problem — and it makes the number unstable: run it twice, get two scores, with nothing wrong at either end. When a check is excluded, the report also shows what the same site would have scored had we zeroed it instead, because that gap is our failure and you are entitled to see its size.
Limitations, stated plainly
We check your homepage and a small set of linked pages, not your whole site — a section that fails while the homepage passes will not show up here. The live fetch carries each bot’s user-agent from our own IP, so a firewall filtering by verified IP range may treat us differently than the real crawler. The schema checks validate structure, not truth: they cannot tell you whether the claims in your markup are correct. And the weights are ours — reasonable, stated on the page, and handed down by no engine, none of which publishes one.
Fair questions.
The same five answers feed this page’s own FAQPage markup — one array, one source.
What does the AI readiness score actually measure?
Whether AI engines can reach and parse your site: crawler access in robots.txt, whether the homepage answers a live request carrying each bot’s user-agent, whether the main content exists without JavaScript, whether Organization and FAQ schema are present and valid, and whether the page is structured as answers. Six checks, fixed weights, all shown with the score.
What happens if one of the checks can’t run?
It is excluded, not zeroed. The check reads not measured with the reason, and its weight is removed from the denominator as well as the numerator — so a score of 70 from 90 measurable points is reported as exactly that. Scoring a failed fetch as zero would punish your site for our network problem and make the number change run to run for no reason.
Does a perfect score mean AI will mention my brand?
No, and any tool implying otherwise is selling something it does not control. This measures whether engines can read and understand your site. Whether they mention you depends on what your pages say, who else answers the question better, and whether the model fetched anything at all. Readability is a precondition, not a cause.
Why can’t this run in my browser?
Because every input to it lives on your domain, not this one. A browser cannot read another site’s robots.txt, raw HTML or JSON-LD — cross-origin responses are unreadable without CORS headers those files never carry. So the check runs on our server, and this page says so rather than borrowing a privacy line that would be false here.
Is page speed part of the score?
No. Speed matters for users and for search ranking, but it is a weak signal of whether an engine can read a page — a slow page that returns complete HTML reads fine, and a fast one that renders everything in JavaScript does not. Mixing the two would make the score mean two things at once and be actionable for neither.
Readable is the precondition, not the result.
See whether AI actually mentions your brand.