How to Measure AI Referral Traffic
Visibility and citations tell you whether AI engines are recommending you. AI Referrals tells you whether that recommendation is actually turning into human visitors on your site. Here's how to set it up and read it.
Step 1: Connect Google Analytics 4
AI Referrals is powered by your connected Google Analytics 4 property. Once it's linked, CiteCue reads your existing analytics data and separates out the sessions that arrived from AI chat surfaces (visitors coming from ChatGPT, Perplexity, and other AI-driven referral sources) from your regular organic and paid traffic. These are real, measured sessions that your analytics attributes to AI referral sources, not a proxy or an estimate. What attribution can't tell you is which answer a visitor read before clicking, so read the numbers as arrivals from AI surfaces rather than proof that one specific mention or citation did the work.
Step 2: Read AI Referrals alongside your visibility score
The most useful way to look at AI Referrals is next to your Prompts Monitoring and Citations data, not in isolation. If you're frequently mentioned and cited on a topic, you'd expect referral traffic to build on the pages those citations point to. Treat that as a correlation worth checking, not a guarantee: mentions don't always come with links, and links don't always get clicked. If your visibility score is strong but AI Referrals stays flat, dig in. It can mean you're being mentioned by name without a link, or cited on a page that isn't compelling enough to click through from.
Step 3: Connect Google Search Console
Search Console connects for a related but distinct reason. It powers the index status checks inside AI Readiness, confirming which of your pages are actually indexed rather than just technically crawlable. It also lets you import your existing SEO keywords directly as prompt ideas in Prompts Monitoring, a fast way to build a prompt list from search terms you already know matter to your business. If you're building a prompt set from scratch instead, our guide to choosing prompts for AI visibility tracking covers how to do it well.
Step 4: Check AI Readiness for what might be blocking crawlers
Before AI Referrals traffic can show up at all, AI crawlers need to be able to read your site in the first place. AI Readiness runs technical checks (sitemap coverage, index status pulled from your connected Search Console) and turns any gap it finds into a concrete fix. It's included on every plan, including Free, because it's a prerequisite for everything downstream: a page an AI crawler can't read is a page that can't generate referral traffic, no matter how good the content on it is. For the underlying mechanics of robots rules, sitemaps, and indexing, see our crawler access guide.
Step 5: A note on AI crawler activity
AI Referrals measures human visitors. Separately, CiteCue also tracks AI agent traffic, meaning the automated crawlers and agents that fetch your pages directly. That's a distinct signal worth knowing about, but the focus of AI Referrals itself is the human side of the equation: real people, arriving after reading a real AI answer.
Step 6: Watch the pattern across scans
Because AI Referrals draws on your ongoing Google Analytics data, it naturally builds a picture over time rather than a single snapshot. Watch it alongside your scan cadence (manual on Free, daily on Pro and Agency) and look for the pattern that matters most: does referral traffic move in the same direction as your visibility and citation numbers? When it does, the mentions and citations you're tracking elsewhere in CiteCue are translating into people actually finding you through AI, not just visibility on paper.
If you haven't connected anything yet, the free AI visibility audit is a quick way to see where you stand before wiring up analytics.