---
language: en
title: "Bot directory"
description: "Bot directories organize identifiers and categories for automated services. Use their records alongside operator sources and observed traffic."
canonical: "https://tropk.ai/en/resources/glossary/bot-directory"
last_modified: "2026-10-12T16:11:06.783Z"
---

# Bot directory

Reviewed on 2026-10-06.

## What it means

A bot directory organizes information about automated services known to its maintainer, such as identifiers and behavior categories. It serves as a reference for investigating traffic and configuring policies. Cloudflare maintains BotBase and makes some of its information available in the public Radar directory; this coverage corresponds to the bots it tracks, not a universal registry.

## Why it matters for marketing

For marketing, consulting a directory helps guide an investigation with more precise information than the generic label of [AI traffic](/en/resources/glossary/ai-referral-traffic). A category may indicate search, training, or user action, with overlap between behaviors. This consultation supports a request to review access, but needs to be checked against the operator’s documentation.

## Example in practice

Imagine a tourism portal that notices frequent visits to its trail guide. The team finds the service in Cloudflare’s directory, classified for search and user action. It decides to review permissions for these two activities on the guide separately, checking the portal’s logs against the operator’s documentation before changing the rules.

## How to apply or verify

To investigate the trail guide, record the directory maintainer, the date consulted, the identifier found, and the assigned categories. Open the operator’s documentation and examine the available evidence of origin. Compare timestamps, URLs, and responses in the portal’s logs; being listed is not enough to attribute any request that presents that name.

## Important distinctions

A directory, an authentication mechanism, and an allowlist serve different purposes. A record can help identify a service, but it does not grant access to the portal’s content. Absence from the directory does not prove nonexistence or discontinuation. Nor does it turn visits to the guide into citations or recommendations: those outcomes require observation in the response and its corresponding context.

## Sources and references

- [BotBase](<https://developers.cloudflare.com/bots/botbase/>) — Cloudflare
- [Verified bots](<https://developers.cloudflare.com/bots/concepts/bot/verified-bots/>) — Cloudflare

## Continue a leitura

- [Crawler purpose category](</en/resources/glossary/crawler-purpose-category>)
- [Discontinued crawler tokens](</en/resources/glossary/discontinued-crawler-tokens>)
- [User agent](</en/resources/glossary/user-agent>)

## About the author

[Vinicius Pacheco](</en/team/vinicius-pacheco>)

Responsible for Tropk’s technical content, focusing on crawling, indexing, structured data, and agent access to content.

---

[All pages in Markdown](<https://tropk.ai/sitemap.md>)