GA4 shows you exit rate. It does not tell you whether that exit was a success or a failure. That distinction matters more than the number itself.

An 85% exit rate on a page where users stay for three minutes means the page did exactly what it was supposed to do. Users arrived, found their answer, and left complete. An 85% exit rate with four seconds means the page failed immediately.

Satisfied Exits vs Abandoned Exits

A satisfied exit has a high exit rate and high engagement duration — 90 seconds or more. The user read, completed their task, and left. Adding more CTAs to reduce the exit rate would interrupt a successful journey and make the page perform worse.

An abandoned exit has a high exit rate and low engagement duration — under 30 seconds. The user arrived, found nothing useful, and left. This page needs attention: it is either attracting the wrong audience, delivering the wrong content, or failing to provide a next step.

The diagnostic question for every high-exit-rate page is not “how do I reduce this?” It is “was this exit satisfied or abandoned?”

The NYC Summer Internships Finding

In a live audit on a real content site, the NYC Summer Internships guide showed an 85% exit rate with 3 minutes 20 seconds average duration. The first instinct — reduce the exit rate — would have been wrong. Users were spending over three minutes reading a comprehensive guide and leaving with the information they needed. The exit rate was a function of the page succeeding, not failing.

Compare that to the same site’s homepage: 65% exit rate with 8-second duration. Lower exit rate, dramatically worse performance. The homepage was failing more users despite fewer exits.

Dead-End Pages

A third pattern exists beyond satisfied and abandoned: the dead end. Users arrive with genuine interest, engage enough to stay, but then have nowhere to go next. No internal links, no navigation to adjacent topics, no next step. The exit is not because the page failed — the site architecture failed.

Dead-end pages show moderate engagement duration and zero internal link click data. Adding one relevant internal link often produces measurable improvement in session depth without any content changes. It requires no developer, no design work, and no new content.

The Internal Link Opportunity Map

The most actionable output from an exit intelligence audit is a specific list of page pairings: which abandoned exit pages should link to which high-engagement destination pages. Google’s Analytics Advisor can generate these recommendations from your actual behavioral data — not guesswork about what users might want next.

This analysis runs in one session using Claude-in-Chrome alongside Analytics Advisor. The methodology is packaged as the Books for Bots: GA4 Exit Intelligence Kit.

Learn more about the GA4 Exit Intelligence Kit →

Open your GA4 referral traffic report and sort by sessions. The source at the top of the list is your most valuable referral partner, right?

Almost certainly not. The default GA4 referral view is sorted by volume. Volume is the wrong metric for understanding referral quality. And the gap between your highest-volume referral source and your highest-quality referral source is almost always larger than you expect.

The Quality Inversion

When you re-rank your referral sources by engagement rate instead of session count, the leaderboard flips completely. The source you have been grateful for because it sends 300 sessions a month is often delivering 6-8% engagement — users who arrive, glance at the page, and leave in under 10 seconds. The source sending 8 sessions a month may be delivering 70%+ engagement — users who read deeply, navigate to related pages, and return weeks later.

From a content investment perspective, those 8 sessions from the high-quality source are worth more than the 300 from the volume source. They represent real readers who found genuine value. The volume source is sending noise.

What Drives the Gap

The gap between volume and quality in referral traffic usually comes down to three things.

Intent alignment. A high-volume referral source often sends users whose intent does not match your content. A directory site might link to you as a resource while its users are looking for a service provider. They arrive, realize you are informational content, and leave. A niche newsletter that links to you as recommended reading sends users who explicitly opted in to this exact type of content. Every session is pre-qualified.

Audience specificity. The broader the audience of the referring site, the lower the average quality of the traffic it sends you. A general-interest news aggregator sends everyone. A specialized community sends people who care about your topic.

Editorial context. When a referring site links to you in the body of a relevant article with a reason to click, the user arrives with context and intent. When your URL appears in a list of 50 links on a resource page, the user arriving has no specific reason to engage with your content over anyone else on the list.

How to Find Your Hidden Gem Referrers

The query you are looking for in GA4 is not “which referral source sends the most sessions.” It is “which referral sources have fewer than 20 sessions but an engagement rate above 50%.”

That filter surfaces your hidden gems — the small sources that nobody is monitoring because they do not show up at the top of the volume-sorted list. These are the sites whose audiences are most aligned with your content, the writers and communities who are genuinely recommending you rather than listing you.

Once you have the list, the outreach writes itself. A referral partner whose audience stays on your site for 4 minutes and returns regularly is a relationship worth formalizing. A content exchange, a guest post, a link placement in their next relevant piece — any of these turns an organic quality referrer into a deliberate partnership.

What Your Bad Traffic Sources Are Costing You

Beyond missing the hidden gems, there is a cost to the volume sources you are currently treating as successes. If a referral source is sending 300 sessions at 6% engagement and you are investing link-building effort to maintain or grow that relationship, you are optimizing for a metric that does not correspond to business value.

The reallocation question is simple: what would happen if you redirected that same effort toward the sites whose audiences actually engage with your content?

Running the Audit

This analysis runs in a single session using Claude-in-Chrome alongside Google’s Analytics Advisor in GA4. The query sequence inverts the default referral view, surfaces your hidden quality sources, identifies your bad traffic sources with specific domain-level data, and produces a partnership opportunity list for outreach.

No SQL. No BigQuery. No data analyst. The methodology is packaged as the Books for Bots: GA4 Referral Quality Audit.

Learn more about the GA4 Referral Quality Audit →

Your GA4 engagement rate is one number. But it is not one audience. It is three audiences — and they behave so differently from each other that the aggregate number actively misleads you about how your content is performing.

Here is what most GA4 users see: a site-wide engagement rate of 35%, an average session duration of 90 seconds, and a top channel list led by Organic Search. What most GA4 users miss: within that same 35% number, three AI platforms are sending traffic with engagement rates of 21%, 46%, and 64% respectively — from the exact same pages, to users with completely different intent profiles.

The AI Referral Split Nobody Is Looking At

ChatGPT, Claude, and Copilot all send referral traffic to content sites. But they do not send the same user. ChatGPT users arrive, scan for a quick answer, and leave in under 30 seconds — engagement rate around 21%, well below the organic search average. Claude users arrive with research intent, read deeply, and stay for 3-4 minutes — engagement rate above 64%. Copilot users are somewhere between, arriving in planning mode, spending 1-2 minutes on civic and services content.

If you blend these three into your site-wide engagement rate, you get a number that does not represent any of your actual users. You get a mathematical average of behaviors that have nothing in common.

Why Your Engagement Rate Lies

The problem is not your content. The problem is that engagement rate without source segmentation is noise. A 35% site-wide engagement rate could mean you have excellent content reaching the wrong distribution channels. It could mean you have mediocre content propped up by one high-engagement source. It could mean your AI referral traffic is dramatically outperforming your social traffic and you have no idea.

The only way to know which is true is to break the number open by source and look at what each channel is actually delivering in terms of engaged session quality — not just volume.

The Four-Question Audit

Before you make any content or distribution decisions based on your GA4 engagement rate, ask these four questions.

Which channel sends the most engaged users — not the most users? The answer is almost never the channel driving the highest session count. In most content sites we have audited, the highest-engagement channel is sending between 8 and 40 sessions per month, not 400.

What is the engagement rate for each AI referral source individually? Blending ChatGPT and Claude traffic treats them as equivalent. They are not. One is a fact-checking audience. The other is a research audience. The content structure that serves one actively fails the other.

Which pages produce satisfied exits versus abandoned exits? A 90% exit rate with a 3-minute duration is a success. A 90% exit rate with a 4-second duration is a dead end. Engagement rate alone does not tell you which you have.

Is your engagement rate rising or falling week-over-week from AI sources? AI referral traffic is growing on most content sites in 2026. If yours is flat or declining, you are losing ground in a channel that is becoming structurally important.

What This Reveals About Your Real Audience

When you segment your GA4 engagement rate by source and run the AI referral breakdown specifically, a picture emerges that the aggregate number completely hides. Your real audience — the people actually reading and acting on your content — is smaller and more specific than your total traffic suggests. It is concentrated in a few sources, a few content types, and in the case of Claude traffic specifically, a few geographic clusters that reflect the academic and professional demographics of that user base.

This is not a problem. It is a targeting signal. It tells you where to invest content development effort and which audience to write for on every new piece.

The Methodology Behind This Analysis

The behavioral profiles in this article come from five live sessions using Claude-in-Chrome to interrogate Google’s Analytics Advisor inside GA4 on a real property. The query architecture — the specific sequence of questions and the capture protocol — is packaged as the Books for Bots: GA4 AI Referral Audit Kit.

It runs in four sessions, requires no SQL, no BigQuery access, and no data analyst. You need Claude-in-Chrome, Editor access to a GA4 property with Analytics Advisor enabled, and approximately 90 minutes. The output is a complete per-AI behavioral profile of your traffic and a content variant framework for acting on it.

Learn more about the GA4 AI Referral Audit Kit →

For the past several weeks I have been running a live experiment on helpnewyork.com: using Claude-in-Chrome to interrogate Google’s Analytics Advisor inside GA4, session by session, until I had a complete behavioral profile of every AI platform sending traffic to the site.

What came out of it is not what I expected. I expected traffic data. I got a content strategy.

The Setup

Claude-in-Chrome is Anthropic’s browser extension that lets Claude operate directly inside your browser — reading pages, clicking elements, filling inputs, capturing output. Analytics Advisor is Google’s Gemini-powered chat interface built into GA4, available to English-language accounts since December 2025. It answers natural language questions about your property data with charts, tables, and narrative interpretation.

The combination is unusual. You are using one AI (Claude) to systematically interrogate another AI (Gemini) about your site’s data, then synthesizing what comes back into strategy. The token budget for the heavy data reasoning stays inside Google’s infrastructure. Claude handles the query architecture, the capture protocol, and the synthesis.

I ran four structured sessions across two sittings, using a specific sequence of queries built to extract progressively deeper signal. Session 1 established baseline traffic. Session 2 closed gaps and confirmed AI referral data existed. Session 3 was the AI deep dive. Session 4 was velocity and geography.

What the Data Showed

Three AI platforms were sending meaningful traffic to helpnewyork.com during the 28-day window: ChatGPT, Claude, and Copilot. The behavioral profiles were so different from each other that treating them as a single “AI traffic” segment would have produced wrong conclusions.

Claude.ai traffic showed a 64% engagement rate and an average session duration of over 3 minutes. The dominant landing page was an NYC Summer Internships guide, accounting for over 60% of all Claude sessions. Geographic concentration was academic: Ithaca (Cornell), State College (Penn State), Washington DC. The users arriving from Claude were reading to act — they needed specific information, they found it, they stayed.

ChatGPT traffic showed a 21% engagement rate and an average session of 24 seconds. The top landing page was a cherry blossom guide. The users were fact-grabbing: they asked ChatGPT where to see cherry blossoms in New York, got a citation, clicked through, confirmed the location, and left. The content served its purpose in under half a minute.

Copilot traffic was between the two: 46% engagement, roughly 2-minute sessions, desktop-heavy, concentrated in New York’s suburbs. The top pages were civic services — SNAP benefits, tenant rights, transit discounts. These users were in planning mode, researching before they decided or applied.

The Finding That Reframes GEO

The cross-AI page overlap query was the most important one in the entire four-session arc. I asked Analytics Advisor which pages appeared in the top landing pages for more than one AI source. Only one real content page appeared in all three: the cherry blossom guide.

The obvious interpretation is that the cherry blossom guide was “AI-optimized.” The actual interpretation, once you look at the full traffic breakdown, is the opposite. Bing drove 59 sessions to that page. Yahoo drove 16 at 75% engagement and a 3-minute 46-second average session. DuckDuckGo drove 35. The combined AI traffic to that page was 32 sessions — 17% of total. The AI platforms were citing it because traditional search engines had already validated it as the highest-quality answer in the index.

AI citations are downstream of search quality, not upstream. The path to getting cited by ChatGPT, Claude, and Copilot is not to optimize for AI retrieval patterns. It is to build pages that win on Bing and Yahoo with enough depth that AI models treat them as authoritative sources. The GEO play is a traditional SEO play with better content.

The Content Strategy That Follows

Once you have the per-AI behavioral profiles, you have a content variant framework. The same article can be written in three structural architectures, each tuned to how one AI model retrieves and presents information.

The Claude variant is dense and process-oriented. Headers, eligibility criteria, numbered steps, official program names. Built for the student or researcher who arrived with a specific question and needs a complete answer they can act on.

The ChatGPT variant is a scannable list. Named items, one specific detail per item, direct answer in the first two sentences. Built for the user who will spend 24 seconds on the page and needs the answer immediately or they’re gone.

The Copilot variant is comparison and planning framing. What to know before you go, Option A versus Option B, cost context, logistics. Built for the desktop user doing research before they make a decision.

The core article is the same. The architecture is different. The AI that cites you depends on which structure you used.

The Methodology Is the Product

The query sequence I developed across these four sessions is a repeatable extraction methodology. It works on any GA4 property with Analytics Advisor enabled. The intelligence it produces — per-AI audience profiles, geographic signals, velocity trends, cross-AI content overlap — is not available through DataForSEO, SpyFu, or GSC. It requires Gemini’s reasoning layer operating on top of your property data, orchestrated by a structured query architecture.

I have packaged the complete methodology as a downloadable kit: the full query architecture across all four sessions, the capture protocol, the content variant framework, and the flags to escalate before your next content sprint. It is called Books for Bots: GA4 AI Referral Audit Kit.

The free version covers Session 3 alone — the AI deep dive queries that surface your ChatGPT, Claude, and Copilot traffic split. That alone will show you something most site owners have never seen: which AI is sending them traffic, to which pages, and how engaged those users actually are.

The full kit covers all four sessions and includes the content variant framework that translates the behavioral data into a writing system.

Both are available at tygartmedia.com. What you do with the data after that is yours.

Short version: In the last 29 days, Claude, ChatGPT, Perplexity, Microsoft Copilot, Gemini, NotebookLM, and Kagi collectively sent at least 94 new readers to tygartmedia.com — a site whose #1 content vertical is explaining Claude. AI assistants are now our #4 traffic source, ahead of Facebook, ahead of LinkedIn, ahead of every search engine except Google and Bing. The product is citing the publication that covers the product. That’s the loop. Here is what it looks like when you can actually measure it.

The finding that made me stop scrolling

I built a Claude-powered browser agent to poke around our GA4 account and surface “interesting stuff” a human analyst would miss. One of the first things it flagged was our Source/Medium report. Here is the top of the list, unedited:

Rank	Source / Medium	New Users (29 days)	Notes
1	(direct) / (none)	738	Mystery bucket
2	google / organic	289	Standard Google SEO
3	bing / organic	70	1m 20s average session — high intent
4	claude.ai / referral	63	Claude itself
5	m.facebook.com	43	Mostly 4-second bounces
6	duckduckgo / organic	41	1m 02s average
13	chatgpt.com / referral	9	ChatGPT
15	perplexity.ai / referral	5	Perplexity
21	copilot.com	3	Microsoft Copilot
24	gemini.google.com	2	Google Gemini
28	notebooklm.google.com	1	Google NotebookLM
35	kagi.com	1	Kagi AI results

Add up everything with an AI-assistant referrer and the combined count is at least 94 new users in 29 days — roughly 6.7% of all new users on the site. Claude alone, at 63 referred users, is our #4 traffic source. It is ahead of Facebook. It is ahead of LinkedIn. It is ahead of every search engine except Google and Bing. And we have been cited, at least once, by every major AI surface in the English-speaking internet: Claude, ChatGPT, Perplexity, Microsoft Copilot, Gemini, NotebookLM, and Kagi.

Why this is different from “we show up in Google”

Generative Engine Optimization (GEO) is the practice of structuring content so that large language models cite it as a source inside their answers. It is the younger, messier cousin of SEO. Most publishers cannot yet prove it is working. The feedback loop is long, the data is hidden inside a chat window, and the traffic that does leak through often lands in a “(direct)” bucket with no attribution at all.

We can see ours. GA4, for reasons that are probably accidental, already records claude.ai, chatgpt.com, perplexity.ai, copilot.com, gemini.google.com, notebooklm.google.com, and kagi.com as discrete referral sources when a user clicks a citation link. That means AI-assistant traffic is measurable as a first-class channel right now, today, with the free version of Google Analytics, on any site that happens to get cited.

The poetic layer of what we are looking at: Claude is the top AI referrer to a website whose #1 content vertical is explaining Claude. The product is sending readers to the publication that covers the product. If that is not a GEO moat, I do not know what one looks like.

These are not bounced visitors. They are readers.

The single biggest worry with any new traffic source is that it might be garbage — bots, previews, accidental clicks. The engagement data says the opposite. Users arriving from claude.ai spend 23 seconds on average and produce 0.56 engaged sessions per user. ChatGPT referrals average 21 seconds and 0.44 engaged sessions per user. For context, the site-wide average engagement time is dragged down hard by in-app social browsers; the Facebook mobile webview, for example, sits at about 14 seconds with 4-second bounces.

People arriving from an AI assistant are not scrolling past. They clicked the citation because the AI told them this was the primary source, and when they got here they read. That is a qualitatively different kind of traffic than Facebook or a random Google search. These are the highest-intent non-search users we have.

The secondary finding: Seattle is reading for three minutes

The same GA4 pass surfaced a city-level pattern we were not expecting. Seattle readers — 61 of them in 29 days — spent an average of 3 minutes and 6 seconds on site at a 61.3% engagement rate. The site-wide average session is roughly 40 seconds. Seattle readers are spending about 4–5x longer on the page than the typical visitor, at nearly twice the engagement rate.

City	Active Users	Engagement Rate	Average Time
Seattle	61	61.3%	3m 06s
The Dalles, OR	31	0%	1s
Shelton, WA	26	27.6%	15s
Des Moines	24	37.5%	10s
Beijing	31	6.5%	0s
Singapore	28	21.4%	5s

A few things jump out. The Dalles, Oregon at 31 users / 0% engagement / 1 second is almost certainly Google’s data center there returning preview requests — ignore it. Shelton, Washington is a real Mason County hyperlocal beachhead; 26 actual humans in our home county in 29 days is a legitimate foothold for the local desk. Beijing at 31 users / 0 seconds has the classic signature of cloud-hosted scrapers. And Seattle at 3 minutes is the single most valuable city in our data and it is not close.

The browser split confirms an unusually technical audience

Browser	Users	Engagement Rate
Chrome	850 (60%)	31.3%
Safari	232 (16%)	32.7%
Edge	99 (7%)	62.3%
Firefox	33 (2.3%)	60.5%

Edge at 62.3% engagement and Firefox at 60.5% engagement are not normal consumer numbers. A typical general-interest site sees those two browsers hovering in the 5–15% range. Microsoft Edge is the default on corporate-managed Windows machines. Firefox is the dev-preferred privacy browser. The combination of high Edge engagement, high Firefox engagement, and a Claude-heavy referral list all point at the same audience: developers and technical professionals at real companies, reading on managed workstations.

How to measure AI-assistant referrals in your own GA4

If you publish anything technical and want to see your own version of this number, the fastest path is a custom GA4 exploration with one segment. Open GA4 → Explore → Free Form. Add a segment with this condition:

Session source contains one of:
  claude.ai
  chatgpt.com
  perplexity.ai
  perplexity
  copilot.com
  gemini.google.com
  notebooklm.google.com
  kagi.com
  you.com
  phind.com

Break it down by landing page, engagement rate, and average engagement time. That is your AI-Referral dashboard. Watch it weekly. A non-trivial number of sites will discover they already have measurable AI traffic and never bothered to look.

Frequently asked questions

What is a GEO referral?

A GEO referral, or AI-assistant referral, is a visit to your site from a user who clicked a citation link inside an answer generated by a large language model such as Claude, ChatGPT, Perplexity, Microsoft Copilot, Gemini, NotebookLM, or Kagi. In Google Analytics 4 these visits appear as referral traffic from the assistant’s domain — for example claude.ai / referral or chatgpt.com / referral.

How many AI-referred users did tygartmedia.com receive in 29 days?

At least 94 new users across seven distinct AI assistants: 63 from Claude, 14 from ChatGPT (9 attributed + 5 unassigned), 10 from Perplexity (5 attributed + 5 unassigned), 3 from Microsoft Copilot, 2 from Gemini, 1 from NotebookLM, and 1 from Kagi. That is roughly 6.7% of all new users on the site for the period.

Are AI-assistant referrals real readers or bots?

Real readers. Average engagement time from claude.ai is 23 seconds and from chatgpt.com is 21 seconds, with engagement rates of 0.56 and 0.44 engaged sessions per user respectively. Those numbers are qualitatively higher than in-app social browser traffic (Facebook mobile webview averages about 14 seconds) and indicate a deliberate click-through from an AI citation, not a scraper.

Can any publisher measure AI-assistant referrals in GA4?

Yes. GA4 records visits from claude.ai, chatgpt.com, perplexity.ai, copilot.com, gemini.google.com, notebooklm.google.com, and kagi.com as discrete referral sources by default. Build a Free Form exploration with a segment that filters Session source on those domains and you will see the channel immediately if it exists for your site.

What is GEO in marketing?

GEO stands for Generative Engine Optimization. It is the practice of structuring web content, schema markup, and publishing signals so that large language models cite the content as a source inside AI-generated answers. GEO is to AI assistants what SEO is to search engines — the discipline of being the answer the machine hands to the reader.

The loop, and why it matters

The most interesting thing about this data is not the traffic. It is the feedback structure. Tygart Media publishes explainers about Claude. Claude crawls and cites those explainers. Readers click through from Claude’s answer back to tygartmedia.com. We publish more. Claude cites more. The site becomes, in effect, training data and a recommended source for the next iteration of the product it covers. That is the recursive loop that makes AI-native publishing a different business than search-era publishing.

I do not think every site can build this loop. It requires a narrow, technically-defensible topic — something an AI assistant would rather cite than paraphrase — and the patience to publish at a cadence LLMs reward. What I do think is that any publisher can check, today, whether the loop has quietly started forming underneath them. Most have not bothered. This post is partly a flex and partly an invitation: go look.

What happens next at Tygart Media

Three things. We are standing up a permanent AI-Referral channel in our GA4 so the number can be watched weekly instead of rediscovered quarterly. We are writing the playbook — the one this post hints at — for publishers who want to do the same. And we are building the browser agent that found this in the first place into a repeatable audit any publisher can run against their own GA4 in an afternoon. If that last one sounds useful, the newsletter is the place to follow along.

Claude sent us 63 readers last month. It will send more next month. We will be counting.