Skip to content
Blog / 7 min read

How to see AI referral traffic in WordPress (without GA4)

You can measure AI referral traffic without GA4, because every click from ChatGPT, Perplexity or Gemini already leaves a line in your server access log. This guide shows three routes: the GA4 route for comparison, a log-based WordPress plugin, and a single grep command that needs no plugin at all.

Each route has a cost. So we look at what each one shows, what it misses, and what you should do with the numbers once you have them.

The Pagereckon team Updated
Ai referral traffic without ga4 at a glance, from Pagereckon

What counts as an AI referral

An AI referral is a visit from a person who clicked a link inside an AI assistant. The assistant answered a question, cited your page, and the reader wanted more. That makes it a human visit, not a bot.

Two signals mark such a visit. First, the browser usually sends a Referer header that names the page the click came from, such as https://chatgpt.com/. Second, some assistants add a tag to the link itself, for example utm_source=chatgpt.com. The tag still works when an app or a privacy setting drops the referrer.

In contrast, an AI crawler is a program. GPTBot or ClaudeBot reads your page to train a model or to build a search index. Crawlers belong in a crawler report, never in your visitor count. Keep this split in mind, since every method below has to respect it.

Way one: the GA4 route

Google Analytics 4 now has a default channel called AI Assistant. According to Google, it collects visits from sources like ChatGPT, Gemini, Copilot and others, matched against a list of AI referrers. So if you already run GA4, open Reports, then Acquisition, then Traffic acquisition, and look for that row first.

If you want one row per assistant, or you miss a source, you build a custom channel group. The steps, taken from Google's help page on custom channel groups, look like this:

  1. Open Admin, then Data display, then Channel groups.
  2. Click Create new channel group. GA4 copies the default group for you.
  3. Add a new channel, for example ChatGPT, with a condition on Source that matches a regex.
  4. Move the new channel above Referral, since traffic goes to the first channel it matches.
  5. Save the group, then pick it in your acquisition reports.
Example regex for the Source condition
chatgpt\.com|chat\.openai\.com|perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|claude\.ai

Where the GA4 route falls short

  • Blocked scripts: GA4 runs in the browser. Ad blockers, privacy browsers and declined cookie banners hide a share of visits before GA4 ever sees them.
  • Referral bucket: a source that is not on the list of AI referrers still lands in Referral, mixed with blogs and forums.
  • Upkeep: new assistants and new domains appear often, so somebody has to update the regex by hand.
  • Limits: a standard property allows two custom channel groups, so the AI split competes with your other needs.

Way two: AI referral traffic without GA4, from your server log

Your web server writes one line per request into its access log. That line holds the address, the page, the referrer and the user agent. It also comes before any script runs, so a blocker cannot hide it.

Pagereckon is a free WordPress plugin that reads that log. It needs no cookies and no tracking script. Instead, it checks each visit with one tiny beacon image to prove a real browser loaded the page. Then it files the visit under its source.

How Pagereckon files AI visits
Signal in the logFiled as
Referrer chatgpt.com or chat.openai.comChatGPT
Referrer perplexity.aiPerplexity
Referrer gemini.google.comGemini
Referrer copilot.microsoft.comCopilot
Referrer claude.aiClaude
No referrer, but utm_source=chatgpt.comChatGPT

Each assistant gets its own row, with a trend and the pages it sends people to. Meanwhile, AI crawlers such as GPTBot and ClaudeBot stay in a separate view, split into training, AI search and live reads. As a result, your AI referral traffic without GA4 contains people only.

The AI referral traffic page explains the report itself. To try it, download the free plugin and let the Find my log wizard locate your log on cPanel, Plesk, CWP or a plain Apache or Nginx server.

Way three: grep the access log, no plugin

If you have SSH access, one command gives you a raw count. It only reads the log, so it changes nothing on the server.

Top pages that AI assistants sent visitors to
grep -E "chatgpt\.com|perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|claude\.ai" access.log \
  | grep -v -i "bot" \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Here is what each part does. The first grep -E keeps lines that mention one of the five AI domains. The dots carry a backslash, so they match a real dot and not any character. Next, grep -v -i "bot" drops any line that mentions bot, which removes most crawlers. Then awk prints the seventh field, which is the requested path in the common log format. Finally, sort | uniq -c | sort -rn counts each path and puts the busiest first.

This route is free and fast. However, it is also rough. It counts every request, including asset files and repeat hits by one reader. It also misses visits that only carry the utm tag in the URL, unless you add utm_source= to the pattern. So treat the number as a quick check, not a report.

Using your AI referral traffic data without GA4

A count alone changes nothing. The value lies in the pages behind it. First, list the pages that receive AI visits. These are the answers an assistant trusts enough to cite.

Next, read each of those pages as an answer. Is the direct reply in the first two sentences? Is the key figure in a table that a model can quote? Small edits there often matter more than new posts.

Then compare them with pages that AI crawlers read often but that never get a click. Those pages get read and passed over. Finally, write down the date of every change. That way you can later see whether the visits moved. Pagereckon Pro does this step with fine-tuning marks and a control-day report, if you want it done for you.

AI referral traffic without GA4: common questions

Can I track AI referral traffic without GA4 at all?

Yes. Your server access log records the referrer of every visit. A log-based plugin like Pagereckon, or a grep command over SSH, can read AI referral traffic without GA4 or any tracking script.

Does GA4 show ChatGPT visits on its own now?

Yes, GA4 has a default AI Assistant channel for sources like ChatGPT, Gemini and Copilot. Still, it only sees visits where its script ran, and a source missing from Google's list falls back to the usual rules.

Why is my log count higher than the GA4 number?

The log line comes from the server, so ad blockers and declined cookie banners cannot hide it. GA4 also drops visits when its script never loads. A gap between the two is normal.

Do AI crawlers count as AI referral traffic without GA4?

They should not. A crawler such as GPTBot is a bot, not a reader. Pagereckon keeps crawlers in their own view. With grep, you remove them by filtering out user agents that contain bot.

Is the grep command safe to run on a live server?

Yes. It only reads the log file and prints a count. On a very large log it can take a moment, so run it outside busy hours if your server is small.

Sources and references

Free plugin, optional Pro

See your own AI traffic in ten minutes

Install the free plugin, point it at your access log and read today's humans, bots and AI visits. Then add Pro when you want Search Console and the before and after reports.