DD DevDome Track. Protect. Grow.
Website Analytics

ChatGPT Referral Traffic: How to See It in Your Analytics and What It Is Worth

AI assistants now send readers, not just crawlers. The visits are small in number and unusually high in intent, and most analytics setups lump them in with direct.

On this page
  1. Two different things called AI traffic
  2. Finding the referrals
  3. Reading the channel
  4. What you can and cannot control
  5. Telling the crawlers apart from the readers in practice
  6. What the numbers typically look like
  7. Report it as a channel

ChatGPT referral traffic is a person clicking a link that an AI assistant cited in its answer. The visit arrives with the assistant’s domain as the referrer, chatgpt.com for ChatGPT, perplexity.ai for Perplexity, claude.ai for Claude, and it behaves like other referral traffic except in one way: the reader already got a summary and clicked through for more. That makes it small and valuable, and it makes the common mistake of mixing it with crawler hits expensive. Here is how to see it and how to read it.

Two different things called AI traffic

Crawlers. GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot and others fetch your pages automatically, to train models, to build a search index, or to answer a question in real time. No human is on your page when they do. These are bots. In honest analytics they sit in the bot report with their user agent and reason, not in the visitor count.

Referrals. A human asked the assistant something, the answer cited your page, the human clicked. That request comes from a normal browser with the assistant’s domain in the referrer. This is a visitor, and a motivated one.

Analytics that cannot tell these apart either inflate your visitors with crawler hits or hide the referrals in noise. DevDome Analytics classifies every hit across six signals and keeps bots out of the human counts, with a referrers report where the assistant domains appear as sources. We make it, so weigh that; whatever you use, confirm that crawler hits are not in your visitor number before you measure this channel.

Finding the referrals

Open the referrers report and look for the assistant domains. The common ones:

  • chatgpt.com and chat.openai.com
  • perplexity.ai
  • claude.ai
  • copilot.microsoft.com and bing.com when the Copilot answer links through Bing
  • gemini.google.com

Individually each is a handful of visits a week on a typical site. Group them into one AI referral source, either in your tool if it supports grouping or in the sheet you report from. The grouped line shows the trend; the individual lines do not.

Expect undercounting. Clicks from desktop apps and some in-app browsers strip the referrer and land in direct. The real number is somewhat higher than the referrer report shows.

Reading the channel

Volume is the wrong lens. Compare the AI referral group with your other referral sources on:

Pages per visit and dwell time. Readers who arrived from an answer tend to read the page they were sent to and often one more. If they bounce in seconds, the cited page did not deliver what the answer promised.

Outbound and affiliate clicks. On commercial content, this is the number. Server-side click capture matters here because these readers are disproportionately on desktop with blockers. DevDome records clicks through a server-side hop so a blocked script does not lose them.

Which pages get cited. The landing pages for AI referrals are the pages assistants find citable. They are usually the clear, factual, answer-first ones. That tells you what to write more of.

What you can and cannot control

You cannot buy a citation. You can make pages easier to cite:

  • Answer the question in the first paragraph, then explain.
  • State facts with sources, because assistants prefer pages they can verify.
  • Keep the page crawlable: no login walls, no interstitials, fast enough to fetch.
  • Decide which crawlers you allow. Blocking training crawlers while allowing the ones that fetch pages to answer questions is a reasonable middle path, and DevDome Bot Protection separates training, search and user-request controls so that choice is per type rather than all or nothing.

If you block every AI crawler, you will not appear in answers, and this referral channel will be zero. That is a legitimate choice; make it knowingly.

Telling the crawlers apart from the readers in practice

The distinction is easy to state and worth checking in your own data. Open the bot report and look for the AI user agents: GPTBot and OAI-SearchBot from OpenAI, ChatGPT-User for pages fetched during a live answer, ClaudeBot from Anthropic, PerplexityBot and others. Those rows are the fetches. Then open the referrers report and look for the assistant domains. Those rows are the readers. If the assistant domains appear in the bot report, or the crawler user agents appear as visitors, your analytics are mixing the two and the referral numbers cannot be trusted.

A second check is timing. Crawler fetches arrive at all hours in bursts, often many pages a minute. Referral clicks follow the pattern of your human traffic, with a daytime peak in the reader’s timezone and one or two pages per visit. If what you are calling AI referral traffic looks like the first pattern, it is crawlers.

What the numbers typically look like

For most content sites the AI referral group is a low single-digit share of visits and has been growing month on month. It is concentrated on a few pages, the clear factual ones, and it has engagement that compares well with search traffic and better than most social referrals. On commercial sites the click-through to affiliate links from these visits is often above the site average, because the reader arrived with a specific question already half answered. None of that makes it a replacement for search; it makes it a channel worth a line in the report and a reason to keep writing the kind of pages assistants can cite.

Report it as a channel

Add the AI referral group to your monthly report next to search, social and other referrals. Three columns: visits, pages per visit, clicks. Small numbers, but the trend over a year is the point, and the engagement column is usually the best on the page.

Related reading: Website Traffic by Country: How to See Where Your WordPress Readers Are.

Disclosure: DevDome publishes this blog and makes the products it mentions. We describe what they do rather than promise results.

Key takeaways

  • When a person clicks a link that ChatGPT, Perplexity or Claude cited, the visit carries a referrer from that assistant's domain. That is referral traffic, from a human.
  • AI crawlers fetching your pages to train or answer are bots and should be counted separately, not as visitors.
  • Group the assistant domains into one AI referral source so the trend is visible; individually they are tiny.
  • Judge the channel on engagement and clicks, not volume. Readers arriving from an answer already know what they want.
  • You cannot buy this traffic. You earn it by being the page an assistant can cite: clear answers, facts, and a crawlable site.

Sources

  1. OpenAI: overview of OpenAI crawlers : GPTBot, OAI-SearchBot and ChatGPT-User, and what each one does
  2. Anthropic: Does Anthropic crawl data from the web : ClaudeBot and how to control it
  3. MDN: Referer header : how referrers are set and when they are stripped

Links last checked October 17, 2026.

Frequently asked questions

Why does ChatGPT traffic show as direct in Google Analytics?

Some assistant clicks arrive without a referrer, for example from a desktop app or a link opened in a way that strips it, so they land in direct. Clicks from the web interface usually carry chatgpt.com as the referrer. Expect the true number to be a little higher than what the referrer shows.

Is traffic from AI crawlers the same thing?

No. GPTBot, ClaudeBot, PerplexityBot and similar fetch pages automatically; nobody is reading at that moment. They are bots and belong in the bot report. The referral traffic in this post is people who clicked a link in an answer.

Should I block AI crawlers to protect my content?

That is a choice with a trade-off. Blocking training crawlers may protect your content from being used to train models; blocking the crawlers that fetch pages to answer questions removes you from the answers, and with it the referral clicks. Tools that separate training, search and user-request crawlers let you choose per type.

How much traffic should I expect?

For most sites, a low single-digit percentage of visits, growing. The useful comparison is not volume against search but engagement against other referral sources, where AI referrals tend to rank well.

DevDome Team WordPress plugin builders

The DevDome team builds lightweight, performance-first WordPress plugins and free tools for site owners, founders and marketers. We write about the exact problems our plugins solve, in plain language for people who run real sites.