Live view digest — 5 November 2026

Google is the most active named crawler in the current 24-hour window at 428 requests, 39% below its average over the previous 44 recorded days.

Snapshot 05 November 2026 13:00 UTC · read from this server’s own nginx log · live view · all digests

Engines today

Google428ClaudeBot269meta-externalagent163Bing111Amazonbot98OAI-SearchBot86GPTBot86Applebot83
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 05 November 2026 13:00 UTC. Verify any figure against /live/ or /data/live.json.
CrawlerRequestsShare of named crawler traffic
Google42829.1%
ClaudeBot26918.3%
meta-externalagent16311.1%
Bing1117.6%
Amazonbot986.7%
OAI-SearchBot865.9%
GPTBot865.9%
Applebot835.6%
PerplexityBot765.2%
CCBot704.8%

Change since the last full day

previouslatestRequests 24h13,0735,759Recognised crawlers3,9491,637
The last completed day (left) against the current 24-hour window (right). Columns are drawn to the same scale. Source: this server's own nginx access log, aggregated every five minutes. Snapshot 05 November 2026 13:00 UTC. Verify any figure against /live/ or /data/live.json.

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 05 November 2026 13:00 UTC. Verify any figure against /live/ or /data/live.json.