fix: seo updates and fixes [sc-00]

site/content/docs/traces-open-telemetry/exporting-traces/dash0.md

@@ -8,6 +8,8 @@ menu:
   platform:
     parent: Export traces to 3rd party tools with Checkly - Checkly Docs
 beta: true
+aliases:
+  - "/docs/open-telemetry/exporting-traces/dash0/"
 ---
 
 1. Create an API key in the **Settings** > **Auth Tokens** section.

site/content/learn/playwright/playwright-vs-cypress.md

@@ -23,7 +23,7 @@ While Cypress is a testing tool, Playwright is an automation solution.
 
 This distinction is important when you compare these solutions to the present day realities of automation.
 
-Playwright is a tool focused on developer productivity with more robust built-in features, the ability to use async/await, built in parallelization, a much lighter weight in CI. Playwright is also less opinionated because it doesn’t have to be, you can use it however you want. Playwright can [monitor your APIs](https://www.checklyhq.com/blog/test-apis-with-playwright/) just as well as it can your frontend web pages. Scraping content for a LLM model? Check! Have a nested app in an iframe you want to test? Go wild! *Three different browser sessions in the same chat instance? Sounds cool! Re-use your tests to monitor production? Absolutely.*
+Playwright is a tool focused on developer productivity with more robust built-in features, the ability to use async/await, built in parallelization, a much lighter weight in CI. Playwright is also less opinionated because it doesn’t have to be, you can use it however you want. Playwright can [monitor your APIs](https://www.checklyhq.com/learn/playwright/testing-apis/) just as well as it can your frontend web pages. Scraping content for a LLM model? Check! Have a nested app in an iframe you want to test? Go wild! *Three different browser sessions in the same chat instance? Sounds cool! Re-use your tests to monitor production? Absolutely.*
 
 ## Playwright Key Features
 - Supports multiple languages: JavaScript, TypeScript, Python, Java, C#

site/content/learn/playwright/steps-decorators.md

@@ -33,7 +33,7 @@ Let me show you how you can replace repetitive `test.step` calls with a single
 
 By default, all your test actions and assertions will be a long wall of instructions shown in UI mode or your test reports. That's not a big deal for twenty instructions, but if you're testing a complex UI flow, your test instruction count will quickly hit a hundred actions. Looking at a report with that many instructions isn't great.
 
-![way too many lines on a top level playwright report](/samples/images/steps1.png)
+![way too many lines on a top level playwright report](/samples/images/steps1.webp)
 
 To solve this problem, you can group your actions in Playwright test steps.
 
@@ -79,7 +79,7 @@ test('Customer is able to create account', async ({
 
 Look at this beautiful and well-structured HTML test report. I'm a fan!
 
-![much nicer html test report](/samples/images/steps2.png)
+![much nicer html test report](/samples/images/steps2.webp)
 
 You might now ask, "Does this work when you implement POMs ([Page Object Model](https://playwright.dev/docs/pom))?".