broken links

Author: patriciasantaana

src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx

@@ -10,7 +10,7 @@ import { GlossaryTooltip, Render } from "~/components"
 
 API Shield sequence custom rules use the configured API Shield <GlossaryTooltip term="session identifier">session identifier</GlossaryTooltip> to track the order of requests a user has made and the time between requests, and makes them available via [Cloudflare Rules](/rules). This allows you to write rules that match valid or invalid sequences.
 
-These rules are different from [cookie sequence rules](/bots/concepts/sequence-rules/) in a few ways: 
+These rules are different from [cookie sequence rules](/bots/additional-configurations/sequence-rules/) in a few ways: 
 
 - They only require an API Shield subscription.
 - They require [session identifiers](/api-shield/get-started/#session-identifiers) to be set in API Shield.

src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/index.mdx

@@ -80,7 +80,7 @@ This sample was generated using [Workers' Cloudflare Object script](/workers/exa
 
 To get more information about potential bot requests, use these JA3 and JA4 fingerprints in:
 
-- [Bot Analytics](/bots/bot-analytics/bm-subscription/)
+- [Bot Analytics](/bots/bot-analytics/#enterprise-bot-management)
 - [Security Events](/waf/analytics/security-events/) and [Security Analytics](/waf/analytics/security-analytics/)
 - [Analytics GraphQL API](/analytics/graphql-api/), specifically the **HTTP Requests** dataset
 - [Logs](/logs/reference/log-fields/zone/http_requests/)

src/content/docs/bots/additional-configurations/ja3-ja4-fingerprint/signals-intelligence.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 import { Render } from "~/components"
 
-For every available [JA4 fingerprint](/bots/concepts/ja3-ja4-fingerprint/), Bot Management customers can view how Cloudflare sees it on the Internet and what behavior we view with the fingerprint. This data can help you understand why a request is scored in a particular fashion or allow you to use the aggregate data in your own ML models, run in either [Cloudflare Workers](/workers/) or at the origin location.
+For every available [JA4 fingerprint](/bots/additional-configurations/ja3-ja4-fingerprint/), Bot Management customers can view how Cloudflare sees it on the Internet and what behavior we view with the fingerprint. This data can help you understand why a request is scored in a particular fashion or allow you to use the aggregate data in your own ML models, run in either [Cloudflare Workers](/workers/) or at the origin location.
 
 Specifically, for each JA4 fingerprint, you will be able to access the following information:
 

src/content/docs/bots/additional-configurations/sequence-rules.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 import { Render } from "~/components"
 
-<Render file="sequence-rules" product="bots" params={{ one: "Sequence rules", two: "/bots/concepts/sequence-rules/" }} />
+<Render file="sequence-rules" product="bots" params={{ one: "Sequence rules", two: "/bots/additional-configurations/sequence-rules/" }} />
 
 Sequence rules is currently in private beta. If you would like to be included in the beta, contact your account team.
 

src/content/docs/bots/bot-analytics.mdx

@@ -41,7 +41,7 @@ Business and Enterprise customers without Bot Management can use Bot Analytics t
 - Study recent attacks to find trends and detailed information
 - Learn more about Cloudflare’s detection engines with real data
 
-For more details and granular control over bot traffic, consider upgrading to [Bot Management for Enterprise](/bots/bot-analytics/bm-subscription/).
+For more details and granular control over bot traffic, consider upgrading to [Bot Management for Enterprise](/bots/bot-analytics/#enterprise-bot-management).
 
 ## Enterprise Bot Management
 
@@ -63,13 +63,13 @@ To use Bot Analytics, open the Cloudflare dashboard and select **Security** > **
 
 Bot Management customers can use Bot Analytics to:
 
-- Understand traffic during [your onboarding phase](/bots/get-started/bm-subscription/).
+- Understand traffic during [your onboarding phase](/bots/get-started/bot-management/).
 - Tune WAF custom rules to be effective but not overly aggressive.
 - Study recent attacks to find trends and detailed information.
 - Learn more about Cloudflare’s detection engines with real data.
 
 ### API
 
-Data from Bot Analytics is also available via the GraphQL API. You can access <GlossaryTooltip term="bot score">bot scores</GlossaryTooltip>, bot sources, <GlossaryTooltip term="bot tags" link="/bots/concepts/cloudflare-bot-tags/">bot tags</GlossaryTooltip>, and bot _decisions_ (_automated_, _likely automated_, etc.), and more.
+Data from Bot Analytics is also available via the GraphQL API. You can access <GlossaryTooltip term="bot score">bot scores</GlossaryTooltip>, bot sources, <GlossaryTooltip term="bot tags" link="/bots/concepts/bot-tags/">bot tags</GlossaryTooltip>, and bot _decisions_ (_automated_, _likely automated_, etc.), and more.
 
 Read the [GraphQL Analytics API documentation](/analytics/graphql-api/) for more information about GraphQL and basic querying.

src/content/docs/bots/concepts/feedback-loop.mdx

@@ -213,7 +213,7 @@ The instructions below apply to Enterprise subscription with Bot Management only
 
 After submitting a false positive, you can explicitly allow the traffic if you are confident that this traffic source cannot be used for abuse in the future. To allow traffic, you can create a WAF custom rule with a [Skip the remaining custom rules](/waf/custom-rules/skip/options/) action that matches the characteristics of your false positive report. We recommend any skip rule that you create uses the most narrow possible scope, including restricting the request methods and URIs that the expected traffic has access to, to limit potential abuse.
 
-* Allowing a **[JA3/JA4 fingerprint](/bots/concepts/ja3-ja4-fingerprint/)**:  If you want to allow access to a stable software client that does not come from a dedicated IP, you can do so by looking up the JA3 fingerprint(s) used by that client in the Bot Analytics dashboard, and creating a WAF custom rule to allow traffic based on that JA3 fingerprint. JA3 fingerprints will only match a client’s TLS library, so be cautious in looking for both overlap with other clients and with variation based on the operating system. <br/><br/>Cloudflare does not recommend relying on JA3 rules for mobile applications that may be abused. If you have questions about how to securely allow traffic from your mobile application, please contact your account team.
+* Allowing a **[JA3/JA4 fingerprint](/bots/additional-configurations/ja3-ja4-fingerprint/)**:  If you want to allow access to a stable software client that does not come from a dedicated IP, you can do so by looking up the JA3 fingerprint(s) used by that client in the Bot Analytics dashboard, and creating a WAF custom rule to allow traffic based on that JA3 fingerprint. JA3 fingerprints will only match a client’s TLS library, so be cautious in looking for both overlap with other clients and with variation based on the operating system. <br/><br/>Cloudflare does not recommend relying on JA3 rules for mobile applications that may be abused. If you have questions about how to securely allow traffic from your mobile application, please contact your account team.
 
 :::note
 

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

@@ -52,6 +52,6 @@ You can see bot-related actions by going to **Security** > **Events**. Any reque
 
 ## Limitations
 
-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/pro/).
+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/).
 
 Bot Fight Mode can still trigger if you have IP Access rules, but it cannot trigger if an IP Access rule matches the request. For example, the IP Access rule matches the connecting IP.

src/content/docs/bots/index.mdx

@@ -27,11 +27,11 @@ While Cloudflare offers several products that relate to bot traffic, this sectio
 
 ## Features
 
-<Feature header="Bot Fight Mode" href="/bots/get-started/free/">
+<Feature header="Bot Fight Mode" href="/bots/get-started/bot-fight-mode/">
 Detect and mitigate bot traffic on your domain. 
 </Feature>
 
-<Feature header="Super Bot Fight Mode" href="/bots/get-started/pro/">
+<Feature header="Super Bot Fight Mode" href="/bots/get-started/super-bot-fight-mode/">
 Identify traffic matching patterns of known bots, challenge or block bots, protect static resources, and view analytics to help you understand bot traffic using Super Bot Fight Mode. 
 </Feature>
 

src/content/docs/bots/plans/bm-subscription.mdx

@@ -23,7 +23,7 @@ import { Render } from "~/components"
 
 :::note
 
-Zones that have [Enterprise Bot Management](/bots/get-started/bm-subscription/) enabled will not see Bot Fight Mode or Super Bot Fight Mode under **Security** > **Bots**.
+Zones that have [Enterprise Bot Management](/bots/get-started/bot-management/) enabled will not see Bot Fight Mode or Super Bot Fight Mode under **Security** > **Bots**.
 :::
 
 ## How do I get started?

src/content/docs/bots/troubleshooting/bot-management-skips.mdx

@@ -8,7 +8,7 @@ sidebar:
 
 import { GlossaryTooltip } from "~/components"
 
-There are instances in which Bot Management does not run and certain fields, such as the [JA3/JA4 field](/bots/concepts/ja3-ja4-fingerprint/), are not populated because it has been determined that running Bot Management would not be necessary.
+There are instances in which Bot Management does not run and certain fields, such as the [JA3/JA4 field](/bots/additional-configurations/ja3-ja4-fingerprint/), are not populated because it has been determined that running Bot Management would not be necessary.
 
 Refer to <GlossaryTooltip term="bot score" link="/bots/concepts/bot-score/#not-computed">bot scores</GlossaryTooltip> for more information about why a request is not scored.