Monitoring bot access of my sites
My hypothesis is that non-human requests can be identified by non-human review with a good collection strategy. This is how five days worth of data was interpreted by claude:
1,849 records, 181 distinct user agents
- User-initiated fetches.
- ChatGPT-User fetched two pages (5 October 19:17 and 6 October 17:30), with no referer. One minute after the first, OAI-SearchBot began a 30-path crawl that lasted an hour.
- Google-NotebookLM made one fetch on 4 October.
- ClaudeBot. It made 59 requests, all to
robots.txtandsitemap.xml(2 distinct paths), and never fetched a page. - Meta. 190 requests are almost all with a referer.
- GPTBot. Seven requests, first seen 4 October 08:28.
- Bursts.
- 277 requests in two minutes on 5 October at 00:42, from Chrome 131 on Linux, across 272 distinct paths, with no referer. That pattern fits a path scanner. The status column would confirm it.
- 34 requests from Chrome 128 with
OPR/114in two minutes at 23:48 that night, across 32 paths. - 38
AhrefsSiteAuditrequests in one minute (an audit run, separate from AhrefsBot).
- Scanners and profilers. Palo Alto (25), Censys (7), MerchantSecurityScanner (2), BuiltWith (2) and gitscan (2).
- Google tools.
Google-InspectionToolmade 9 requests and Googlebot appeared between 19:49 and 19:53 today. If you ran a live test in Search Console around 20:50 BST, those are yours (NB: I did do this). - Stale browser strings. Chrome 48, 57, 76, 80, 85, 89, 99 and 113 appear.
This is a new feature of https://clientlog.bayis.co.uk which already captures client-side requests from privacy respecting beacon script.