AI Traffic:
How Many Visitors AI Assistants Send You
GA4 sees AI traffic only when its script runs and a referrer or UTM tag survives the trip. Citerank counts it at your own server instead: every time ChatGPT, Perplexity, Claude, Gemini or Copilot reads a page for someone, and every person who comes through, tagged or not, per platform, per day.
Browser analytics see part of your AI traffic. Your server sees all of it.
A browser analytics tag like GA4 learns where a visitor came from through the referrer or a UTM tag, and only once its script has loaded and consent allows it. Ad blockers, declined cookie banners, AI apps that open links in the system browser, and outages like ChatGPT's October 2026 bug that dropped both the referrer and the tag all leave AI visitors filed as "direct". And no browser tag ever sees ChatGPT, Claude or Perplexity reading your pages, because those requests never run JavaScript.
Citerank connects the two. A visit is credited to an assistant only when it carries an AI referrer or tag, or when it lands with no referrer on a page that assistant read for someone in the previous 15 minutes. Each read is credited once, and a read that fails verification credits nothing.
One report, per platform, per day
-
Daily visits by platform
ChatGPT, Perplexity, Claude, Gemini, Copilot, Meta AI, Grok and DeepSeek, stacked per day, with each visit's evidence: an AI referrer, an AI utm tag, or the read it followed.
-
Reads to visits
How often each assistant read your pages to answer someone, how many of those answers sent a visitor, and which pages assistants read constantly but nobody visits.
-
Verified, not claimed
AI agents are checked against each vendor's published IP ranges or Web Bot Auth signature. Anything pretending to be ChatGPT is counted separately and kept out of every other number.
-
Alerts when something breaks
A firewall rule blocking ChatGPT, a search crawler that stopped visiting, an AI agent refused with a 403, a source that went quiet: flagged with what to fix.
Cloudflare, WordPress, Vercel, Netlify, or your log files
Deploy the Citerank Cloudflare Worker in front of any site, install the WordPress plugin, point a Vercel, Netlify or Cloudflare Logpush log drain at Citerank, or upload nginx and Apache access logs to see up to 12 months of history at once. No visitor IP address is stored.
Frequently Asked Questions
- How can you count ChatGPT visitors who arrive without a referrer or UTM tag?
- When ChatGPT answers someone, it reads the pages it uses: a request from the ChatGPT-User agent reaches your server. Citerank records that read at your server, then credits a visitor who lands on that same page with no referrer within the next 15 minutes. Each read is credited with one visit at most, so these visits can never outnumber the reads behind them.
- Is this more accurate than GA4?
- For AI traffic, yes, for concrete reasons. GA4 runs in the browser: it counts a visit only after its script loads and the visitor's consent and ad blocker allow it, and it credits an AI assistant only when the referrer or UTM tag arrives intact. It never sees AI assistants reading your pages, because they do not run JavaScript. Citerank counts at your server, where every request arrives, so it sees the reads, the tagged visits and the untagged ones. Keep GA4 for on-site behaviour; use this for what AI actually sends you.
- Is any of this estimated?
- No. Every visit is a request your server received, from a person with an AI referrer, an AI utm_source tag, or a no-referrer landing that followed an assistant's read of the same page. Every read is checked against the vendor's published IP ranges or Web Bot Auth signature where the vendor offers one, and reads that fail the check are left out of every number.
- What do I need to install?
- One of four sources: the Citerank Cloudflare Worker (any platform behind Cloudflare, sees cached pages too), the Citerank WordPress plugin (version 1.8 or later), a log drain from Vercel, Netlify or Cloudflare Logpush, or an upload of your existing access logs going back up to 12 months.
- Does it collect personal data about my visitors?
- No visitor's IP address is stored, and the Worker and plugin never send one. For a matched visit they send the time, the page and the device type. An AI agent's IP address is checked against the vendor's list and then discarded. Uploaded log files are read in your browser, and only the AI lines are sent.
- How is this different from AI visibility or citation tracking?
- Citation tracking tells you whether an assistant mentions you when asked a question. AI Traffic tells you what actually happened at your site: how often each assistant read your pages for someone, and how many people came through from each one, per day.