Traffic Logs

Open Logs when a summary points to a problem and you need to inspect the individual requests behind it. The table shows identified bot requests, newest first, with provider, bot type, user agent, page path, HTTP status, and timestamp.

Search by page path or user agent to narrow the rows. This is useful when checking whether a particular page is repeatedly requested, or when you want to find one bot by its recorded user-agent text. The search only narrows the loaded log results; it does not change the collection of events or the other report tabs.

Use the status with the path and time to decide what to do next. A 2xx response means the request succeeded, a 3xx means it was redirected, a 4xx means the page was unavailable or access was refused, and a 5xx means the server failed to handle the request. A missing status can occur on older recorded requests that did not include one.

Export downloads the rows currently shown for the selected project and period. Logs shows at most the 200 newest matching requests, so an export is not a complete archive when the site received more than 200 requests in that range. The live indicator means new signals are received as bots visit; it does not mean every automated request on the internet can be identified. If a request is absent, check that the tracker is installed on the right project and that the visitor matches a bot PromptEye recognizes.

A row shows the name the visitor gave for itself, and that name is a claim anyone can write. PromptEye separately compares the address each request came from with the addresses its supposed operator publishes, and records whether the claim held up. That result is not shown in this table yet; it is available through the PromptEye API. So a row naming a well-known assistant tells you what the visitor said, not whether it was telling the truth. See Settings and setup for what the three possible answers mean.

For a response error, note the path and status and share them with whoever maintains the website. A 404 on an old URL may be expected; a 404 on a current product page may need a redirect or a fix. A 403 may come from access rules or a firewall. Logs can show the symptom but do not identify which server rule caused it. See AI crawl health to group repeated errors and redirects.

Not every error here is about your content. Requests for paths such as /.env.backup or /.git/config are automated probing for a way into the site, and they return 404 because those files are not there — which is the correct answer. Crawl health counts how many of these you received, so you can tell a page that genuinely broke from a stranger trying door handles.