Fix broken links

dcpena · dcpena · commit e6aab8efbe53 · 2025-05-28T16:39:56.000-05:00
diff --git a/src/content/docs/analytics/network-analytics/index.mdx b/src/content/docs/analytics/network-analytics/index.mdx
@@ -19,7 +19,7 @@ For a technical deep-dive into Network Analytics, refer to our [blog post](https
 
 ## Remarks
 
-* The Network Analytics logs refer to IP traffic of Magic Transit customer prefixes/leased IP addresses or Spectrum applications. These logs are not directly associated with the [zones](/fundamentals/accounts-and-zones/#zones) in your Cloudflare account.
+* The Network Analytics logs refer to IP traffic of Magic Transit customer prefixes/leased IP addresses or Spectrum applications. These logs are not directly associated with the [zones](/fundamentals/concepts/accounts-and-zones/#zones) in your Cloudflare account.
 
 * The data retention for Network Analytics is 16 weeks. Additionally, data older than eight weeks might have lower resolution when using narrow time frames.
 
diff --git a/src/content/docs/ddos-protection/reference/reports.mdx b/src/content/docs/ddos-protection/reference/reports.mdx
@@ -19,7 +19,7 @@ Additionally, if you are a Magic Transit or Spectrum BYOIP customer, you will re
 
 :::note[Note]
 
-To receive DDoS reports by email you must have opted in to the **Analytics** category in the [communication preferences](/fundamentals/account/customize-account/communication-preference/) for your profile.
+To receive DDoS reports by email you must have opted in to the **Analytics** category in the [communication preferences](/fundamentals/account/customize-account/#communication-preference) for your profile.
 :::
 
 ## Weekly DDoS reports
diff --git a/src/content/docs/email-routing/setup/subdomains.mdx b/src/content/docs/email-routing/setup/subdomains.mdx
@@ -6,7 +6,7 @@ sidebar:
 
 ---
 
-Email Routing is a [zone-level](/fundamentals/accounts-and-zones/#zones) feature. A zone has a top-level domain (the same as the zone name) and it can have subdomains (managed under the DNS feature.) As an example, you can have the `example.com` zone, and then the `mail.example.com` and `corp.example.com` sub-domains under it.
+Email Routing is a [zone-level](/fundamentals/concepts/accounts-and-zones/#zones) feature. A zone has a top-level domain (the same as the zone name) and it can have subdomains (managed under the DNS feature.) As an example, you can have the `example.com` zone, and then the `mail.example.com` and `corp.example.com` sub-domains under it.
 
 You can use Email Routing with any subdomain of any zone in your account. Follow these steps to add Email Routing features to a new subdomain:
 
diff --git a/src/content/docs/fundamentals/concepts/accounts-and-zones.mdx b/src/content/docs/fundamentals/concepts/accounts-and-zones.mdx
@@ -34,7 +34,7 @@ end
 
 ## User profiles
 
-Each user has a profile that contains several settings, such as [Communication preferences](/fundamentals/account/customize-account/communication-preference/) and [Language preferences](/fundamentals/account/customize-account/language-preference/).
+Each user has a profile that contains several settings, such as [Communication preferences](/fundamentals/account/customize-account/#communication-preference/) and [Language preferences](/fundamentals/account/customize-account/#language-preference/).
 
 ### Navigation
 
diff --git a/src/content/docs/fundamentals/reference/scans-penetration.mdx b/src/content/docs/fundamentals/reference/scans-penetration.mdx
@@ -4,7 +4,7 @@ title: Scans and penetration testing policy
 
 ---
 
-Customers may conduct scans and penetration tests (with certain restrictions) on application and network-layer aspects of their own assets, such as their [zones](/fundamentals/accounts-and-zones/#zones) within their Cloudflare accounts, provided they adhere to Cloudflare's policy.
+Customers may conduct scans and penetration tests (with certain restrictions) on application and network-layer aspects of their own assets, such as their [zones](/fundamentals/concepts/accounts-and-zones/#zones) within their Cloudflare accounts, provided they adhere to Cloudflare's policy.
 
 - **Permitted targets** - all scans or testing must be limited to the following:
 
diff --git a/src/content/docs/fundamentals/reference/troubleshooting.mdx b/src/content/docs/fundamentals/reference/troubleshooting.mdx
@@ -9,7 +9,7 @@ head:
 
 ---
 
-When you [set up Cloudflare](/fundamentals/setup/), you may experience the following issues or error messages.
+When you [set up Cloudflare](/fundamentals/account/), you may experience the following issues or error messages.
 
 ## Error messages
 
diff --git a/src/content/docs/learning-paths/mtls/mtls-app-security/index.mdx b/src/content/docs/learning-paths/mtls/mtls-app-security/index.mdx
@@ -6,7 +6,7 @@ sidebar:
 ---
 
 :::note
-This implementation requires an active [Zone](/fundamentals/accounts-and-zones/#zones), a valid [Edge Certificate](/ssl/edge-certificates/), and [proxied](/dns/proxy-status/) hostname. <br />
+This implementation requires an active [Zone](/fundamentals/concepts/accounts-and-zones/#zones), a valid [Edge Certificate](/ssl/edge-certificates/), and [proxied](/dns/proxy-status/) hostname. <br />
 
 API Shield is not required to use mTLS. <br />
 
diff --git a/src/content/docs/logs/instant-logs.mdx b/src/content/docs/logs/instant-logs.mdx
@@ -15,7 +15,7 @@ Instant Logs allows Cloudflare customers to access a live stream of the traffic
 
 ## Instant Logs via Cloudflare Dashboard
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select the [zone](/fundamentals/accounts-and-zones/#zones) you want to use with Instant Logs.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select the [zone](/fundamentals/concepts/accounts-and-zones/#zones) you want to use with Instant Logs.
 
 2. Go to **Analytics** > **Instant Logs**.
 
diff --git a/src/content/docs/magic-network-monitoring/faq.mdx b/src/content/docs/magic-network-monitoring/faq.mdx
@@ -12,7 +12,7 @@ Below you will find answers to our most commonly asked questions. If you cannot
 
 This probably means that your account name has unsupported characters. Make sure your account name does not have characters like, for example, `&`, `<`, `>`, `"`, `'`, ``` ` ```.
 
-Refer to [Account name](/fundamentals//account/customize-account/account-name/) to learn how to change your account name.
+Refer to [Account name](/fundamentals/account/customize-account/account-name/) to learn how to change your account name.
 
 ## Can I send NetFlow/sFlow data to Cloudflare in a secure, encrypted way?
 
diff --git a/src/content/docs/magic-network-monitoring/rules/index.mdx b/src/content/docs/magic-network-monitoring/rules/index.mdx
@@ -30,7 +30,7 @@ If you get the following error when trying to create a rule:
 
 Make sure the name for your Cloudflare account does not contain unsupported characters, like, for example, `&`, `<`, `>`, `"`, `'`, ``` ` ```.
 
-Refer to [Account name](/fundamentals/account/customize-account/account-name/) to learn how to change your account name.
+Refer to [Account name](/fundamentals/account/customize-account/#account-name) to learn how to change your account name.
 :::
 
 To create a new rule:
diff --git a/src/content/docs/r2/buckets/public-buckets.mdx b/src/content/docs/r2/buckets/public-buckets.mdx
@@ -59,7 +59,7 @@ To specify the minimum TLS version of a custom hostname of an R2 bucket, you can
 
 ## Add your domain to Cloudflare
 
-The domain being used must have been added as a [zone](/fundamentals/accounts-and-zones/#zones) in the same account as the R2 bucket.
+The domain being used must have been added as a [zone](/fundamentals/concepts/accounts-and-zones/#zones) in the same account as the R2 bucket.
 
 - If your domain is already managed by Cloudflare, you can proceed to [Connect a bucket to a custom domain](/r2/buckets/public-buckets/#connect-a-bucket-to-a-custom-domain).
 - If your domain is not managed by Cloudflare, you need to set it up using a [partial (CNAME) setup](/dns/zone-setups/partial-setup/) to add it to your account.
diff --git a/src/content/docs/registrar/account-options/inter-account-transfer.mdx b/src/content/docs/registrar/account-options/inter-account-transfer.mdx
@@ -21,7 +21,7 @@ Before proceeding, please be aware of the following:
 
 Before you request the move, you will need to do the following:
 
-* Obtain the [account ID](/fundamentals/setup/find-account-and-zone-ids) of the new account.
+* Obtain the [account ID](/fundamentals/account/find-account-and-zone-ids/) of the new account.
 * Add the domain as a website to the new account and select a plan.
 * [Disable DNSSEC](/dns/dnssec/#disable-dnssec) for the domain and ensure it is set up and ready in the new dashboard account you intend to move it to.
 
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx b/src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/index.mdx
@@ -25,7 +25,7 @@ If you are a SaaS provider looking to restrict cipher suites for connections to
 
 Custom cipher suites is a hostname-level setting, which implies that:
 
-* When you customize cipher suites for a zone, this will affect all hostnames within that zone. If you are not familiar with what a Cloudflare zone is, refer to [Fundamentals](/fundamentals/accounts-and-zones/#zones).
+* When you customize cipher suites for a zone, this will affect all hostnames within that zone. If you are not familiar with what a Cloudflare zone is, refer to [Fundamentals](/fundamentals/concepts/accounts-and-zones/#zones).
 * The configuration is applicable to all edge certificates used to connect to the hostname(s), regardless of the [certificate type](/ssl/edge-certificates/) (universal, advanced, or custom).
 * If you need to use a per-hostname cipher suite customization, you must ensure that the hostname is specified on the certificate.
 
diff --git a/src/content/docs/ssl/get-started.mdx b/src/content/docs/ssl/get-started.mdx
@@ -17,7 +17,7 @@ Follow the steps below to enable SSL/TLS protection for your application.
 ## Before you begin
 
 
-* [Create an account and register an application](/fundamentals/setup/)
+* [Create an account and register an application](/fundamentals/account/)
 
 
 
diff --git a/src/content/docs/workers/platform/limits.mdx b/src/content/docs/workers/platform/limits.mdx
@@ -198,7 +198,7 @@ A subrequest is any request that a Worker makes to either Internet resources usi
 
 To make subrequests from your Worker to another Worker on your account, use [Service Bindings](/workers/runtime-apis/bindings/service-bindings/). Service bindings allow you to send HTTP requests to another Worker without those requests going over the Internet.
 
-If you attempt to use global [`fetch()`](/workers/runtime-apis/fetch/) to make a subrequest to another Worker on your account that runs on the same [zone](/fundamentals/accounts-and-zones/#zones), without service bindings, the request will fail.
+If you attempt to use global [`fetch()`](/workers/runtime-apis/fetch/) to make a subrequest to another Worker on your account that runs on the same [zone](/fundamentals/concepts/accounts-and-zones/#zones), without service bindings, the request will fail.
 
 If you make a subrequest from your Worker to a target Worker that runs on a [Custom Domain](/workers/configuration/routing/custom-domains/#worker-to-worker-communication) rather than a route, the request will be allowed.
 
diff --git a/src/content/docs/workers/reference/protocols.mdx b/src/content/docs/workers/reference/protocols.mdx
@@ -14,5 +14,5 @@ Cloudflare Workers support the following protocols and interfaces:
 | **Direct TCP sockets** | Support for handling inbound TCP connections is [coming soon](https://blog.cloudflare.com/workers-tcp-socket-api-connect-databases/)                                                                                                                                                                             | Create outbound TCP connections using the [`connect()` API](/workers/runtime-apis/tcp-sockets/)              |
 | **WebSockets**         | Accept incoming WebSocket connections using the [`WebSocket` API](/workers/runtime-apis/websockets/), or with [MQTT over WebSockets (Pub/Sub)](/pub-sub/learning/websockets-browsers/)                                                                                                                           | [MQTT over WebSockets (Pub/Sub)](/pub-sub/learning/websockets-browsers/)                                     |
 | **MQTT**               | Handle incoming messages to an MQTT broker with [Pub Sub](/pub-sub/learning/integrate-workers/)                                                                                                                                                                                                                  | Support for publishing MQTT messages to an MQTT topic is [coming soon](/pub-sub/learning/integrate-workers/) |
-| **HTTP/3 (QUIC)**      | Accept inbound requests over [HTTP/3](https://www.cloudflare.com/learning/performance/what-is-http3/) by enabling it on your [zone](/fundamentals/accounts-and-zones/#zones) in **Speed** > **Optimization** > **Protocol Optimization** area of the [Cloudflare dashboard](https://dash.cloudflare.com/). |                                                                                                              |
+| **HTTP/3 (QUIC)**      | Accept inbound requests over [HTTP/3](https://www.cloudflare.com/learning/performance/what-is-http3/) by enabling it on your [zone](/fundamentals/concepts/accounts-and-zones/#zones) in **Speed** > **Optimization** > **Protocol Optimization** area of the [Cloudflare dashboard](https://dash.cloudflare.com/). |                                                                                                              |
 | **SMTP**               | Use [Email Workers](/email-routing/email-workers/) to process and forward email, without having to manage TCP connections to SMTP email servers                                                                                                                                                                  | [Email Workers](/email-routing/email-workers/)                                                               |
diff --git a/src/content/docs/zaraz/get-started.mdx b/src/content/docs/zaraz/get-started.mdx
@@ -5,7 +5,7 @@ sidebar:
   order: 1
 ---
 
-Before being able to use Zaraz, it is recommended that you proxy your website through Cloudflare. Refer to [Set up Cloudflare](/fundamentals/setup/) for more information. If you do not want to proxy your website through Cloudflare, refer to [Use Zaraz on domains not proxied by Cloudflare](/zaraz/advanced/domains-not-proxied/).
+Before being able to use Zaraz, it is recommended that you proxy your website through Cloudflare. Refer to [Set up Cloudflare](/fundamentals/account/) for more information. If you do not want to proxy your website through Cloudflare, refer to [Use Zaraz on domains not proxied by Cloudflare](/zaraz/advanced/domains-not-proxied/).
 
 ## Add a third-party tool to your website
 
diff --git a/src/content/partials/cloudflare-one/gateway/get-started/create-dns-policy.mdx b/src/content/partials/cloudflare-one/gateway/get-started/create-dns-policy.mdx
@@ -29,7 +29,7 @@ To create a new DNS policy:
    | ------- | ---------- | ---------- |
    | Account | Zero Trust | Edit       |
 
-2. (Optional) Configure your API environment variables to include your [account ID]() and API token./fundamentals/account/find-account-and-zone-ids/
+2. (Optional) Configure your API environment variables to include your [account ID](/fundamentals/account/find-account-and-zone-ids/) and API token.
 3. Send a `POST` request to the [Create a Zero Trust Gateway rule](/api/resources/zero_trust/subresources/gateway/subresources/rules/methods/create/) endpoint. For example, we recommend adding a policy to block all [security categories](/cloudflare-one/policies/gateway/domain-categories/#security-categories):
 
    ```sh title="curl API DNS policy example"
diff --git a/src/content/partials/fundamentals/verify-email-address.mdx b/src/content/partials/fundamentals/verify-email-address.mdx
@@ -2,7 +2,7 @@
 {}
 ---
 
-For security reasons, Cloudflare attempts to verify the email address associated with your account. You cannot perform certain tasks within the Cloudflare dashboard -- for example, [adding a new member](/fundamentals/manage-members/manage/#add-account-members) or [updating your communication preferences](/fundamentals/account/customize-account/communication-preference/) -- without verifying your email.
+For security reasons, Cloudflare attempts to verify the email address associated with your account. You cannot perform certain tasks within the Cloudflare dashboard -- for example, [adding a new member](/fundamentals/manage-members/manage/#add-account-members) or [updating your communication preferences](/fundamentals/account/customize-account/#communication-preference) -- without verifying your email.
 
 ## When creating your account
 
