[WAF, other] Fix broken anchors (#26194)

pedrosousa · web-flow · commit b9d3a43ddb5a · 2025-10-31T10:10:06.000Z
diff --git a/public/__redirects b/public/__redirects
@@ -667,7 +667,7 @@
 /fundamentals/global-configurations/ /fundamentals/ 301
 /fundamentals/customizations/ /fundamentals/ 301
 /fundamentals/security/cybersafe/ /fundamentals/reference/policies-compliances/cybersafe/ 301
-/fundamentals/security/challenge-passage/ /cloudflare-challenges/challenge-types/challenge-pages/#challenge-passage 301
+/fundamentals/security/challenge-passage/ /cloudflare-challenges/challenge-types/challenge-pages/challenge-passage/ 301
 /fundamentals/glossary/ /fundamentals/reference/glossary/ 301
 /fundamentals/account-and-billing/login/ /fundamentals/user-profiles/login/ 301
 /fundamentals/account-and-billing/account-maintenance/delete-account/ /fundamentals/user-profiles/delete-account/ 301
@@ -782,7 +782,7 @@
 /fundamentals/concepts/the-internet/ https://www.cloudflare.com/learning/network-layer/how-does-the-internet-work/ 301
 /fundamentals/concepts/free-plan/ /billing/ 301
 /fundamentals/setup/manage-domains/connect-your-domain/ /fundamentals/manage-domains/add-site/ 301
-/fundamentals/security/cloudflare-challenges/challenge-passage/ /cloudflare-challenges/challenge-types/challenge-pages/#challenge-passage 301
+/fundamentals/security/cloudflare-challenges/challenge-passage/ /cloudflare-challenges/challenge-types/challenge-pages/challenge-passage/ 301
 /fundamentals/security/cloudflare-challenges/challenge-solve-rate/ /cloudflare-challenges/reference/challenge-solve-rate/ 301
 /fundamentals/security/cloudflare-challenges/challenge-solve-issues/ /cloudflare-challenges/troubleshooting/challenge-solve-issues/ 301
 /fundamentals/security/cloudflare-challenges/ /cloudflare-challenges/ 301
@@ -1676,7 +1676,7 @@
 /waf/analytics/security-events/paid-plans/ /waf/analytics/security-events/ 301
 /waf/analytics/security-events/additional-information/ /waf/tools/validation-checks/ 301
 /waf/reference/cloudflare-challenges/ /cloudflare-challenges/ 301
-/waf/tools/challenge-passage/ /cloudflare-challenges/challenge-types/challenge-pages/#challenge-passage 301
+/waf/tools/challenge-passage/ /cloudflare-challenges/challenge-types/challenge-pages/challenge-passage/ 301
 /waf/reference/migration-guides/ /waf/reference/legacy/ 301
 /waf/reference/migration-guides/old-rate-limiting-deprecation/ /waf/reference/legacy/old-rate-limiting/upgrade/ 301
 /waf/reference/migration-guides/waf-managed-rules-migration/ /waf/reference/legacy/old-waf-managed-rules/upgrade/ 301
diff --git a/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/verify-ai-crawler.mdx b/src/content/docs/ai-crawl-control/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/verify-ai-crawler.mdx
@@ -15,7 +15,7 @@ C --> D[Crawl pages]
 classDef highlight fill:#F6821F,color:white
 ```
 
-Once you have connected your Stripe account, set up your AI crawler as a [verified bot](/bots/concepts/bot/#verified-bots).
+Once you have connected your Stripe account, set up your AI crawler as a [verified bot](/bots/concepts/bot/verified-bots/).
 
 ## Content access restriction
 
diff --git a/src/content/docs/api-shield/changelog.mdx b/src/content/docs/api-shield/changelog.mdx
@@ -69,7 +69,7 @@ Customers can now route requests to different back-end services through [API Rou
 
 **Use JWT claims in Advanced Rate Limiting, Transform Rules, and as session IDs**
 
-Customers can now use the fields inside [JSON Web Tokens (known as claims)](/api-shield/security/jwt-validation/transform-rules/#enhance-transform-rules-with-jwt-claims) as [session identifiers in API Shield](/api-shield/get-started/#session-identifiers), to count values in [Advanced Rate Limiting](/waf/rate-limiting-rules/), and to send on useful information in [Transform Rules](/rules/transform/#transform-rules).
+Customers can now use the fields inside [JSON Web Tokens (known as claims)](/api-shield/security/jwt-validation/transform-rules/#enhance-transform-rules-with-jwt-claims) as [session identifiers in API Shield](/api-shield/get-started/#session-identifiers), to count values in [Advanced Rate Limiting](/waf/rate-limiting-rules/), and to send on useful information in [Transform Rules](/rules/transform/).
 
 ## 2024-04-30
 
@@ -81,4 +81,4 @@ Customers can now build [Sequence mitigation](/api-shield/security/sequence-miti
 
 **Endpoint management supports hostname variables**
 
-Customers can now save endpoints in [Endpoint management](/api-shield/management-and-monitoring/) that contain variables in the hostname. Hostname variables are supported across all product features.
+Customers can now save endpoints in [Endpoint management](/api-shield/management-and-monitoring/) that contain variables in the hostname. Hostname variables are supported across all product features.
diff --git a/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx b/src/content/docs/bots/concepts/bot/verified-bots/policy.mdx
@@ -9,7 +9,7 @@ sidebar:
 
 import { GlossaryTooltip } from "~/components"
 
-In order to be listed by Cloudflare as a <GlossaryTooltip term="verified bot" link="/bots/concepts/bot/#verified-bots">verified bot</GlossaryTooltip>, your <GlossaryTooltip term="bot">bot</GlossaryTooltip> 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.
+In order to be listed by Cloudflare as a <GlossaryTooltip term="verified bot" link="/bots/concepts/bot/verified-bots/">verified bot</GlossaryTooltip>, your <GlossaryTooltip term="bot">bot</GlossaryTooltip> 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.
 
 ## Bot policy
 
diff --git a/src/content/docs/bots/get-started/bot-management.mdx b/src/content/docs/bots/get-started/bot-management.mdx
@@ -43,7 +43,7 @@ Bot Management is automatically enabled for Enterprise zones entitled with the a
       3. Go to **Bot management**.
       4. Turn **Bot management** on.
       5. Choose how your domain should respond to various types of traffic by selecting the associated edit icon.
-            - For more details on verified bots, refer to [Verified Bots](/bots/concepts/bot/#verified-bots).
+            - For more details on verified bots, refer to [Verified Bots](/bots/concepts/bot/verified-bots/).
             - For more details on supported file types, refer to [Static resource protection](/bots/additional-configurations/static-resources/).
             - For more details on invisible code injection, refer to [JavaScript detections](/bots/additional-configurations/javascript-detections/).
             - For more details on WordPress optimization, refer to [Super Bot Fight Mode for WordPress](/bots/troubleshooting/wordpress-loopback-issue/).
diff --git a/src/content/docs/bots/get-started/super-bot-fight-mode.mdx b/src/content/docs/bots/get-started/super-bot-fight-mode.mdx
@@ -47,7 +47,7 @@ To start using Super Bot Fight Mode:
       3. Select **Configure Super Bot Fight Mode**.
       4. Choose how your domain should respond to various types of traffic:
 
-          - For more details on verified bots, refer to [Verified Bots](/bots/concepts/bot/#verified-bots).
+          - For more details on verified bots, refer to [Verified Bots](/bots/concepts/bot/verified-bots/).
           - For more details on supported file types, refer to [Static resource protection](/bots/additional-configurations/static-resources/).
           - For more details on invisible code injection, refer to [JavaScript detections](/bots/additional-configurations/javascript-detections/).
     </Steps>
@@ -62,7 +62,7 @@ To start using Super Bot Fight Mode:
       4. Turn **Super Bot Fight Mode** on.
       5. Choose how your domain should respond to various types of traffic by selecting the associated edit icon:
 
-          - For more details on verified bots, refer to [Verified Bots](/bots/concepts/bot/#verified-bots).
+          - For more details on verified bots, refer to [Verified Bots](/bots/concepts/bot/verified-bots/).
           - For more details on supported file types, refer to [Static resource protection](/bots/additional-configurations/static-resources/).
           - For more details on invisible code injection, refer to [JavaScript detections](/bots/additional-configurations/javascript-detections/).
           - For more details on WordPress optimization, refer to [Super Bot Fight Mode for WordPress](/bots/troubleshooting/wordpress-loopback-issue/).
diff --git a/src/content/docs/fundamentals/performance/improve-seo.mdx b/src/content/docs/fundamentals/performance/improve-seo.mdx
@@ -47,7 +47,7 @@ If you notice SEO issues, make sure your:
 
 * [WAF custom rules](/waf/troubleshooting/faq/#caution-about-potentially-blocking-bots) are allowing **Verified Bots**.
 * [Rate limiting rules](/waf/rate-limiting-rules/) are allowing **Verified Bots**.
-* [Bot protection](/bots/concepts/bot/#verified-bots) settings are not blocking **Verified Bots**.
+* [Bot protection](/bots/concepts/bot/verified-bots/) settings are not blocking **Verified Bots**.
 
 If you still notice issues with search engine crawlers, refer to our [Troubleshooting guide](/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors/).
 
diff --git a/src/content/docs/page-shield/how-it-works/index.mdx b/src/content/docs/page-shield/how-it-works/index.mdx
@@ -18,7 +18,7 @@ Enabling resource monitoring adds a <GlossaryTooltip term="content security poli
 
 The client-side resource monitoring dashboard shows the list of active scripts, connections, and cookies. The **All Reported Scripts** and **All Reported Connections** dashboards show the full list of detected scripts and connections in your domain, respectively, including infrequent and inactive ones.
 
-Cloudflare adds a CSP report-only HTTP header used to monitor webpage resources to a sample of sent responses. This means that there may be a [small delay](/page-shield/troubleshooting/#page-shield-does-not-show-any-resources-after-activating-it) between deploying a script or cookie and having its data displayed in the resource monitoring dashboards.
+Cloudflare adds a CSP report-only HTTP header used to monitor webpage resources to a sample of sent responses. This means that there may be a [small delay](/page-shield/troubleshooting/#cloudflare-does-not-show-any-client-side-resources-after-activation) between deploying a script or cookie and having its data displayed in the resource monitoring dashboards.
 
 Enterprise customers with a paid add-on have access to additional classification mechanisms based on threat feeds to determine if a script, or a connection made by a script, is malicious. For more information, refer to [Malicious script and connection detection](/page-shield/how-it-works/malicious-script-detection/).
 
diff --git a/src/content/docs/rules/transform/managed-transforms/reference.mdx b/src/content/docs/rules/transform/managed-transforms/reference.mdx
@@ -33,7 +33,7 @@ Requires an Enterprise plan with [Bot Management](/bots/plans/bm-subscription/)
 Adds HTTP headers with bot-related values to the request sent to the origin server:
 
 - `cf-bot-score`: Contains the <GlossaryTooltip term="bot score" link="/bots/concepts/bot-score/">bot score</GlossaryTooltip> (for example, `30`).
-- `cf-verified-bot`: Contains `true` if the request comes from a <GlossaryTooltip term="verified bot" link="/bots/concepts/bot/#verified-bots">verified bot</GlossaryTooltip>, or `false` otherwise.
+- `cf-verified-bot`: Contains `true` if the request comes from a <GlossaryTooltip term="verified bot" link="/bots/concepts/bot/verified-bots/">verified bot</GlossaryTooltip>, or `false` otherwise.
 - `cf-ja3-hash`: Contains the <GlossaryTooltip term="JA3 fingerprint" link="/bots/additional-configurations/ja3-ja4-fingerprint/">JA3 fingerprint</GlossaryTooltip>.
 - `cf-ja4`: Contains the <GlossaryTooltip term="JA3 fingerprint" link="/bots/additional-configurations/ja3-ja4-fingerprint/">JA4 fingerprint</GlossaryTooltip>.
 
diff --git a/src/content/docs/security/settings.mdx b/src/content/docs/security/settings.mdx
@@ -59,7 +59,7 @@ Additionally, you can manage the following settings:
 - [Block AI Bots](/bots/concepts/bot/#ai-bots)
 - [Bot Management](/bots/get-started/bot-management/) (depending on your Enterprise subscriptions)
 - [Browser Integrity Check](/waf/tools/browser-integrity-check/)
-- [Challenge Passage](/cloudflare-challenges/challenge-types/challenge-pages/#challenge-passage)
+- [Challenge Passage](/cloudflare-challenges/challenge-types/challenge-pages/challenge-passage/)
 - [Cloudflare managed ruleset](/waf/managed-rules/reference/cloudflare-managed-ruleset/)
 - [Firewall for AI](/waf/detections/firewall-for-ai/)
 - [Schema learning](/api-shield/management-and-monitoring/endpoint-management/schema-learning/)
diff --git a/src/content/docs/waf/custom-rules/use-cases/allow-traffic-from-verified-bots.mdx b/src/content/docs/waf/custom-rules/use-cases/allow-traffic-from-verified-bots.mdx
@@ -6,7 +6,7 @@ head:
     content: Allow traffic from search engine bots and other verified bots
 ---
 
-This example custom rule challenges requests from a list of countries, but allows traffic from search engine bots — such as Googlebot and Bingbot — and from other [verified bots](/bots/concepts/bot/#verified-bots).
+This example custom rule challenges requests from a list of countries, but allows traffic from search engine bots — such as Googlebot and Bingbot — and from other [verified bots](/bots/concepts/bot/verified-bots/).
 
 The rule expression uses the [`cf.client.bot`](/ruleset-engine/rules-language/fields/reference/cf.client.bot/) field to determine if the request originated from a known good bot or crawler.
 
