diff --git a/src/assets/images/turnstile/challenge-outcomes.png b/src/assets/images/turnstile/challenge-outcomes.png
new file mode 100644
index 00000000000000..0fa137a241ae0c
Binary files /dev/null and b/src/assets/images/turnstile/challenge-outcomes.png differ
diff --git a/src/assets/images/turnstile/solve-rates.png b/src/assets/images/turnstile/solve-rates.png
new file mode 100644
index 00000000000000..531d1f3cdccd4b
Binary files /dev/null and b/src/assets/images/turnstile/solve-rates.png differ
diff --git a/src/assets/images/turnstile/token-validation.png b/src/assets/images/turnstile/token-validation.png
new file mode 100644
index 00000000000000..ed9b51adf1d4d6
Binary files /dev/null and b/src/assets/images/turnstile/token-validation.png differ
diff --git a/src/assets/images/turnstile/top-actions.png b/src/assets/images/turnstile/top-actions.png
new file mode 100644
index 00000000000000..4d825ca1c47fb3
Binary files /dev/null and b/src/assets/images/turnstile/top-actions.png differ
diff --git a/src/content/docs/turnstile/turnstile-analytics.mdx b/src/content/docs/turnstile/turnstile-analytics.mdx
deleted file mode 100644
index 8616a880b0bf7f..00000000000000
--- a/src/content/docs/turnstile/turnstile-analytics.mdx
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: Turnstile Analytics
-pcx_content_type: how-to
-sidebar:
- order: 6
-head: []
-description: Use Turnstile Analytics to view the number of challenges issued,
- the challenge solve rate, and the metrics of issued challenges.
-
----
-
-Using Turnstile Analytics, you can:
-
-- Assess the number of challenges issued.
-- Evaluate the Challenge Solve Rate (CSR).
-- View the metrics of issued challenges.
-
-## View metrics of your widgets
-
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
-2. Go to **Turnstile** and then navigate to your website to see an overview of its widget metrics.
-
-These metrics show changes in the solve rate, widget traffic, and top actions for your website.
-
-## Change in Solve Rate
-
-The change in Solve Rate is expected to be relatively stable over time. It is an indication of something happening on the website, such as undergoing attacks from bots.
-
-View the history of your website’s widget Solve Rate with Turnstile Analytics.
-
-:::note
-
-You can filter the data by `Action=(free input)` or by time.
-:::
-
-### Visitor Solve Rate
-
-Visitor Solve Rate considers all humans who have viewed the widget, whether it was interactive or non-interactive. It measures the percentage of people who completed the widget. For example, if 100 people saw the widget and 20 of them completed it successfully, the Visitor Solve Rate would be 20%.
-
-A full Turnstile Challenge Token Flow consists of a few things:
-
-- A challenge is rendered (issued).
-- A challenge is solved on the front end and a token is harvested (solved).
-- The token is passed to siteverify, and it is consumed (siteverified).
-
-Visitor Solve Rate is the percentage of tokens that were solved but have not necessarily been siteverified compared to issued challenges.
-
-### API Solve Rate
-
-API Solve Rate is the share of tokens that were siteverified compared to issued. It focuses only on humans who interacted with the widget through the website’s API. It measures the percentage of successful widget completions among all visitors detected through the API. This metric looks specifically at the number of people who successfully completed the widget. For example, if 100 people viewed the widget, 20 of them completed it successfully, and only 15 of them had their token siteverified, the API Solve Rate would be 15%.
-
-## Widget traffic
-
-Widget traffic metrics provide you with data on the number of instances where the widget was displayed, the number of instances where interactive widget was solved, and the number of instances where non-interactive widget was solved on your website over time.
-
-## Top Actions
-
-Top Actions refer to the custom labels you created for your widgets.
-
-Action can be used in analytics and is more limited in size. It should identify different pages in a website where a widget is used. Action should not contain any personally identifiable information (PII) as this is placed into the analytics.
-
-cData is not stored in our analytics. It can contain data that may vary by each challenge instance.
-
-Both cData and action are returned by the siteverify API if a valid token is presented.
-
-## GraphQL
-
-You can use the `turnstileAdaptiveGroups` [dataset in GraphQL](/analytics/graphql-api/features/data-sets/) to get Turnstile widget analytics.
diff --git a/src/content/docs/turnstile/turnstile-analytics/challenge-outcomes.mdx b/src/content/docs/turnstile/turnstile-analytics/challenge-outcomes.mdx
new file mode 100644
index 00000000000000..03fd359793ea3e
--- /dev/null
+++ b/src/content/docs/turnstile/turnstile-analytics/challenge-outcomes.mdx
@@ -0,0 +1,48 @@
+---
+title: Challenge outcome
+pcx_content_type: concept
+sidebar:
+ order: 2
+---
+
+import { Render } from "~/components"
+
+When a visitor encounters Turnstile, it assesses whether they are human or bot-like based on various signals. These outcomes help you evaluate how effectively Turnstile is protecting your application.
+
+## Metrics
+
+A "solved" Turnstile challenge does not automatically confirm the visitor is human. You must [call the siteverify API](#call-siteverify) to validate the token and proceed only if the response returns `success:true`.
+
+For example, the challenge outcome values in your analytics may look like this:
+
+
+
+- **Challenges issued**: The total number of challenges presented to visitors within a specific timeframe.
+- **Challenges solved**: The number of challenges successfully completed by visitors in that period.
+- **Challenges unsolved**: Challenges that were abandoned or failed in that period.
+- **Likely human**: The total number of challenges solved or the total number of challenges issued.
+- **Likely bot**: The total number of challenges unsolved or the total number challenges issued.
+
+By analyzing these metrics, you can identify trends such as high failure rates in specific regions, device types, or traffic sources, which may indicate bot activity or misconfigurations.
+
+### Call siteverify
+
+
+
+## Solve rates
+
+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).
+
+For example, the solve rate values in your analytics may look like this:
+
+
+
+### Metrics
+
+- **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.
+
+A low solve rate might indicate increased bot activity attempting to bypass Turnstile or anomalous traffic patterns that require further investigation.
\ No newline at end of file
diff --git a/src/content/docs/turnstile/turnstile-analytics/index.mdx b/src/content/docs/turnstile/turnstile-analytics/index.mdx
new file mode 100644
index 00000000000000..0c48cd6aac6775
--- /dev/null
+++ b/src/content/docs/turnstile/turnstile-analytics/index.mdx
@@ -0,0 +1,36 @@
+---
+title: Turnstile Analytics
+pcx_content_type: how-to
+sidebar:
+ order: 6
+description: Use Turnstile Analytics to view the number of challenges issued,
+ the challenge solve rate, and the metrics of issued challenges.
+
+---
+
+import { Render, DirectoryListing } from "~/components"
+
+Turnstile Analytics provides you with a view of the top widget statistics across different metadata dimensions to understand where your traffic is coming from, which environments have the highest challenge activity, and whether certain sources are disproportionately failing or bypassing challenges, allowing you to fine-tune your security settings, apply more granular mitigations, and proactively respond to evolving threats.
+
+## Available statistics
+
+- **Top Hostnames**: If the Turnstile widget is placed across multiple hostnames, this will display the highest traffic hostnames where challenges are being issued.
+- **Top Browsers**: A breakdown of browsers that are most commonly encountering Turnstile challenges, helping customers spot trends in visitor traffic.
+- **Top Countries**: View the top originating countries for visitors completing challenges, which can help identify regional traffic anomalies.
+- **Top User Agents**: Identify which user agents are generating the most Turnstile challenge requests.
+- [**Top ASNs**](https://cloudflare.com/learning/network-layer/what-is-an-autonomous-system): Displays the highest volume of challenges issued from specific Autonomous System Numbers (ASNs), helping customers detect potential bot activity.
+- **Top Operating Systems**: Shows which operating systems are most common among visitors passing or failing challenges.
+- [**Top Source IPs**](https://cloudflare.com/learning/ddos/glossary/ip-spoofing): Identify the highest-volume IP addresses issuing Turnstile challenges, which can be useful in identifying attack sources or repeated challenge failures.
+
+## View widget metrics
+
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
+2. Go to **Turnstile** and then navigate to your widget to see an overview of its analytics.
+
+The metrics show changes in the solve rate, widget traffic, and top actions for your widget.
+
+
+
+Refer to the pages below for more information about Turnstile Analytics:
+
+
\ No newline at end of file
diff --git a/src/content/docs/turnstile/turnstile-analytics/token-validation.mdx b/src/content/docs/turnstile/turnstile-analytics/token-validation.mdx
new file mode 100644
index 00000000000000..264db26da83a84
--- /dev/null
+++ b/src/content/docs/turnstile/turnstile-analytics/token-validation.mdx
@@ -0,0 +1,24 @@
+---
+title: Token validation
+pcx_content_type: concept
+sidebar:
+ order: 3
+---
+
+import { Render } from "~/components"
+
+After a visitor successfully completes a Turnstile challenge, a token is generated and validated via the siteverify API. Token validation data provides crucial insights into your security posture.
+
+For example, the token validation values in your analytics may look like this:
+
+
+
+## Metrics
+
+- **Siteverify requests**: The total number of requests made to the siteverify API in the given timeframe.
+- **Valid tokens**: The number of siteverify requests with `success:true` responses.
+- **Invalid tokens**: The number of siteverify requests with `success:false` responses.
+
+### Call siteverify
+
+
\ No newline at end of file
diff --git a/src/content/partials/turnstile/siteverify.mdx b/src/content/partials/turnstile/siteverify.mdx
new file mode 100644
index 00000000000000..84e05cec455cc9
--- /dev/null
+++ b/src/content/partials/turnstile/siteverify.mdx
@@ -0,0 +1,10 @@
+---
+{}
+
+---
+
+It is important to [call the siteverify API](/turnstile/get-started/server-side-validation/). Without calling siteverify API to validate the tokens, your website or application is not protected. Skipping token validation means you cannot confirm the visitor's legitimacy.
+
+- Tokens can only be redeemed once. Even valid tokens will return `success:false` if they are reused, preventing token theft and replay attacks.
+- Tokens expire after five minutes. Validation must occur within this window to be effective.
+- Tokens can be invalid. Bots might complete challenges, but Cloudflare can detect bot-like signals and mark the token as invalid.
\ No newline at end of file