Skip to content

[Bots] New dash #23375

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Jul 2, 2025
Merged

[Bots] New dash #23375

Show file tree
Hide file tree
Changes from 5 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
2c5e7b3
new dash
patriciasantaana Jul 1, 2025
5f4257e
missing commas
patriciasantaana Jul 1, 2025
43c8866
fix faq
patriciasantaana Jul 1, 2025
ca65d28
toggle language
patriciasantaana Jul 1, 2025
485a137
edits
patriciasantaana Jul 1, 2025
93fe6e7
Merge branch 'production' into patricia/pcx17423-bots-newdash
patriciasantaana Jul 2, 2025
8c0e5aa
edits
patriciasantaana Jul 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 20 additions & 12 deletions src/content/docs/bots/additional-configurations/ai-labyrinth.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,22 +5,30 @@ sidebar:
order: 7
---

import { Render, Tabs, TabItem } from "~/components"
import { Render, Tabs, TabItem, Steps } from "~/components"

The AI Labyrinth adds invisible links on your webpage with specific `Nofollow` tags to block AI crawlers that do not adhere to the recommended guidelines and crawl without permission. AI crawlers that scrape your website content without permission will be stuck in a maze of never-ending links, and their details are recorded and used by all Cloudflare customers who choose to block [AI bots](/bots/concepts/bot/#ai-bots).

These links do not impact your search engine optimization (SEO) or your website's appearance, and are only seen by bots. AI bots that respect no-crawl instructions will safely ignore this honeypot.

To enable [AI Labyrinth](/bots/additional-configurations/ai-labyrinth) based on your plan:
To enable [AI Labyrinth](/bots/additional-configurations/ai-labyrinth):

<Tabs>
<TabItem label="Bot Fight Mode">
<Render file="ai-labyrinth-enable" params={{ one: "Bot Fight Mode" }} />
</TabItem>
<TabItem label="Super Bot Fight Mode">
<Render file="ai-labyrinth-enable" params={{ one: "Super Bot Fight Mode" }} />
</TabItem>
<TabItem label="Bot Management for Enterprise">
<Render file="ai-labyrinth-enable" params={{ one: "Bot Management" }} />
</TabItem>
<Tabs syncKey="dashNewNav">
<TabItem label="Old dashboard">
<Steps>
<Render
file="ai-labyrinth-enable"
params={{ one: "Bot Fight Mode" }}
/>
</Steps>
</TabItem>
<TabItem label="New dashboard" icon="rocket">
<Steps>
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
2. Go to **Security** > **Settings**.
3. Filter by **Bot traffic**.
4. Go to **AI Labyrinth**.
4. Switch the toggle to **On**.
</Steps>
</TabItem>
</Tabs>
6 changes: 4 additions & 2 deletions src/content/docs/bots/additional-configurations/block-ai-bots.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ sidebar:
label: Block AI Bots
---

import { Render, Tabs, TabItem } from "~/components"
import { Render, Steps } from "~/components"

:::note[Block AI bots availability]
Note that **Block AI bots** feature is only available in the new application security dashboard (beta).
Expand All @@ -18,7 +18,8 @@ You can choose to block AI bots by activating **Block AI bots**. Activating this

To block [AI bots](/bots/concepts/bot/#ai-bots):

1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
<Steps>
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
2. Go to **Security** > **Settings**.
3. Filter by **Bot traffic**.
4. Go to **Block AI bots**.
Expand All @@ -27,5 +28,6 @@ To block [AI bots](/bots/concepts/bot/#ai-bots):
- **Block on all pages**: Use this option if you wish to block AI bots on all your pages.
- **Do not block (off)**: Use this option if you wish to allow AI bots on all your pages.
6. Select **Save** to save your configuration.
</Steps>

To block individual AI crawlers (rather than blocking all crawlers), use [AI Audit](/ai-audit/).
81 changes: 64 additions & 17 deletions src/content/docs/bots/additional-configurations/detection-ids.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ sidebar:
order: 2
---

import { Render } from "~/components"
import { Render, Tabs, TabItem, Steps } from "~/components"

<Render file="detection-ids" />

Expand Down Expand Up @@ -40,26 +40,43 @@ You can create or edit existing Logpush jobs to include the new Bot Detection ID

### Via the Cloudflare dashboard

1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
<Steps>
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
2. Go to **Analytics & Logs** > **Logs**.
3. Select **Add Logpush Job**.
4. Select **HTTP Requests** as the dataset.
5. Select **BotDetectionIDs** under the General data field category.
6. Select and enter the destination information.
7. Prove the ownership.
8. Select **Save**.
</Steps>

### Via the API

[Update your logpush job](/logs/reference/log-output-options/) by adding `BotDetectionIDs` to the `output_options:` parameters.

## Create or edit an expression

1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
2. Go to **Security** > **Bots**, apply filters and select **Create custom rule** to create a [custom rule](/waf/custom-rules/create-dashboard/) based on those filters.
- Alternatively, if you already created a custom rule, go to **Security** > **WAF** > **Custom rules** and edit the expression of an existing custom rule.
3. Use the `cf.bot_management.detection_ids` field in the rule expression.
4. Select **Save**.
<Tabs syncKey="dashNewNav">
<TabItem label="Old dashboard">
<Steps>
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
2. Go to **Security** > **Bots**, apply filters and select **Create custom rule** to create a [custom rule](/waf/custom-rules/create-dashboard/) based on those filters. Alternatively, if you already created a custom rule, go to **Security** > **WAF** > **Custom rules** and edit the expression of an existing custom rule.
3. Use the `cf.bot_management.detection_ids` field in the rule expression.
4. Select **Save**.
</Steps>
</TabItem>
<TabItem label="New dashboard" icon="rocket">
<Steps>
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
2. Go to **Security** > **Analytics**.
3. Apply filters and select **Create custom security rule** to create a custom rule based on your filters. Alternatively, if you have already created a custom rule, you can go to the existing rule in **Security** > **Security rules** and edit the expression based on your filters.
4. Use the `cf.bot_management.detection_ids` field in the rule expression.
5. Select **Deploy**.
</Steps>
</TabItem>
</Tabs>


## Use cases

Expand Down Expand Up @@ -92,11 +109,26 @@ Cloudflare's [Managed Challenge](/cloudflare-challenges/challenge-types/challeng

To access account takeover detections:

1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
2. Go to **Security** > **WAF**.
3. Under **Custom Rules**, select **Create rule**.
4. Fill out the form using **Bot Detection IDs** along with other necessary information.
5. Select **Save as draft** to return to it later, or **Deploy** to deploy the rule.
<Tabs syncKey="dashNewNav">
<TabItem label="Old dashboard">
<Steps>
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
2. Go to **Security** > **WAF**.
3. Under **Custom Rules**, select **Create rule**.
4. Fill out the form using **Bot Detection IDs** along with other necessary information.
5. Select **Save as draft** to return to it later, or **Deploy** to deploy the rule.
</Steps>
</TabItem>
<TabItem label="New dashboard" icon="rocket">
<Steps>
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
2. Go to **Security** > **Security rules**.
3. Select **Create rule** and choose **Custom rule**.
4. Fill out the form using **Bot Detection IDs** along with other necessary information.
5. Select **Save as draft** to return to it later, or **Deploy** to deploy the rule.
</Steps>
</TabItem>
</Tabs>

```js title="Rule example"

Expand All @@ -109,11 +141,26 @@ Rate limiting rules can limit the number of logins from a particular IP, JA4 Fin

To use rate limiting rules with account takeover detections:

1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
2. Go to ***Security** > **WAF**.
3. Under **Rate limiting rules**, select **Create rule**.
4. Fill out the form using the **Custom expression builder** and `cf.bot_management_detection_ids` along with other necessary information.
5. Select **Save as draft** to return to it later, or **Deploy** to deploy the rule.
<Tabs syncKey="dashNewNav">
<TabItem label="Old dashboard">
<Steps>
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
2. Go to **Security** > **WAF**.
3. Under **Rate limiting rules**, select **Create rule**.
4. Fill out the form using the **Custom expression builder** and `cf.bot_management_detection_ids` along with other necessary information.
5. Select **Save as draft** to return to it later, or **Deploy** to deploy the rule.
</Steps>
</TabItem>
<TabItem label="New dashboard" icon="rocket">
<Steps>
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
2. Go to **Security** > **Security rules**.
3. Select **Create rule** and choose **Rate limiting rule**.
4. Fill out the form using the **Custom expression builder** and `cf.bot_management_detection_ids` along with other necessary information.
5. Select **Save as draft** to return to it later, or **Deploy** to deploy the rule.
</Steps>
</TabItem>
</Tabs>

:::note
The rule can be enhanced with Leaked Credential Checks. Refer to the [WAF documentation](/waf/detections/leaked-credentials/) for more information on how to include leaked credentials and account takeover detections in a rate limiting rule.
Expand Down
43 changes: 21 additions & 22 deletions src/content/docs/bots/additional-configurations/managed-robots-txt.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ sidebar:
label: Managed robots.txt
---

import { Render, Tabs, TabItem } from "~/components";
import { Render, Tabs, TabItem, Steps } from "~/components";

Protect your website or application from AI crawlers by implementing a `robots.txt` file on your domain to direct AI bot operators on what content they can and cannot scrape for AI model training.

Expand Down Expand Up @@ -45,27 +45,26 @@ If your website does not have a `robots.txt` file, Cloudflare creates a new file

## Implementation

To implement a `robots.txt` file on your domain based on your plan:

<Tabs>
<TabItem label="Bot Fight Mode">
<Render
file="enable-managed-robots-txt"
params={{ one: "Bot Fight Mode" }}
/>
</TabItem>
<TabItem label="Super Bot Fight Mode">
<Render
file="enable-managed-robots-txt"
params={{ one: "Super Bot Fight Mode" }}
/>
</TabItem>
<TabItem label="Bot Management for Enterprise">
<Render
file="enable-managed-robots-txt"
params={{ one: "Bot Management" }}
/>
</TabItem>
To implement a `robots.txt` file on your domain:

<Tabs syncKey="dashNewNav">
<TabItem label="Old dashboard">
<Steps>
<Render
file="enable-managed-robots-txt"
params={{ one: "Bot Fight Mode" }}
/>
</Steps>
</TabItem>
<TabItem label="New dashboard" icon="rocket">
<Steps>
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
2. Go to **Security** > **Settings**.
3. Filter by **Bot traffic**.
4. Go to **Managed robots.txt**.
5. Switch the toggle to **On**.
</Steps>
</TabItem>
</Tabs>

## Availability
Expand Down
26 changes: 14 additions & 12 deletions src/content/docs/bots/additional-configurations/sequence-rules.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ sidebar:
order: 4
---

import { Render } from "~/components"
import { Render, Steps } from "~/components"

<Render file="sequence-rules" product="bots" params={{ one: "Sequence rules", two: "/bots/additional-configurations/sequence-rules/" }} />

Expand All @@ -20,14 +20,17 @@ Sequence rules is currently in private beta. If you would like to be included in

## Enable sequence rules via the API

<Steps>
1. [Create an API token](/fundamentals/api/get-started/create-token/) if you do not already have one. The API token must include the _Zone_ > _Fraud Detection_ > _Edit_ permission.
2. [Get the zone ID](/fundamentals/account/find-account-and-zone-ids/) for the zone(s) where you want to enable sequence rules.
3. [Add the endpoints](/api-shield/management-and-monitoring/) that you want to track in your sequence rules using API Shield's Endpoint Management and make note of the short ID.
:::note

The short ID will not be visible until our account team has enabled this feature for you.
:::
4. Enable the sequence cookie by adding your API token and zone ID to the following API call.
</Steps>

:::note

The short ID will not be visible until our account team has enabled this feature for you.
:::

```bash title="API call"
curl --request PUT \
Expand All @@ -40,7 +43,6 @@ https://api.cloudflare.com/client/v4/zones/{zone_id}/fraud_detection/sequence_co
5. Use the expression editor to write sequence or timing based rules via [custom rules](/waf/custom-rules/), [rate limiting rules](/waf/rate-limiting-rules/), or [transform rules](/rules/transform/). You can put these rules in log only mode to monitor.

:::note

When you enable sequence rules, Cloudflare will start setting cookies for all requests that match your endpoints.
:::

Expand Down Expand Up @@ -92,16 +94,16 @@ Disabling sequence rules will stop the rules fields from being populated. If you

To disable sequence rules:

<Steps>
1. [Create an API token](/fundamentals/api/get-started/create-token/) if you do not already have one. The API token must include the _Zone_ > _Fraud Detection_ > _Edit_ permission.
2. [Get the zone ID](/fundamentals/account/find-account-and-zone-ids/) for the zone(s) where you want to enable sequence rules.
3. [Add the endpoints](/api-shield/management-and-monitoring/) that you want to track in your sequence rules using API Shield's Endpoint Management and make note of the short ID.

:::note

The short ID will not be visible until our account team has enabled this feature for you.
:::

4. Disable the sequence cookie using your API token, zone ID, and by setting `enabled` to `false` on the following API call.
</Steps>

:::note
The short ID will not be visible until our account team has enabled this feature for you.
:::

```bash title="API call"
curl --request PUT https://api.cloudflare.com/client/v4/zones/{zone_id}/fraud_detection/sequence_cookies \
Expand Down
23 changes: 19 additions & 4 deletions src/content/docs/bots/additional-configurations/static-resources.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ sidebar:

---

import { GlossaryTooltip, Render } from "~/components"
import { Render, Tabs, TabItem, Steps, GlossaryTooltip } from "~/components";

Pro, Business, and Enterprise customers can use Cloudflare's bot solutions to protect their <GlossaryTooltip term="static content">static resources</GlossaryTooltip> from bots.

Expand All @@ -19,9 +19,24 @@ If you enable static resource protection, you may block good bots — like mail

To enable this feature as a Pro or Business customer or an Enterprise customer without Bot Management:

1. Go to **Security** > **Bots**.
2. Select **Configure Super Bot Fight Mode**.
3. For **Static resource protection**, select **On**.
<Tabs syncKey="dashNewNav">
<TabItem label="Old dashboard">
<Steps>
1. Go to **Security** > **Bots**.
2. Select **Configure Super Bot Fight Mode**.
3. For **Static resource protection**, select **On**.
</Steps>
</TabItem>
<TabItem label="New dashboard" icon="rocket">
<Steps>
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
2. Go to **Security** > **Settings**.
3. Filter by **Bot traffic**.
4. Go to **Super Bot Fight Mode**.
5. Under **Configurations**, select the edit icon for **Static resource protection** to switch the toggle to **On**.
</Steps>
</TabItem>
</Tabs>

:::caution

Expand Down
12 changes: 10 additions & 2 deletions src/content/docs/bots/bot-analytics.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,11 @@ Business and Enterprise customers without Bot Management can use **Bot Analytics

### Access

To use Bot Analytics, open the Cloudflare dashboard and select **Security** > **Bots**.
You can access Bot Analytics by going to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and selecting your account and domain.

Old dashboard: **Security** > **Bots**.

New dashboard: **Security** > **Analytics** > **Bot analysis**.

![View Bot Analytics in the Cloudflare dashboard. For more details, keep reading.](~/assets/images/bots/bot-analytics-dashboard-biz.png)

Expand Down Expand Up @@ -49,7 +53,11 @@ Enterprise customers with Bot Management can use **Bot Analytics** to dynamicall

### Access

To use Bot Analytics, open the Cloudflare dashboard and select **Security** > **Bots**.
You can access Bot Analytics by going to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and selecting your account and domain.

Old dashboard: **Security** > **Bots**.

New dashboard: **Security** > **Analytics** > **Bot analysis**.

![View Bot Analytics in the Cloudflare dashboard. For more details, keep reading.](~/assets/images/bots/bot-analytics-dashboard-ent.png)

Expand Down
2 changes: 1 addition & 1 deletion src/content/docs/bots/concepts/bot/verified-bots/policy.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ In order to be listed by Cloudflare as a <GlossaryTooltip term="verified bot" li

### Minimum Traffic

A bot or proxy must have a minimum amount of traffic for Cloudflare to be able find it in the sampled data. The minimum traffic should have more than 1000 requests per day across multiple domains.
A bot or proxy 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 1000 requests per day across multiple domains.

### Minimum Zones

Expand Down
Loading
Loading