How do you check a site for the agentic web?
In one sentence
The CrawlCheck library is the guides, findings and glossary behind the scanner: each guide checks one thing on any site and reports how often it fails across every scan, each finding is a dated case from a real measurement, and each glossary term is defined once and linked from the report that measures it.
Nothing here is advice from a survey. A guide tells you how to check one thing on any site and what the check usually finds; a finding is a case from a real scan with the bytes behind it; a term is defined once and linked from the report that measures it.
Paying never changes a reading. The rulebook · The crawlers · How a scan works
Guides. Findings. Glossary.
Guides
How to check one thing.
Each guide is one check: what to fetch, what to look for, what it means, and how often it fails across every scan. Start with the three that explain how to read a report.
Findings
What real scans found.
Dated case studies from the public dataset: a robots.txt that could not be read, a crawler name Google says it never sends, a page that served two businesses one identity.
Glossary
Every term, defined once.
751 terms across the machine layer, each with the page that measures it. The definitions are the ones the report and the API use.
Every number here is read from the manifest that publishes it.
Three guides that explain the report.
What the guides cover.
- Security and email — Headers and DNS records a crawler can read: HSTS, CSP, DMARC, SPF, DKIM. (3)
- AI crawlers and access — Who is fetching, whether they can get in, and whether they are who they say. (18)
- AI visibility and answer engines — What can actually be measured about a site inside a generated answer. (8)
- Entities, schema and local presence — Declaring who you are so a resolver does not guess: JSON-LD, NAP, listings. (6)
- Machine files and delivery — robots.txt, llms.txt, sitemaps, canonicals, caches, status codes. (12)
- Site quality, links and accessibility — What a reader, a screen reader and a link checker each need from a page. (17)
Measured this month.
- Agent conduct, October 2026: 34,676 verified crawler requests, and what they did with robots.txt 2026-10-15
- MCP reliability, October 2026: 6,000 remote MCP servers, 39,484 handshakes 2026-10-15
- Share of preflight, October 2026: 0 of 5,643 verified agent requests carried a receipt 2026-10-15
- Robots.txt says yes, the server says no: 57 top sites refuse AI crawlers their own rules allow 2026-10-15
- Release notes 14 Oct 2026: doors, signed weekly figures, trial 2026-10-14