Live view digest — 14 November 2026

Applebot is the most active named crawler in the current 24-hour window at 272 requests, 33% below its average over the previous 53 recorded days.

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

Engines today

Applebot272Yandex145Bing59Amazonbot30Google28GPTBot6OAI-SearchBot5Bytespider2
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 14 November 2026 13:00 UTC. Verify any figure against /live/ or /data/live.json.
CrawlerRequestsShare of named crawler traffic
Applebot27249.5%
Yandex14526.4%
Bing5910.7%
Amazonbot305.5%
Google285.1%
GPTBot61.1%
OAI-SearchBot50.9%
Bytespider20.4%
DuckDuckBot20.4%
meta-externalagent10.2%

Change since the last full day

previouslatestRequests 24h4,9542,471Recognised crawlers1,469550
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 14 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 14 November 2026 13:00 UTC. Verify any figure against /live/ or /data/live.json.