Someone asks ChatGPT which WordPress plugin handles redirects best. The answer cites your comparison post, they click, and they land on your site. In your analytics that visit might show up as "chatgpt.com / referral", as an "AI Assistant" session, or as "(direct) / (none)" — depending on the app they used, how your GA4 property is set up and whether a referrer survived the trip.
AI assistants are still a small traffic source, but a fast-growing and unusually valuable one. This guide shows how AI visits reach a WordPress site, how to separate them in Google Analytics 4 in about ten minutes, how to track them inside WordPress without GA4, and which numbers are worth watching.
Why Track AI Search Traffic in 2026
The share is small, and it is growing fast:
- In SE Ranking's 2026 study of 101,574 websites, AI platforms sent 0.32% of all website traffic, up from 0.02% in 2024 — a sixteenfold increase in two years.
- Previsible counted 527% more AI-referred sessions in January–May 2025 than in the same months of 2024 across the sites it tracked.
- OpenAI reported 900 million weekly ChatGPT users in February 2026.
The same SE Ranking study shows where that traffic comes from:
| AI platform | Share of AI referral traffic (2026) |
|---|---|
| ChatGPT | 74.78% |
| Google Gemini | 11.56% |
| Perplexity | 7.23% |
| Microsoft Copilot | 3.51% |
| Claude | 2.62% |
Volume isn't the main reason to track it, though. Visitors from AI answers arrive after the assistant has already explained the topic, so they tend to be further along. Ahrefs found that AI visitors were 0.5% of its traffic but produced 12.1% of sign-ups over 30 days, and Semrush estimated that an average AI search visitor is worth 4.4 times an organic one. These are single-company figures, and there is no reliable cross-industry conversion benchmark yet — which is exactly why you want your own numbers.
How AI Visits Reach Your Site (and Why Some Look "Direct")
An AI referral is a human click on a link inside an AI answer. How it is recorded depends on what the browser passes along:
- A referrer. When the click happens in a web browser, the visit usually carries a referrer such as
chatgpt.com,perplexity.ai,claude.ai,gemini.google.comorcopilot.microsoft.com. Analytics tools read it and attribute the session. - A UTM tag. ChatGPT adds
utm_source=chatgpt.comto many of the links it cites, so the source survives even without a referrer. In practice it appears mostly on citation links, not on every link. - Nothing. Desktop and mobile apps often open links without a referrer. Those visits land in "(direct) / (none)", and no analytics tool can attribute them reliably.
Two things are easy to confuse here. First, bots are not visitors. When ChatGPT-User or Perplexity-User fetches your page to read it for someone, that's a server request without JavaScript — GA4 never sees it. Those fetches show up only in server logs or a crawler monitor (see our AI crawler guide). Second, Google's AI features are not separable. Clicks from AI Overviews and AI Mode arrive as ordinary google / organic, and Google says that sites appearing in its AI features are included in the overall search traffic in Search Console.
Method 1: Google Analytics 4
Check the built-in "AI Assistant" channel first
GA4's default channel group now includes an AI Assistant channel for traffic from recognized AI assistants — Google's examples include ChatGPT, Gemini, DeepSeek, Copilot and Grok. Open Reports → Acquisition → Traffic acquisition and look for it in the "Session default channel group" column. It does not cover AI Overviews or AI Mode, which stay in Organic Search.
The built-in channel lumps every assistant together. If you want each platform on its own row — or if you need visits from tools Google doesn't recognize — add a custom channel group.
Create a custom channel group (10 minutes)
- Go to Admin → Data display → Channel groups and click Create new channel group (you need the Editor role). Standard properties allow two custom groups.
- Name it "Channels with AI".
- Add a channel called AI Assistants with the condition Session source → matches regex:
.*(chatgpt\.com|chat\.openai\.com|perplexity\.ai|claude\.ai|gemini\.google\.com|copilot\.microsoft\.com|edgeservices\.bing\.com|deepseek\.com|grok\.com|meta\.ai|you\.com|phind\.com).* - Optionally add one channel per platform instead (for example "ChatGPT" for
chatgpt\.com|chat\.openai\.com, "Perplexity" forperplexity, "Claude" forclaude\.ai). - Drag the AI channels above Referral in the list. GA4 assigns each session to the first channel whose rules match, so if Referral comes first it swallows AI visits.
- Save, then pick the new group in the Traffic acquisition report's channel dropdown.
Custom channel groups apply to your reports retroactively, so you see historical AI traffic right away — no need to wait for new data.
Find which pages AI assistants send people to
For page-level detail, create a Free form exploration:
- Rows: Session source, then Landing page + query string
- Values: Sessions, Engaged sessions, Average engagement time, Key events
- Filter: Session source matches the regex above
The result is your list of AI-cited pages, ranked by how many people they bring and what those people do next.
Method 2: Track AI Visits Inside WordPress
GA4 isn't on every site — consent rules, ad blockers or simple preference keep many WordPress owners away from it. You can track AI referrals from WordPress itself instead.
SEO Fury PRO's AI Search Traffic module detects visits by their referrer — ChatGPT, Perplexity, Gemini, Copilot, Claude, You.com, Phind and Kagi — and stores them in your own WordPress database, with no GA4 property and no cookies. Once you switch it on, the report shows totals per platform, a daily chart, and the top landing pages for AI visitors.
Because it runs alongside the AI Crawler Monitor, the report also puts two numbers next to each page: how many times AI assistants fetched it on a user's behalf (ChatGPT-User, Perplexity-User, Claude-User) and how many visitors then clicked through. That pairing is something analytics alone can't show. A page that assistants read often but that gets few clicks is being answered in the chat window — a cue to add something worth the visit, such as a calculator, a template or original data.
Like any referrer-based method, it can't attribute app visits that arrive without a referrer, so compare its totals with GA4's rather than expecting them to match exactly.
Method 3: Other Options
- Server logs record every AI fetch and every human visit, including those that block JavaScript. They are the most complete source, but turning them into reports takes work.
- Cloudflare users can see AI crawler activity in Cloudflare's AI crawler dashboard — useful for the bot side, not for human referrals.
- Dedicated AI-traffic tools are appearing. One example is Loamly, an open-source detector that tries to classify AI-driven visits even when the referrer is missing. These tools are new; check what each one actually verifies before relying on its numbers.
| Method | Best for | Setup | Cost |
|---|---|---|---|
| GA4 AI Assistant channel | A quick total | None | Free |
| GA4 custom channel group | Per-platform split and page-level analysis | About 10 minutes | Free |
| SEO Fury PRO AI Search Traffic | Sites without GA4; fetches vs clicks per page | One switch | Included in PRO |
| Server logs | Complete record, including bots | Technical | Free with hosting |
The Metrics That Matter
Once AI visits are separated, watch a short list:
- AI sessions by platform, month over month — is the channel growing, and on which assistant?
- Top landing pages — the content AI answers cite and people click. Update these first.
- Engagement rate and engagement time compared with organic search on the same pages
- Key events and conversions — sign-ups, leads, purchases — per AI session versus organic
- Fetches vs clicks per page — how often assistants read a page compared with how often readers follow the citation
- Unexplained growth in direct traffic to deep content pages, which often hides app-based AI visits
Don't judge the channel on sessions alone. At well under 1% of traffic on most sites, a handful of high-intent visits can matter more than the totals suggest — which is why conversions per session are the number to bring to a budget meeting.
Turning Tracking Into More AI Traffic
The data tells you which pages AI assistants already trust. Use it:
- Refresh the winners. Keep facts, prices and screenshots on top AI landing pages current, and update the modified date honestly.
- Copy the pattern. Look at what cited pages share — answer-first sections, tables, sourced numbers, a clear FAQ — and apply it to similar pages. Our guide on writing FAQ content that AI cites covers the format.
- Make sure the bots get in. A page can't be cited if OAI-SearchBot or PerplexityBot gets a 403 — check crawler access before rewriting anything.
- Give a reason to click. On pages with many AI fetches and few clicks, add something an answer can't contain: a tool, a downloadable template, original data.
30-Minute Setup Checklist
- Open GA4 Traffic acquisition and check the AI Assistant channel.
- Create the "Channels with AI" custom group with the regex above, AI channels placed above Referral.
- Build the Free form exploration of AI landing pages and save it.
- If you don't use GA4 — or want fetches and clicks side by side — enable AI Search Traffic in SEO Fury PRO.
- Confirm that AI search crawlers can reach your key pages.
- Put a monthly review on the calendar: platforms, landing pages, conversions.
For the full picture of how AI search chooses what to cite, see our GEO for WordPress guide.
Try SEO Fury Free
50+ SEO features, unlimited sites, no credit card. Install it and score your first post in under five minutes.
Get SEO Fury Free