Log Explorer: your raw request log, filterable and shareable
A new Log Explorer page shows the raw request-level log for any site, filter by time range, bot, verification status, IP, path, status, method, country or user agent, click any value to drill in, open any row for full detail, and share the exact view as a link.
Every report in the dashboard is built from request-level data, and now you can see it directly. The new Log Explorer shows the raw log for any site:
- Filter on what matters: time range, bot name or classification
(human / search / AI), verification status, client IP, path, status code or class, method, hostname, country, and user-agent substring, combined freely.
- Click to drill. Click any value in the table, an IP, a bot name, a
status code, and it becomes a filter.
- Full request detail. Open any row for the complete enriched record:
geography, ASN and network owner, bot verification verdict, protocol and TLS version, device, browser, OS, timing and byte counts.
- Share the exact view. Filters live in the URL, so any slice of the
log is a link you can hand to a colleague.
- Alerts link straight to the evidence. Alert emails and the alerts
page now deep-link to the Log Explorer pre-filtered to the traffic that triggered them, from "something happened" to the raw rows in one click.
- Honest about freshness. Recent data streams in near-real-time for
sites with detailed analytics; historical queries note when the archive is still being searched instead of showing an empty page.
- See the shape before you dig. A volume histogram above the table
shows matching-request counts over time (bots highlighted), click any bar to zoom the view to that moment.
- Your table, your columns. A column chooser adds host, referer, full
user agent, device, network owner and response time; choices are remembered in your browser.
- Saved views. Name a filter set ("GPTBot errors") and reapply it in
one click. Stored in your browser only.
And it ships across every surface at once: the same filtered query is available on the public API (GET /public/v1/websites/{id}/requests), as a get_requests MCP tool (ask Claude "show me GPTBot's 404s yesterday" and get the actual rows), and as loglens requests in the CLI, plus an "Export this view" button that hands your current filter set straight to the background export system. MCP server v1.5.0; CLI v1.6.0.