Skip to main content
All free tools

06 · Bench

Check AI traffic in your analytics export

Analyze your analytics CSV locally: AI referrers, ChatGPT visits and available conversions. Free, without an account. Optional landing-page status checks.

BenchFree tool

Analyze your analytics export

Your CSV and traffic values are processed locally in the browser. A separate, optional status check sends only the selected public URLs after you review the list.

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 CSV analysis runs locally in your browser. An optional status check sends only the selected public landing-page URLs for a separate check; the file and traffic values stay local.

Start free

Measure the AI visits your export can identify

Begin with an export that includes the source and landing page. Add sessions, conversions or revenue if you want to compare those measures. Review the suggested column mapping before starting the analysis.

Compare the data by source and landing page. A source with more sessions does not automatically have a higher conversion rate or business value. Missing conversion data stays missing; the checker does not invent it.

If a landing page needs investigation, use the optional URL status check and review its evidence. For a wider technical investigation, continue with Site Audit.

If a landing page receives AI referrals but fails visitors, check its access with the AI Crawler Checker. Investigate broken paths across the domain with Site Audit.

What AI Traffic Checker checks

Use your own analytics export to identify known AI referrers and UTM sources. The result groups those rows by assistant and landing page. Sessions, conversions and revenue appear only when the export contains usable columns.

This is a report on identifiable referrals, not an estimate of all AI visits or a traffic estimate for other websites. Visits without usable source information remain unknown.

After the local analysis, you can choose a separate status check for public landing-page URLs. Review the URL list before sending it. The CSV and its traffic values stay in the browser.

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
A source parameter that can identify a ChatGPT referral when it is included in the export. Treat it as one recognizable marker, not proof that every AI visit is recorded.
Dark traffic
Visits without usable source information. They cannot be assigned to an AI assistant from missing referrer data alone.
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.

  • Assuming AI visits convert better

    Compare the sessions and conversions available in your own export. The source name alone does not establish intent, lead quality or a better conversion rate.

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.

Can I check another website’s estimated traffic?

This tool analyzes an analytics CSV you provide. It does not estimate another domain’s visitors. You need your own source and landing-page data for the local analysis.

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 Crawl Foundry

Investigate the landing pages behind the report

The export describes the selected period. Use its landing-page list to decide which URLs to check next.

  • Inspect the selected public URLs with the optional status check.
  • Use Site Audit to investigate technical findings on the website.
  • Compare later exports using the same source rules and measurement window.

No payment details required. The free check above stays usable without an account.

Related free tools

Where this continues in Crawl Foundry

Use the source and landing-page report to choose which URLs need further investigation.

Continue in Crawl Foundry

Ready 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.