06 · Bench
Free AI Traffic Checker
Find visits from ChatGPT, Perplexity, Claude and Gemini in your analytics export - and the landing pages where they run into nothing.
Analyze your analytics export
Your CSV is parsed in a browser worker. The file, its rows, traffic values and hashes never leave this device.
Drop your analytics export here
CSV only · UTF-8 · comma, semicolon or tab · up to 10 MiB and 100,000 rows
How the result is produced
The analyzer reads a supported CSV locally in the browser and groups rows with transparent source rules.
Start freeThe most valuable traffic in the report is the traffic the report does not name
A visit from an AI assistant comes about differently from a visit from Google Search. Someone asked a question, got an answer, and then chose to follow a named source. Those visits are rare, but the intent behind them is unusually concrete - and in standard reports they are invisible, because they disappear into the “Referral” bucket or into direct traffic.
The more expensive part of the problem lies elsewhere. AI assistants frequently cite from an older snapshot. A URL you moved a year ago keeps being named - Google followed the move long ago, the recommendation in the chat did not. If a redirect chain or a 404 is waiting there, you do not lose one visit but every visit from that recommendation, for as long as it circulates.
What you can do about it is unspectacular and effective: check the named destinations for status, collapse chains to a single hop, and point dead addresses at the nearest equivalent page rather than the homepage. The effort is small, and it applies retroactively to every recommendation already out there.
What AI Traffic Checker checks
Visits from AI assistants almost never appear as their own line in standard analytics reports. They land in the catch-all “Referral” channel among every other referring site or - when no referrer is transmitted - in direct traffic. Either way, a growing channel stays invisible in the reports.
The checker goes through your export for known AI referrers and their UTM sources and presents them as one group. The second and more important part is landing-page status: an AI assistant frequently names a URL it knows from an older snapshot. If that URL now runs through a redirect chain or into nothing, the visit is lost - and it is precisely the visit that arrived with high intent.
Deliberately without extrapolation: what is not in the export is not estimated. Part of AI traffic is fundamentally not attributable from referrer data, and an invented dark figure would make the numbers unusable.
The terms, briefly
- Referrer
- The page a visit came from. Browsers transmit it - app clients and some privacy settings do not, which is why a share of AI visits shows up as direct traffic.
- utm_source=chatgpt.com
- The parameter ChatGPT appends to outbound links. It is the most reliable marker for this channel because it survives even when the referrer is missing.
- Dark traffic
- Visits with no usable origin. Disproportionately common with AI assistants, because many arrive from native apps rather than a browser.
- Redirect chain
- Several consecutive redirects before the destination. Each hop costs time, and past a certain length clients give up - the visit ends before the page appears.
Reading the result
Landing page reachable
The linked URL answers directly with status 200. The visit arrives where it should.
Nothing.
Redirect chain found
The named URL reaches its destination through two or more hops. That costs load time and some clients abandon it entirely.
Collapse the chain to a single redirect, and link the destination directly wherever you control the source.
404 destination
The assistant names a URL that no longer exists - usually after a relaunch or a slug change. Every one of these visits is lost.
Redirect to the closest equivalent page, not blanket to the homepage.
No AI referrers in the export
Either this traffic does not exist yet, or the export lacks the referrer column or covers too short a window.
Re-export with source, landing page and at least 30 days.
Three mistakes we see constantly
Treating direct traffic as AI traffic
Missing origin is not evidence of AI. Bookmarks, email clients and QR codes land there too. Only the referrers and UTM sources you can actually identify are defensible - the rest stays unknown and should be labelled that way.
Redirecting to the homepage
An AI assistant names a URL because it expects specific content there. Sending every dead destination to the homepage converts a concrete intention into a bounce.
Judging the channel by sessions
AI referrals arrive in small numbers but with unusually high intent - the user asked for a recommendation and deliberately opened the link. Measuring the channel by sessions undervalues it.
Questions about AI Traffic Checker
Why doesn't GA4 show AI traffic as its own channel?
Because the default channel grouping does not know AI assistants. Their referrals fall into “Referral” or - without a referrer - into “Direct”. A custom channel group can retrofit this; this check works on the export regardless.
How much AI traffic am I not seeing?
That cannot be quantified honestly, and we deliberately do not estimate it. The mechanism is known: requests from native apps frequently transmit no referrer. Only what is actually in the export is defensible.
Which sources are recognised?
The known assistant domains - among them chatgpt.com, perplexity.ai, claude.ai and the Gemini surfaces - plus their UTM sources. The list grows, which is why it is shown in the result rather than hidden behind a single number.
Why do broken landing pages matter so much here?
Because AI assistants often cite from an older snapshot. A URL you moved a year ago keeps being named. Unlike Google, which follows the change, the old address stays in circulation - a 404 there costs you continuously.
Do I need an analytics account with you for this?
No. The check works on an export you already have. No script is embedded, no tracking is added, and no connection to your analytics account is established.
Primary sources
The claims on this page come from the providers' own documentation, not from secondhand summaries. Every source is linked so you can read what it actually says.
Continue with Contextter
An export is a snapshot
A one-off look shows what is broken today. It does not show what breaks next month when the next relaunch moves slugs around.
- Monitors landing pages continuously instead of checking one export at one point in time.
- Reports new 404 destinations and redirect chains before they cost visits.
- Connects AI referrals to the content that triggered them, so you know what is actually being cited.
No payment details required. The free check above stays usable without an account.
Related free tools
Where this continues in Contextter
Turn broken or high-value landing paths into URL-level opportunities and verification work.
Continue in ContextterReady when you are.
Start the check in the form above. Resource-intensive runs require a short browser verification and use strict limits.
Inputs are used only for the selected check. Browser-only tools never upload pasted text or files.
No payment details required. The free check above stays usable without an account.