CrawlCheck

Agent conduct

Google-Agent conduct record

Google · live fetch. No rule broken in what was measured: robots.txt does not govern this user-triggered fetcher by its operator’s statement; busiest minute 17 requests, all its addresses combined.

Conductno violations observed
Verified requests217 (from Google’s published ranges)
Forged claims0 — 0% of requests using this name were impersonators
robots.txtnot applicable · 2 robots.txt fetches · 3 fetches of disallowed paths (/r/, /backup/, /admin-old/)
Ratemeasured · busiest minute 17 requests (2026-11-09T19:13 UTC), all its addresses combined; no crawl rate is published here, so this is reported, not judged · measured since 2026-10-31
Revalidation13 conditional requests (6% of verified)
Seen here2026-10-31 → 2026-11-09
Other sites, 14 days0 visitor checks: 0 verified, 0 spoofed

this agent fetches pages a user asked for; its operator states robots.txt does not govern those fetches, so disallowed fetches are reported, not judged the busiest minute of verified requests observed here since the counter started, all of the operator's addresses combined; a lower bound. This site publishes no crawl rate (its robots.txt has no Crawl-delay), so the rate is reported, never judged

Signed record for this agent: /api/v1/conduct/Google-Agent (verify with crawlcheck-verify.mjs). Generated 2026-11-09 20:49 UTC; rebuilt every ten minutes.