[Bots] FAQ to Docs (#25821)

* bots general faq

* web bot auth faq

* remove faq and reorder sidebar

* redirect

* broken link

Author: patriciasantaana

public/__redirects

@@ -278,6 +278,7 @@
 /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
 /bots/concepts/bot/verified-bots/overview/  /bots/concepts/bot/verified-bots/ 301
+/bots/frequently-asked-questions/ /bots/ 301
 
 #browser-rendering
 /browser-rendering/get-started/browser-rendering-with-DO/ /browser-rendering/workers-bindings/browser-rendering-with-do/ 301

src/content/docs/bots/changelog.mdx

@@ -4,7 +4,7 @@ title: Changelog
 release_notes_file_name:
   - bots
 sidebar:
-  order: 13
+  order: 10
 ---
 
 import { ProductReleaseNotes } from "~/components";

src/content/docs/bots/concepts/bot-score.mdx

@@ -52,8 +52,6 @@ The Heuristics engine immediately gives automated requests a score of 1.
 
 <Render file="bots-ml" product="bots" />
 
-The ML engine produces scores 2 through 99.
-
 ### Anomaly detection
 
 <Render file="bots-ad" product="bots" />

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

@@ -83,6 +83,19 @@ Verified Bot Categories is available on all plans.
 | Webhooks                   | `Webhooks`                   | Payment processors, WordPress Integration tools                         |
 | Other                      | `Other`                      |                                                                         |
 
+
+### Known issues
+
+The Yandex bot is classified as a Verified Bot, but traffic may occasionally be blocked by a [WAF Managed Rule](/waf/managed-rules/) (such as the rule with ID `...f6cbb163`).
+
+This typically occurs when Yandex updates its source IP address ranges. The new IPs are temporarily unrecognized by the WAF Managed Rules until the updated Verified Bot IP list is fully synchronized across the Cloudflare network.
+
+To restore Yandex traffic, deploy a [WAF exception](/waf/managed-rules/waf-exceptions/) that temporarily skips the managed rule with ID `<RuleID id="2854e3f18ad946049e6d90ccf6cbb163" />` when a request is coming from the **Yandex IP** and the user-agent contains **Yandex**. This ensures that legitimate Yandex traffic bypasses the blocking rule without disabling security features for other traffic.
+
+You can also create a [WAF Custom Rule](/waf/custom-rules/skip/) with the _Skip_ action targeting the managed ruleset that contains the blocking rule. The rule expression should specifically match the request's Yandex IP and User-Agent.
+
+The issue is transient and will resolve automatically once the new Yandex IP addresses are fully propagated to Cloudflare's systems. This propagation typically takes up to 48 hours. If the bot remains blocked after 48 hours, contact [Cloudflare Support](/support/contacting-cloudflare-support/).
+
 ---
 
 ## Availability

src/content/docs/bots/frequently-asked-questions.mdx

@@ -25,6 +25,14 @@ Accounts with an Enterprise subscription but not the [Bot Management add-on](/bo
 
 <Render file="about-plan-considerations" product="bots" />
 
+### WAF custom rules 
+
+[WAF custom rules](/waf/custom-rules/) are executed before Super Bot Fight Mode.
+
+This order has a critical impact on traffic processing. If a WAF custom rule performs a terminating action (such as _Block_, _Managed Challenge_, or _JS Challenge_), the request will not be processed further, and the Super Bot Fight Mode configuration will not be evaluated.
+
+To configure exceptions to Super Bot Fight Mode, you should use the [_Skip_ action in your WAF custom rules](/waf/custom-rules/skip/). The _Skip_ action allows the request to bypass the Super Bot Fight Mode phase without terminating the request, enabling it to continue through the rest of the security stack.
+
 ## Enable Super Bot Fight Mode
 
 <Render file="sbfm-upgrade" product="bots" />

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

@@ -2,7 +2,7 @@
 title: Glossary
 pcx_content_type: glossary
 sidebar:
-  order: 12
+  order: 9
 
 ---
 

src/content/docs/bots/glossary.mdx

@@ -13,7 +13,11 @@ import { Render } from "~/components"
 Bot Management provides access to several [new variables](/ruleset-engine/rules-language/fields/reference/?field-category=Bots) within the expression builder of Ruleset Engine-based products such as [WAF custom rules](/waf/custom-rules/).
 
 - **Bot Score** (`cf.bot_management.score`): An integer between 1-99 that indicates [Cloudflare's level of certainty](/bots/concepts/bot-score/) that a request comes from a bot.
-- **Verified Bot** (`cf.bot_management.verified_bot`): A boolean value that is true if the request comes from a good bot, like Google or Bing. Most customers choose to allow this traffic. For more details, see [Traffic from known bots](/waf/troubleshooting/faq/#how-does-the-waf-handle-traffic-from-known-bots).
+- **Verified Bot** (`cf.bot_management.verified_bot`): A boolean value that indicates whether a request originates from a Cloudflare allowed bot. 
+  
+  Cloudflare maintains a large allowlist of good, automated bots (such as Google Search Engine and Pingdom) that perform beneficial tasks. Cloudflare identifies and verifies these bots primarily through reverse DNS validation, ensuring the source IP matches the requesting service. 
+  
+  We also use additional validation methods, including checking ASN blocks and public lists. If these methods are unavailable, Cloudflare utilizes internal data and machine learning to identify and verify legitimate IP addresses from good bots. Most customers choose to [allow this traffic](/ruleset-engine/rules-language/fields/reference/cf.bot_management.verified_bot/).
 - **Serves Static Resource** (`cf.bot_management.static_resource`): An identifier that matches [file extensions](/bots/additional-configurations/static-resources/) for many types of static resources. Use this variable if you send emails that retrieve static images.
 - **ja3Hash** (`cf.bot_management.ja3_hash`) and **ja4** (`cf.bot_management.ja4`): A [**JA3/JA4 fingerprint**](/bots/additional-configurations/ja3-ja4-fingerprint/) helps you profile specific SSL/TLS clients across different destination IPs, Ports, and X509 certificates.
 - **Bot Detection IDs** (`cf.bot_management.detection_ids`): List of IDs that correlate to the Bot Management heuristic detections made on a request (you can have multiple heuristic detections on the same request).