SpyderBot Documentation
Understand Data Availability
Documentation and the product UI must reflect what is currently measurable. A missing value is not always a measured zero.
Release states
- Available now â supported by current SpyderBot data.
- Available with connection â supported when the named source and required fields are receiving data.
- Available after configuration â supported after goals, critical pages, policies, or mappings are defined.
- Audit-only â available from a GEO Audit probe, not continuous tracking.
- Not measurable from this evidence â the available signal cannot support the claim.
Capability guide (high level)
| Capability | State | What to expect |
|---|---|---|
| Observed bot activity | Available where bot collection exists | May be partial when the source is not request-complete |
| Bot or operator classification | Available now | Shows classification source and evidence level |
| Likely purpose | Available as classified or inferred | Always review confidence or limitation labels |
| AI-active pages | Available now | Needs bot events and canonical URL normalization |
| AI referral sessions | With connection | GA4 or SpyderBot Script as primary human source |
| Engagement signals | With connection | Only configured or received events apply |
| Goals | After configuration | Do not conclude conversions before goal mapping |
| Orders and revenue | With commerce connection | Shopify or configured GA4 ecommerce; deduplicate supported orders |
| HTTP status and block outcome | With qualifying source | Cloudflare or supported server or plugin evidence |
| Raw vs rendered content difference | Audit-only | Run LLM Readability; do not infer from request logs |
| Prompt-level referral attribution | Not measurable from ordinary referral data | Requires direct deterministic evidence |
| Model-training usage | Not measurable from a request | Never claim a request proves training use |
Continue with Read Overview after Measurement Health looks healthy.