Skip to content

Commit bd84838

Browse files
verified bots availability and wording (#24773)
1 parent 6f3c10f commit bd84838

File tree

6 files changed

+38
-21
lines changed

6 files changed

+38
-21
lines changed

src/content/docs/bots/concepts/bot/index.mdx

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -19,15 +19,12 @@ Bots can be used for good (chatbots, search engine crawlers) or for evil (invent
1919
For more background, refer to [What is a bot?](https://www.cloudflare.com/learning/bots/what-is-a-bot/).
2020
:::
2121

22-
## Verified bots
22+
## Verified bots and signed agents
2323

2424
<Render file="verified-bots" product="bots" />
2525

26-
For more information, refer to [Verified bots](/bots/concepts/bot/verified-bots/).
27-
2826
:::note
29-
30-
The method for allowing or blocking verified bots depends on [your plan](/bots/get-started/).
27+
The method for allowing or blocking verified bots depends on [your plan](/bots/concepts/bot/verified-bots/#availability).
3128
:::
3229

3330
## AI bots

src/content/docs/bots/concepts/bot/verified-bots/index.mdx

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -55,10 +55,14 @@ The bot must be verified using one of the following validation methods:
5555

5656
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.
5757

58-
:::note
58+
:::caution
5959
The Verified Bot Categories field is not compatible with legacy Firewall rules.
6060
:::
6161

62+
:::note
63+
Verified Bot Categories is available on all plans.
64+
:::
65+
6266
| Name | String value | Example |
6367
| -------------------------- | ---------------------------- | ----------------------------------------------------------------------- |
6468
| Academic research | `Academic Research` | Library of Congress, TurnItInBot, Bibliothèque nationale de France |
@@ -79,6 +83,10 @@ The Verified Bot Categories field is not compatible with legacy Firewall rules.
7983
| Webhooks | `Webhooks` | Payment processors, WordPress Integration tools |
8084
| Other | `Other` | |
8185

82-
### Availability
86+
---
8387

84-
Verified Bot Categories is available on all plans.
88+
## Availability
89+
90+
Verified bots are excluded by default when [Bot Fight Mode](/bots/get-started/bot-fight-mode/) is enabled to block definite bots.
91+
92+
[Super Bot Fight Mode](/bots/get-started/super-bot-fight-mode/) and [Enterprise Bot Management](/bots/get-started/bot-management/) customers have the option to block or allow verified bots.

src/content/docs/bots/get-started/bot-fight-mode.mdx

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,8 @@ Bot Fight Mode is a simple, free product that helps detect and mitigate bot traf
2121

2222
<Render file="about-plan-considerations" product="bots" />
2323

24+
---
25+
2426
## Enable Bot Fight Mode
2527

2628
To start using Bot Fight Mode:
@@ -46,6 +48,8 @@ To start using Bot Fight Mode:
4648

4749
<Render file="sbfm-upgrade" product="bots" />
4850

51+
---
52+
4953
## Disable Bot Fight Mode
5054

5155
If you find that **Bot Fight Mode** is causing problems with your application traffic, you may want to disable it.
@@ -71,6 +75,8 @@ To disable Bot Fight Mode:
7175
</TabItem>
7276
</Tabs>
7377

78+
---
79+
7480
## Block AI bots
7581

7682
Refer to [Block AI bots](/bots/additional-configurations/block-ai-bots/).
@@ -80,10 +86,14 @@ Refer to [Block AI bots](/bots/additional-configurations/block-ai-bots/).
8086
You can view blocked AI bot traffic via [Security Analytics](/waf/analytics/security-analytics/).
8187
:::
8288

89+
---
90+
8391
## Visibility
8492

8593
You can see bot-related actions by going to **Security** > **Events**. Any requests challenged by this product will be labeled **Bot Fight Mode** in the **Service** field. This allows you to observe, analyze, and follow trends in your bot traffic over time.
8694

95+
---
96+
8797
## Limitations
8898

8999
You cannot bypass or skip Bot Fight Mode using the _Skip_ action in WAF custom rules or using Page Rules. _Skip_, _Bypass_, and _Allow_ actions apply to rules or rulesets running on the [Ruleset Engine](/ruleset-engine/). While Super Bot Fight Mode rules are implemented in the Ruleset Engine, Bot Fight Mode checks are not. This is why you can skip Super Bot Fight Mode, but not Bot Fight Mode. If you need to skip Bot Fight Mode, consider using [Super Bot Fight Mode](/bots/get-started/super-bot-fight-mode/).

src/content/docs/bots/get-started/bot-management.mdx

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,8 @@ This Enterprise product provides the most flexibility to customers by:
1919
- Allowing customers to take action on this score with [WAF custom rules](/waf/custom-rules/) or [`Workers`](/workers/runtime-apis/request/#incomingrequestcfproperties).
2020
- Allowing customers to view this score in Bot Analytics or Logs.
2121

22+
---
23+
2224
## Enable Bot Management for Enterprise
2325

2426
Bot Management is automatically enabled for Enterprise zones entitled with the add-on.
@@ -53,6 +55,8 @@ Bot Management is automatically enabled for Enterprise zones entitled with the a
5355
If you are not seeing Bot Management enabled on your zone or if you still see **Add Bot Management** on the Cloudflare dashboard, contact your account team for the proper entitlements.
5456
:::
5557

58+
---
59+
5660
## Setup
5761

5862
Cloudflare recommends that you deploy the following basic settings and customize them according to the traffic in your zone.
@@ -69,12 +73,6 @@ Refer to [Block AI bots](/bots/additional-configurations/block-ai-bots/).
6973
You can view blocked AI bot traffic via [Security Analytics](/waf/analytics/security-analytics/).
7074
:::
7175

72-
### Enable JavaScript detections
73-
74-
Enabling [JavaScript detections](/bots/additional-configurations/javascript-detections/) validates that the browser can run JavaScript, and is stored in the `cf.bot_management.js_detection.passed` variable.
75-
76-
<Render file="javascript-detections-enable" params={{ one: "Bot Management" }} product="cloudflare-challenges" />
77-
7876
### Deploy default templates
7977

8078
Cloudflare has [default templates](https://dash.cloudflare.com/?to=/:account/:zone/security/security-rules?template=bot_traffic) for definite bots, which have a [bot score](/bots/concepts/bot-score/) of 1, and likely bots which have a bot score of 2 to 29. In our templates, Cloudflare recommends to allow verified bots such as Google SEO Crawler and access to cached static resources.

src/content/docs/bots/get-started/super-bot-fight-mode.mdx

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -64,10 +64,10 @@ To start using Super Bot Fight Mode:
6464
If your organization also uses [Cloudflare Tunnel](/cloudflare-one/connections/connect-networks/), keep **Definitely Automated** set to **Allow**. Otherwise, tunnels might fail with a `websocket: bad handshake` error.
6565
:::
6666

67-
### Conditions
68-
6967
<Render file="flexible-sbfm" product="bots" />
7068

69+
---
70+
7171
## Disable Super Bot Fight Mode
7272

7373
If you find that **Super Bot Fight Mode** is causing problems with your application traffic, you may want to disable it.
@@ -99,6 +99,8 @@ To disable Super Bot Fight Mode:
9999

100100
<Render file="flexible-sbfm" product="bots" />
101101

102+
---
103+
102104
## Block AI bots
103105

104106
Refer to [Block AI bots](/bots/additional-configurations/block-ai-bots/).
@@ -108,6 +110,8 @@ Refer to [Block AI bots](/bots/additional-configurations/block-ai-bots/).
108110
You can view blocked AI bot traffic via [Security Analytics](/waf/analytics/security-analytics/).
109111
:::
110112

113+
---
114+
111115
## Analytics
112116

113117
### Bot Report
@@ -122,6 +126,8 @@ To access the **Bot Report**, go to **Security** > **Bots**. If you see a double
122126

123127
You can see bot-related actions by going to **Security** > **Events**. Any requests challenged by this product will be labeled **Super Bot Fight Mode** in the **Service** field. This allows you to observe, analyze, and follow trends in your bot traffic over time.
124128

129+
---
130+
125131
## Ruleset Engine
126132

127133
Super Bot Fight Mode runs during the `http_request_sbfm` phase of the [Ruleset Engine](/ruleset-engine/about/phases/).

src/content/partials/bots/verified-bots.mdx

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,8 @@
33

44
---
55

6-
import { GlossaryTooltip } from "~/components"
6+
Cloudflare maintains an internal directory of [verified bot](/bots/concepts/bot/verified-bots/) and [signed agents](/bots/concepts/bot/signed-agents/) that are associated with search engine optimization (SEO), website monitoring, and more.
77

8-
Cloudflare maintains an internal list of <GlossaryTooltip term="verified bot">verified bots</GlossaryTooltip> that are associated with search engine optimization (SEO), website monitoring, and more.
8+
You can use this directory to prevent any bot protection measures from impacting otherwise helpful bots and agents, such as search crawlers.
99

10-
You can use this list to prevent any bot protection measures from impacting otherwise helpful bots, such as search crawlers.
11-
12-
For a partial list of verified bots, refer to [Cloudflare Radar](https://radar.cloudflare.com/verified-bots).
10+
For a partial list of verified bots and signed agents, refer to [Cloudflare Radar](https://radar.cloudflare.com/verified-bots).

0 commit comments

Comments
 (0)