Everyone selling GEO tools has a conversion story. Most of the industry’s traffic stories disagree.
On November 1, 2026, Marco Giordano published The LLM Measurement Guide: Metrics, Methods & Tools — a skeptical, method-first tour of what LLM visibility data can and cannot prove. The same week, OtterlyAI updated AI Visibility Metrics: The GEO KPIs That Predict Revenue with the opposite emphasis: 25% of Otterly’s revenue from ChatGPT and Claude, mostly invisible in Google Analytics.
Both can be true. LLM referral sessions are tiny and noisy in GA4. AI-influenced revenue can still be large when buyers read an answer, then type your brand into Google — or tell a sales form “ChatGPT recommended you.”
This article synthesizes the November 2026 measurement discourse into a single playbook for brands that need to invest in GEO without fooling themselves — or their CFO.
Start with non-determinism — then measure anyway
Giordano’s opening constraint is real: LLM outputs are non-deterministic. The same prompt can yield different mentions, citations, and wording across minutes — not just across model versions.
That breaks rank-tracker mental models. It does not break business relevance. If a buyer chooses your CRM because Claude named you in a comparison, the interaction mattered — even if the log file shows google / organic three days later.
Obsurfable treats each answer as an observation in a corpus precisely because point-in-time snapshots beat pretending a single scrape is “the ranking.” See AI citation volatility.
Determinism is a reason to use panels and distributions, not a reason to ignore AI surfaces.
What the conversion studies actually say
Giordano summarizes conflicting evidence:
| Study / dataset | Finding |
|---|---|
| Amsive (54 sites, statistical test) | No significant conversion difference: B2B LLM 2.17% vs organic 1.16%; B2C 6.58% vs 6.78%; p > 0.4 |
| University of Hamburg (973 ecommerce sites, $20B revenue) | ChatGPT traffic converted worse than organic; only paid social was lower |
| Search Engine Land aggregate (13 months) | LLM referrals 0.15–1.5% of referral traffic; ~18% conversion rate on that thin slice — highest channel rate, ~25× less volume than SEO/direct |
Giordano’s read: do not pivot strategy because LLM traffic converts “better” in a deck — sample sizes, selection bias, and last-touch attribution corrupt most vendor case studies.
Otterly’s read: do not ignore revenue because GA4 undercounts — self-reported attribution captures journeys analytics miss.
Synthesis for operators: LLM referral rows in GA4 are necessary but insufficient. They are a lower bound, often a misleading lower bound, on influence.
The branded-search laundering problem
Giordano highlights a mechanism that explains the Otterly/GA gap:
Brands that got recommended were 2.5× more likely to get a site visit within seven days, with 55.9% of that traffic arriving as branded search instead of an AI referral.
The model persuades; Google gets the credit. Your GEO program looks idle in channel reports while brand query volume rises.
Practical fixes:
- Track brand + product name search console queries weekly alongside AI panels
- Add “How did you hear about us?” with explicit AI options (and allow multiple selections)
- Compare coverage lifts to branded search lifts on the same prompt themes — lagged by 7–14 days
This pairs with How to Measure AI Visibility KPIs Beyond CTR.
Crawler reality check — why on-site SEO tools mislead
Giordano’s technical section matters for measurement validity, not just implementation:
- Fetch bots (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Meta-ExternalAgent) read raw HTML — not rendered JS
- In a 14-page canary test, JSON-LD never survived fetch regardless of placement
- Googlebot renders — so Google AI Overviews / AI Mode behave differently from ChatGPT-on-your-docs checks
If your “LLM readiness” scanner scores schema injected client-side, you may be measuring artifacts that never reach most AI retrievers. That does not mean schema is useless on Google — it means engine-specific verification beats one green checklist.
Cross-read Semantic HTML doubles AI citation rates and Page optimization only helps high-authority domains — page signals compound after retrieval eligibility.
Giordano’s tool taxonomy — what to use where
The guide groups LLM measurement into:
- Prompt trackers / brand monitors — coverage, SoV, sentiment on fixed question sets
- Log analyzers — AI bot hits vs human referrals (different questions)
- Analytics hacks — UTM discipline, segment experiments (fragile as ChatGPT drops UTM parameters)
- Search Console — Generative AI performance on Google; not transferable to ChatGPT
Obsurfable adds a fifth: public corpus browsing — qualitative sanity checks when a metric spike makes no sense.
Rule: never mix bot log spikes with mention rate in one chart. Crawler access is necessary for many engines; it is not sufficient for mentions — see Is your robots.txt hurting AI visibility?.
Otterly’s stability layer — why mentions beat citations in the headline
Otterly’s September 2026 panel (252,407 answers, seven engines, up to 91 days) supports Giordano’s volatility point with numbers:
- 66.5% of Google AI Mode cited sources appeared one day only
- Day-to-day citation retention as low as ~26% on ChatGPT and Google AI Mode
- Brand one-day-only rates ~12–19% on comparable engines
We unpacked implications in Brand coverage is more stable than citations.
For measurement leaders: report mention coverage to executives; report citation mix to content and PR teams.
A November 2026 measurement stack that survives audit
Tier 1 — Strategic (CMO monthly)
- Brand coverage and AI share of voice on a fixed buyer prompt panel
- Self-reported revenue / pipeline by source (include AI)
- Branded search trend for core product names
Tier 2 — Operational (SEO + comms weekly)
- Citation mix by source type (owned, docs, reviews, forums, media) — earned media still dominates many categories
- Engine-specific dashboards — platform-specific strategy is mandatory per SiteProNews Nov 2, 2026
- Volatility flags — one-day citation spikes on Google AI Mode
Tier 3 — Technical (engineering as needed)
- AI bot allowlists vs training blocks — especially with shared training opt-out drafts landing in 2027
- Rendered vs raw HTML checks on template pages
- Search Console generative report for Google-only regressions
What not to put in Tier 1
- Raw AI referrer session count without branded search context
- Composite “GEO scores” from opaque vendors — engine-agnostic scores fail to predict citations
- Single-day citation screenshots as proof
Sample size and panel hygiene
Giordano warns that 250–300 prompts is too small for strategic claims. Otterly’s stability work required quarter-million answer rows because they repeated prompts daily.
Minimum viable discipline for mid-market brands:
- 40–80 core buyer prompts, frozen for 90 days
- Daily or weekly runs depending on engine volatility
- Explicit competitor set in comparisons — not generic category words
Obsurfable’s free corpus helps teams seed prompt lists from real observed questions in their vertical before they pay for automation.
Policy changes coming — measure after robots.txt edits
November 2026 vendor posts on AI training preferences (Google, Microsoft, OpenAI) will change grounding eligibility on some surfaces without touching classic search rankings. Microsoft’s March 2027 NoArchive sunset is a concrete deadline — see Microsoft Copilot training vs grounding controls.
Any measurement program that only watches Googlebot will miss Copilot or Gemini Apps regressions until mention rates drop.
Bottom line
Giordano and Otterly argue from different angles — skeptic vs operator — but agree on the hard part: last-click web analytics cannot be your GEO truth layer.
Build reporting around mentions first, citations second, branded search and self-report third, and treat LLM referrer traffic as a sanity check, not a scoreboard.
That is how you invest in AI visibility with evidence strong enough for finance — and honest enough for engineers.