[ FREE TOOL ]
Agent readiness scan
Most AI agents and answer engines read your site as raw text: no browser, no JavaScript, no patience. This scan reads it the same way and scores what they can actually see.
The scan needs JavaScript on. Everything else on this page works without it.
[ CHECKS ]
What it checks
Sixteen checks in four groups, weighted by how much they change what an agent can do with your site.
crawlable · 36 points
Can agents get in and move around?
- The first file every crawler reads. It should welcome them and point at your sitemap.
- GPTBot, ClaudeBot, PerplexityBot, Google-Extended and CCBot are named separately in robots.txt. Blocking them is yours to choose, and it settles whether those assistants can quote you at all.
- The index of everything you want found, with dates so crawlers know what changed.
- One stray noindex tag and the page is invisible everywhere. Worth checking monthly.
- Tells machines which address is the real one, so your signals don't split.
- Agents walk a site by following hrefs. Navigation that only appears once JavaScript runs is a dead end to them.
understood · 25 points
Does the page explain itself?
- The line agents quote first. 15 to 70 characters lands cleanly everywhere.
- Your one-sentence answer to "what is this site". 50 to 160 characters.
- A single top heading gives the page one unambiguous subject.
- One attribute that tells every parser what language it's reading.
- Without it, mobile rendering is guesswork and crawlers notice.
- Most agents don't run JavaScript. If your content only exists after a framework boots, they start from a blank page.
answerable · 20 points
Can machines quote you accurately?
- JSON-LD is how machines learn your prices, services and FAQs without guessing.
- og:title and og:image decide how every shared link looks.
agent-ready · 19 points
Is anything written for agents?
- A plain-text briefing for AI assistants at /llms.txt. Most sites don't have one yet.
- A title, a summary and a linked list of pages make the file liftable; a bare paragraph gets skimmed.
[ METHOD ]
How it reads your site
The scan fetches your page server-side and reads the raw HTML, plus robots.txt, your sitemap and llms.txt. No browser, no JavaScript execution: the view most crawlers and AI agents start from.
robots.txt is read agent by agent, past the blanket rule at the top. A site can welcome Googlebot and still turn away GPTBot, ClaudeBot and PerplexityBot by name, and that block is invisible to an ordinary SEO audit.
Nothing is stored. The scan runs, the report renders, and your URL goes nowhere else.
This site scores 100 on its own test: scan daysprint.dev →
[ FAQ ]
Questions
What doesn't it measure?
Rankings, traffic, page speed and writing quality. This is about whether machines can read and quote your site at all - the layer underneath all of those.
Is my website AI-ready?
Run it through the scan above and you'll know in about ten seconds. AI-ready here means an assistant can fetch the page, read what it's about and quote it without guessing. 90 or above is agent-ready; anything under 70 is leaving real gaps, and each one is named in the report with what to change.
What is llms.txt?
llms.txt is a plain-text file at /llms.txt that tells AI assistants what your site offers, in a form they can lift directly: a title, a short summary and a list of your key pages with one-line descriptions. Few sites have one yet, so adding one puts you ahead of most. This scan checks whether yours exists and whether it says anything useful.
Is this the same as GEO or AI SEO?
Close, and underneath it. Generative engine optimisation (GEO) and answer engine optimisation (AEO) are the names for getting your site cited in AI answers. This scan measures the layer that has to work first: whether an assistant can fetch, parse and quote the site at all. A page that fails here is hard to cite however good the content is.
I block AI crawlers on purpose. Is that a fail?
The scan scores reach, so yes, it costs points: those assistants can't quote a site they can't fetch. If the block is a decision you've already made, read that check as confirmation it's working.
Is my URL stored?
No. The scan fetches your site, builds the report in memory, and returns it. There's no database behind this page.
[ NEXT ]
Fix the gaps
Every check above is something I build into client sites by default. If your score has room to move, send me the site and I'll quote the fix.
Get a quote