SpyderBot Documentation
Route to GEO Audit
AI Traffic runtime evidence hands off to GEO Audit diagnostics when the signal suggests a technical or content issueânot for every observation.
| AI Traffic signal | Primary destination | Secondary |
|---|---|---|
| Repeated 4xx/5xx, redirect, canonical, robots, or WAF issue | URL Optimization | LLM Readability Access |
| Critical page with no observed AI activity | LLM Readability Discovery | URL Optimization |
| Raw/rendered or extraction issue with audit evidence | LLM Readability | URL Optimization |
| Duplicate URL, parameters, or locale routing | URL Optimization | LLM Readability |
| Conflicting entity facts or schema | Entity Understanding | URL Optimization |
| Referral engagement weakness only | Content / CRO action | No automatic GEO Audit |
| Attribution coverage problem | Measurement Setup | No GEO Audit |
| Suspicious identity | AI Access Policies | No GEO Audit |
Score governance
- AI Traffic findings do not automatically change GEO Audit scores.
- Unmeasured tracking fields are not passed audit checks.
- Audit scores follow their own versioned specifications.
- Rerunning an audit creates a new result version and preserves history.