diff --git a/public/__redirects b/public/__redirects index cac3938db49579f..d1f261f493d3f60 100644 --- a/public/__redirects +++ b/public/__redirects @@ -263,6 +263,9 @@ /bots/get-started/pro/ /bots/get-started/super-bot-fight-mode/ 301 /bots/additional-configurations/javascript-detections/ /cloudflare-challenges/challenge-types/javascript-detections/ 301 /bots/troubleshooting/frequently-asked-questions/ /bots/frequently-asked-questions/ 301 +/bots/concepts/bot/verified-bots/categories/ /bots/concepts/bot/verified-bots/#categories 301 +/bots/concepts/bot/verified-bots/ip-validation/ /bots/reference/bot-verification/ip-validation/ 301 +/bots/concepts/bot/verified-bots/web-bot-auth/ /bots/reference/bot-verification/web-bot-auth/ 301 #browser-rendering /browser-rendering/get-started/browser-rendering-with-DO/ /browser-rendering/workers-bindings/browser-rendering-with-do/ 301 diff --git a/src/content/docs/ai-audit/features/manage-ai-crawlers.mdx b/src/content/docs/ai-audit/features/manage-ai-crawlers.mdx index 5094141f50bab6f..24960b0f873be95 100644 --- a/src/content/docs/ai-audit/features/manage-ai-crawlers.mdx +++ b/src/content/docs/ai-audit/features/manage-ai-crawlers.mdx @@ -25,7 +25,7 @@ The **AI Crawlers** tab displays a table of AI crawlers that are requesting acce | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | AI Crawlers | The name of the AI crawler. | | Operator | The name of the entity who owns the AI crawler. Note that an operator may have multiple AI crawlers. | -| Category | The category of the AI crawler. Refer to [Verified bot categories](/bots/concepts/bot/verified-bots/categories/). | +| Category | The category of the AI crawler. Refer to [Verified bot categories](/bots/concepts/bot/verified-bots/#categories). | | Block | Toggle for blocking specific AI crawlers. | @@ -33,7 +33,7 @@ The **AI Crawlers** tab displays a table of AI crawlers that are requesting acce | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | AI Crawlers | The name of the AI crawler. | | Operator | The name of the entity who owns the AI crawler. Note that an operator may have multiple AI crawlers. | -| Category | The category of the AI crawler. Refer to [Verified bot categories](/bots/concepts/bot/verified-bots/categories/). | +| Category | The category of the AI crawler. Refer to [Verified bot categories](/bots/concepts/bot/verified-bots/#categories). | | Requests | The number of times the AI crawler has requested to crawl your content. | | Robots.txt violations | The number of times the AI crawler has violated your `robots.txt` file. | | Action | The action you wish to take for the AI crawler. Refer to [Take action for each AI crawler](/ai-audit/features/manage-ai-crawlers/#take-action-for-each-ai-crawler). | diff --git a/src/content/docs/ai-audit/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/crawl-pages.mdx b/src/content/docs/ai-audit/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/crawl-pages.mdx index ef4f3729857c258..f1f507bf0706aac 100644 --- a/src/content/docs/ai-audit/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/crawl-pages.mdx +++ b/src/content/docs/ai-audit/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/crawl-pages.mdx @@ -33,7 +33,7 @@ To access this content, the AI crawler must provide headers for paid access. ### 2.1. Include WBA headers -Include Web Bot Auth headers by following the steps [Sign your requests](/bots/concepts/bot/verified-bots/web-bot-auth/#4-after-verification-sign-your-requests) +Include Web Bot Auth headers by following the steps [Sign your requests](/bots/reference/bot-verification/web-bot-auth/#4-after-verification-sign-your-requests) ### 2.2. Include payment headers diff --git a/src/content/docs/ai-audit/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/verify-ai-crawler.mdx b/src/content/docs/ai-audit/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/verify-ai-crawler.mdx index c96b438f1cf7b5f..201e18fa20d1004 100644 --- a/src/content/docs/ai-audit/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/verify-ai-crawler.mdx +++ b/src/content/docs/ai-audit/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/verify-ai-crawler.mdx @@ -37,7 +37,7 @@ To access this content, you must verify your AI crawler. Ensure your AI crawler identifies itself with the required headers for Web Bot Auth. -Follow the steps found in [Web Both Auth](/bots/concepts/bot/verified-bots/web-bot-auth/). +Follow the steps found in [Web Both Auth](/bots/reference/bot-verification/web-bot-auth/). ## 2. Follow verified bot policy diff --git a/src/content/docs/bots/additional-configurations/block-ai-bots.mdx b/src/content/docs/bots/additional-configurations/block-ai-bots.mdx index b0896149b590228..d86440809f8a4bb 100644 --- a/src/content/docs/bots/additional-configurations/block-ai-bots.mdx +++ b/src/content/docs/bots/additional-configurations/block-ai-bots.mdx @@ -14,7 +14,7 @@ import { Render, Steps } from "~/components" The **Block AI bots** feature is only available in the new [application security dashboard](/security/). ::: -You can choose to block AI bots by activating **Block AI bots**. Activating this setting will block [verified bots](/bots/concepts/bot/verified-bots/overview/) that are classified as AI crawlers, as well as a number of unverified bots that behave similarly. +You can choose to block AI bots by activating **Block AI bots**. Activating this setting will block [verified bots](/bots/concepts/bot/verified-bots/) that are classified as AI crawlers, as well as a number of unverified bots that behave similarly. To block [AI bots](/bots/concepts/bot/#ai-bots): diff --git a/src/content/docs/bots/concepts/bot/index.mdx b/src/content/docs/bots/concepts/bot/index.mdx index e30ce06822b6cff..dc99df6e16d7db2 100644 --- a/src/content/docs/bots/concepts/bot/index.mdx +++ b/src/content/docs/bots/concepts/bot/index.mdx @@ -23,7 +23,7 @@ For more background, refer to [What is a bot?](https://www.cloudflare.com/learni -For more information, refer to [Verified bots](/bots/concepts/bot/verified-bots/overview/). +For more information, refer to [Verified bots](/bots/concepts/bot/verified-bots/). :::note diff --git a/src/content/docs/bots/concepts/bot/signed-agents/index.mdx b/src/content/docs/bots/concepts/bot/signed-agents/index.mdx new file mode 100644 index 000000000000000..d42bd2853ad52ab --- /dev/null +++ b/src/content/docs/bots/concepts/bot/signed-agents/index.mdx @@ -0,0 +1,41 @@ +--- +pcx_content_type: overview +title: Signed agents +sidebar: + order: 3 +learning_center: + title: What is a bot? + link: https://www.cloudflare.com/learning/bots/what-is-a-bot/ + +--- + +A signed agent is controlled by an end user and a verified signature-agent from their Web Bot Auth implementation. + +You can request for your agent to be added to Cloudflare's bots and agents directory by filling out an [online application](https://dash.cloudflare.com/?to=/:account/configurations/verified-bots) in the Cloudflare dashboard. + +:::note +A bot cannot be registered as both a verified bot and a signed agent. Review Cloudflare's [verified bots](/bots/concepts/bot/verified-bots/) to determine how to identify your bot. +::: + +## Signed agent requirement + +For an agent to be recognized, it must meet the following requirements: + +1. The agent must follow the [signed agents policy](/bots/concepts/bot/signed-agents/policy/). +2. The bot must be using [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/). + +Once Cloudflare approves a signed agent, it should appear on [Cloudflare Radar's bots and agents directory](https://radar.cloudflare.com/verified-bots). + +--- + +## Transient false negatives + +Once Cloudflare lists an agent as a signed agent, this entry is cached and may get delisted if no traffic is seen in the Cloudflare network coming from the agent for a defined period of time. + +An agent can remain unlisted until Cloudflare sees traffic being sourced from the agent. When the agent is revalidated, it is listed as a signed agent again. + +--- + +## Verification method + +The bot must be verified using [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/). diff --git a/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx b/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx new file mode 100644 index 000000000000000..b69972d6c1722e0 --- /dev/null +++ b/src/content/docs/bots/concepts/bot/signed-agents/policy.mdx @@ -0,0 +1,68 @@ +--- +pcx_content_type: reference +title: Signed agents policy +sidebar: + order: 3 + label: Policy + +--- + +In order to be listed by Cloudflare as a signed agent, your agent must conform to the below requirements. To provide the best possible protection to our customers, this policy may change in the future as we adapt to new bot behaviors. + +## Agent policy + +### Minimum traffic + +An agent must have a minimum amount of traffic for Cloudflare to be able to find it in the sampled data. The minimum traffic should have more than 1,000 requests per day across multiple domains. + +### Minimum zones + +Service must be made for a widespread use of zones. + +#### Example + +A bot crawling one site is not valid. + +### Agent identification + +The user-agent field is optional as it is not required for Web Bot Authentication. + +However, if you choose to provide a user-agent, it and the message signature must meet the following requirements: + +- Have at least five characters. +- Must not contain special characters. +- Must not include the same user-agent of another verified service. + +#### Example + +`cloudflare-browser-rendering` is a valid message signature. + +### Service purpose + +The purpose of the service should be benign or helpful to both the owner of a zone and the users of the service. The service cannot perform any of the following: + +- Bot tooling +- Scalpers +- Credential-stuffing +- Directory-traversal scanning +- Excessive data scraping +- DDoS botnets + +#### Example + +Price scraping direct e-commerce competitors is not a valid use case. + +### Public documentation + +The agent must have a publicly documented purpose and expected behavior. + +--- + +## Breach of policy + +If any of the requirements to validate are breached, a service will be removed from the signed agent list. + +The following are examples of breaches of policy: + +- The service has vulnerabilities that have not been patched. +- The disclosed purpose of the service does not reflect on the traffic. diff --git a/src/content/docs/bots/concepts/bot/verified-bots/categories.mdx b/src/content/docs/bots/concepts/bot/verified-bots/categories.mdx deleted file mode 100644 index cd6fb55dfd3cd26..000000000000000 --- a/src/content/docs/bots/concepts/bot/verified-bots/categories.mdx +++ /dev/null @@ -1,41 +0,0 @@ ---- -pcx_content_type: reference -title: Verified bot categories -sidebar: - order: 20 - label: Categories - ---- - -You can segment your verified bot traffic by its type and purpose by adding the Verified Bot Categories field `cf.verified_bot_category` as a filter criteria in [WAF Custom rules](/waf/custom-rules/), [Advanced Rate Limiting](/waf/rate-limiting-rules/), and Late Transform rules. - -:::note - -The Verified Bot Categories field is not compatible with legacy Firewall rules. -::: - -## Categories - -| Name | String value | Example | -| -------------------------- | ---------------------------- | ----------------------------------------------------------------------- | -| Academic research | `Academic Research` | Library of Congress, TurnItInBot, Bibliothèque nationale de France | -| Accessibility | `Accessibility` | Accessible Web Bot | -| Advertising or marketing | `Advertising & Marketing` | Google Adsbot | -| Aggregators | `Aggregator` | Pinterest, Indeed Jobsbot | -| AI Assistant | `AI Assistant` | Perplexity-User, DuckAssistBot | -| AI Crawler | `AI Crawler` | Google Bard, ChatGPT bot | -| AI Search | `AI Search` | OAI-SearchBot | -| Archiver | `Archiver` | Internet Archive, CommonCrawl | -| Feed fetcher | `Feed Fetcher` | RSS or Podcast feed updaters | -| Monitoring or analytics | `Monitoring & Analytics` | Uptime Monitors | -| Page preview | `Page Preview` | Facebook, Slack, Twitter, or Discord Link Preview tools | -| Search engine crawler | `Search Engine Crawler` | Googlebot, Bingbot, Yandexbot, Baidubot | -| Search engine optimization | `Search Engine Optimization` | Google Lighthouse, GT Metrix, Pingdom, AddThis | -| Security | `Security` | Vulnerability Scanners, SSL Domain Control Validation (DCV) Check Tools | -| Social media marketing | `Social Media Marketing` | Brandwatch | -| Webhooks | `Webhooks` | Payment processors, WordPress Integration tools | -| Other | `Other` | | - -## Availability - -Verified Bot Categories is available on all plans. diff --git a/src/content/docs/bots/concepts/bot/verified-bots/index.mdx b/src/content/docs/bots/concepts/bot/verified-bots/index.mdx index fd962c4586cd46c..00106578965009e 100644 --- a/src/content/docs/bots/concepts/bot/verified-bots/index.mdx +++ b/src/content/docs/bots/concepts/bot/verified-bots/index.mdx @@ -1,9 +1,7 @@ --- -pcx_content_type: navigation +pcx_content_type: overview title: Verified bots sidebar: - group: - hideIndex: true order: 2 learning_center: title: What is a bot? @@ -11,10 +9,76 @@ learning_center: --- -import { Render, DirectoryListing } from "~/components"; +import { GlossaryTooltip } from "~/components" - +A verified bot is a bot which has been added to Cloudflare's list of verified bots. -Refer to the pages below for additional resources on verified bots. +You can request for your bot to be added to Cloudflare's bots and agents directory by filling out an [online application](https://dash.cloudflare.com/?to=/:account/configurations/verified-bots) in the Cloudflare dashboard. - \ No newline at end of file +:::note +A bot cannot be registered as both a verified bot and a signed agent. Review Cloudflare's [signed agents](/bots/concepts/bot/signed-agents/) to determine how to identify your bot. +::: + +## Verified bot requirement + +For a bot to be verified, it must meet the following requirements: + +1. The bot must follow [verified bots policy](/bots/concepts/bot/verified-bots/policy/). +2. The bot must be verified using one of the following verification methods: + - [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/) + - [IP validation](/bots/reference/bot-verification/ip-validation/) + +Once Cloudflare approves a verified bot, it should appear on [Cloudflare Radar's bots and agents directory](https://radar.cloudflare.com/verified-bots). + +--- + +## Transient false negatives + +Once Cloudflare lists a bot as a verified bot, this entry is cached and may get delisted if no traffic is seen in the Cloudflare network coming from the bot for a defined period of time. + +It takes 24 hours for an inactive IP to be removed as a verified bot. + +A bot can remain unlisted until Cloudflare sees traffic being sourced from the bot. When the bot is revalidated, it is listed as a verified bot again. + +--- + +## Verification methods + +The bot must be verified using one of the following validation methods: + +- [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/) +- [IP validation](/bots/reference/bot-verification/ip-validation/) + +--- + +## Categories + +You can segment your verified bot traffic by its type and purpose by adding the Verified Bot Categories field `cf.verified_bot_category` as a filter criteria in [WAF Custom rules](/waf/custom-rules/), [Advanced Rate Limiting](/waf/rate-limiting-rules/), and Late Transform rules. + +:::note +The Verified Bot Categories field is not compatible with legacy Firewall rules. +::: + +| Name | String value | Example | +| -------------------------- | ---------------------------- | ----------------------------------------------------------------------- | +| Academic research | `Academic Research` | Library of Congress, TurnItInBot, Bibliothèque nationale de France | +| Accessibility | `Accessibility` | Accessible Web Bot | +| Advertising or marketing | `Advertising & Marketing` | Google Adsbot | +| Aggregators | `Aggregator` | Pinterest, Indeed Jobsbot | +| AI Assistant | `AI Assistant` | Perplexity-User, DuckAssistBot | +| AI Crawler | `AI Crawler` | Google Bard, ChatGPT bot | +| AI Search | `AI Search` | OAI-SearchBot | +| Archiver | `Archiver` | Internet Archive, CommonCrawl | +| Feed fetcher | `Feed Fetcher` | RSS or Podcast feed updaters | +| Monitoring or analytics | `Monitoring & Analytics` | Uptime Monitors | +| Page preview | `Page Preview` | Facebook, Slack, Twitter, or Discord Link Preview tools | +| Search engine crawler | `Search Engine Crawler` | Googlebot, Bingbot, Yandexbot, Baidubot | +| Search engine optimization | `Search Engine Optimization` | Google Lighthouse, GT Metrix, Pingdom, AddThis | +| Security | `Security` | Vulnerability Scanners, SSL Domain Control Validation (DCV) Check Tools | +| Social media marketing | `Social Media Marketing` | Brandwatch | +| Webhooks | `Webhooks` | Payment processors, WordPress Integration tools | +| Other | `Other` | | + +### Availability + +Verified Bot Categories is available on all plans. diff --git a/src/content/docs/bots/concepts/bot/verified-bots/overview.mdx b/src/content/docs/bots/concepts/bot/verified-bots/overview.mdx deleted file mode 100644 index 086e8d42a7382a9..000000000000000 --- a/src/content/docs/bots/concepts/bot/verified-bots/overview.mdx +++ /dev/null @@ -1,37 +0,0 @@ ---- -pcx_content_type: concept -title: Overview -sidebar: - order: 3 - label: Overview - ---- - -import { GlossaryTooltip } from "~/components" - -A **verified bot** is a bot which has been added to Cloudflare's list of verified bots. - -You can request for your bot to be added to Cloudflare's list of verified bots by filling out an [online application](https://dash.cloudflare.com/?to=/:account/configurations/verified-bots) in the Cloudflare dashboard. - -## Verified bot requirement - -For a bot to be verified, it must meet the following requirements: - -1. The bot must follow [verified bots policy](/bots/concepts/bot/verified-bots/policy/). -2. The bot must be verified using one of the following verification methods: - - [Web Bot Auth](/bots/concepts/bot/verified-bots/web-bot-auth/) - - [IP validation](/bots/concepts/bot/verified-bots/ip-validation/) - -Once Cloudflare verifies a bot, it should appear on the [Cloudflare Radar's list of verified bots](https://radar.cloudflare.com/verified-bots). - -:::note -Bot operators who prefer not to create a free Cloudflare account can do so using our [old form](https://docs.google.com/forms/d/e/1FAIpQLSdqYNuULEypMnp4i5pROSc-uP6x65Xub9svD27mb8JChA_-XA/viewform?usp=sf_link), but the waiting time is up to several weeks for verified bot requests to be evaluated. -::: - -## Transient false negatives - -Once Cloudflare lists a bot as a verified bot, this entry is cached and may get delisted if no traffic is seen in the Cloudflare network coming from the bot for a defined period of time. - -It takes 24 hours for an inactive IP to be removed as a verified bot. - -A bot can remain unlisted until Cloudflare sees traffic being sourced from the bot. When the bot is revalidated, it is listed as a verified bot again. diff --git a/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx b/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx index d3c4de6f258f3be..f385c3eda60ac3d 100644 --- a/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx +++ b/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx @@ -2,7 +2,7 @@ pcx_content_type: reference title: Verified bots policy sidebar: - order: 5 + order: 2 label: Policy --- @@ -13,11 +13,11 @@ In order to be listed by Cloudflare as a diff --git a/src/content/docs/bots/concepts/bot/verified-bots/ip-validation.mdx b/src/content/docs/bots/reference/bot-verification/ip-validation.mdx similarity index 92% rename from src/content/docs/bots/concepts/bot/verified-bots/ip-validation.mdx rename to src/content/docs/bots/reference/bot-verification/ip-validation.mdx index 92791b9070240e1..fddaf085d4c0ce6 100644 --- a/src/content/docs/bots/concepts/bot/verified-bots/ip-validation.mdx +++ b/src/content/docs/bots/reference/bot-verification/ip-validation.mdx @@ -2,14 +2,14 @@ pcx_content_type: concept title: IP validation sidebar: - order: 7 + order: 3 label: IP validation --- import { GlossaryTooltip, Steps } from "~/components" -The IP validation method aims to identify all of the IP addresses that a bot may use to send requests. +The IP validation method aims to identify all of the IP addresses that a bot may use to send requests. IP validation is only used as a verification method for [verified bots](/bots/concepts/bot/verified-bots/). Cloudflare can achieve this in two ways: diff --git a/src/content/docs/bots/concepts/bot/verified-bots/web-bot-auth.mdx b/src/content/docs/bots/reference/bot-verification/web-bot-auth.mdx similarity index 98% rename from src/content/docs/bots/concepts/bot/verified-bots/web-bot-auth.mdx rename to src/content/docs/bots/reference/bot-verification/web-bot-auth.mdx index d2950a0129d4b08..c6d50229050a587 100644 --- a/src/content/docs/bots/concepts/bot/verified-bots/web-bot-auth.mdx +++ b/src/content/docs/bots/reference/bot-verification/web-bot-auth.mdx @@ -2,14 +2,14 @@ pcx_content_type: concept title: Web Bot Auth sidebar: - order: 6 + order: 2 label: Web Bot Auth --- import { GlossaryTooltip, Steps } from "~/components" -Web Bot Auth is an authentication method that leverages cryptographic signatures in HTTP messages to verify that a request comes from an automated bot. +Web Bot Auth is an authentication method that leverages cryptographic signatures in HTTP messages to verify that a request comes from an automated bot. Web Bot Auth is used as a verification method for [verified bots](/bots/concepts/bot/verified-bots/) and [signed agents](/bots/concepts/bot/signed-agents/). It relies on two active IETF drafts: a [directory draft](https://datatracker.ietf.org/doc/html/draft-meunier-http-message-signatures-directory) allowing the crawler to share their public keys, and a [protocol draft](https://datatracker.ietf.org/doc/html/draft-meunier-web-bot-auth-architecture) defining how these keys should be used to attach crawler's identity to HTTP requests. diff --git a/src/content/docs/browser-rendering/reference/automatic-request-headers.mdx b/src/content/docs/browser-rendering/reference/automatic-request-headers.mdx index b04ded3188893d3..4f27c887d62747d 100644 --- a/src/content/docs/browser-rendering/reference/automatic-request-headers.mdx +++ b/src/content/docs/browser-rendering/reference/automatic-request-headers.mdx @@ -21,4 +21,4 @@ These headers are meant to ensure transparency and cannot be removed or overridd | `Signature-agent` | [The location of the bot public keys](https://web-bot-auth.cloudflare-browser-rendering-085.workers.dev), used to sign the request and verify it came from Cloudflare | | `Signature` and `Signature-input`| A digital signature, used to validate requests, as shown in [this architecture document](https://datatracker.ietf.org/doc/html/draft-meunier-web-bot-auth-architecture) | -The `Signature` headers use an authentication method called [Web Bot Auth](/bots/concepts/bot/verified-bots/web-bot-auth/). Web Bot Auth leverages cryptographic signatures in HTTP messages to verify that a request comes from an automated bot. To verify a request originated from Cloudflare Browser Rendering, use the keys found on [this directory](https://web-bot-auth.cloudflare-browser-rendering-085.workers.dev/.well-known/http-message-signatures-directory) to verify the `Signature` and `Signature-Input` found in the headers from the incoming request. A successful verification proves that the request originated from Cloudflare Browser Rendering and has not been tampered with in transit. +The `Signature` headers use an authentication method called [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/). Web Bot Auth leverages cryptographic signatures in HTTP messages to verify that a request comes from an automated bot. To verify a request originated from Cloudflare Browser Rendering, use the keys found on [this directory](https://web-bot-auth.cloudflare-browser-rendering-085.workers.dev/.well-known/http-message-signatures-directory) to verify the `Signature` and `Signature-Input` found in the headers from the incoming request. A successful verification proves that the request originated from Cloudflare Browser Rendering and has not been tampered with in transit. diff --git a/src/content/fields/index.yaml b/src/content/fields/index.yaml index beb58e63c26749b..9f162076d58e918 100644 --- a/src/content/fields/index.yaml +++ b/src/content/fields/index.yaml @@ -497,7 +497,7 @@ entries: keywords: [request, bots, client, visitor] summary: Provides the type and purpose of a verified bot. description: |- - For more details, refer to [Verified bot categories](/bots/concepts/bot/verified-bots/categories/). + For more details, refer to [Verified bot categories](/bots/concepts/bot/verified-bots/#categories). - name: cf.bot_management.score data_type: Number