Free tools

See which AI crawlers reach your site.

Find known AI crawler user agents in Apache, Nginx, or CDN logs. Separate search, user-requested fetch, training, and ads traffic, then review status codes and requested paths.

Runs in this browserNo signupNo uploadLOG, TXT, CSV, or TSV

Your data stays on this device

Files are read in your browser and are not sent to Trakkr. Refreshing or resetting clears the analysis. Analytics record only the tool name, input method, file-size band, and row count, never file names or contents.

The downloadable result omits IP addresses and raw user-agent strings.

[01]

Add access logs

Apache and Nginx combined logs work as pasted text. CSV or TSV needs user agent, path, and status columns.

[02]

Method and limits

Purpose matters

Search and user-requested fetchers are separated from training and ads agents. A 200 response does not prove a page appeared in an answer.

Identity needs verification

Bots can copy a user agent. Confirm requests with current operator IP ranges, reverse DNS, and your CDN or WAF data before allowing or blocking them.

Privacy by reduction

The parser retains the named agent, date, method, path, and status for matched rows. It drops IP addresses, query strings, and raw user-agent values from results.

Turn one log sample into monitoring

Trakkr compares crawler activity with separately observed citations, rankings, and AI referral traffic by page and time window. It keeps correlation visible without claiming that a crawl caused a result.

Explore crawler monitoring
[03]

Continue the investigation

[04]

Common questions

Which log formats work?

Paste Apache or Nginx combined access logs, or export CSV or TSV with user agent, path, and status columns. Cloudflare-style column names are recognized.

Does a user-agent match prove it was an AI crawler?

No. User agents can be copied. Treat a match as a clue, then verify source IPs against the operator’s current published ranges before changing firewall rules.

Why is Google-Extended not counted?

Google documents Google-Extended as a robots.txt product token, not a separate HTTP user agent. Googlebot requests can serve several products, so a log line alone cannot attribute a request to Google-Extended.

Are IP addresses or raw logs uploaded?

No. Analysis runs in your browser. IP addresses and full user-agent strings are discarded from the derived result and are not included in the CSV download.