Learning Path
Navigate the AXO curriculum
Websites
Website Deep Dives
Measurement & Analytics
What you can actually measure about AI visibility in 2026 — Search Console's Generative AI report, the visibility tool market, Share of Voice and why it is not comparable across tools, GA4's attribution gap, and a minimum tracking stack that is honest about its blind spots.
Measuring AXO success requires tracking how AI agents discover, process, and reference your content. Unlike traditional web analytics, agent measurement focuses on citation rates, content quality scores, and authority signals.
AI Bot Traffic Reality
Read those ratios as a warning about measurement: AI crawlers fetch your pages orders of magnitude more often than they send a visitor back, so referral analytics alone will badly understate how much your content is being consumed.
Search Console's Generative AI Report
Start here. Launched June 3, 2026, this is the first first-party AI visibility data most sites can get, it is free, and it is already sitting in an account you own. For a long time the honest answer to "how much do we show up in AI Overviews?" was "nobody can tell you." This closes part of that gap.
What it gives you
- AI Overviews and AI Mode impressions separated from ordinary Search. Previously these were blended into your overall Performance numbers, so you could not tell an AI impression from a blue link. Now you can size the AI surface independently and watch it move.
- A control to exclude content from AI Overviews, AI Mode and Discover AI without affecting normal Search rankings. This matters: previously the only lever was
Google-Extendedornosnippet, both of which came with collateral damage. You can now opt out of the AI surfaces and keep your conventional search presence intact.
What it does not give you — read before you build a dashboard on it
- Impressions only. No clicks. You cannot compute a click-through rate for AI surfaces from this report, which means you cannot answer the question everyone actually wants answered.
- No queries. You cannot see which prompts surfaced you, so you cannot do prompt-level optimization from this data.
- Google surfaces only. Nothing about ChatGPT, Perplexity, Claude or Copilot. It sizes one engine, not your AI visibility overall.
Used correctly it is a trend line for one engine: is our AI-surface presence growing or shrinking, and on which pages. Used incorrectly it becomes "our AI traffic," which it is not — impressions are not visits.
Full walkthrough: the Search Console Generative AI report, explained. Google's announcement: Search Central blog, June 2026.
Citation Tracking
Agent Citation Monitoring
Track when and how AI agents reference your content:
Practical Citation Tracking Playbook
1. Detect AI Crawlers in Server Logs
# Nginx/Apache log analysis
grep -E "(GPTBot|OAI-SearchBot|ChatGPT-User|OAI-AdsBot|ClaudeBot|Claude-SearchBot|Claude-User|Google-Extended|Google-Agent|PerplexityBot|Perplexity-User)" access.log
# Count crawls by user agent
awk '$12 ~ /GPTBot/ {count++} END {print "GPTBot crawls:", count}' access.log2. Track Referrals from AI Platforms
- • Monitor referrals from
chatgpt.com(thechat.openai.comhost was retired in May 2024) - • Also track
perplexity.ai,gemini.google.com,copilot.microsoft.com, andclaude.ai - • Set up GA4 custom dimensions for AI referrals
- • Use UTM parameters for citation links when possible
3. Set Up Crawl Rate Alerts
- • Alert when AI bot traffic increases >50% week-over-week
- • Monitor for unusual crawl patterns or errors
- • Track which content sections get most agent attention
4. Spot-Check Citation Presence
- • Regularly search ChatGPT for your brand/content topics
- • Check Perplexity.ai results for your domain citations
- • Monitor Google's AI Overviews for your content
- • Set up Google Alerts for your domain + "according to"
Advanced Monitoring Procedures
GA4 Custom Dimensions Setup
// GA4 Enhanced Measurement
gtag('config', 'GA_MEASUREMENT_ID', {
custom_map: {
'custom_parameter_1': 'user_agent_type',
'custom_parameter_2': 'crawler_category'
}
});
// Track AI crawler visits
gtag('event', 'ai_crawler_visit', {
'user_agent_type': 'GPTBot',
'crawler_category': 'training',
'page_path': window.location.pathname
});BigQuery Analysis Queries
-- Track AI crawler trends vs content updates SELECT DATE(event_timestamp) as date, event_name, COUNT(*) as events, COUNTIF(user_agent LIKE '%GPTBot%') as gpt_crawls, COUNTIF(user_agent LIKE '%PerplexityBot%') as perplexity_crawls, COUNTIF(user_agent LIKE '%ClaudeBot%') as claude_crawls FROM `your-project.analytics_123456789.events_*` WHERE _TABLE_SUFFIX BETWEEN '20260101' AND '20261231' AND event_name = 'page_view' GROUP BY date, event_name ORDER BY date DESC;
Citation Verification Workflow
- Weekly: Search "site:yourdomain.com" in ChatGPT, Claude, Perplexity
- Monthly: Query your key topics + brand name in each AI platform
- Document citation frequency and accuracy in a tracking sheet
- Cross-reference with crawler activity spikes in your logs
- Alert on 50%+ drops in citation mentions month-over-month
// Shape of a citation-tracking record. Values are illustrative:
// there is no API that returns these numbers. You assemble them
// from AI-visibility tooling, server logs, and manual spot checks.
interface CitationReport {
periodStart: string // ISO date
periodEnd: string
totalCitations: number // from your AI visibility tool
byEngine: Record<string, number> // engines diverge widely — keep them separate
topCitedUrls: Array<{ url: string; citations: number }>
crawlerHits: Record<string, number> // from server logs, by user agent
}
// Track engines separately rather than summing them. Research in 2026
// found only ~11% of domains cited by both ChatGPT and Perplexity
// overlapped, so a single blended "citation count" hides more than
// it reveals.Citation Volatility: Why One Check Proves Nothing
Before you act on any citation check, understand that the same prompt does not reliably return the same sources. Research published in July 2026 documented ChatGPT drawing on multiple retrieval pipelines, with roughly 11.6% of prompts switching primary source between runs and producing substantially different URL sets as a result.
What this breaks, practically
- Single-run citation checks are unreliable. "We lost our citation" after one query is more likely sampling noise than a real change. So is "we won one."
- Before/after tests on a single run are worthless. If you publish a change and re-run one prompt, you cannot distinguish your edit from pipeline variance.
- Vendor screenshots prove very little. Any single captured result — yours or a competitor's — is one draw from a distribution.
Do this instead: sample each prompt repeatedly — several runs across several days — and treat citation presence as a rate rather than a binary. Record how many of N runs cited you. Only compare rates with a consistent N, and be suspicious of any change smaller than your observed run-to-run variance.
Source: Search Engine Land, July 2026
AI Share of Voice — and Its Big Caveat
AI Share of Voice is the headline metric practitioners have converged on: roughly, how often your brand appears in AI answers for a defined set of prompts, relative to competitors. It is a reasonable thing to want to know, and it is the number most tools lead with.
A note on vocabulary, since it trips people up here more than anywhere else. “AI visibility” settled as the name for the metric, which is why every tracker uses it, while AEO and GEO stuck as names for the practice. That split is the whole reason the terminology feels unresolved — we unpack it in the post on what to call this.
There is no standardized formula
This is the caveat that gets left out of every vendor deck. No standard definition of AI Share of Voice exists. Vendors differ on what counts as an appearance (a link? a brand mention without a link?), which prompts make up the denominator, how many runs they average, which engines they include, and how they weight position within an answer.
The consequence is specific and worth stating plainly: cross-tool comparison is meaningless. A 12% share in one tool and 30% in another may describe identical reality. Two practical rules follow — pick one tool and stay with it, because the trend within a consistent methodology is the only signal you have; and never put two vendors' share numbers on the same chart.
Also ask any vendor how many runs per prompt they average. Given the volatility above, a share figure built on single runs is measuring noise.
Always segment by engine
Do not blend engines into one number. Ahrefs research in 2026 found that only about 11% of domains cited by both ChatGPT and Perplexity overlapped. The engines are drawing on substantially different source sets, so a blended average describes no engine in particular and can stay flat while you collapse on one and climb on another.
Report per-engine, and expect your strategy to differ by engine too. That divergence is also why no single tool can claim complete coverage.
The AI-Visibility Tool Market
These are categories with examples, not endorsements — we have not benchmarked these tools against each other, and given the lack of a standard Share of Voice formula, a like-for-like benchmark would be difficult to construct honestly. What is worth knowing is the shape of the market: it consolidated hard in 2026, and the independent tool you evaluate this quarter may be a feature inside a larger suite by the next.
Enterprise suites
- Profound — raised at a $1B valuation in February 2026.
- Adobe Brand Visibility — formerly LLM Optimizer, renamed after Adobe completed its $1.9B acquisition of Semrush in April 2026.
- Scrunch — acquired by Sitecore in June 2026.
Two of these three were independent a year ago. Ask about product roadmap and contract portability.
Mid-market, purpose-built
- • Peec
- • Otterly
- • Rankscale
- • Evertune
Focused on prompt tracking and citation monitoring, usually at a price point that suits a single brand rather than a portfolio.
Features in tools you may already own
- • Ahrefs Brand Radar
- • Semrush AI Visibility Toolkit
- • Similarweb AI Traffic Tracker
Check your existing SEO subscription before buying anything new — this is often enough to establish whether the channel matters to you.
The honest framing: no tool sees all engines. Every one of them works by sampling prompts and reading the answers, because no engine publishes citation data. That means coverage is a sampling choice, results carry the volatility described above, and any vendor claiming complete visibility is describing a sample. Buy one to get a consistent trend line, not a ground truth.
Agent Analytics
Separating Agent Traffic
Distinguish between human users and AI agent crawlers:
Bot User-Agent Reference (Copy-Paste Ready)
| User-Agent String | Purpose | robots.txt Respect |
|---|---|---|
GPTBot/1.0 | OpenAI training data | ✓ Usually |
OAI-SearchBot | ChatGPT search index (citations) | ✓ Usually |
ChatGPT-User | User-requested browsing | ⚠ May ignore |
OAI-AdsBot | OpenAI ads crawler (added January 2026) | ✓ Usually |
ClaudeBot/1.0 | Anthropic training crawler | ✓ Usually |
Claude-SearchBot | Anthropic search index | ✓ Usually |
Claude-User | User-triggered fetch | ⚠ May ignore |
Google-Extended | Gemini training/grounding opt-out token | ✓ Yes |
Google-Agent | User-triggered fetch (added March 2026) | ⚠ Ignores robots.txt by design |
PerplexityBot | Perplexity search index | ✓ Usually |
Perplexity-User | User-triggered fetch | ⚠ May ignore |
Applebot-Extended | Apple AI training opt-out token | ✓ Yes |
meta-externalagent | Meta AI crawler | ✓ Usually |
Amazonbot | Amazon/Alexa crawler | ✓ Usually |
Bytespider | ByteDance crawler | ⚠ Inconsistent |
CCBot/2.0 | Common Crawl | ✓ Usually |
MistralAI-User | Mistral user-triggered fetch | ⚠ May ignore |
DuckAssistBot | DuckDuckGo AI answers | ✓ Usually |
Reference: Cloudflare Radar AI crawler analysis (2026) and each vendor's published crawler documentation. Verify tokens against vendor docs before relying on them—the roster changes several times a year.
Quick Detection
# Quick grep for AI crawlers grep -E "(GPTBot|OAI-SearchBot|ChatGPT-User|OAI-AdsBot|ClaudeBot|Claude-SearchBot|Claude-User|Google-Extended|Google-Agent|PerplexityBot|Perplexity-User|Applebot-Extended|meta-externalagent|Amazonbot|Bytespider|CCBot|MistralAI-User|DuckAssistBot)" access.log
Key Metrics
- • Agent crawl frequency
- • Content depth accessed
- • Time spent on structured data
- • Schema markup interaction
Attribution Reality: GA4 Undercounts AI Traffic
Building AI-referral channel groups in GA4 is standard practice and you should do it. But you need to know its failure mode before you report the numbers to anyone: 35–70% of AI-referred sessions arrive with no referrer and therefore land in Direct. Depending on the mix of engines and clients sending you traffic, GA4 can undercount AI traffic by roughly 2x.
The cause is mundane: many AI clients are native apps or strip the referrer on outbound links, so there is nothing for GA4 to attribute. This is not a tagging mistake you can fix — it is a ceiling on what referrer-based attribution can see. Report your GA4 AI number as a floor, not a measurement.
Referral domains to group
chatgpt.com perplexity.ai gemini.google.com copilot.microsoft.com claude.ai
Create a custom channel group matching these as referral sources. Review the list quarterly — hosts change, as chat.openai.com did when it was retired in May 2024.
Cross-check with a Direct-traffic watch
Since the missing sessions land in Direct, watch Direct for the fingerprint of hidden AI referrals: growth in Direct landings on deep pages that nobody would type from memory, especially pages your logs show AI crawlers fetching heavily.
This is an inference, not a measurement. Use it to sanity-check magnitude, and label it clearly when you report it.
Server logs: the more reliable signal, for a different question
Crawler analysis in your server logs is far more trustworthy than referral analytics, because it counts requests you actually received rather than inferring from a header that may not be sent. Every AI crawler hit is a fact in your log file.
But be precise about what it answers. Logs measure consumption — who fetched what, how often, which sections. They say nothing about citation: a crawler fetching your page a thousand times tells you nothing about whether you were ever named in an answer. Consumption and citation are different questions and need different instruments. Use logs for the first, prompt sampling for the second, and never let one stand in for the other.
Content Quality Scoring
Automated Quality Assessment
Score content based on agent-friendly characteristics:
// Content quality scoring system
function calculateAXOScore(content, metadata) {
const scores = {
structure: assessStructuralQuality(content),
clarity: assessContentClarity(content),
completeness: assessInformationCompleteness(content),
trustSignals: assessTrustSignals(metadata),
technicalImplementation: assessTechnicalQuality(content)
};
const weightedScore = (
scores.structure * 0.25 +
scores.clarity * 0.20 +
scores.completeness * 0.20 +
scores.trustSignals * 0.20 +
scores.technicalImplementation * 0.15
);
return {
overallScore: Math.round(weightedScore),
componentScores: scores,
recommendations: generateRecommendations(scores)
};
}ROI Measurement
Business Impact Metrics
Connect AXO improvements to business outcomes:
Brand Authority
- • Brand mention increase
- • Quality of associations
- • Competitive advantage
Traffic Impact
- • Agent referral traffic
- • Direct brand searches
- • Search positioning
Lead Generation
- • Qualified leads from agents
- • Conversion rate improvements
- • Acquisition cost reduction
Measure Conversion Rate, Not Session Volume
If you judge AI referrals by session count, you will conclude the channel does not matter. It is a small share of sessions for almost everyone. That is the wrong denominator.
Multiple 2026 analyses found AI referral traffic converting several times better than organic search — Semrush put the gap at roughly 4.4x. The intuition behind it is straightforward: someone who arrives after an assistant has already answered their question and recommended you has done their evaluation before they clicked. They land further down the funnel than a search visitor.
How to report it
- Report conversion rate and revenue per session for the AI channel alongside session count — never session count alone.
- Compare AI referrals against organic search on the same conversion definition and the same window, or the comparison means nothing.
- Watch your sample size. A small channel with a high rate produces volatile percentages; a handful of conversions can swing it wildly. Give it enough time to stabilize before drawing a conclusion.
- Remember the attribution gap above cuts both ways: if a large share of AI sessions is landing in Direct, your measured AI conversion rate is computed on a subset, and Direct is quietly absorbing the rest.
Performance Monitoring
Automated Quality Alerts
Set up monitoring for content quality degradation and technical issues:
- Quality score drops below threshold
- Schema markup validation failures
- Citation rate decreases
- Agent crawl errors or blocks
What to Actually Track
You do not need a large stack. You need four instruments that fail in different directions, because each one is blind to something the others catch. Here is the recommended minimum, with an honest statement of what each cannot tell you.
1. Search Console Generative AI report
Tells you: whether your presence in Google's AI Overviews and AI Mode is growing or shrinking, and on which pages. First-party, free, no sampling.
Cannot tell you: clicks, queries, or anything about ChatGPT, Perplexity, Claude or Copilot.
2. GA4 AI-referral segment
Tells you: what AI-referred visitors do once they arrive — conversion rate, revenue per session, which landing pages work. This is where the business case lives.
Cannot tell you: the true size of the channel. It misses the 35–70% of AI sessions that arrive with no referrer. Treat every AI number here as a floor.
3. Server-log crawler monitoring
Tells you: exactly which AI crawlers fetch what, how often, and whether they are getting 200s. The most reliable data on this page, because it counts requests rather than inferring them — and the only thing that will catch a misconfigured block.
Cannot tell you: anything about citation. Consumption is not visibility. It is also blind to agentic browsers, which arrive with ordinary browser user-agents.
4. Periodic manual prompt sampling
Tells you: whether you are actually named in answers, how you are characterized, and who is named instead. The only instrument that sees the answer itself — and the only one that catches a confidently wrong description of your product. Keep a fixed prompt set so runs are comparable.
Cannot tell you: anything reliable from a single run. Sample each prompt several times across several days and record a citation rate. Your sample is also not a traffic-weighted picture of what real users actually ask.
A paid visibility tool is optional
It automates instrument 4 at greater scale and across more engines, which is genuinely useful if AI search is material to your business. It does not replace the other three. If you buy one, buy it to stop doing prompt sampling by hand — not because you expect it to reveal a number the free tools are hiding from you.
AXO Measurement Framework
- Citation Tracking: Monitor how often agents reference your content
- Agent Analytics: Separate agent traffic from human user analytics
- Quality Scoring: Automated assessment of content agent-friendliness
- ROI Measurement: Connect AXO improvements to business outcomes
- Continuous Monitoring: Automated alerts for quality degradation
- Benchmarking: Compare performance against industry standards