Method
A one-off audit, from an export of your logs: nothing to install on your website.
How it works
You export thirty days of logs
From Cloudflare, Akamai or your servers. With fewer than thirty days, the report says so and gives its figures for the period available.
You sign the data processing agreement
Before anything is sent: logs contain your visitors’ IP addresses.
LogGrain reads the logs
Each agent request is tied to its assistant and checked against the addresses published by its operator; refusals and fake agents are set apart.
You receive the cross-section report
Within five working days of receiving the export.
The logs to export
- Cloudflare
- A Logpush job, “HTTP requests” dataset, in ndjson. Cloudflare does not keep these logs by default: without an existing job, one has to be created, then thirty days awaited.
- Your servers (nginx, Apache)
- Logs in the “combined” or “main” format, raw or compressed. Behind a CDN, the log must also contain the visitor’s original address.
- Akamai
- DataStream 2, in JSON.
To attach: the sitemap of your product pages, to measure the share of the catalogue that agents read.
The cross-section report
A written report, without any visitor address, in eight parts:
- What LogGrain read
- Agents, by assistant
- Agents refused by the site
- Product pages most read by agents
- Probable impersonation
- Humans referred by an AI
- The two signals
- What this report does not say
The connector
Agent visits written into Piano or GA4, next to human traffic. In development.
What are agents reading on your site?
To request the audit: hello@loggrain.com