broken links

patriciasantaana · patriciasantaana · commit 896b08b52e19 · 2025-08-25T09:44:22.000-07:00
diff --git a/src/content/docs/ai-audit/features/manage-ai-crawlers.mdx b/src/content/docs/ai-audit/features/manage-ai-crawlers.mdx
@@ -25,15 +25,15 @@ The **AI Crawlers** tab displays a table of AI crawlers that are requesting acce
 | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | AI Crawlers           | The name of the AI crawler.                                                                                                                                         |
 | Operator              | The name of the entity who owns the AI crawler. Note that an operator may have multiple AI crawlers.                                                                |
-| Category              | The category of the AI crawler. Refer to [Verified bot categories](/bots/concepts/bot/verified-bots/categories/).                                                   |
+| Category              | The category of the AI crawler. Refer to [Verified bot categories](/bots/concepts/bot/verified-bots/#categories).                                                   |
 | Block                 | Toggle for blocking specific AI crawlers.                                                                                                                           |
 
 </TabItem> <TabItem label="Paid plan">
 | Column                | Details                                                                                                                                                             |
 | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | AI Crawlers           | The name of the AI crawler.                                                                                                                                         |
 | Operator              | The name of the entity who owns the AI crawler. Note that an operator may have multiple AI crawlers.                                                                |
-| Category              | The category of the AI crawler. Refer to [Verified bot categories](/bots/concepts/bot/verified-bots/categories/).                                                   |
+| Category              | The category of the AI crawler. Refer to [Verified bot categories](/bots/concepts/bot/verified-bots/#categories).                                                   |
 | Requests              | The number of times the AI crawler has requested to crawl your content.                                                                                             |
 | Robots.txt violations | The number of times the AI crawler has violated your <GlossaryTooltip term="robots.txt">`robots.txt`</GlossaryTooltip> file.                                        |
 | Action                | The action you wish to take for the AI crawler. Refer to [Take action for each AI crawler](/ai-audit/features/manage-ai-crawlers/#take-action-for-each-ai-crawler). |
diff --git a/src/content/docs/ai-audit/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/crawl-pages.mdx b/src/content/docs/ai-audit/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/crawl-pages.mdx
@@ -33,7 +33,7 @@ To access this content, the AI crawler must provide headers for paid access.
 
 ### 2.1. Include WBA headers
 
-Include Web Bot Auth headers by following the steps [Sign your requests](/bots/concepts/bot/verified-bots/web-bot-auth/#4-after-verification-sign-your-requests)
+Include Web Bot Auth headers by following the steps [Sign your requests](/bots/reference/bot-verification/web-bot-auth/#4-after-verification-sign-your-requests)
 
 ### 2.2. Include payment headers
 
diff --git a/src/content/docs/ai-audit/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/verify-ai-crawler.mdx b/src/content/docs/ai-audit/features/pay-per-crawl/use-pay-per-crawl-as-ai-owner/verify-ai-crawler.mdx
@@ -37,7 +37,7 @@ To access this content, you must verify your AI crawler.
 
 Ensure your AI crawler identifies itself with the required headers for Web Bot Auth.
 
-Follow the steps found in [Web Both Auth](/bots/concepts/bot/verified-bots/web-bot-auth/).
+Follow the steps found in [Web Both Auth](/bots/reference/bot-verification/web-bot-auth/).
 
 ## 2. Follow verified bot policy
 
diff --git a/src/content/docs/bots/concepts/bot/index.mdx b/src/content/docs/bots/concepts/bot/index.mdx
@@ -23,7 +23,7 @@ For more background, refer to [What is a bot?](https://www.cloudflare.com/learni
 
 <Render file="verified-bots" product="bots" />
 
-For more information, refer to [Verified bots](/bots/concepts/bot/verified-bots/overview/).
+For more information, refer to [Verified bots](/bots/concepts/bot/verified-bots/).
 
 :::note
 
diff --git a/src/content/docs/bots/concepts/bot/verified-bots/index.mdx b/src/content/docs/bots/concepts/bot/verified-bots/index.mdx
@@ -25,7 +25,7 @@ For a bot to be verified, it must meet the following requirements:
 
 1. The bot must follow [verified bots policy](/bots/concepts/bot/verified-bots/policy/).
 2. The bot must be verified using one of the following verification methods:
-   - [Web Bot Auth](/bots/concepts/bot/verified-bots/web-bot-auth/)
+   - [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/)
    - [IP validation](/bots/concepts/bot/verified-bots/ip-validation/)
 
 Once Cloudflare verifies a bot, it should appear on [Cloudflare Radar's list of verified bots](https://radar.cloudflare.com/verified-bots).
diff --git a/src/content/docs/bots/frequently-asked-questions.mdx b/src/content/docs/bots/frequently-asked-questions.mdx
@@ -232,8 +232,8 @@ Cloudflare uses [`http-signature-directory` tool](https://crates.io/crates/http-
 
 ### My message is failing validation. What could be the cause?
 
-- Ensure you have a [`Signature-Agent` header](/bots/concepts/bot/verified-bots/web-bot-auth/#signature-agent-header), and that its value is in double-quotes.
-- Ensure you include `signature-agent` in the component list in your [`Signature-Input` header](/bots/concepts/bot/verified-bots/web-bot-auth/#signature-agent-header).
+- Ensure you have a [`Signature-Agent` header](/bots/reference/bot-verification/web-bot-auth/#signature-agent-header), and that its value is in double-quotes.
+- Ensure you include `signature-agent` in the component list in your [`Signature-Input` header](/bots/reference/bot-verification/web-bot-auth/#signature-agent-header).
 - Ensure your `expires` timestamp is not too short, such that, by the time it arrives at Cloudflare servers, it has already expired. A minute is often sufficient.
 - Ensure you are not signing components containing non-ASCII values, or on the unsupported list.
 
diff --git a/src/content/docs/bots/reference/alerts.mdx b/src/content/docs/bots/reference/alerts.mdx
@@ -69,5 +69,5 @@ You can also choose to group by the following dimensions so that they can be ale
 - Bot Detection IDs
 
 :::note
-Bot Detection Alerts exclude [verified bots](/bots/concepts/bot/verified-bots/categories/). 
+Bot Detection Alerts exclude [verified bots](/bots/concepts/bot/verified-bots/). 
 :::
diff --git a/src/content/docs/bots/reference/bot-management-variables.mdx b/src/content/docs/bots/reference/bot-management-variables.mdx
@@ -17,7 +17,7 @@ Bot Management provides access to several [new variables](/ruleset-engine/rules-
 - **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).
-- **Verified Bot Categories** (`cf.verified_bot_category`): A string that allows you to segment your verified bot traffic by its [type and purpose](/bots/concepts/bot/verified-bots/categories/).
+- **Verified Bot Categories** (`cf.verified_bot_category`): A string that allows you to segment your verified bot traffic by its [type and purpose](/bots/concepts/bot/verified-bots/#categories).
 
 ## Workers variables
 
diff --git a/src/content/docs/browser-rendering/reference/automatic-request-headers.mdx b/src/content/docs/browser-rendering/reference/automatic-request-headers.mdx
@@ -21,4 +21,4 @@ These headers are meant to ensure transparency and cannot be removed or overridd
 | `Signature-agent`    | [The location of the bot public keys](https://web-bot-auth.cloudflare-browser-rendering-085.workers.dev), used to sign the request and verify it came from Cloudflare                                       |
 | `Signature` and `Signature-input`| A digital signature, used to validate requests, as shown in [this architecture document](https://datatracker.ietf.org/doc/html/draft-meunier-web-bot-auth-architecture)                     |
 
-The `Signature` headers use an authentication method called [Web Bot Auth](/bots/concepts/bot/verified-bots/web-bot-auth/). Web Bot Auth leverages cryptographic signatures in HTTP messages to verify that a request comes from an automated bot. To verify a request originated from Cloudflare Browser Rendering, use the keys found on [this directory](https://web-bot-auth.cloudflare-browser-rendering-085.workers.dev/.well-known/http-message-signatures-directory) to verify the `Signature` and `Signature-Input` found in the headers from the incoming request. A successful verification proves that the request originated from Cloudflare Browser Rendering and has not been tampered with in transit.
+The `Signature` headers use an authentication method called [Web Bot Auth](/bots/reference/bot-verification/web-bot-auth/). Web Bot Auth leverages cryptographic signatures in HTTP messages to verify that a request comes from an automated bot. To verify a request originated from Cloudflare Browser Rendering, use the keys found on [this directory](https://web-bot-auth.cloudflare-browser-rendering-085.workers.dev/.well-known/http-message-signatures-directory) to verify the `Signature` and `Signature-Input` found in the headers from the incoming request. A successful verification proves that the request originated from Cloudflare Browser Rendering and has not been tampered with in transit.
diff --git a/src/content/fields/index.yaml b/src/content/fields/index.yaml
@@ -497,7 +497,7 @@ entries:
     keywords: [request, bots, client, visitor]
     summary: Provides the type and purpose of a verified bot.
     description: |-
-      For more details, refer to [Verified bot categories](/bots/concepts/bot/verified-bots/categories/).
+      For more details, refer to [Verified bot categories](/bots/concepts/bot/verified-bots/#categories).
 
   - name: cf.bot_management.score
     data_type: Number
