The AI Visibility tab
The AI Visibility tab shows you how AI assistants and AI agents interact with your site. You will find it in the left sidebar, under your site, labelled AI Visibility.
It answers two separate questions, and it is split into two sections to match:
- AI agents — software (crawlers and agents) accessing your site.
- Visitors from AI — real people who arrived from an AI assistant like ChatGPT or Perplexity.
These two things are easy to mix up. They are not the same. If the difference is not clear, read Understanding AI agents vs visitors from AI first.
[Screenshot: The AI Visibility tab with both sections]
Reading the period and privacy mode
At the top of the tab you will see a privacy-mode badge (for example Mode A) and a one-line description: How AI assistants and agents interact with your-domain.com.
Like the rest of the dashboard, this tab follows the period selector at the top of your dashboard. On Mode A sites, every count here is at pageview grain — Mode A has no visitor or session IDs, so we count page views, not unique people. See Privacy modes explained for why.
Section 1 — AI agents
This section is always shown, even if you have turned on the Humans only filter elsewhere in the dashboard. That is the whole point of the tab — to show you the agent traffic the rest of the dashboard can hide.
Subheading: Crawlers and agents accessing this site.
The stat cards
- Agent pageviews — the total page views from AI agents in the selected period.
- Share of traffic — those agent pageviews as a percentage of all page views on the site for the period (the total here counts everything, so the share is not understated).
- Top operator — the operator (the company or product behind the agent) with the most agent pageviews.
The AI bot activity table
Below the stats is a table titled AI bot activity, subtitled By operator. Each row is one operator:
| Column | What it means |
|---|---|
| operator | The named operator behind the agent (for example, an AI assistant’s crawler). |
| pageviews | How many page views that operator generated in the period. |
| share | That operator’s share of agent pageviews. |
| observed user-agent | The user-agent string we saw, shown in monospace. A dash (—) means none was recorded. |
Important: search crawlers are not here
This section shows AI agents only. Classic search-engine crawlers like Googlebot and Bingbot are classified as search crawlers, not AI agents, so they are not shown here. This is deliberate, so the view matches what the rest of Voris means by “AI”. If you are looking for Googlebot, you will not find it on this tab, and that is expected.
The agent-trust filter
In the top-right of the AI agents section there is a small filter with three buttons:
- All agents (the default)
- Verified
- Unverified
This filters the operator table by how the agent was identified:
- Verified means the agent was cryptographically verified (via the Web Bot Auth standard), or it is a known operator that publishes signing keys and we treat as verified.
- Unverified means we recognised an agent identity but could not verify it cryptographically.
The filter describes the software, never the person behind a visit. Switching it re-scopes only this table; the rest of the dashboard is unaffected.
Section 2 — Visitors from AI
Subheading: Real people arriving from AI assistants.
This section counts humans who clicked through to your site from an AI assistant. These are people, not agents — so unlike the AI agents section, they are counted the way other human traffic is.
The stat cards
- AI-referred pageviews — page views from people who arrived from a tracked AI assistant.
- AI sources — how many distinct AI assistants sent you traffic in the period.
The AI referrals table
Titled AI referrals, subtitled By source. One row per AI assistant (ChatGPT, Perplexity, Gemini, Copilot, Claude, Grok, You):
| Column | What it means |
|---|---|
| source | The AI assistant the visitor came from. |
| pageviews | Page views from people referred by that source. |
| conversion | The conversion rate for that source (see the caveat below). A dash (—) means there is no goal data to compute it. |
| revenue | AI-attributed revenue for that source, where a goal tracks revenue or a purchase carries a value. |
About the revenue column: it shows a dash (—) when there is no goal-matched revenue. It will not show $0.00. A dash means “no revenue data to attribute here”, not “zero sales”.
About the conversion rate (please read): under the table you will see this caveat:
Conversion is measured at humans-filtered pageview grain, not unique sessions — directional until session de-duplication (Privacy Mode B).
AI source is captured at each visitor’s first arrival and isn’t reclassified retroactively.
In plain terms:
- The conversion rate is directional, not exact. On Mode A there are no session IDs, so we cannot tell two visits by the same person apart. Treat the number as a guide to which assistants drive outcomes, not as a precise per-person rate. It becomes session-accurate when Mode B ships.
- The AI source is frozen at the visitor’s first arrival. We do not go back and re-label past visits. So this section is forward-only: it reflects what was captured at the time, and nothing changes those past visits retroactively.
Top AI landing pages
Titled Top AI landing pages, subtitled Where AI-referred people land. A ranked list of the pages people land on when they arrive from an AI assistant, with a pageviews count per page. Useful for seeing which of your pages AI assistants are pointing people to.
The empty state
Each section has its own empty state, so you may see one section populated and the other empty.
- AI agents, with no agent traffic yet:
No AI agent activity yet
When AI crawlers and agents access your-domain.com, their operators appear here.
- Visitors from AI, with no AI referrals yet:
No visitors from AI yet
When people reach your-domain.com from an AI assistant, their referrals and landing pages appear here.
If both are empty, it usually just means no AI agents have crawled your site and no one has clicked through from an AI assistant in the selected period yet. Try widening the period, or check back after more traffic.
Troubleshooting
The AI agents section is empty but I expected Googlebot. Search crawlers are not AI agents and never appear here — see the note above.
“Visitors from AI” is empty even though I get AI traffic. AI assistants often strip the referrer, so a person can arrive from ChatGPT with no trace of where they came from. We only count click-throughs where the referrer clearly identifies a tracked AI assistant. Visits without that referrer fall into your normal Direct traffic, not here.
A source I expected is missing. Only the curated AI assistants are tracked. See The AI traffic channel for the current list.
The conversion column shows a dash. That site has no goal data to compute a rate from. Conversion needs goals configured in site settings.
Related
- Understanding AI agents vs visitors from AI — the two are different things.
- The humans-only filter — how AI agents are included or excluded from your other reports.
- The AI traffic channel — the “AI” channel in the Referrers report.
- Understanding your dashboard — the rest of the dashboard.
- Privacy modes explained — why counts here are at pageview grain.