Live view digest — 6 October 2026

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

Snapshot 06 October 2026 12:00 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.
ClaudeBot476PerplexityBot360GPTBot252meta-externalagent168Bytespider168CCBot167Google160Amazonbot157
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 06 October 2026 12:00 UTC. Verify any figure against /live/ or /data/live.json.
CrawlerRequestsShare of named crawler traffic
ClaudeBot47621.5%
PerplexityBot36016.2%
GPTBot25211.4%
meta-externalagent1687.6%
Bytespider1687.6%
CCBot1677.5%
Google1607.2%
Amazonbot1577.1%
OAI-SearchBot1567.0%
ChatGPT-User1546.9%

How to read this

  • What 'unmatched' means. Unmatched requests are those whose user agent does not match a recognised search engine or AI crawler. On a public site almost all of them are ordinary automation: scanners, libraries, monitoring, scrapers. They are published as a separate number precisely so they are not mistaken for search traffic.

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 06 October 2026 12:00 UTC. Verify any figure against /live/ or /data/live.json.