Skip to content

Know which AI crawlers reach your site.

Runs in this browser. No signup. No data upload.

Find known AI user agents in access logs. Review their purpose, response codes and requested paths.

Add access logs

LOG, TXT, CSV or TSV · Up to 5 MB

UTF-8 text. Read locally, never uploaded.

Add data to begin

Your data stays on this device.

Files are read locally. Refresh or reset clears the analysis. Usage analytics record summary metadata, never file names or contents. Only the first 50,000 rows are analysed.

A match is not
a verified identity.

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.

Connect a supported log source to follow crawler activity over time. Review page-level access alongside separately measured citations, rankings and AI referrals, then investigate persistent gaps.

Explore crawler monitoring

Continue the investigation.

Verify a crawler profile ↗

Check official purpose, control tokens, user agents and identity guidance.

Read the crawler study ↗

Use the dated sample, method and limits behind Trakkr crawler observations.

Compare observed request share ↗

See the current panel denominator, provider and purpose distinctions.

Install ongoing monitoring ↗

Choose a source for Cloudflare, Vercel, Netlify, WordPress, CDN or self-hosted sites.

Before you
change access.

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.