See exactly how we test your site.
- Free scan
- One page’s HTML, 19 rules
- Website test
- An AI agent in a real browser
- Comparison
- Same tasks, browser vs connector
- Rules version
- agent-readiness-0.3
Three ways in. One kind of evidence.
- Your pageAny page for a scan. A site you’ve verified for agent tests.
- ScanFetch the HTMLOne page, no JavaScript, free
- Website testAI agent in a real browserYour tasks, 1, 3 or 5 runs each
- Connector testSame tasks through your connectorIts tools only, no browser
- Checks we control
- 19 published scan rules
- A success check the agent never sees
- Evidence you can open
- Findings with fixes
- Every step, replayed
- Result per run, with uncertainty
We read your page the way most AI tools do.
What one scan fetches
- GET/robots.txtrules read
- GET/your-pageHTML, up to 750 KB
- GET/sitemap.xmllooked for
- GET/llms.txtlooked for
- —JavaScriptnot run
- —Formsnever submitted
- Wait
- 8 s, then one retry of up to 45 s
- Redirects
- Up to 3, crawler rules rechecked at each
- Access restrictions
- Respected, never bypassed
What we check
- Page accessHigh impact
- AI search and assistant accessHigh impact
- Search indexingHigh impact
- Response timeMedium impact
- Page textHigh impact
- Content without JavaScriptHigh impact
- Title and headingMedium impact
- Image descriptionsLow impact
- Phrase to findHigh impact
- HeadingsLow impact
- Structured dataMedium impact
- Structured data matches the pageMedium impact
- Language and descriptionLow impact
- Business identityLow impact
- Heading orderLow impact
- Links in the pageMedium impact
- Links and buttons agents can useMedium impact
- Form labelsLow impact
- Link to findMedium impact
Points follow impact.
How a score adds up
- Passed
- Passed
- Passed
- Failed
- Passed
- Passed
- Failed
- Passed
- Passed
- Not assessed
- Couldn’t assess a check
- It counts neither for nor against you
- Score shown when
- 6+ checks have results and the page was readable
- Never scored
- Training-crawler rules, llms.txt, protection findings
An AI agent tries your tasks in a real browser.
Every step is recorded
- 010:04Opens the home page
- 020:11Clicks
My products
- 030:23Clicks
Bosch dishwasher
- 040:38Reads
Warranty ends 14 Mar 2027
- 050:41Answers
14 March 2027
The agent never sees the check
- Check
- Answer matches
- Expected
- 14 Mar 2027
- Agent answered
- 14 March 2027
- Result
- Passed
- NumbersMust match exactly
- Different wordingCan go to an AI grader
- Other checksA page to reach, or text to find
Each run gets one of five results
What a test may do
- Signed out
- Reads only
- With a test account you provide
- Makes the changes you allow
- Never
- Pays, closes accounts or messages other people
Same tasks, same AI, two ways in.
Browser vs connector
- Held the same
- AI, tasks, checks and limits
- Trials
- 3 to 10, order alternates
Only matched passes count
| Trial | Browser | Connector |
|---|---|---|
| 1Browser first | Passed | Passed |
| 2Connector first | Passed | Passed |
| 3Browser first | Failed | Passed |
| 4Connector first | Passed | Passed |
| 5Browser first | Passed | Couldn’t be checked |
| Both passed | 3 of 5 trials | |
No speed-up without three matched passes.
Know what a scan can’t tell you.
Read the fine print.
Every scan check, in full
| Check | What it asks | Impact |
|---|---|---|
| Page accessAccess | Did the server return the page’s HTML, or an error or verification screen? | High impact |
| AI search and assistant accessAccess | Do your robots.txt rules allow the crawlers behind Google and Bing search, ChatGPT, Perplexity, Siri and other AI assistants? Blocking AI training crawlers is reported separately and doesn’t count. | High impact |
| Search indexingAccess | Does the page ask search engines not to index it (noindex)? | High impact |
| Response timeAccess | Did your server answer within 5 seconds? If the first request gets no answer within 8 seconds, we try once more, waiting up to 45 seconds, and report how long it took. A slow response can have several causes, including a server waking from idle. | Medium impact |
| Page textContent | Can we extract main text from the HTML? | High impact |
| Content without JavaScriptContent | Is the main content in the HTML, or does the page look like an empty shell filled in by JavaScript? This is an inference; we don’t run the page in a browser. | High impact |
| Title and headingContent | Are a page title and main heading present? | Medium impact |
| Image descriptionsContent | Do images have alt text or a decorative marker? Only scored when the page has images. | Low impact |
| Phrase to findContent | Does a phrase you supply appear in the text? Only scored when you supply one. | High impact |
| HeadingsStructure | Does the main content have headings? | Low impact |
| Structured dataStructure | Can we parse the page’s JSON-LD? Having none isn’t a failure. | Medium impact |
| Structured data matches the pageStructure | Do prices and names in the structured data also appear on the visible page? | Medium impact |
| Language and descriptionStructure | Does the page declare its language and include a meta description? | Low impact |
| Business identityStructure | Does the page say which business or person it belongs to, through Organization structured data or a site name? | Low impact |
| Heading orderStructure | Is there exactly one main (H1) heading, with no skipped levels such as H2 to H4? | Low impact |
| Links in the pageActions | Does the main content contain web links? | Medium impact |
| Links and buttons agents can useActions | Are clickable elements real links and buttons, or click handlers that only work with JavaScript? | Medium impact |
| Form labelsActions | Does every form field have a label? Only scored when the page has a form. | Low impact |
| Link to findActions | Does a link you supply appear in the main content? Only scored when you supply one. | Medium impact |
What happens during a scan
We read your robots.txt, request the page and pull out its main text and links. We also look for a sitemap and an optional llms.txt file. We limit request time, response size and redirects, and we never bypass access restrictions or submit forms.
How the score is calculated
Each check that passes earns points by impact: high is worth 3, medium 2 and low 1. The score is the share of available points earned, among the checks we could assess. A check we couldn’t assess doesn’t count for or against you. We only show a score when at least six checks have results and we could read the page.
Reported, never scored
We also report AI training crawler rules, TransicaBot’s crawler access, your sitemap, llms.txt, the page’s preferred address, link-preview tags and publication dates. These don’t change the score. Blocking training crawlers is a legitimate choice, and optional files like llms.txt aren’t required by the major AI services.
Protection findings
Some controls are hidden from people but still available to agents. We classify what we find by its purpose and behaviour: helpful shortcuts, spam traps, controls worth confirming, or hidden forms that send data. The free scan reads HTML and inline styles; it doesn’t use these controls. Protection findings never change your AI readiness score.
How agent tests are graded
On a site you’ve verified, an AI agent tries your tasks in a real browser, several fresh runs each. Each task has a success check: an expected answer, a page to reach or text to find. The agent doesn’t see that check. Numbers must match exactly; different wording can go to an AI grader. Without a check, the result is labelled self-reported.
Signed out, a test only reads. With a test account you provide, it can make changes you allow. It never pays, closes accounts or sends messages to other people.
How comparisons count a speed-up
A comparison runs the same tasks in the browser and through your connector, with the same AI and limits, alternating which goes first. We show a speed-up only when at least three runs passed their check on both sides, and we report medians with their ranges.
See the checks on a real report.
Rules version agent-readiness-0.3