Readers who click a link inside ChatGPT are probably in your stats already. In most analytics setups they sit in a long list of referring sites, or they’ve been counted as direct traffic, and you can’t tell them apart from a forum link or a bookmark.

To track them, you need to know how these visits arrive. After that it’s a matter of grouping them in one place.

How a visit from ChatGPT arrives

When someone clicks a link in an assistant’s answer, their browser opens your page and tells your site where the click came from. That’s the referrer. Browsers only pass the origin of the page by default, so your site sees https://chatgpt.com/ and nothing about the conversation. Perplexity arrives as perplexity.ai, Claude as claude.ai, Gemini as gemini.google.com and Copilot as copilot.microsoft.com.

ChatGPT also adds a tag to the links it cites. OpenAI says it appends utm_source=chatgpt.com to referral URLs, so the page address itself carries the source:

https://example.com/best-trail-shoes/?utm_source=chatgpt.com

Those two signals overlap, and they fail in different places. Apps often strip the referrer, so a link tapped in a phone app may arrive with no referrer at all. The UTM tag survives that, but only ChatGPT adds one, and only an analytics tool that reads UTM tags will see it.

Some visits leave no trace at all. A reader who copies your address out of an answer, or reads your brand name and searches for it later, arrives as direct or as a Google search. Every method below undercounts AI traffic for that reason, so read the figures as a floor.

Checking by hand

If you have access to your server’s access logs, each line records the referrer of the request. Searching the log for chatgpt.com or perplexity.ai shows you the clicks and which pages they landed on. It’s slow, logs usually rotate after a few days or weeks, and you’re reading raw lines instead of a report.

In Google Analytics 4 you’d build a custom channel group with a rule that matches the assistants’ domains. That works if you’re staying on GA4. If you’re leaving it, or never used it, you want the grouping done inside WordPress.

AI assistants as their own source in Vireo

Vireo Analytics files every visit under one of six sources: Direct, Search, AI assistants, Social, Email and Other sites. A visit counts as AI assistants when its referrer matches one of the assistants Vireo recognises: ChatGPT, Claude, Gemini, Perplexity, Copilot, DeepSeek, Grok, Mistral, Poe, You.com, Phind and Meta AI.

Three places show them.

The Where visitors come from card on the Overview has an AI assistants group, with each assistant on its own line. Click an assistant’s name, such as chatgpt.com, and you get its own screen: pageviews and visitors in the range, a daily chart, and “Posts it sent people to”. That last list is the useful one. It tells you which of your posts the assistant is recommending.

The Source filter at the top of the dashboard narrows the totals, Where visitors come from and What changed to one group. Set it to AI assistants and the headline numbers show only the readers assistants sent you, with the change on the previous period.

The Search & AI tab has the AI assistants card, which lists the readers each assistant sent next to the pages their crawlers fetched from your site. What AI crawlers take, and what AI assistants send back goes through that comparison.

The grouping happens when you look at the report, against referrers Vireo has already stored. So it covers the history you collected before you knew to look, and if you import your Google Analytics 4 history, the visits GA4 recorded with a chatgpt.com referrer come across and land under ChatGPT too.

The UTM tag, with Vireo Pro

The free plugin reads the referrer only.

Vireo Pro reports UTM tags. Its Campaigns tab lists visits by source, medium and campaign, so the tagged ChatGPT visits show up there under chatgpt.com, including the ones whose referrer was stripped. The campaign is taken from the first page of the visit.

Reading the numbers

AI referrals are small on most sites. A post might get a handful of ChatGPT visits in a week, and one person sharing an answer can double that. Set the range to 30 or 90 days before you draw any conclusion.

Then look at which posts the assistants send people to. A post that shows up in “Posts it sent people to” is answering questions for readers you never see, so keep it current. An assistant citing an out-of-date page sends people to an answer that lets them down.

The ratio matters too. If AI crawlers fetch thousands of pages for every reader the assistants send back, that’s your site feeding answers that rarely link out. The AI assistants card puts the two figures side by side, and the AI assistants docs explain how each one is counted.

Adding an assistant

A developer can add an assistant to the list with the vireo_ai_sources filter, matched on the referrer’s host name.

Vireo answers the practical questions: whether assistants send you anyone, and which posts they point to. The referrers docs cover the other four sources.