SpyderBot Documentation
Quick Overview estimates and benchmarks
Quick Overview estimates and observed AI performance answer different questions. The four overview values below use their named external source. They are not silently replaced by connected observed traffic or by GEO measurements.
The overview snapshot uses the 30 complete calendar days preceding its anchor date in the declared timezone. The source’s observation or publication time remains visible. Running or reopening a report later does not move that original window or backfill it with future information.
On this page
Total Visits — Estimated · AI Referrals — Estimated · Bot Traffic — Estimated · Category Rank — External Estimate · Benchmark Organic Visibility · Benchmark Recommendation · Benchmark Sentiment · Benchmark Capture and Control Checks
Total Visits — Estimated
Unit: Estimated visits
The external source’s estimated visits for the declared domain and frozen overview window.
How it is calculated
Use the source-provided estimate and its supported scope, period and methodology label. Do not label it as measured sessions from your connected analytics. If the required estimate is unavailable, show unavailable rather than inventing a replacement.
How to interpret it
External estimates can differ from first-party analytics. Visits and unique people are different units.
What to do next
Use the estimate for context and connected analytics for observed measurement.
Measurement scope and aggregation ↗ · Evidence and availability ↗
AI Referrals — Estimated
Unit: Estimated AI referral activity
An external estimate of AI referral activity in the frozen overview snapshot.
How it is calculated
Use the estimate provided for the supported domain, source and window. Preserve whether its unit is visits or another explicit referral unit. Do not relabel it as observed SpyderBot sessions or derive it from visibility.
How to interpret it
AI Visibility is not a traffic estimator. Missing external data is unavailable.
What to do next
Compare with connected AI referral sessions only with the source distinction visible.
Related concepts: AI Referral Sessions ↗
Measurement scope and aggregation ↗ · Evidence and availability ↗
Bot Traffic — Estimated
Unit: External estimated activity
The external source’s bot-traffic estimate for the frozen overview snapshot.
How it is calculated
The value uses the external source’s supported estimate, unit and frozen period. It remains separate from observed server, edge or CDN activity. Without a supported external estimate, the value is unavailable.
How to interpret it
The estimate does not establish which model trained on your content.
What to do next
Use connected request evidence to investigate actual access behaviour.
Related concepts: Observed AI Bot Activity ↗
Measurement scope and aggregation ↗ · Evidence and availability ↗
Category Rank — External Estimate
Unit: Ordinal rank in an external category
The domain’s category ranking as reported or derived from the declared external ranking source.
How it is calculated
The ranking comes from the external category, comparison set, period and rank basis associated with the overview snapshot. The category and source define its meaning. SpyderBot AI Share of Voice does not determine this rank.
How to interpret it
This rank is not an AI recommendation position, a GEO leaderboard or a universal market rank.
What to do next
Check the external category and scope before comparing domains.
Related concepts: Average Rank When Ranked ↗ · AI Share of Voice ↗
Measurement scope and aggregation ↗ · Evidence and availability ↗
Benchmark Organic Visibility
Unit: Percent under the fixed benchmark scope
Organic visibility measured for each benchmark entity on the same eligible observation pool.
How it is calculated
Apply the organic visibility definition symmetrically to the declared benchmark entities, prompts and systems. Keep the benchmark anchor and roster fixed for comparison. Named-brand controls remain separate from organic discovery.
How to interpret it
A benchmark does not establish absolute quality or market share. Its roster and question scope matter.
What to do next
Compare the same entities on the same benchmark basis.
Related concepts: Organic Visibility ↗ · Visibility and Recommendation Gaps ↗
Measurement scope and aggregation ↗ · Evidence and availability ↗
Benchmark Recommendation
Unit: Percent under the fixed benchmark scope
Substantive recommendation outcomes for benchmark entities in the same eligible task.
How it is calculated
Apply the same recommendation definition and balanced opportunity scope to each entity. Keep mentions, candidate inclusion and primary recommendation separate.
How to interpret it
A blended overall benchmark score is not provided by combining unrelated dimensions.
What to do next
Compare task-aligned metrics and inspect answer evidence.
Related concepts: Organic Recommendation Rate ↗ · Candidate Inclusion Rate ↗
Measurement scope and aggregation ↗ · Evidence and availability ↗
Benchmark Sentiment
Unit: Classified portrayal distribution in the named cohort
Sentiment of benchmark entities in the explicitly named organic or controlled question group.
How it is calculated
Apply the sentiment definition within the declared cohort. Controlled questions that introduce an entity do not become organic sentiment observations. Use the same cohort and classification coverage for entity comparisons.
How to interpret it
Different cohorts can reasonably produce different portrayal. They cannot be merged without changing the meaning.
What to do next
Read the question-group label and distribution.
Related concepts: Sentiment Distribution ↗
Measurement scope and aggregation ↗ · Evidence and availability ↗
Benchmark Capture and Control Checks
Unit: Observation and control status
Whether the benchmark observation and its declared controls support the intended comparison.
How it is assessed
Capture status describes whether benchmark observations were obtained on the intended comparable scope. Control observations describe a declared check on the measurement setup. Neither adds positive brand-performance outcomes: incomplete capture is missing evidence, and a completed control is not organic visibility.
How to interpret it
Control results validate aspects of the measurement setup, not the truth of every answer or guaranteed production behaviour.
What to do next
Resolve capture or comparability gaps before interpreting the benchmark.
Measurement scope and aggregation ↗ · Evidence and availability ↗