Live view digest — 27 September 2026

ChatGPT-User shows up in the current 24-hour window with 1,991 requests and had not appeared in any previous daily aggregate for this site.

Snapshot 27 September 2026 12:05 UTC · read from this server’s own nginx log · live view · all digests

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.
ClaudeBot5,862Google4,648PerplexityBot3,817Amazonbot2,067OAI-SearchBot2,029CCBot1,998ChatGPT-User1,991Applebot1,965
Requests by engine, current 24-hour window. AI answer engines and AI training crawlers are highlighted; search engines are grey. Source: this server's own nginx access log, aggregated every five minutes. Snapshot 27 September 2026 12:05 UTC. Verify any figure against /live/ or /data/live.json.
CrawlerRequestsShare of named crawler traffic
ClaudeBot5,86220.7%
Google4,64816.4%
PerplexityBot3,81713.5%
Amazonbot2,0677.3%
OAI-SearchBot2,0297.2%
CCBot1,9987.1%
ChatGPT-User1,9917.0%
Applebot1,9656.9%
meta-externalagent1,9626.9%
Bytespider1,9586.9%

How to read this

  • What counts as a scan path. Requests to paths that only an automated scanner would ask for (credential files, admin panels, common CMS probes). They are blocked at the edge and counted separately, never inside the crawler figures. They are listed here only to show the noise a public site attracts.

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

Source: this server's own nginx access log, aggregated every five minutes. Snapshot 27 September 2026 12:05 UTC. Verify any figure against /live/ or /data/live.json.