First batch of changes

RebeccaTamachiro · RebeccaTamachiro · commit 672914a68548 · 2025-10-28T10:05:49.000Z
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/certificate-transparency-monitoring.mdx b/src/content/docs/ssl/edge-certificates/additional-options/certificate-transparency-monitoring.mdx
@@ -36,7 +36,7 @@ CT Monitoring alerts are triggered not only by Cloudflare processes - including
 
 ## Opt in and out
 
-Alerts are turned off by default. If you want to receive alerts, go to [**SSL/TLS** > **Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates#ct-alerting-card) and enable **Certificate Transparency Monitoring**. If you are in a Business or Enterprise zone, select **Add Email**.
+Alerts are turned off by default. If you want to receive alerts, go to the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates#ct-alerting-card) page and enable **Certificate Transparency Monitoring**. If you are in a Business or Enterprise zone, select **Add Email**.
 
 To stop receiving alerts, disable **Certificate Transparency Monitoring** or remove your email from the feature card.
 
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/index.mdx b/src/content/docs/ssl/edge-certificates/additional-options/index.mdx
@@ -10,6 +10,6 @@ sidebar:
 
 import { DirectoryListing } from "~/components"
 
-Once you set up SSL/TLS on your application, you can adjust the following settings in **SSL/TLS** > **Edge Certificates**:
+Once you set up SSL/TLS on your application, you can adjust the following settings on the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page:
 
 <DirectoryListing />
diff --git a/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx b/src/content/docs/ssl/edge-certificates/advanced-certificate-manager/manage-certificates.mdx
@@ -8,29 +8,31 @@ description: Learn how to create, delete and perform other operations to manage
   your Cloudflare Advanced SSL certificates.
 ---
 
-import { AvailableNotifications, Render, TabItem, Tabs } from "~/components";
+import { AvailableNotifications, Render, TabItem, Tabs, DashButton } from "~/components";
 
 ## Create a certificate
 
 If you are using an existing [Universal SSL certificate](/ssl/edge-certificates/universal-ssl/), Cloudflare will automatically replace this certificate once you finish ordering your advanced certificate.
 
-Once you order a certificate, you can review the [certificate's status](/ssl/reference/certificate-statuses/) in the dashboard at **SSL/TLS** > **Edge Certificates** or via the API with a [GET request](/api/resources/ssl/subresources/certificate_packs/methods/list/).
+Once you order a certificate, you can review the [certificate's status](/ssl/reference/certificate-statuses/) on the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page or via the API with a [GET request](/api/resources/ssl/subresources/certificate_packs/methods/list/).
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
 To create a new advanced certificate in the dashboard:
 
-1. Log in to your Cloudflare account and select a domain.
-2. Go to **SSL/TLS** > **Edge Certificates**.
-3. Select **Order Advanced Certificate**.
-4. If Cloudflare does not have your billing information, you will need to enter that information.
-5. Enter the following information:
+1. In the Cloudflare dashboard, go to the **Edge Certificates** page.
+
+   <DashButton url="/?to=/:account/:zone/ssl-tls/edge-certificates" />
+
+2. Select **Order Advanced Certificate**.
+3. If Cloudflare does not have your billing information, you will need to enter that information.
+4. Enter the following information:
    - Certificate authority
    - Certificate hostnames
      - For hostnames longer than 64 characters, use the API.
    - Validation method
    - Certificate validity period
-6. Select **Save**.
+5. Select **Save**.
 
 </TabItem> <TabItem label="API">
 
@@ -54,10 +56,12 @@ If you need certificates for hostnames longer than 64 characters ([RFC 5280](htt
 
 To delete an advanced certificate in the dashboard:
 
-1. Log in to your Cloudflare account and select a domain.
-2. Select **SSL/TLS** > **Edge Certificates**.
-3. Select a certificate.
-4. Select **Delete Certificate**.
+1. In the Cloudflare dashboard, go to the **Edge Certificates** page.
+
+   <DashButton url="/?to=/:account/:zone/ssl-tls/edge-certificates" />
+
+2. Select a certificate.
+3. Select **Delete Certificate**.
 
 </TabItem> <TabItem label="API">
 
diff --git a/src/content/docs/ssl/edge-certificates/caa-records.mdx b/src/content/docs/ssl/edge-certificates/caa-records.mdx
@@ -5,7 +5,7 @@ sidebar:
   order: 6
 ---
 
-import { Render, TabItem, Tabs } from "~/components";
+import { Render, TabItem, Tabs, DashButton } from "~/components";
 
 <Render file="caa-records-definition" product="ssl" /> <br />
 
@@ -38,15 +38,17 @@ Create a CAA record for each Certificate Authority (CA) that you plan to use for
 
 To add a CAA record in the dashboard,
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and application.
-2. Go to **DNS** > **Records**.
-3. Select **Add record**.
-4. For **Type**, select **CAA**.
-5. For **Name**, type your domain.
-6. Choose a **Tag**, which specifies the behavior associated with the record.
-7. For **CA domain name**, enter the CA name.
-8. Select **Save**.
-9. Repeat for each CA associated with your domain.
+1. In the Cloudflare dashboard, go to the **DNS Records** page.
+
+   <DashButton url="/?to=/:account/:zone/dns/records" />
+
+2. Select **Add record**.
+3. For **Type**, select **CAA**.
+4. For **Name**, type your domain.
+5. Choose a **Tag**, which specifies the behavior associated with the record.
+6. For **CA domain name**, enter the CA name.
+7. Select **Save**.
+8. Repeat for each CA associated with your domain.
 
 </TabItem> <TabItem label="API">
 
diff --git a/src/content/docs/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv.mdx b/src/content/docs/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv.mdx
@@ -45,7 +45,7 @@ As explained in the [announcement blog post](https://blog.cloudflare.com/introdu
 To set up Delegated DCV:
 
 1. Order an [advanced certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/) for your zone, choosing `TXT` as the **Certificate validation method**.
-2. On **SSL/TLS** > **Edge Certificates**, go to **DCV Delegation for Partial Zones**.
+2. On the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page, go to **DCV Delegation for Partial Zones**.
 3. Copy the Cloudflare validation URL.
 4. At your authoritative DNS provider, create `CNAME` record(s) considering the following:
 
diff --git a/src/content/docs/ssl/edge-certificates/changing-dcv-method/methods/index.mdx b/src/content/docs/ssl/edge-certificates/changing-dcv-method/methods/index.mdx
@@ -30,7 +30,7 @@ For guidance on when you need to perform DCV, refer to [Domain Control Validatio
 
 ## Verify DCV status
 
-To verify the [DCV status](/ssl/reference/certificate-statuses/) of a certificate, either monitor the certificate's status in the dashboard at **SSL/TLS** > **Edge Certificates** or use the [Verification Status endpoint](/api/resources/ssl/subresources/verification/methods/get/).
+To verify the [DCV status](/ssl/reference/certificate-statuses/) of a certificate, either monitor the certificate's status on the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page or use the [Verification Status endpoint](/api/resources/ssl/subresources/verification/methods/get/).
 
 A status of `active` means that the certificate has been deployed to Cloudflare’s global network and will be served as soon as HTTP traffic is proxied to Cloudflare.
 
diff --git a/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx b/src/content/docs/ssl/edge-certificates/custom-certificates/renewing.mdx
@@ -44,6 +44,6 @@ For example if you have a custom certificate made of an ECSDA and a RSA certific
 
 If you no longer want to use your custom certificate but still want your website or application to be covered with SSL/TLS, you can do the following:
 
-1. Go to [**SSL/TLS** > **Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates).
+1. Go to the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page.
 2. Make sure there is already an active [universal](/ssl/edge-certificates/universal-ssl/) or [advanced](/ssl/edge-certificates/advanced-certificate-manager/) certificate covering the same hostnames.
 3. Delete your custom certificate.
diff --git a/src/content/docs/ssl/edge-certificates/custom-certificates/troubleshooting.mdx b/src/content/docs/ssl/edge-certificates/custom-certificates/troubleshooting.mdx
@@ -99,7 +99,7 @@ If you try to upload a certificate **type** but have already reached your quota,
 
 **Solution**
 
-First, check your custom certificate entitlements at **SSL/TLS** > **Edge Certificates**.
+First, check your custom certificate entitlements on the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page.
 
 Then, when actually uploading or editing the certificate, make sure you select the appropriate option for **Legacy Client Support**.
 
diff --git a/src/content/docs/ssl/edge-certificates/custom-certificates/uploading.mdx b/src/content/docs/ssl/edge-certificates/custom-certificates/uploading.mdx
@@ -165,7 +165,7 @@ For more guidance, refer to [Create a CAA record](/ssl/edge-certificates/caa-rec
 
 ## Update an existing custom certificate
 
-Before you update an existing custom certificate, you might want to consider having active [universal](/ssl/edge-certificates/universal-ssl/) or [advanced](/ssl/edge-certificates/advanced-certificate-manager/) certificates as fallback options. Go to [**SSL/TLS** > **Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) to check a list of hostnames and status of the edge certificates in your zone.
+Before you update an existing custom certificate, you might want to consider having active [universal](/ssl/edge-certificates/universal-ssl/) or [advanced](/ssl/edge-certificates/advanced-certificate-manager/) certificates as fallback options. Go to the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page to check a list of hostnames and status of the edge certificates in your zone.
 
 If you are on an Enterprise plan and want to update a custom (modern) certificate, also consider requesting access to [Staging environment (Beta)](/ssl/edge-certificates/staging-environment/).
 
diff --git a/src/content/docs/ssl/edge-certificates/ech.mdx b/src/content/docs/ssl/edge-certificates/ech.mdx
@@ -8,6 +8,8 @@ sidebar:
 
 ---
 
+import { DashButton } from "~/components";
+
 ECH stands for [Encrypted Client Hello](https://datatracker.ietf.org/doc/draft-ietf-tls-esni/16/). It is a protocol extension in the context of Transport Layer Security (TLS). ECH encrypts part of the handshake and masks the Server Name Indication (SNI) that is used to negotiate a TLS session. This means that whenever a user visits a website on Cloudflare that has ECH enabled, intermediaries will be able to see that you are visiting a website on Cloudflare, but they will not be able to determine which one.
 
 ## What ECH does
@@ -47,10 +49,11 @@ For more details about ECH protocol technology, refer to our [introductory blog]
 
 ECH is enabled by default on Free zones. Other plans can turn it on or off following the steps below.
 
-1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com).
-2. Select your account and zone.
-3. Go to **SSL** > **Edge Certificates**.
-4. For **Encrypted ClientHello (ECH)**, change the setting to **Enabled**.
+1. In the Cloudflare dashboard, go to the **Edge Certificates** page.
+
+   <DashButton url="/?to=/:account/:zone/ssl-tls/edge-certificates" />
+
+2. For **Encrypted ClientHello (ECH)**, change the setting to **Enabled**.
 
 ## Enterprise network applicability
 
diff --git a/src/content/docs/ssl/edge-certificates/staging-environment.mdx b/src/content/docs/ssl/edge-certificates/staging-environment.mdx
@@ -6,7 +6,7 @@ sidebar:
 
 ---
 
-import { FeatureTable } from "~/components"
+import { FeatureTable, DashButton } from "~/components"
 
 Use your certificate staging environment to test new custom (modern) certificates before pushing them to your production environment. This process helps you solve potential certificate problems **before** there's an incident, such as when:
 
@@ -26,14 +26,17 @@ Use your certificate staging environment to test new custom (modern) certificate
 
 To upload custom (modern) certificates to your staging environment:
 
-1. Go to **SSL/TLS** > **Staging Certificates**.
+1. In the Cloudflare dashboard, go to the **Staging Certificates** page.
+
+   <DashButton url="/?to=/:account/:zone/ssl-tls/staging-certificates" />
+
 2. Select **Upload Custom Staging Certificate**.
 3. Upload your custom (modern) certificate ([detailed instructions](/ssl/edge-certificates/custom-certificates/uploading/)).
 4. Your certificate will appear in the dashboard with a status of **Staging Deployment**. If you refresh the page, its status should go to **Staging Active**.
 
 ### 2. Test certificate
 
-Test your custom (modern) certificate by sending `curl` requests to the IP addresses listed in the dashboard card at **SSL/TLS** > **Staging Certificates**:
+Test your custom (modern) certificate by sending `curl` requests to the IP addresses listed on the [**Staging Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/staging-certificates) page:
 
 ```txt
 curl --resolve <HOSTNAME>:<PORT>:<STAGING_IP> https://<HOSTNAME> -iv
@@ -49,7 +52,10 @@ You should confirm whether:
 
 Assuming there are no issues, push your custom (modern) certificate to your production environment:
 
-1. Go to **SSL/TLS** > **Staging Certificates**.
+1. In the Cloudflare dashboard, go to the **Staging Certificates** page.
+
+   <DashButton url="/?to=/:account/:zone/ssl-tls/staging-certificates" />
+
 2. Select a custom certificate.
 3. Select **Push to Production**.
 
@@ -59,7 +65,10 @@ If there were issues with your certificate, you can keep it in your staging envi
 
 If you roll out a custom (modern) certificate to production and encounter issues, you can deactivate that certificate to delete the certificate from the edge and then push the certificate back to your staging environment for additional testing:
 
-1. Go to **SSL/TLS** > **Edge Certificates**.
+1. In the Cloudflare dashboard, go to the **Edge Certificates** page.
+
+   <DashButton url="/?to=/:account/:zone/ssl-tls/edge-certificates" />
+
 2. Select a custom certificate.
 3. Select **Deactivate**.
 4. Select **Push to Staging**.
diff --git a/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx b/src/content/docs/ssl/edge-certificates/universal-ssl/disable-universal-ssl.mdx
@@ -5,7 +5,7 @@ sidebar:
   order: 3
 ---
 
-import { TabItem, Tabs } from "~/components";
+import { TabItem, Tabs, DashButton } from "~/components";
 
 Some customers may need to manage their own SSL certificates or rely on specific Certificate Authorities.
 
@@ -36,12 +36,13 @@ Before you disable Universal SSL/TLS, make sure you have [uploaded a custom cert
 
 To disable Universal SSL in the dashboard:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
-2. Select your domain.
-3. Go to **SSL/TLS** > **Edge Certificates**.
-4. For **Disable Universal SSL**, select **Disable Universal SSL**.
-5. Read the warnings in the **Acknowledgement**.
-6. Select **I Understand** and select **Confirm**.
+1. In the Cloudflare dashboard, go to the **Edge Certificates** page.
+
+   <DashButton url="/?to=/:account/:zone/ssl-tls/edge-certificates" />
+
+2. For **Disable Universal SSL**, select **Disable Universal SSL**.
+3. Read the warnings in the **Acknowledgement**.
+4. Select **I Understand** and select **Confirm**.
 
 </TabItem> <TabItem label="API">
 
@@ -55,10 +56,11 @@ To disable Universal SSL with the Cloudflare API, send a [`PATCH`](/api/resource
 
 To re-enable Universal SSL in the dashboard:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
-2. Select your domain.
-3. Go to **SSL/TLS** > **Edge Certificates**.
-4. For **Disable Universal SSL**, select **Enable Universal SSL**.
+1. In the Cloudflare dashboard, go to the **Edge Certificates** page.
+
+   <DashButton url="/?to=/:account/:zone/ssl-tls/edge-certificates" />
+
+2. For **Disable Universal SSL**, select **Enable Universal SSL**.
 
 </TabItem> <TabItem label="API">
 
diff --git a/src/content/docs/ssl/edge-certificates/universal-ssl/enable-universal-ssl.mdx b/src/content/docs/ssl/edge-certificates/universal-ssl/enable-universal-ssl.mdx
@@ -44,7 +44,7 @@ Unless you cover and validate multiple subdomains with an [advanced certificate]
 
 ## Verify your certificate is active
 
-Once you enable Universal SSL, you can review the [activation status](/ssl/reference/certificate-statuses/) in the dashboard at **SSL/TLS** > **Edge Certificates** or via the API with a [GET request](/api/resources/ssl/subresources/certificate_packs/methods/list/).
+Once you enable Universal SSL, you can review the [activation status](/ssl/reference/certificate-statuses/) on the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page or via the API with a [GET request](/api/resources/ssl/subresources/certificate_packs/methods/list/).
 
 ---
 
