Page and site audit, version audit-2027.1
How the AISeeWhy page audit and site audit test a page, and what every saved report records so it can be reproduced.
Version audit-2027.1, released 2026-11-22. First versioned release. Each saved report records the engine version, the rules version, the git commit of the service and the network the check ran from.
What is tested
- The page is fetched as each AI crawler would fetch it: robots.txt rules, the server's answer to each crawler's user agent, and what the page shows without JavaScript.
- Each rule gives a finding with a priority (P1, P2, P3) and a fix; the score is 100 minus the penalties of the findings.
- The full list of rules and the score formula are on the methodology page.
What a saved report records
- The engine version and the rules version (rules change only with a new rules version).
- The git commit of the service that ran the check.
- The vantage: the network the check ran from. A site can answer differently to different networks.
Known limits
- The audit is an external test from one network at one moment. A firewall can treat real crawlers differently from our checker.
- Rules added after a site's previous audit are reported separately, so they do not look like a regression of the site.
How the score works · Other versions: vis-2027.1