Merge pull request #417 from checkly/docs/ahrefs-p0-p1-link-fixes

Fix broken & stale internal links from Ahrefs site audit (P0 + P1)

Author: Dgiordano33

ai/rocky-ai.mdx

@@ -29,7 +29,7 @@ When your invocation quota is reached, no overages are charged. Invocations refr
 ## Data Privacy and Security
 
 - All AI features are designed to operate on the data you provide or the data generated by your checks. This data is already stored in Checkly, and we do not send any additional data to third-party AI providers.
-- Any provided [environment secrets](https://www.checklyhq.com/docs/api-checks/variables/) are scrubbed before being sent to the AI provider.
+- Any provided [environment secrets](/platform/variables) are scrubbed before being sent to the AI provider.
 - We do not train any custom models on your data.
 - Any data used by the AI features is processed in real-time and not stored for future training.
 

comparisons/frameworks/playwright-vs-cypress.mdx

@@ -87,7 +87,7 @@ The architectural differences between Playwright and Cypress reflect distinct de
 ### **Impact of Architectural Differences**
 
 1. **Browser and Platform Support**  
-   - Playwright supports all modern browsers (Chromium, Firefox, WebKit) and can run on multiple operating systems with little configuration (sidenote: Checkly currently supports using Chromium or Chrome with Playwright Test and Playwright library, with Chromium being the default browser for all checks. [Read more about using Chrome](https://www.checklyhq.com/docs/browser-checks/#using-other-browsers)).
+   - Playwright supports all modern browsers (Chromium, Firefox, WebKit) and can run on multiple operating systems with little configuration (sidenote: Checkly currently supports using Chromium or Chrome with Playwright Test and Playwright library, with Chromium being the default browser for all checks. [Read more about using Chrome](/detect/synthetic-monitoring/browser-checks/overview#using-other-browsers)).
    - Cypress, with its Electron-based architecture, requires adaptation for each browser and does not support Safari or tabs.
 
 2. **Testing Flexibility**  
@@ -174,7 +174,7 @@ Further, Cypress asynchrony may not act as expected if we're used to asynchrony
 
 ### Playwright Pros  
 - Supports more browsers, including Firefox and Safari/WebKit  
-- Suitable for complex web apps with [API](https://www.checklyhq.com/learn/playwright/testing-apis/), UI, and [visual testing](https://www.checklyhq.com/docs/browser-checks/visual-regression-snapshot-testing/) combined  
+- Suitable for complex web apps with [API](https://www.checklyhq.com/learn/playwright/testing-apis/), UI, and [visual testing](/detect/synthetic-monitoring/browser-checks/visual-regressions) combined  
 - Superior parallelism and scalability for larger test suites  
 - Works on multiple platforms  
 

constructs/multistep-check.mdx

@@ -15,7 +15,7 @@ Before creating Multistep Checks, ensure you have:
 
 - An initialized Checkly CLI project
 - Public endpoints you want to monitor
-- Runtime `2023.09` or later (Multistep Checks require [newer runtimes](platform/runtimes/runtime-specification))
+- Runtime `2023.09` or later (Multistep Checks require [newer runtimes](/platform/runtimes/runtime-specification))
 
 For additional setup information, see [CLI overview](/cli/overview).
 </Accordion>

detect/overview.mdx

@@ -34,7 +34,7 @@ Run automated Playwright tests to validate functionality and user workflows befo
 <Step title="Add Monitors to your project">
 Start with the monitoring approach that best fits your immediate needs:
 - Create them inside the Checkly UI
-- Create them in your repository as [constructs](/constructs)
+- Create them in your repository as [constructs](/constructs/overview)
 </Step>
 
 <Step title="Configure Locations, Frequency, and Alerting">

detect/synthetic-monitoring/api-checks/openapi-spec.mdx

@@ -63,7 +63,7 @@ You can assert on different sources. These could be:
 - A specific response header
 - A specific response time
 
-[Read more about assertions](assertions)
+[Read more about assertions](/detect/assertions)
 
 ### Scheduling & locations
 

detect/synthetic-monitoring/api-checks/quickstart.mdx

@@ -48,7 +48,7 @@ You can assert on different sources. These could be:
 - A specific response header
 - A specific response time
 
-[Read more about assertions](assertions)
+[Read more about assertions](/detect/assertions)
 
 ### Scheduling & locations
 

detect/synthetic-monitoring/api-checks/response-limits.mdx

@@ -17,7 +17,7 @@ You can set two thresholds:
 The benefit of using the degraded state is that it does not affect your check's success ratio like a failed state does. 
 
 You can enable alerts to be send when an API checks is degraded. This way you are notified of possible problems before things
-get out of hand. See [alerting](/communicate/alerts/) for more details.
+get out of hand. See [alerting](/communicate/alerts/overview) for more details.
 
 
 > All API checks are hard capped at a timeout of **30 seconds**, this means the **"Fail at"** threshold has a maximum value of 30 seconds.

detect/synthetic-monitoring/api-checks/setup-and-teardown.mdx

@@ -11,7 +11,7 @@ Setup and teardown scripts execute arbitrary JavaScript/TypeScript code before a
 Both script types have access to environment variables, runtime objects like `request` and `response`, and popular npm packages
 like `moment`, `axios`, and `lodash`.
 
-To get the most power out of API checks with setup and teardown scripts, we advise using [the Checkly CLI](/cli).
+To get the most power out of API checks with setup and teardown scripts, we advise using [the Checkly CLI](/cli/overview).
 You can also use them [via the web UI](#using-setup-and-teardown-scripts-via-the-ui).
 
 > Setup and teardown scripts have a **maximum execution time of 10 seconds** each.

detect/synthetic-monitoring/browser-checks/overview.mdx

@@ -104,7 +104,7 @@ test('User login workflow', async ({ page }) => {
 
 </Tabs>
 <Info>
-To learn more about Playwright, see the our [Playwright documentation](/learn/playwright).
+To learn more about Playwright, see the our [Playwright documentation](/learn/playwright/overview).
 </Info>
 
 ## Browser Check Results

detect/synthetic-monitoring/browser-checks/playwright-support.mdx

@@ -149,7 +149,7 @@ the check is passing or failing. For scheduled check runs videos are only preser
 
 ## PageObject Model (POM)
 
-If you are structuring your test codebase following the [PageObject pattern](https://martinfowler.com/bliki/PageObject.html), you can use the [Checkly CLI](/cli) out of the box. Just make sure that:
+If you are structuring your test codebase following the [PageObject pattern](https://martinfowler.com/bliki/PageObject.html), you can use the [Checkly CLI](/cli/overview) out of the box. Just make sure that:
 
 - the folder you initialize your CLI in when building your project sits above your test spec files and their dependencies
 - your `testMatch` is pointing to the path(s) where your test specs live