diff --git a/src/content/docs/workers/ci-cd/builds/index.mdx b/src/content/docs/workers/ci-cd/builds/index.mdx
index fa8c4e8da9f60de..7f3fb2498cbac05 100644
--- a/src/content/docs/workers/ci-cd/builds/index.mdx
+++ b/src/content/docs/workers/ci-cd/builds/index.mdx
@@ -3,10 +3,10 @@ pcx_content_type: concept
 title: Builds
 description: Use Workers Builds to integrate with Git and automatically build and deploy your Worker when pushing a change
 sidebar:
-  group:
     badge:
       text: Beta
 ---
+import { DashButton } from "~/components";
 
 The Cloudflare [Git integration](/workers/ci-cd/builds/git-integration/) lets you connect a new or existing Worker to a GitHub or GitLab repository, enabling automated builds and deployments for your Worker on push.
 
@@ -15,9 +15,12 @@ The Cloudflare [Git integration](/workers/ci-cd/builds/git-integration/) lets yo
 ### Connect a new Worker
 
 To create a new Worker and connect it to a GitHub or GitLab repository:
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to **Workers & Pages**.
-3. Select **Create**.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
+2. Select **Create application**.
+3. Select **Get started** next to **Import a repository**.
 4. Under **Import a repository**, select a **Git account**.
 5. Select the repository you want to import from the list. You can also use the search bar to narrow the results.
 6. Configure your project and select **Save and Deploy**.
@@ -26,12 +29,14 @@ To create a new Worker and connect it to a GitHub or GitLab repository:
 ### Connect an existing Worker
 
 To connect an existing Worker to a GitHub or GitLab repository:
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to **Workers & Pages**.
-3. Select the Worker you want to connect to a repository.
-4. Select **Settings** and then **Builds**.
-5. Select **Connect** and follow the prompts to connect the repository to your Worker and configure your [build settings](/workers/ci-cd/builds/configuration/).
-6. Push a commit to your Git repository to trigger a build and deploy to your Worker.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
+2. Select the Worker you want to connect to a repository.
+3. Select **Settings** and then **Builds**.
+4. Select **Connect** and follow the prompts to connect the repository to your Worker and configure your [build settings](/workers/ci-cd/builds/configuration/).
+5. Push a commit to your Git repository to trigger a build and deploy to your Worker.
 
 :::caution
 
@@ -54,9 +59,11 @@ If a build succeeds, it is uploaded as a version. If the build is configured to
 ## Disconnecting builds
 
 To disconnect a Worker from a GitHub or GitLab repository:
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to **Workers & Pages**.
-3. Select the Worker you want to disconnect from a repository.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
+2. Select the Worker you want to disconnect from a repository.
 4. Select **Settings** and then **Builds**.
 5. Select **Disconnect**.
 
diff --git a/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx b/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx
index b2a5df906d37e3c..2d2e915ca6c60aa 100644
--- a/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx
+++ b/src/content/docs/workers/ci-cd/external-cicd/gitlab-cicd.mdx
@@ -3,6 +3,7 @@ pcx_content_type: how-to
 title: GitLab CI/CD
 description: Integrate Workers development into your existing GitLab Pipelines workflows.
 ---
+import { DashButton } from "~/components";
 
 You can deploy Workers with [GitLab CI/CD](https://docs.gitlab.com/ee/ci/pipelines/index.html). Here is how you can set up your GitHub Actions workflow.
 
@@ -18,11 +19,13 @@ To find your Cloudflare account ID, refer to [Find account and zone IDs](/fundam
 
 To create an API token to authenticate Wrangler in your CI job:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. Select **My Profile** > **API Tokens**.
-3. Select **Create Token** > find **Edit Cloudflare Workers** > select **Use Template**.
-4. Customize your token name.
-5. Scope your token.
+1. In the Cloudflare dashboard, go to the **Account API tokens** page.
+
+   <DashButton url="/?to=/:account/api-tokens" />
+
+2. Select **Create Token** > find **Edit Cloudflare Workers** > select **Use Template**.
+3. Customize your token name.
+4. Scope your token.
 
 You will need to choose the account and zone resources that the generated API token will have access to. We recommend scoping these down as much as possible to limit the access of your token. For example, if you have access to three different Cloudflare accounts, you should restrict the generated API token to only the account on which you will be deploying a Worker.
 
diff --git a/src/content/docs/workers/configuration/integrations/momento.mdx b/src/content/docs/workers/configuration/integrations/momento.mdx
index a25c05e7217b442..331bc83e1944a0f 100644
--- a/src/content/docs/workers/configuration/integrations/momento.mdx
+++ b/src/content/docs/workers/configuration/integrations/momento.mdx
@@ -3,6 +3,7 @@ pcx_content_type: configuration
 title: Momento
 
 ---
+import { DashButton } from "~/components";
 
 [Momento](https://gomomento.com/) is a truly serverless caching service. It automatically optimizes, scales, and manages your cache for you.
 
@@ -18,14 +19,16 @@ To set up an integration with Momento Cache:
 
 3. Add the Momento database integration to your Worker:
 
-   1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-   2. In **Account Home**, select **Workers & Pages**.
-   3. In **Overview**, select your Worker.
-   4. Select **Integrations** > **Momento**.
-   5. Follow the setup flow, review and grant permissions needed to add secrets to your Worker.
-   6. Next, connect to Momento.
-   7. Select a preferred region.
-   8. Click **Add integration**.
+   1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+      <DashButton url="/?to=/:account/workers-and-pages" />
+
+   2. In **Overview**, select your Worker.
+   3. Select **Integrations** > **Momento**.
+   4. Follow the setup flow, review and grant permissions needed to add secrets to your Worker.
+   5. Next, connect to Momento.
+   6. Select a preferred region.
+   7. Click **Add integration**.
 
 4. The following example code show how to set an item in your cache, get it, and return it as a JSON object. The credentials needed to connect to Momento Cache have been automatically added as [secrets](/workers/configuration/secrets/) to your Worker through the integration.
 
diff --git a/src/content/docs/workers/configuration/previews.mdx b/src/content/docs/workers/configuration/previews.mdx
index e55304a9c600d8c..01b42f47a203567 100644
--- a/src/content/docs/workers/configuration/previews.mdx
+++ b/src/content/docs/workers/configuration/previews.mdx
@@ -8,7 +8,7 @@ sidebar:
 description: Preview URLs allow you to preview new versions of your project without deploying it to production.
 ---
 
-import { Render, WranglerConfig } from "~/components";
+import { Render, WranglerConfig, DashButton } from "~/components";
 
 # Overview
 
@@ -57,7 +57,11 @@ The [`wrangler versions upload`](/workers/wrangler/commands/#upload) command upl
 
 #### View versioned preview URLs on the Workers dashboard
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/workers) and select your project.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
+2. Select your Worker.
 2. Go to the **Deployments** tab, and find the version you would like to view.
 
 ### Aliased preview URLs
@@ -93,12 +97,13 @@ The resulting alias would be associated with this version, and immediately avail
 When enabled, all preview URLs are available publicly. You can use [Cloudflare Access](/cloudflare-one/policies/access/) to require visitors to authenticate before accessing preview URLs. You can limit access to yourself, your teammates, your organization, or anyone else you specify in your [access policy](/cloudflare-one/policies/access).
 
 To limit your preview URLs to authorized emails only:
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
-1. Log in to the [Cloudflare Access dashboard](https://one.dash.cloudflare.com/?to=/:account/access/apps).
-2. Select your account.
-3. Add an application.
-4. Select **Self Hosted**.
-5. Name your application (for example, "my-worker") and add your `workers.dev` subdomain as the **Application domain**.
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
+2. Select **Create application**.
+3. Select **Self Hosted**.
+4. Name your application (for example, "my-worker") and add your `workers.dev` subdomain as the **Application domain**.
 
 For example, if you want to secure preview URLs for a Worker running on `my-worker.my-subdomain.workers.dev`.
 
@@ -126,9 +131,11 @@ Note:
 ### From the Dashboard
 
 To toggle Preview URLs for a Worker:
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+   <DashButton url="/?to=/:account/workers-and-pages" />
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to **Workers & Pages** and in **Overview**, select your Worker.
+2. In **Overview**, select your Worker.
 3. Go to **Settings** > **Domains & Routes**.
 4. For Preview URLs, click **Enable** or **Disable**.
 5. Confirm your action.
diff --git a/src/content/docs/workers/configuration/routing/workers-dev.mdx b/src/content/docs/workers/configuration/routing/workers-dev.mdx
index 964660b9059c73d..f5157913a6a25df 100644
--- a/src/content/docs/workers/configuration/routing/workers-dev.mdx
+++ b/src/content/docs/workers/configuration/routing/workers-dev.mdx
@@ -3,7 +3,7 @@ pcx_content_type: concept
 title: workers.dev
 ---
 
-import { WranglerConfig } from "~/components";
+import { WranglerConfig, DashButton } from "~/components";
 
 Cloudflare Workers accounts come with a `workers.dev` subdomain that is configurable in the Cloudflare dashboard. Your `workers.dev` subdomain allows you getting started quickly by deploying Workers without first onboarding your custom domain to Cloudflare.
 
@@ -13,9 +13,11 @@ It's recommended to run production Workers on a [Workers route or custom domain]
 
 `workers.dev` subdomains take the format: `<YOUR_ACCOUNT_SUBDOMAIN>.workers.dev`. To change your `workers.dev` subdomain:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Select **Workers & Pages**.
-3. Select **Change** next to **Your subdomain**.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
+2. Select **Change** next to **Your subdomain**.
 
 All Workers are assigned a `workers.dev` route when they are created or renamed following the syntax `<YOUR_WORKER_NAME>.<YOUR_SUBDOMAIN>.workers.dev`. The [`name`](/workers/wrangler/configuration/#inheritable-keys) field in your Worker configuration is used as the subdomain for the deployed Worker.
 
@@ -25,8 +27,11 @@ All Workers are assigned a `workers.dev` route when they are created or renamed
 
 To disable the `workers.dev` route for a Worker:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to **Workers & Pages** and in **Overview**, select your Worker.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
+2. In **Overview**, select your Worker.
 3. Go to **Settings** > **Domains & Routes**.
 4. On `workers.dev` click "Disable".
 5. Confirm you want to disable.
diff --git a/src/content/docs/workers/configuration/secrets.mdx b/src/content/docs/workers/configuration/secrets.mdx
index 984aff4e32a9508..5bbb777454ec658 100644
--- a/src/content/docs/workers/configuration/secrets.mdx
+++ b/src/content/docs/workers/configuration/secrets.mdx
@@ -5,7 +5,7 @@ head: []
 description: Store sensitive information, like API keys and auth tokens, in your Worker.
 ---
 
-import { Render } from "~/components";
+import { Render,DashButton } from "~/components";
 
 ## Background
 
@@ -66,14 +66,15 @@ npx wrangler versions secret put <KEY>
 #### Via the dashboard
 
 To add a secret via the dashboard:
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
-1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
-2. Select **Workers & Pages**.
-3. In **Overview**, select your Worker > **Settings**.
-4. Under **Variables and Secrets**, select **Add**.
-5. Select the type **Secret**, input a **Variable name**, and input its **Value**. This secret will be made available to your Worker but the value will be hidden in Wrangler and the dashboard.
-6. (Optional) To add more secrets, select **Add variable**.
-7. Select **Deploy** to implement your changes.
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
+2. In **Overview**, select your Worker > **Settings**.
+3. Under **Variables and Secrets**, select **Add**.
+4. Select the type **Secret**, input a **Variable name**, and input its **Value**. This secret will be made available to your Worker but the value will be hidden in Wrangler and the dashboard.
+5. (Optional) To add more secrets, select **Add variable**.
+6. Select **Deploy** to implement your changes.
 
 ### Delete secrets from your project
 
@@ -97,13 +98,15 @@ npx wrangler versions secret delete <KEY>
 
 To delete a secret from your Worker project via the dashboard:
 
-1. Log in to [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
-2. Select **Workers & Pages**.
-3. In **Overview**, select your Worker > **Settings**.
-4. Under **Variables and Secrets**, select **Edit**.
-5. In the **Edit** drawer, select **X** next to the secret you want to delete.
-6. Select **Deploy** to implement your changes.
-7. (Optional) Instead of using the edit drawer, you can click the delete icon next to the secret.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
+2. In **Overview**, select your Worker > **Settings**.
+3. Under **Variables and Secrets**, select **Edit**.
+4. In the **Edit** drawer, select **X** next to the secret you want to delete.
+5. Select **Deploy** to implement your changes.
+6. (Optional) Instead of using the edit drawer, you can click the delete icon next to the secret.
 
 <Render file="env_and_secrets" product="workers" />
 
diff --git a/src/content/docs/workers/configuration/smart-placement.mdx b/src/content/docs/workers/configuration/smart-placement.mdx
index 13f448cd4862ace..cba6b7f264ce409 100644
--- a/src/content/docs/workers/configuration/smart-placement.mdx
+++ b/src/content/docs/workers/configuration/smart-placement.mdx
@@ -9,7 +9,7 @@ sidebar:
     text: Beta
 ---
 
-import { WranglerConfig } from "~/components";
+import { WranglerConfig, DashButton } from "~/components";
 
 By default, [Workers](/workers/) and [Pages Functions](/pages/functions/) are invoked in a data center closest to where the request was received. If you are running back-end logic in a Worker, it may be more performant to run that Worker closer to your back-end infrastructure rather than the end user. Smart Placement automatically places your workloads in an optimal location that minimizes latency and speeds up your applications.
 
@@ -64,13 +64,15 @@ To enable Smart Placement via Wrangler:
 
 To enable Smart Placement via the dashboard:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. In **Account Home**, select **Workers & Pages**.
-3. In **Overview**,select your Worker.
-4. Select **Settings** > **General**.
-5. Under **Placement**, choose **Smart**.
-6. Wait for Smart Placement to analyze your Worker. Smart Placement requires consistent traffic to the Worker from multiple locations around the world to make a placement decision. The analysis process may take up to 15 minutes.
-7. View your Worker's [request duration analytics](/workers/observability/metrics-and-analytics/#request-duration)
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
+2. In **Overview**,select your Worker.
+3. Select **Settings** > **General**.
+4. Under **Placement**, choose **Smart**.
+5. Wait for Smart Placement to analyze your Worker. Smart Placement requires consistent traffic to the Worker from multiple locations around the world to make a placement decision. The analysis process may take up to 15 minutes.
+6. View your Worker's [request duration analytics](/workers/observability/metrics-and-analytics/#request-duration)
 
 ## Observability
 
diff --git a/src/content/docs/workers/configuration/versions-and-deployments/rollbacks.mdx b/src/content/docs/workers/configuration/versions-and-deployments/rollbacks.mdx
index d5545da72fef2d5..9147ba883970e96 100644
--- a/src/content/docs/workers/configuration/versions-and-deployments/rollbacks.mdx
+++ b/src/content/docs/workers/configuration/versions-and-deployments/rollbacks.mdx
@@ -4,6 +4,7 @@ title: Rollbacks
 head: []
 description: Revert to an older version of your Worker.
 ---
+import { DashButton } from "~/components";
 
 You can roll back to a previously deployed [version](/workers/configuration/versions-and-deployments/#versions) of your Worker using [Wrangler](/workers/wrangler/commands/#rollback) or the Cloudflare dashboard. Rolling back to a previous version of your Worker will immediately create a new [deployment](/workers/configuration/versions-and-deployments/#deployments) with the version specified and become the active deployment across all your deployed routes and domains.
 
@@ -14,9 +15,11 @@ To roll back to a specified version of your Worker via Wrangler, use the [`wrang
 ## Via the Cloudflare Dashboard
 
 To roll back to a specified version of your Worker via the Cloudflare dashboard:
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/workers) and select your account.
-2. Go to **Workers & Pages** > select your Worker > **Deployments**.
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
+2. Select your Worker > **Deployments**.
 3. Select the three dot icon on the right of the version you would like to roll back to and select **Rollback**.
 
 :::caution
diff --git a/src/content/docs/workers/observability/errors.mdx b/src/content/docs/workers/observability/errors.mdx
index 8c1c3e3affe9b11..6b0e1cc3fc9fe8f 100644
--- a/src/content/docs/workers/observability/errors.mdx
+++ b/src/content/docs/workers/observability/errors.mdx
@@ -5,7 +5,7 @@ head: []
 description: Review Workers errors and exceptions.
 ---
 
-import { TabItem, Tabs } from "~/components";
+import { TabItem, Tabs, DashButton } from "~/components";
 
 Review Workers errors and exceptions.
 
@@ -230,10 +230,11 @@ Runtime errors will occur within the runtime, do not throw up an error page, and
 ## Identify errors: Workers Metrics
 
 To review whether your application is experiencing any downtime or returning any errors:
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. In **Account Home**, select **Workers & Pages**.
-3. In **Overview**, select your Worker and review your Worker's metrics.
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
+2. In **Overview**, select your Worker and review your Worker's metrics.
 
 ### Worker Errors
 
diff --git a/src/content/docs/workers/observability/logs/logpush.mdx b/src/content/docs/workers/observability/logs/logpush.mdx
index 2169bf3744718b5..c3a2c71bd6a3db3 100644
--- a/src/content/docs/workers/observability/logs/logpush.mdx
+++ b/src/content/docs/workers/observability/logs/logpush.mdx
@@ -9,7 +9,7 @@ sidebar:
 
 ---
 
-import { WranglerConfig } from "~/components";
+import { WranglerConfig, DashButton } from "~/components";
 
 [Cloudflare Logpush](/logs/logpush/) supports the ability to send [Workers Trace Event Logs](/logs/logpush/logpush-job/datasets/account/workers_trace_events/) to a [supported destination](/logs/logpush/logpush-job/enable-destinations/). Worker’s Trace Events Logpush includes metadata about requests and responses, unstructured `console.log()` messages and any uncaught exceptions. This product is available on the Workers Paid plan. For pricing information, refer to [Pricing](/workers/platform/pricing/#workers-trace-events-logpush).
 
@@ -28,10 +28,11 @@ Minimum required Wrangler version: 2.2.0. Check your version by running `wrangle
 :::
 
 To configure a Logpush job, verify that your Cloudflare account role can use Logpush. To check your role:
+1. In the Cloudflare dashboard, go to the **Members** page.
 
-1. Log in the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. Select your account and scroll down to **Manage Account** > **Members**.
-3. Check your account permissions. Roles with Logpush configuration access are different than Workers permissions. Super Administrators, Administrators, and the Log Share roles have full access to Logpush.
+   <DashButton url="/?to=/:account/members" />
+
+2. Check your account permissions. Roles with Logpush configuration access are different than Workers permissions. Super Administrators, Administrators, and the Log Share roles have full access to Logpush.
 
 Alternatively, create a new [API token](/fundamentals/api/get-started/create-token/) scoped at the Account level with Logs Edit permissions.
 
@@ -40,12 +41,13 @@ Alternatively, create a new [API token](/fundamentals/api/get-started/create-tok
 ### Via the Cloudflare dashboard
 
 To create a Logpush job in the Cloudflare dashboard:
+1. In the Cloudflare dashboard, go to the **Logpush** page.
+
+   <DashButton url="/?to=/:account/logs" />
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com), and select your account.
-2. Select **Analytics & Logs** > **Logpush**.
-3. Select **Create a Logpush job**.
-4. Select **Workers trace events** as the data set > **Next**.
-5. If needed, customize your data fields. Otherwise, select **Next**.
+2. Select **Create a Logpush job**.
+3. Select **Workers trace events** as the data set > **Next**.
+4. If needed, customize your data fields. Otherwise, select **Next**.
 
 6. Follow the instructions on the dashboard to verify ownership of your data's destination and complete job creation.
 
@@ -108,12 +110,13 @@ curl --request PUT \
 ### Dashboard
 
 To enable Logpush logging via the dashboard:
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+   <DashButton url="/?to=/:account/workers-and-pages" />
 
-1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Go to **Compute (Workers)**.
-3. Select your Worker.
-4. Go to **Settings** > **Observability**.
-5. For **Logpush**, select **Enable** (this is only available if you have already [created a logpush job](/workers/observability/logs/logpush/#create-a-logpush-job)).
+2. Select your Worker.
+3. Go to **Settings** > **Observability**.
+4. For **Logpush**, select **Enable** (this is only available if you have already [created a logpush job](/workers/observability/logs/logpush/#create-a-logpush-job)).
 
 ## Limits
 
diff --git a/src/content/docs/workers/observability/logs/workers-logs.mdx b/src/content/docs/workers/observability/logs/workers-logs.mdx
index 8d5b1c97be45d5b..e1844914b7d74d7 100644
--- a/src/content/docs/workers/observability/logs/workers-logs.mdx
+++ b/src/content/docs/workers/observability/logs/workers-logs.mdx
@@ -7,7 +7,7 @@ sidebar:
   order: 2
 ---
 
-import { TabItem, Tabs, Steps, Render, WranglerConfig } from "~/components";
+import { TabItem, Tabs, Steps, Render, WranglerConfig, DashButton } from "~/components";
 
 Workers Logs lets you automatically collect, store, filter, and analyze logging data emitted from Cloudflare Workers. Data is written to your Cloudflare Account, and you can query it in the dashboard for each of your Workers. All newly created Workers will come with the observability setting enabled by default.
 
@@ -56,14 +56,14 @@ You must add the observability setting for your Worker to write logs to Workers
 
 ## View logs from the dashboard
 
-Access logs for your Worker from the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/workers/services/view/:worker/production/observability/logs/).
+Access logs for your Worker from the Cloudflare dashboard:
 
-<Steps>
-	1. Log in to the [Cloudflare
-	dashboard](https://dash.cloudflare.com/?to=/:account/workers/services/view/:worker/production/observability/logs/)
-	and select your account. 2. In Account Home, go to **Workers & Pages**. 3. In
-	**Overview**, select your **Worker**. 4. Select **Logs**.
-</Steps>
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
+2. In **Overview**, select your **Worker**.
+3. Select **Logs**.
 
 ## Best Practices
 
diff --git a/src/content/docs/workers/observability/metrics-and-analytics.mdx b/src/content/docs/workers/observability/metrics-and-analytics.mdx
index 5b0915402cfcc23..e3752f2523c5925 100644
--- a/src/content/docs/workers/observability/metrics-and-analytics.mdx
+++ b/src/content/docs/workers/observability/metrics-and-analytics.mdx
@@ -9,7 +9,7 @@ description: Diagnose issues with Workers metrics, and review request data for a
 
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip, DashButton } from "~/components"
 
 There are two graphical sources of information about your Workers traffic at a given time: Workers metrics and zone-based Workers analytics.
 
@@ -21,9 +21,11 @@ Zone analytics show how much traffic all Workers assigned to a zone are handling
 
 Workers metrics aggregate request data for an individual Worker (if your Worker is running across multiple domains, and on `*.workers.dev`, metrics will aggregate requests across them). To view your Worker's metrics:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Select **Compute (Workers)**.
-3. In **Overview**, select your Worker to view its metrics.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
+2. In **Overview**, select your Worker to view its metrics.
 
 There are two metrics that can help you understand the health of your Worker in a given moment: requests success and error metrics, and invocation statuses.
 
@@ -63,9 +65,11 @@ The Duration per request chart shows historical [duration](/workers/platform/lim
 
 To review invocation statuses:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Select **Workers & Pages**.
-3. Select your Worker.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
+2. Select your Worker.
 4. Find the **Summary** graph in **Metrics**.
 5. Select **Errors**.
 
@@ -106,9 +110,11 @@ Worker metrics can be inspected for up to three months in the past in maximum in
 Zone analytics aggregate request data for all Workers assigned to any [routes](/workers/configuration/routing/routes/) defined for a zone.
 
 To review zone metrics:
+1. In the Cloudflare dashboard, go to the **Account home** page.
+
+   <DashButton url="/?to=/:account/home" />
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Select your site.
+2. Select your domain.
 3. In **Analytics & Logs**, select **Workers**.
 
 Zone data can be scoped by time range within the last 30 days. The dashboard includes charts and information described below.
diff --git a/src/content/docs/workers/observability/query-builder.mdx b/src/content/docs/workers/observability/query-builder.mdx
index ce95b6416e2fc36..2a2dd3060654a86 100644
--- a/src/content/docs/workers/observability/query-builder.mdx
+++ b/src/content/docs/workers/observability/query-builder.mdx
@@ -11,11 +11,13 @@ sidebar:
 
 ---
 
-import { TabItem, Tabs, Steps, Render, WranglerConfig, YouTube, Markdown } from "~/components"
+import { TabItem, Tabs, Render, WranglerConfig, YouTube, Markdown, DashButton, Steps } from "~/components"
 
 The Query Builder helps you write structured queries to investigate and visualize your telemetry data. The Query Builder searches the Workers Observability dataset, which currently includes all logs stored by [Workers Logs](/workers/observability/logs/workers-logs/).
 
-The Query Builder can be found in the [Workers' Observability tab in the Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/investigate/).
+The Query Builder can be found in the **Observability** page of the Cloudflare dashboard:
+
+<DashButton url="/?to=/:account/workers-and-pages/observability" />
 
 <YouTube id="nu4pTU8fR78" />
 
@@ -36,15 +38,16 @@ The Query Builder is available to all developers and requires no enablement. Que
 
 ## Write a query in the Cloudflare dashboard
 
-<Steps>
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/investigate/) and select your account.
-2. In Account Home, go to **Workers & Pages**.
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+   <DashButton url="/?to=/:account/workers-and-pages" />
+
+2. Select your Worker.
 3. Select **Observability** in the left-hand navigation panel, and then the **Investigate** tab.
 4. Select a **Visualization**.
 5. Optional: Add fields to Filter, Group By, Order By, and Limit. For more information, see what [composes a query](/workers/observability/query-builder/#query-composition).
 6. Optional: Select the appropriate time range.
 7. Select **Run**. The query will automatically run whenever changes are made.
-</Steps>
 
 ## Query composition
 
@@ -161,11 +164,13 @@ Queries can be starred by users. Starred queries are unique to the user, and not
 
 Saved queries can be deleted from the **Queries** tab. If you delete a query, the query is deleted for all users in the account.
 
-<Steps>
-1. Select the [Queries](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/queries) tab in the Observability dashboard.
-2. On the right-hand side, select the three dots for additional actions.
-3. Select **Delete Query** and follow the instructions.
-</Steps>
+1. In the Cloudflare dashboard, go to the **Observability** page.
+
+   <DashButton url="/?to=/:account/workers-and-pages/observability" />
+
+2. Select the **Queries** tab.
+3. On the right-hand side, select the three dots for additional actions.
+4. Select **Delete Query** and follow the instructions.
 
 ## Share queries
 
diff --git a/src/content/docs/workers/platform/limits.mdx b/src/content/docs/workers/platform/limits.mdx
index 43e03ccff1ab8f1..8f38c6314388e10 100644
--- a/src/content/docs/workers/platform/limits.mdx
+++ b/src/content/docs/workers/platform/limits.mdx
@@ -7,7 +7,7 @@ head: []
 description: Cloudflare Workers plan and platform limits.
 ---
 
-import { Render, WranglerConfig } from "~/components";
+import { Render, WranglerConfig, DashButton } from "~/components";
 
 ## Account plan limits
 
@@ -142,11 +142,13 @@ Cloudflare’s abuse protection methods do not affect well-intentioned traffic.
 
 You can also confirm if you have been rate limited by anti-abuse Worker Rate Limiting by logging into the Cloudflare dashboard, selecting your account and zone, and going to **Security** > **Events**. Find the event and expand it. If the **Rule ID** is `worker`, this confirms that it is the anti-abuse Worker Rate Limiting.
 
-The burst rate and daily request limits apply at the account level, meaning that requests on your `*.workers.dev` subdomain count toward the same limit as your zones. Upgrade to a [Workers Paid plan](https://dash.cloudflare.com/?account=workers/plans) to automatically lift these limits.
+The burst rate and daily request limits apply at the account level, meaning that requests on your `*.workers.dev` subdomain count toward the same limit as your zones.
 
 :::caution
 
-If you are currently being rate limited, upgrade to a [Workers Paid plan](https://dash.cloudflare.com/?account=workers/plans) to lift burst rate and daily request limits.
+If you are currently being rate limited, in the Cloudflare dashboard go to the **Workers plans** page to update to a Workers Paid plan to lift burst rate and daily request limits.
+
+<DashButton url="/?to=/:account/workers/plans" />
 
 :::
 
@@ -155,9 +157,11 @@ If you are currently being rate limited, upgrade to a [Workers Paid plan](https:
 Accounts using the Workers Free plan are subject to a burst rate limit of 1,000 requests per minute. Users visiting a rate limited site will receive a Cloudflare `1015` error page. However if you are calling your Worker programmatically, you can detect the rate limit page and handle it yourself by looking for HTTP status code `429`.
 
 Workers being rate-limited by Anti-Abuse Protection are also visible from the Cloudflare dashboard:
+1. In the Cloudflare dashboard, go to the **Security events** page.
+
+   <DashButton url="/?to=/:account/security-center/events" />
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and your website.
-2. Select **Security** > **Events** > scroll to **Sampled logs**.
+2. Scroll to **Sampled logs**.
 3. Review the log for a Web Application Firewall block event with a `ruleID` of `worker`.
 
 ### Daily request
@@ -181,9 +185,11 @@ Each [isolate](/workers/reference/how-workers-works/#isolates) of your Worker's
 When an isolate running your Worker exceeds 128 MB of memory, the Workers runtime handles this gracefully instead of failing immediately. It allows in-flight requests to complete while simultaneously creating a new isolate for your Worker for new requests. While this approach typically allows in-flight requests to complete, during periods of extremely high load, some incoming requests may be cancelled to maintain system stability.
 
 To view out-of-memory errors (OOM), as well as CPU limit overages:
+1. In the Cloudflare dashboard, go to the **Workers & Pages** page.
+
+   <DashButton url="/?to=/:account/workers-and-pages" />
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
-2. Select **Workers & Pages** and in **Overview**, select the Worker you would like to investigate.
+2. Select the Worker you would like to investigate.
 3. Under **Metrics**, select **Errors** > **Invocation Statuses** and examine **Exceeded Memory**.
 
 To avoid exceeding memory limits, where possible you should avoid buffering large objects or responses in memory, and instead use streaming APIs such as [`TransformStream`](/workers/runtime-apis/streams/transformstream/) or [`node:stream`](/workers/runtime-apis/nodejs/streams/) to stream responses. Manipulating streams allows you to avoid buffering entire responses in memory.
diff --git a/src/content/docs/workers/tutorials/generate-youtube-thumbnails-with-workers-and-images/index.mdx b/src/content/docs/workers/tutorials/generate-youtube-thumbnails-with-workers-and-images/index.mdx
index 524a6facf9c3c2d..f02d8b45483fcb9 100644
--- a/src/content/docs/workers/tutorials/generate-youtube-thumbnails-with-workers-and-images/index.mdx
+++ b/src/content/docs/workers/tutorials/generate-youtube-thumbnails-with-workers-and-images/index.mdx
@@ -10,7 +10,7 @@ tags:
   - Rust
 ---
 
-import { Render, PackageManagers, WranglerConfig } from "~/components";
+import { Render, PackageManagers, WranglerConfig, DashButton } from "~/components";
 
 In this tutorial, you will learn how to programmatically generate a custom YouTube thumbnail using Cloudflare Workers and Cloudflare Image Resizing. You may want to generate a custom YouTube thumbnail to customize the thumbnail's design, call-to-actions and images used to encourage more viewers to watch your video.
 
@@ -37,11 +37,12 @@ Cloudflare Images allows you to store, resize, optimize and deliver images in a
 ### Upload with the dashboard
 
 To upload an image using the Cloudflare dashboard:
+1. In the Cloudflare dashboard, go to the **Images** page.
 
-1. Log in to the [Cloudflare Dashboard](https://dash.cloudflare.com) and select your account.
-2. Select **Images**.
-3. Use **Quick Upload** to either drag and drop an image or click to browse and choose a file from your local files.
-4. After the image is uploaded, view it using the generated URL.
+   <DashButton url="/?to=/:account/images" />
+
+2. Use **Quick Upload** to either drag and drop an image or click to browse and choose a file from your local files.
+3. After the image is uploaded, view it using the generated URL.
 
 ### Upload with the API
 
diff --git a/src/content/docs/workers/wrangler/commands.mdx b/src/content/docs/workers/wrangler/commands.mdx
index ad2ea74057e142c..383044d7e36322a 100644
--- a/src/content/docs/workers/wrangler/commands.mdx
+++ b/src/content/docs/workers/wrangler/commands.mdx
@@ -17,6 +17,7 @@ import {
 	WranglerCommand,
 	WranglerNamespace,
 	PackageManagers,
+	DashButton,
 } from "~/components";
 
 Wrangler offers a number of commands to manage your Cloudflare Workers.
@@ -1260,8 +1261,10 @@ wrangler logout
 
 If you are using `CLOUDFLARE_API_TOKEN` instead of OAuth, and you can logout by deleting your API token in the Cloudflare dashboard:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/).
-2. Go to **My Profile** > **API Tokens**.
+1. In the Cloudflare dashboard, go to the **Account API tokens** page.
+
+   <DashButton url="/?to=/:account/api-tokens" />
+
 3. Select the three-dot menu on your Wrangler token.
 4. Select **Delete**.