Short answer: mostly no. Google Analytics 4 does not show bot or AI crawler traffic in a standard setup. Crawlers such as GPTBot, ClaudeBot and PerplexityBot fetch your pages without running the GA4 tag, and GA4 automatically excludes the bots it does recognize. Your site can be crawled thousands of times while GA4 shows none of it.
That does not mean the crawlers are not visiting. GA4 is built to measure people in browsers, and it is not the place to look.
Why GA4 can miss crawlers
A typical GA4 browser-tag setup records events when a page runs the Google tag's JavaScript. Crawlers that fetch HTML without running that script may be absent. GA4 automatically excludes recognized bots and spiders where possible, but unidentified automation can remain. GA4 also supports server-sent events through its Measurement Protocol. Browser analytics therefore does not provide a complete crawler-request count.
Why GPTBot is not showing up in your GA4 setup
GA4 records a visit when a browser loads your page and runs the Google tag's JavaScript, which then sends an event to Google. GPTBot requests the HTML from your server and stops there. It never runs the script, so no event is ever sent and nothing reaches GA4. There is no setting to switch on: the request simply never touches Google Analytics.
The same is true of most crawlers, including ClaudeBot, PerplexityBot, OAI-SearchBot, Bytespider and CCBot. The few automated clients that do run JavaScript are either removed by GA4's known-bot exclusion, which you cannot turn off or inspect, or slip through and are counted as people.
To see GPTBot you have to look where its requests actually arrive: your server or CDN. GPTBot is also only one of OpenAI's crawlers, and the others matter more for visibility.
Crawler requests vs. AI referrals
Two different things get called "AI traffic":
- AI crawler and fetcher requests. Automated clients such as GPTBot, OAI-SearchBot, PerplexityBot or ChatGPT-User request your pages directly. Standard browser tagging can miss these requests; GA4 is not a complete record of crawler activity.
- AI referrals. A person clicks a link inside an AI assistant and lands on your site in a normal browser. These can appear in GA4 as referral traffic when the assistant passes a referrer or tracking tag.
A crawler fetching your page doesn't mean you were cited, that someone visited or that you made a sale. Keep the two measurements apart.
Where crawler traffic actually shows up
Every request reaches your infrastructure somewhere, so measure there:
- Server access logs from Apache, Nginx or Caddy can record origin requests. Filtering, sampling and retention affect coverage.
- CDN or edge logs also include requests your cache answers without touching the origin.
- Server middleware in your application can record requests as they are served.
Mind the cache. If a CDN answers a request, an origin-only collector never sees it. Know which layer you're measuring before comparing numbers.
Questions server-side data can answer
- Which pages do AI crawlers request most, and how often?
- Are crawlers hitting errors, redirects or pages you meant to retire?
- How much activity is training crawling, and how much is user-triggered fetching?
- Did a change to
robots.txtchange what crawlers request? - Which requests claim a bot name but fail the operator's network check?
Measuring it with PulseAI Analytics
PulseAI collects request records on your server through a WordPress plugin, Node.js middleware, a Cloudflare Worker or an access-log import. The dashboard separates verified operators, crawler claims, suspected automation and estimated human visits, and shows the evidence behind each label. It reports activity and never blocks visitors. Estimated human means not identified as automation, so it can include AI browsers that don't identify themselves. Starter costs $29/month for one website. Read how crawler verification works or check installation requirements first.
For the full picture of what to measure, see AI crawler analytics: what to measure and how to start. If you report to clients, see AI traffic reporting for agencies.
Quick answers
Does Google Analytics 4 track bot or AI crawler traffic?
Mostly no. GA4 records visits when a browser runs its JavaScript tag. Most bots and AI crawlers fetch pages without running it, and GA4 automatically excludes the bots it recognizes. A standard GA4 setup therefore shows little or no crawler traffic.
Why is GPTBot traffic not showing up in my standard GA4 setup?
GPTBot requests your HTML from the server and never runs the GA4 tag, so no event is sent to Google. There is no GA4 setting that changes this. GPTBot requests appear in server-side records such as access logs or a CDN.
Can I see which bots GA4 filtered out?
No. Google says known bot-traffic exclusion is automatic, cannot be disabled, and does not report how much traffic was excluded.
How do I track AI crawler traffic instead?
Measure where requests arrive: server access logs, application middleware, or a CDN or edge worker. A server-side tool can then name each crawler and count its requests.
Does traffic from ChatGPT show up in GA4?
Visits from people who click a link inside ChatGPT can appear as referral traffic when a referrer or tracking tag is passed. That is separate from crawler requests, which GA4 does not show.