broken links

patriciasantaana · patriciasantaana · commit 96b388615036 · 2025-08-06T13:31:27.000-07:00
diff --git a/src/content/docs/cloudflare-challenges/concepts/clearance.mdx b/src/content/docs/cloudflare-challenges/concepts/clearance.mdx
@@ -72,7 +72,7 @@ To enable pre-clearance, you must ensure that the hostname of the Turnstile widg
 
 The prerequisite is crucial for pre-clearance to function properly. If set up correctly, visitors who successfully solve Turnstile will receive a cookie with the security clearance level set by the customer. When encountering a WAF challenge on the same zone, they will bypass additional challenges for the configured clearance level and below.
 
-For more details on managing hostnames, refer to the [Hostname Management documentation](/turnstile/concepts/hostname-management/).
+For more details on managing hostnames, refer to the [Hostname Management documentation](/turnstile/additional-configuration/hostname-management/).
 
 <Render file="cf-clearance-cookie" product="cloudflare-challenges" />
 
diff --git a/src/content/docs/cloudflare-challenges/frequently-asked-questions.mdx b/src/content/docs/cloudflare-challenges/frequently-asked-questions.mdx
@@ -85,7 +85,7 @@ Block Amazon Web Services (AWS) and Google Cloud Platform (GCP) because of large
 
 Previously, unless you customize your front-end application, any AJAX request that is challenged will fail because AJAX calls are not rendered in the DOM.
 
-Now, you can [opt-in to Turnstile's Pre-clearance cookies](/turnstile/concepts/pre-clearance-support/). This allows you to issue a Challenge early in your web application flow and pre-clear users to interact with sensitive APIs. Clearance cookies issued by a Turnstile widget are automatically applied to the Cloudflare zone that the Turnstile widget is embedded on, with no configuration necessary. The duration of the clearance cookie's validity is controlled by the zone-specific configurable [Challenge Passage](/cloudflare-challenges/challenge-types/challenge-pages/challenge-passage/) security setting.
+Now, you can [opt-in to Turnstile's Pre-clearance cookies](/cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile). This allows you to issue a Challenge early in your web application flow and pre-clear users to interact with sensitive APIs. Clearance cookies issued by a Turnstile widget are automatically applied to the Cloudflare zone that the Turnstile widget is embedded on, with no configuration necessary. The duration of the clearance cookie's validity is controlled by the zone-specific configurable [Challenge Passage](/cloudflare-challenges/challenge-types/challenge-pages/challenge-passage/) security setting.
 
 ## Why would I not find any failed Challenges?
 
diff --git a/src/content/docs/turnstile/concepts/widgets.mdx b/src/content/docs/turnstile/concepts/widgets.mdx
@@ -48,11 +48,11 @@ Invisible mode is ideal for users who want to prioritize visitor and visual expe
 
 Widgets can be implemented in normal, flexible, or compact sizes.
 
-Refer to [Widget configurations](/turnstile/get-started/widget-configurations/) for detailed configuration options and code examples.
+Refer to [Widget configurations](/turnstile/get-started/client-side-rendering/widget-configurations/) for detailed configuration options and code examples.
 
 ### Appearance and themes
 
-Turnstile widgets support multiple appearance modes and themes to match your website's design. Refer to [Widget configurations](/turnstile/get-started/widget-configurations/) for implementation details.
+Turnstile widgets support multiple appearance modes and themes to match your website's design. Refer to [Widget configurations](/turnstile/get-started/client-side-rendering/widget-configurations/) for implementation details.
 
 ---
 
diff --git a/src/content/docs/turnstile/extensions/google-firebase.mdx b/src/content/docs/turnstile/extensions/google-firebase.mdx
@@ -31,7 +31,7 @@ It is important to register your web app first to connect it with Turnstile late
 1. Create a Cloudflare Turnstile site by going to the [Cloudflare Turnstile dashboard](https://dash.cloudflare.com/?to=/:account/turnstile).
 2. Create a new widget and get the [sitekey and secret key](/turnstile/get-started/#get-a-sitekey-and-secret-key).
    - The domain you configure with the Turnstile widget should be the domain of your web app.
-   - The [widget mode](/turnstile/concepts/widget/) must be **Invisible**.
+   - The [widget mode](/turnstile/concepts/widgets/) must be **Invisible**.
 
 ## Integrate Firebase App Check with Turnstile
 
diff --git a/src/content/docs/turnstile/get-started/client-side-rendering/index.mdx b/src/content/docs/turnstile/get-started/client-side-rendering/index.mdx
@@ -63,7 +63,7 @@ Add widget containers where you want the challenges to appear on your website.
 
 #### 3. Configure with data attributes
 
-[Customize your widgets](/turnstile/get-started/widget-management/widget-configurations/) using data attributes.
+[Customize your widgets](/turnstile/get-started/widget-configurations/) using data attributes.
 
 ```html
 <div class="cf-turnstile" 
@@ -405,7 +405,7 @@ Both implicit and explicit rendering methods support the same configuration opti
 | `execution` | WHen to run the challenge | `render`, `execute` |
 | `appearance` | When the widget is visible | `always`, `execute`, `interaction-only` |
 
-For a complete list of configuration options, refer to [Widget configurations](/turnstile/get-started/widget-management/widget-configurations/).
+For a complete list of configuration options, refer to [Widget configurations](/turnstile/get-started/widget-configurations/).
 
 ---
 
diff --git a/src/content/docs/turnstile/get-started/index.mdx b/src/content/docs/turnstile/get-started/index.mdx
@@ -31,16 +31,16 @@ Every widget has:
   - **Configuration**: Mode, hostnames, appearance settings, and other options
 
 :::note[Important]
-Regardless of how you create and manage your widgets, you will still need to [embed the widget](/turnstile/get-started/widget-management/client-side-rendering/) on your webpage and [validate the token](/turnstile/get-started/widget-management/server-side-validation/) on your server.
+Regardless of how you create and manage your widgets, you will still need to [embed the widget](/turnstile/get-started/client-side-rendering/) on your webpage and [validate the token](/turnstile/get-started/server-side-validation/) on your server.
 :::
 
 Implementing Turnstile involves two essential components that work together:
 
-1. **Client-side**: [Embed the widget](/turnstile/get-started/widget-management/client-side-rendering/)
+1. **Client-side**: [Embed the widget](/turnstile/get-started/client-side-rendering/)
 
     Add the Turnstile widget to your webpage to challenge visitors and generate verification tokens.
 
-2. **Server-side**: [Validate the token](/turnstile/get-started/widget-management/server-side-validation/)
+2. **Server-side**: [Validate the token](/turnstile/get-started/server-side-validation/)
 
     Verify the tokens on your server using the Siteverify API to ensure they are authentic and have not been tampered with.
 
@@ -64,13 +64,13 @@ Select your preferred implementation method:
 
 Add the Turnstile widget to your webpage forms and applications.
 
-Refer to [Embed the widget](/turnstile/get-started/widget-management/client-side-rendering/) to learn more about implicit and explicit rendering methods
+Refer to [Embed the widget](/turnstile/get-started/client-side-rendering/) to learn more about implicit and explicit rendering methods
 
 ### 3. Validate tokens
 
 Implement server-side validation to verify the tokens generated by your widgets.
 
-Refer to [Validate the token](/turnstile/get-started/widget-management/server-side-validation/) to secure your implementation with proper token verification.
+Refer to [Validate the token](/turnstile/get-started/server-side-validation/) to secure your implementation with proper token verification.
 
 ## Additional implementation options
 
diff --git a/src/content/docs/turnstile/get-started/mobile-implementation.mdx b/src/content/docs/turnstile/get-started/mobile-implementation.mdx
@@ -40,7 +40,7 @@ When implementing Turnstile with WebViews, the user agent must stay consistent a
 
 ## Use clearance cookies
 
-When using [clearance cookies](/turnstile/concepts/pre-clearance-support/) with Turnstile, make sure that it is executed in the same environment where the challenges will occur, including the same browser and device configuration. The `cf_clearance` cookie will be only accepted in the same configured domain for Turnstile widget with the corresponding zone. Domains configured with the Turnstile widget must match the Cloudflare zone that issues [challenges](/cloudflare-challenges/).
+When using [clearance cookies](/cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile) with Turnstile, make sure that it is executed in the same environment where the challenges will occur, including the same browser and device configuration. The `cf_clearance` cookie will be only accepted in the same configured domain for Turnstile widget with the corresponding zone. Domains configured with the Turnstile widget must match the Cloudflare zone that issues [challenges](/cloudflare-challenges/).
 
 If pre-clearance is done in a different environment, the clearance cookie may become invalid and lead to more issued challenges.
 
diff --git a/src/content/docs/turnstile/index.mdx b/src/content/docs/turnstile/index.mdx
@@ -38,7 +38,7 @@ These challenges include: proof-of-work, proof-of-space, probing for web APIs, a
 
 ## Widget types
 
-Turnstile [widget types](/turnstile/widgets/) include:
+Turnstile [widget types](/turnstile/concepts/widgets/) include:
 
 - **Non-interactive**: Visitors never need to interact with the widget.
 - **Managed**: Visitors are presented with an interactive checkbox if they are a suspected bot.
diff --git a/src/content/docs/turnstile/reference/content-security-policy.mdx b/src/content/docs/turnstile/reference/content-security-policy.mdx
@@ -24,6 +24,6 @@ You cannot set your own CSP and/or Referer-Policy via meta tags or [Transform ru
 
 ## Pre-clearance support
 
-If you are using [Turnstile in pre-clearance mode](/turnstile/concepts/pre-clearance-support/), Turnstile sets the `cf_clearance` cookie by doing a fetch request to a special endpoint in [`/cdn-cgi/`](/fundamentals/reference/cdn-cgi-endpoint/) of your domain.
+If you are using [Turnstile in pre-clearance mode](/cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile), Turnstile sets the `cf_clearance` cookie by doing a fetch request to a special endpoint in [`/cdn-cgi/`](/fundamentals/reference/cdn-cgi-endpoint/) of your domain.
 
 For this request to succeed, your `connect-src` directive must include `'self'`.
diff --git a/src/content/docs/turnstile/troubleshooting/feedback-reports.mdx b/src/content/docs/turnstile/troubleshooting/feedback-reports.mdx
@@ -6,7 +6,7 @@ sidebar:
 
 ---
 
-When Cloudflare detects that a challenge has failed or the user cannot be verified on a page with Turnstile, the user will encounter an [error](/turnstile/concepts/widget/#error-states) on the widget and may be asked to send feedback on the issue that they have encountered by choosing one of the options listed.
+When Cloudflare detects that a challenge has failed or the user cannot be verified on a page with Turnstile, the user will encounter an [error](/turnstile/concepts/widgets/#error-states) on the widget and may be asked to send feedback on the issue that they have encountered by choosing one of the options listed.
 
 :::note
 
diff --git a/src/content/docs/turnstile/troubleshooting/testing.mdx b/src/content/docs/turnstile/troubleshooting/testing.mdx
@@ -12,7 +12,7 @@ import { GlossaryTooltip } from "~/components"
 
 The following <GlossaryTooltip term="sitekey">sitekeys</GlossaryTooltip> and <GlossaryTooltip term="secret key">secret keys</GlossaryTooltip> are available for testing. It is recommended that you use these keys in your development environment to ensure the challenges running in Turnstile do not conflict with your developer tools.
 
-To test locally with real keys, you need to add your testing hostnames (like `localhost`) to your [domain allowlist](/turnstile/concepts/hostname-management/).
+To test locally with real keys, you need to add your testing hostnames (like `localhost`) to your [domain allowlist](/turnstile/additional-configuration/hostname-management/).
 
 Dummy sitekeys can be used from any domain, including on `localhost`.
 
diff --git a/src/content/docs/turnstile/turnstile-analytics/challenge-outcomes.mdx b/src/content/docs/turnstile/turnstile-analytics/challenge-outcomes.mdx
@@ -33,7 +33,7 @@ By analyzing these metrics, you can identify trends such as high failure rates i
 
 Turnstile's solve rate is a critical metric that helps gauge how many legitimate visitors are passing a challenge. Solve rates can be broken down into the total number of challenges solved and whether they are interactive, non-interactive, or pre-clearance solves.
 
-If you are using [managed mode](/turnstile/concepts/widget/#widget-types), you can monitor how many of your visitors were prompted interactivity to check the box on the widget (interactive solves) and how many were verified without any disruptions to their experience (non-interactive solves).
+If you are using [managed mode](/turnstile/concepts/widgets/#managed-mode-recommended), you can monitor how many of your visitors were prompted interactivity to check the box on the widget (interactive solves) and how many were verified without any disruptions to their experience (non-interactive solves).
 
 For example, the solve rate values in your analytics may look like this:
 
@@ -43,6 +43,6 @@ For example, the solve rate values in your analytics may look like this:
 
 - **Non-interactive solves**: Challenges solved without requiring the visitor to click a checkbox.
 - **Interactive solves**: Challenges solved that required visitor interaction to be solved.
-- [**Pre-clearance solves**](/turnstile/concepts/pre-clearance-support/): Challenges solved that issued the `cf_clearance` cookie along with the Turnstile token.
+- [**Pre-clearance solves**](/cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile): Challenges solved that issued the `cf_clearance` cookie along with the Turnstile token.
 
 A low solve rate might indicate increased bot activity attempting to bypass Turnstile or anomalous traffic patterns that require further investigation.
diff --git a/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx b/src/content/docs/turnstile/tutorials/integrating-turnstile-waf-and-bot-management.mdx
@@ -63,7 +63,7 @@ Turnstile adds an extra layer of security by analyzing browser and client-side s
 
 ### Enable the option to use the existing clearance cookie
 
-If your site is on Cloudflare, you can enable the option to use the existing [clearance cookie](/turnstile/concepts/pre-clearance-support/) in Turnstile's settings. This integration allows Turnstile to use the clearance cookie as part of its determination of whether a user should receive a challenge. This integration is optional, but recommended if you already are using WAF and Bot Management.
+If your site is on Cloudflare, you can enable the option to use the existing [clearance cookie](/cloudflare-challenges/concepts/clearance/#pre-clearance-support-in-turnstile) in Turnstile's settings. This integration allows Turnstile to use the clearance cookie as part of its determination of whether a user should receive a challenge. This integration is optional, but recommended if you already are using WAF and Bot Management.
 
 ## Integrate Turnstile into your application
 
diff --git a/src/content/docs/waiting-room/how-to/create-waiting-room.mdx b/src/content/docs/waiting-room/how-to/create-waiting-room.mdx
@@ -22,7 +22,7 @@ For additional context on creating a waiting room, refer to [Get started](/waiti
 2. Select **Create**.
 3. Customize the [settings](/waiting-room/reference/configuration-settings/) for your waiting room. For additional guidance refer to [Best practices](/waiting-room/reference/best-practices/).
 4. Select **Next**.
-5. In this section, you can choose whether to enable [Turnstile](/turnstile/) for your waiting room. If you select **Yes**, you will need to choose your [Widget mode](/turnstile/concepts/widget/) and define the action to take if a turnstile challenge fails. The available Widget modes and actions depend on your plan type. Refer to the [Plans](/waiting-room/plans/) for more details.
+5. In this section, you can choose whether to enable [Turnstile](/turnstile/) for your waiting room. If you select **Yes**, you will need to choose your [Widget mode](/turnstile/concepts/widgets/) and define the action to take if a turnstile challenge fails. The available Widget modes and actions depend on your plan type. Refer to the [Plans](/waiting-room/plans/) for more details.
 6. If you wish to [customize your waiting room](/waiting-room/how-to/customize-waiting-room/), update the HTML and CSS as needed. If you are using this waiting room to manage traffic for your mobile app or API, enable the JSON response toggle. Make sure that you have set up a [JSON friendly response](/waiting-room/how-to/json-response/) for your client (mobile or web app).
 7. Select the **Queuing status code** to determine the HTTP status code that is returned when a user is in the waiting room.
 8. Select **Next**.
diff --git a/src/content/docs/waiting-room/reference/configuration-settings.mdx b/src/content/docs/waiting-room/reference/configuration-settings.mdx
@@ -209,7 +209,7 @@ You can customize a variety of options for your waiting rooms.
       </td>
       <td>Yes, defaults <code>invisible</code>.</td>
       <td>
-        The type of Turnstile widget to use - refer to the [Turnstile documentation](/turnstile/concepts/widget/#widget-types) for details. Valid values are <code>off</code>, <code>invisible</code>, <code>visible_non_interactive</code>, and <code>visible_managed</code>. Setting this to <code>off</code> will completely disable the Turnstile integration.
+        The type of Turnstile widget to use - refer to the [Turnstile documentation](turnstile/concepts/widgets/#widget-modes) for details. Valid values are <code>off</code>, <code>invisible</code>, <code>visible_non_interactive</code>, and <code>visible_managed</code>. Setting this to <code>off</code> will completely disable the Turnstile integration.
       </td>
       <td>
         Setting this to <code>invisible</code> makes sense for most rooms, unless you would like end users to be aware the challenge is running.
diff --git a/src/content/partials/turnstile/implementation-methods.mdx b/src/content/partials/turnstile/implementation-methods.mdx
@@ -5,8 +5,8 @@
 
 import { LinkButton } from "~/components"
 
-<LinkButton href="/turnstile/get-started/widget-management/implementation-methods/dashboard/">Cloudflare dashboard</LinkButton>
+<LinkButton href="/turnstile/get-started/widget-management/dashboard/">Cloudflare dashboard</LinkButton>
 
-<LinkButton href="/turnstile/get-started/widget-management/implementation-methods/api/">API</LinkButton>
+<LinkButton href="/turnstile/get-started/widget-management/api/">API</LinkButton>
 
-<LinkButton href="/turnstile/get-started/widget-management/implementation-methods/terraform/">Terraform</LinkButton>
+<LinkButton href="/turnstile/get-started/widget-management/terraform/">Terraform</LinkButton>
