Live view digest — 4 November 2026
ChatGPT-User shows up in the current 24-hour window with 352 requests and had not appeared in any previous daily aggregate for this site.
The new arrival
- A first appearance means the crawler found the site on its own or followed a link; nothing here was submitted by hand.
- One day of activity says little. What matters is whether it returns, and whether it fetches pages that are meant to be found.
- It is still only a crawl: no citation, ranking or traffic follows automatically.
| Crawler | Requests | Share of named crawler traffic |
|---|---|---|
| ClaudeBot | 1,039 | 21.0% |
| 762 | 15.4% | |
| meta-externalagent | 648 | 13.1% |
| Bing | 382 | 7.7% |
| GPTBot | 379 | 7.7% |
| PerplexityBot | 354 | 7.2% |
| ChatGPT-User | 352 | 7.1% |
| Bytespider | 351 | 7.1% |
| CCBot | 347 | 7.0% |
| OAI-SearchBot | 337 | 6.8% |
How to read this
- How a crawler is identified here. Crawler identity comes from the user agent string in the request. That can be claimed by anything, so these numbers are indicative rather than audited: a request that says ClaudeBot is counted as ClaudeBot, and anything unrecognised is reported as unmatched instead of being folded into a named engine.
What this is not
- One site only. This is a dated record of one small site, not a benchmark, an index or a projection.
- Crawler identity is claimed, not proven. User agents can be spoofed, so unrecognised traffic stays unverified rather than being assigned to a named engine.
- A crawl is not a citation. Being fetched is a precondition for being mentioned, never evidence of it.
- Every figure is derived from this server's own access log. No third-party analytics are used, so there is no second set of numbers.
Do the same on your own site
- AI Crawler Radar — check whether your pages are readable to the engines you just saw
- AI Access Badge — state your crawler policy in one line
Source: this server's own nginx access log, aggregated every five minutes. Snapshot 04 November 2026 13:00 UTC. Verify any figure against /live/ or /data/live.json.