# Understand bot classifications and coverage | answer.cloud Docs

> Canonical source: [Understand bot classifications and coverage | answer.cloud Docs](https://www.answer.cloud/docs/analytics/bots/)

Interpret user-bot, training-bot, and other-bot reporting, understand identification limits, and evaluate observed crawler activity without inferring citations.

guide

# Understand bot classifications and coverage

Interpret user-bot, training-bot, and other-bot reporting, understand identification limits, and evaluate observed crawler activity without inferring citations.

Reviewed November 1, 2026

Answer Cloud identifies bot activity from received request information and groups recognized names for reporting. These classifications help you inspect access patterns. They do not authenticate the caller or reveal the content of a person's outside AI conversation.

## Reporting groups

**User bots** groups recognized retrieval-oriented clients such as ChatGPT-User, OpenAI SearchBot, Claude-User, Claude-SearchBot, Perplexity-User, and DuckAssistBot. The group describes the product's reporting taxonomy. A request in this group does not prove a unique human prompt, a visible answer, or a citation.

**Training bots** includes recognized training and indexing crawlers such as GPTBot, ClaudeBot, PerplexityBot, Googlebot, Amazonbot, and CCBot. The label covers a mix of crawler purposes. Seeing Googlebot in this group is not proof that a specific page was used for model training.

**Other bots** covers identified bots outside those two AI groups. A request not classified as a bot can contribute to human page views, so “human” is also a reporting classification rather than identity verification.

The exact recognized names can change as services and the product's taxonomy evolve. Use the current dashboard and tool output when diagnosing a specific name instead of treating this guide's examples as an exhaustive permanent list.

## Interpret the evidence conservatively

A user-agent header can be spoofed. Do not describe a recognized name as provider-verified solely because it appears in the report. Counts describe recorded requests, not necessarily distinct organizations, users, or model sessions.

A crawler may request several pages or revisit one page. It may request `robots.txt`, `llms.txt`, or `sitemap.xml` without using an article in an answer. Discovery-resource activity appears separately from ordinary pages in the dashboard.

## Review a change in bot activity

1. Confirm the selected site and reporting dates.
2. Open **User bots** or **Training bots** for the relevant group.
3. Inspect which pages account for the change.
4. Check recent **Agent logs** for examples of current requests.
5. Review route, host, and crawler-access changes before attributing the change to content quality.

Browser-only collection can miss clients that do not execute JavaScript. An external site's edge integration provides different coverage, so a new Worker installation can change the measured mix without a corresponding change in market demand.

## Connect activity to a useful question

Ask whether important pages are accessible and whether observed referrals or site conversations changed separately. Avoid treating a rise in crawler traffic as a rise in revenue or guaranteed AI recommendations.

Continue with [collection methods](https://www.answer.cloud/docs/analytics/collection/), [AI referrals](https://www.answer.cloud/docs/analytics/ai-referrals/), and [crawler access](https://www.answer.cloud/docs/ai-visibility/crawler-access/).