GEO Three-Tier Metrics Whitepaper
Measure GEO with citations, recommendations and qualified opportunities
A three-tier reporting framework for deciding what to improve: whether your pages are cited, whether your brand is recommended, and what qualified opportunities can be connected to those interactions. Keep the definitions and evidence for each tier separate.
v1.1 · October 2026 · Tenten GEO Research
CH.01
Traffic is one part of the outcome
Traffic remains useful when it is tied to a business objective. It cannot, by itself, tell you how often an AI answer cites your work, whether a recommendation is positive, or whether a lead meets your sales criteria.
Our Zero-Click Whitepaper compares studies with different samples, periods and click definitions. They help explain why visibility and website visits can move differently; they do not prove that traffic must keep falling or that a fall is evidence of successful GEO.
Pew Research studied browsing from 900 U.S. adults in March 2025 and collected the corresponding search results in April. A link in the AI summary was clicked on 1% of visits to Google search pages with a summary. That denominator is search-page visits, not citation links, all AI users or your website visitors. Use your own conversion counts and definitions when judging commercial value.
Chapter takeaway
Read visibility, website activity and sales outcomes together. A citation is an observed answer feature; it is not a qualified lead or revenue.
CH.02
Tier one: citation rate
Citation rate measures how often a captured answer links to your target pages. Track unlinked brand mentions separately. Neither metric replaces search rankings; each describes a different surface.
For this framework, citation rate is the number of eligible captured answers containing at least one target URL divided by all eligible captured answers, reported per engine. Count an answer once even if it cites several target URLs. Define eligibility before collection, and report requested runs, captured answers, missing answers and errors alongside the rate. Record when an AI Overview does not appear and state how that observation enters your denominator.
How to measure it
- →Prompt set: start with the buying questions that matter to your business. A 100–300 prompt set can be a planning range, not a statistical requirement. Label educational, recommendation, comparison and validation questions; version the set when the business changes.
- →Sampling: repeated runs reveal variation. Three runs per prompt can be an initial cost estimate, not proof of reliability. Retain each answer and report the numerator, denominator and variation; do not silently replace missing results with zero or hide them through majority voting.
- →Collection: record engine, product surface, model or mode when available, date, locale and account context. An API response is not automatically equivalent to the consumer interface. Use manual checks or permitted tooling that matches the surface you intend to measure.
Common misreadings
- →A single screenshot shows one answer, not a stable citation rate. Keep the prompt and collection context so the observation can be repeated.
- →A linked citation and an unlinked brand mention are different fields. A citation also does not prove endorsement, factual correctness or purchase intent; inspect its context.
- →Report engines separately and show sample counts. A combined rate can change merely because the share of observations from each engine changed.
Chapter takeaway
Use citation changes to form a question for investigation. Check access, relevance, competing sources and sampling before deciding that a rewrite is needed. The observation alone does not prove business value or a cause.
CH.03
Tier two: share of answer
A brand can be cited as a source without being recommended to a buyer. This tier records recommendation presence and sentiment in a defined set of buying questions.
Here, share of answer means the share of eligible recommendation or comparison answers in which the brand belongs to a predefined recommendation group. Specify whether that group is an explicit top pick or the first 1–3 listed options; those are different rules. This is a reporting convention, not a universal industry standard or measured buyer shortlist.
How to measure it
- →Use the recommendation and comparison subset of the versioned prompt set. Show its own answer count; its denominator differs from the full citation-rate set.
- →Define the coding rule before reviewing answers. Record first-group recommendation, other mention or absence, plus positive, neutral or negative context. Preserve the supporting answer for ambiguous cases.
- →Aggregate at a cadence suited to sample volume and decisions. Monthly review is a planning recommendation, not proof that recommendation presence changes more slowly. Human review can check ambiguous automated labels.
Common misreadings
- →High citation rate on educational questions does not imply recommendation presence on buying questions. Compare the subsets before deciding what information is missing.
- →Share of answer is an observation in your chosen sample, not market share or a demonstrated correlation with sales.
- →Negative mentions need their own label. More appearances can mean more criticism, so a raw count is not a success measure.
Chapter takeaway
Use this tier to inspect how the brand is described at a buying decision. Test possible explanations before calling a gap an authority or positioning problem.
CH.04
Tier three: pipeline contribution
The third tier connects observable interactions to qualified opportunities. Pipeline value, closed revenue and causal impact are different measures; a report should name which one it can support.
Define the qualification stage, opportunity value, observation window and credit rule with sales before calculating contribution. Keep an observed referrer, a buyer-reported influence and model-assigned credit as separate evidence fields. Match permitted records by an appropriate identifier and avoid counting the same opportunity more than once. Missing source information remains unknown.
Observed referral
Group identifiable AI referrals
Use documented source or referrer data to group identifiable AI visits. Confirm the rule against actual records and distinguish session acquisition from event attribution. This misses interactions without a usable referral; Pew’s Google-summary 1% figure is not the coverage rate of this channel.
Sales confirmation
Record the buyer’s explanation
When a buyer explains how they found you, retain that statement in the permitted CRM process. Separate what the buyer said from what the sales team inferred, and allow multiple influences or an unknown source.
Self-report
Compare an existing source answer
If you already collect how a buyer found you, compare that answer with referral and sales records. Resolve duplicate opportunities and conflicting answers. Agreement is useful context; it does not establish incremental impact.
Common misreadings
- →Small samples need counts, qualification rules and uncertainty. Do not assume AI referrals convert better because of a channel label or another company’s reported multiple.
- →A credit model assigns contribution under its rules; it does not prove causation. Show the selected model and lookback window. First-user acquisition and event-attribution reports answer different questions.
- →Use a window that fits the actual sales cycle and data availability. Monthly reporting and quarterly decisions can be useful cadences, but they do not establish a universal 6–18 month cycle or guarantee that pipeline will arrive.
Chapter takeaway
Citation growth may occur without qualified pipeline. Report that result plainly, investigate the gap and use the agreed scope and commercial terms when deciding what to continue.
CH.05
A reporting field specification you can adapt
The table below is Tenten’s proposed field specification. Use the fields needed for the decision, document their definitions and assign an owner; it is not a record of measured client performance.
Keep raw observations and interpreted metrics distinguishable. Publish numerator, denominator, sample coverage and update date with each rate. When a definition changes, keep its previous version and mark the break in comparability rather than freezing a known error forever.
| Field name | Definition | Data source | Update frequency |
|---|---|---|---|
| Citation rate by engine | Captured answers with a target URL / eligible captured answers; unlinked mentions separate | Versioned prompt, surface and run records | Each collection round |
| Citation-rate change | Difference in percentage points under comparable definitions, with both sample counts | Current and previous eligible answer records | Each comparable round |
| New citations | Previously unobserved prompt, engine and cited URL combinations | Retained answer evidence | Each collection round |
| Lost citations | Previously observed citations absent in this sample; cause remains to be investigated | Retained answers, coverage and error records | Each collection round |
| Competitor comparison | The same citation rule for predefined competitors under the same scope | Same collection method and dates | Each comparable round |
| Investigation or rewrite queue | Observed gap, proposed explanation, next action and owner | Evidence review | As priorities change |
| Review-loop status | Investigation, change or observation stage; inconclusive outcomes retained | Change log and observation records | As work changes |
| Recommendation presence | Answers meeting the declared recommendation-group rule / eligible buying-question answers | Answer review with sentiment and subset count | At the agreed review cadence |
| Identifiable AI-referral sessions | Sessions matching the documented channel rule; unknown sources separate | Consented analytics records | At the agreed reporting cadence |
| AI referral to qualified lead | Qualified leads and the declared user or session denominator; qualification and deduplication explicit | Permitted analytics and CRM matching | After qualification is available |
| Observed pipeline contribution | Deduplicated opportunity value under the agreed evidence and credit rules; not closed revenue | CRM stages and source evidence | At the agreed commercial review |
| Crawler access | Requests and access failures separated by provider and documented crawler purpose | Server or CDN logs, with bot identity checks | At the agreed technical review |
Proposed reporting fields; version any definition change and preserve the underlying evidence.
Chapter takeaway
A useful report lets another person reproduce the count and understand its limits. Remove fields that do not support a decision; keep the evidence needed to explain those that do.
CH.06
Connect each review to a decision
Choose the review cadence from the decision and available evidence. Weekly, monthly and quarterly meetings are options, not proof that the three metrics form a causal sequence.
Start the report with the question to be decided, the relevant observations and the unresolved limits. A change in one tier can suggest a follow-up question in another; it cannot substitute for that tier’s evidence.
| Metric tier | Reporting cadence | Question it answers | Corresponding budget decision |
|---|---|---|---|
| Citation rate | Operational review; weekly when samples support it | Which access, relevance or sampling issue should we investigate? | Prioritize a specific investigation or content change |
| Recommendation presence | Positioning review; monthly when useful | How is the brand described in the buying-question sample? | Test a specific information or positioning gap |
| Observed pipeline contribution | Commercial review aligned to qualification and the sales cycle | Which qualified opportunities have usable source evidence? | Continue, adjust or stop within agreed terms and evidence limits |
Suggested review decisions; cadence and attribution must fit the actual business.
Baseline
Agree on the definitions
Document questions, product surfaces, qualification rules and available records. Do not forecast a result from an unverified conversion multiple.
Observation
Compare only compatible samples
Retain missing data, changes in collection and concurrent site work. If citations rise but qualified leads do not, report both observations without forcing a success narrative.
Decision
Use the strongest evidence available
Compare costs, qualified opportunities and completed outcomes within a suitable window. State remaining attribution limits and choose a concrete next action; more citations alone do not justify more budget.
Keep the three tiers connected and distinct
The framework organizes evidence for decisions. It does not establish that citations cause recommendations or that recommendations cause revenue. Those conclusions require additional evidence.
Data sources and research methodology
Updated October 5, 2026. The citation, recommendation and pipeline definitions are Tenten’s proposed reporting conventions, not published client outcomes. Pew’s July 22, 2025 study used browsing from 900 U.S. adults during March and search results collected April 7–17; its 1% measure concerns visits to Google search pages with an AI summary, not the share of citation links clicked or all AI interfaces. https://www.pewresearch.org/short-reads/2025/07/22/google-users-are-less-likely-to-click-on-links-when-an-ai-summary-appears-in-the-results/ Google Analytics distinguishes session/user acquisition from event-scoped attribution; the selected model and lookback settings affect credit. https://support.google.com/analytics/answer/10597962 The library’s Zero-Click and ranking/citation papers contain their own study scopes. This framework supplies no verified client conversion multiplier, universal sampling minimum or causal revenue claim.
© 2026 Tenten GEO · You're welcome to cite the contents of this whitepaper; please credit the source.
Discuss your AI search priorities
Request a 30-minute benchmark interpretationSend a booking request. We’ll email you to confirm a time within 24 hours.