Agent conduct
How each AI and search agent actually behaves
What every verifiable agent did on this site, counted only from requests that came from the address ranges its operator publishes: whether it fetched paths robots.txt disallows, its busiest minute against this site’s own rate limit, and how often its name is forged by others. One property’s census with its thresholds stated; the signed record is at /api/v1/conduct.
| Agent | Verified requests | Forged claims | robots.txt | Busiest minute | Conduct |
|---|---|---|---|---|---|
| Googlebot Google · indexing | 5,517 | 74 | respected | 3/min | no violations observed |
| PerplexityBot Perplexity · indexing | 5,018 | 71 | respected | 23/min | no violations observed |
| GPTBot OpenAI · training | 4,013 | 99 | respected | not yet | no violations observed |
| ClaudeBot Anthropic · training | 3,531 | 67 | respected | 4/min | no violations observed |
| Applebot Apple · indexing | 3,231 | 83 | respected | 4/min | no violations observed |
| OAI-SearchBot OpenAI · indexing | 1,496 | 79 | respected | 4/min | no violations observed |
| Bingbot Microsoft · indexing | 1,244 | 47 | respected | 3/min | no violations observed |
| ChatGPT-User OpenAI · live fetch | 511 | 72 | not applicable | 1/min | no violations observed |
| Google-CWS Google · store listing fetch | 83 | 0 | respected | 1/min | no violations observed |
| Claude-User Anthropic · live fetch | 79 | 53 | not applicable | 2/min | no violations observed |
| Perplexity-User Perplexity · live fetch | 8 | 50 | insufficient data | not yet | insufficient data |
| Google-Site-Verification Google · ownership check | 2 | 0 | insufficient data | not yet | insufficient data |
| Google-Extended Google · training | 0 | 49 | insufficient data | not yet | insufficient data |
| Claude-SearchBot Anthropic · indexing | 0 | 37 | insufficient data | not yet | insufficient data |
| anthropic-ai Anthropic · robots.txt token, not a crawler | 0 | 4 | insufficient data | not yet | insufficient data |
| Applebot-Extended Apple · training | 0 | 1 | insufficient data | not yet | insufficient data |
| FeedFetcher-Google Google · feed fetch | 0 | 1 | insufficient data | not yet | insufficient data |
Verified = source address inside the operator’s published ranges. Forged claims = requests that used the agent’s name from outside them; they are counted against the impersonator, never the agent. A verdict needs 50 verified requests; the site limit is 30 requests a minute; disallowed paths are /r/, /backup/, /admin-old/. Rate and revalidation counters started 7 October 2026. Generated 2026-10-07 16:49 UTC.
Not assessed
These agents were seen here but their operators publish no address ranges, so nothing they did can be separated from an impersonator using their name.
| Agent | Claimed requests | Why |
|---|---|---|
| DuckDuckBot | 48 | no published address ranges: cannot be told from an impersonator |
| Meta-ExternalAgent | 9,665 | no published address ranges: cannot be told from an impersonator |
| Amazonbot | 20,670 | no published address ranges: cannot be told from an impersonator |
| Baiduspider | 924 | no published address ranges: cannot be told from an impersonator |
| AhrefsBot | 4,591 | no published address ranges: cannot be told from an impersonator |
| Bytespider | 185 | no published address ranges: cannot be told from an impersonator |
| CCBot | 240 | no published address ranges: cannot be told from an impersonator |
| Diffbot | 1 | no published address ranges: cannot be told from an impersonator |
| SemrushBot | 6,962 | no published address ranges: cannot be told from an impersonator |
| DataForSeoBot | 2,229 | no published address ranges: cannot be told from an impersonator |
| YandexBot | 2,340 | no published address ranges: cannot be told from an impersonator |
| Timpibot | 4 | no published address ranges: cannot be told from an impersonator |
| YouBot | 190 | no published address ranges: cannot be told from an impersonator |
| Scrapy | 10 | no published address ranges: cannot be told from an impersonator |
| MistralAI-User | 9 | no published address ranges: cannot be told from an impersonator |
| cohere-ai | 9 | no published address ranges: cannot be told from an impersonator |
| FacebookBot | 1 | no published address ranges: cannot be told from an impersonator |
Where the counts come from
Every request to this site that names a tracked agent is checked against the operator’s published ranges and counted by path. Other sites add what they found through Visitor Resolve (the site_checks column in the record). The method and limits are in the glossary; the monthly population view is the Agent Traffic Index.