How much of your traffic comes from AI assistants
Published 28 October 2026 · 6 min read
People now ask a chat assistant where they used to search, and some of them follow the links it gives. Those visits are worth knowing about on their own: they arrive with a question already answered, and they grow or shrink with how assistants describe you. Most analytics files them under Referral, beside every blog that ever linked to you, so they are hard to see.
This article covers how a visit from an assistant reaches your site, which of them can be recognised, which cannot, and what to look at once you can see them.
How a visit from an assistant arrives
A visitor who clicks a link in an assistant's answer arrives in one of three ways:
- With a referrer. The browser tells your site which site the visitor came from, as it does for any link. Across sites, browsers send only the hostname, such as
chatgpt.comorperplexity.ai, never the page or the conversation. That hostname is enough to name the assistant. - With a tagged link. Some assistants add a campaign tag to the links they show. OpenAI says ChatGPT adds
utm_source=chatgpt.comto the links it refers (OpenAI: publishers and developers FAQ), so the visit names its source even when the browser sends no referrer. - With neither. A link copied out of an answer and pasted into a browser, or opened from an app that sends no referrer, arrives with nothing to say where it came from. It counts as Direct, like a typed address or a bookmark.
The first two can be counted as assistant traffic. The third cannot, by any tool, because nothing in the visit says where it came from. So assistant traffic is always a floor: at least this many came that way, and some of your Direct visits did too.
What is not assistant traffic
Two things look like it and are not:
- Crawlers. Assistants and the companies behind them fetch pages to read them. A crawler is not a person, and analytics that counts people should not count it. A crawler that fetches a page without running its scripts never sends an analytics event at all.
- Answers inside search results. When a search engine shows an AI-written answer above its results and someone clicks a link in it, the visit comes from the search engine. It is Organic Search, and nothing in the visit says that an answer, not a result, was clicked.
Reading it once you can see it
Counting assistant visits as a channel of their own, beside Organic Search, Social, Email and Referral, answers three questions:
- How much, and is it growing? The channel's visitors over time, against the period before.
- Where do they land? Filter to the channel and read the entry pages: the pages assistants point people to, which need not be the ones search sends them to.
- Do they convert? Choose a goal, such as a sign-up, beside the channels. A small channel with a high conversion rate is worth more attention than its size suggests. The conversion article covers goals and funnels.
Each assistant can also be read on its own, by source: ChatGPT, Claude, Perplexity, Gemini, Copilot and others each have a row.
Reading Direct with care
Because some assistant visits arrive as Direct, Direct itself carries a hint. A typed address or a bookmark usually lands on the home page; a link copied out of an answer usually lands on the page that answers the question, such as a guide, a comparison or a pricing page. So a rise in Direct visits to deep pages, with no campaign or newsletter to explain it, is worth noticing beside a rise in the AI Assistants channel. It is a hint, not a measurement: a shared link in a chat app or an email arrives the same way, and nothing in the visit tells them apart.
The same care applies to comparisons over time. If the assistant channel doubles, it may be that more people use assistants, that assistants mention you more, or that one of them started tagging its links. Read it next to the other channels, not on its own.
Letting assistants find you
An assistant can only send visitors to pages it knows about, and the ones that search the web use crawlers of their own. OpenAI, for example, says its search crawler, OAI-SearchBot, must be allowed to read a site for that site to appear in ChatGPT's search answers (OpenAI: publishers and developers FAQ). Check that your robots.txt does not block the crawlers of the assistants you want to be found in.
Analytics cannot tell you whether a crawler read your page: a crawler that does not run your scripts sends no event, and one that does is dropped. Your server's own logs can, if you keep them.
Common questions
Can I see what the visitor asked the assistant?
No, and no analytics tool can. The referrer is a hostname, never the conversation, and the tagged link names the assistant, not the question.
Why is my assistant traffic smaller than I expected?
Because it is a floor. Visits that arrive with neither a referrer nor a tag count as Direct, and clicks from AI answers inside search results count as Organic Search.
Should I tag my own links in assistants?
You cannot: the assistant writes the link. You can tag links you publish elsewhere, which is the subject of the UTM campaign article.
How AnalyticsTrend does it
AnalyticsTrend has a channel of its own for assistants, AI Assistants, in the Sources report. A visit is counted there when its referrer is a known assistant, or its tagged link names one, such as utm_source=chatgpt.com. The assistants it recognises include ChatGPT, Claude, Perplexity, Gemini, Copilot, DeepSeek, Grok, Meta AI and Mistral, each as a source of its own. Traffic from crawlers and headless browsers is dropped before it is stored, so it never counts as a visitor.
The referrer is kept as a hostname only, and of the landing URL only the campaign parameters are read; see What it collects. Any goal can be chosen beside the channels to see each one's conversions and conversion rate, and every number that bounds the reports is in Capabilities and limits.
To start, see Install on a website.
Checked against the sources linked above on 28 October 2026. Assistants change how they link; check the linked pages for the current text.