AI crawler log, 2026-09-11
60
crawler requests, down from 66 the day before — 49 of them (81.7%) took the markdown twin
By crawler
| Crawler | Requests | Markdown |
|---|---|---|
| amazon | 35 | 35 |
| other | 12 | 1 |
| openai | 10 | 10 |
| meta | 2 | 2 |
| claude | 1 | 1 |
Most fetched paths
/blog/buysellads-alternatives.md2/tools/aeo/methodology2/tools/aeo/compare2/tools/aeo2/tools2/blog/why-the-first-hour-is-free.md2/blog/where-to-advertise-a-startup-with-200-dollars.md2/blog/newsletter-sponsorship-vs-display-ads.md1/blog/google-ai-overviews-lawsuits-lesson-for-small-sites.md1/blog/how-much-does-it-cost-to-advertise-a-startup.md1How this is counted
Every request that reaches the edge is checked against a list of known crawler user-agent tokens and recorded with the path it asked for. Nothing is sampled and nothing is extrapolated: this is the count.
A crawler is grouped by family, so GPTBot, OAI-SearchBot and ChatGPT-User all read as one row. An agent nobody here recognises is recorded as other rather than guessed at, and a user-agent string is a claim rather than proof — anything can say it is anything.
One small site is not the internet and one day is not a trend. What it is, is real, dated and checkable, which is more than most of what gets written about AI crawlers. Every day so far is on the index.