Fixed broken links

dcpena · dcpena · commit 04f664bcf66a · 2025-02-10T10:35:11.000-06:00
diff --git a/src/content/changelogs/trace.yaml b/src/content/changelogs/trace.yaml
@@ -1,7 +1,7 @@
 ---
-link: "/fundamentals/basic-tasks/trace-request/changelog/"
+link: "/fundamentals/security/trace-request/changelog/"
 productName: Trace
-productLink: "/fundamentals/basic-tasks/trace-request/"
+productLink: "/fundamentals/security/trace-request/"
 productArea: Core platform
 productAreaLink: /fundamentals/reference/changelog/platform/
 entries:
diff --git a/src/content/docs/cloudflare-one/applications/configure-apps/self-hosted-public-app.mdx b/src/content/docs/cloudflare-one/applications/configure-apps/self-hosted-public-app.mdx
@@ -27,7 +27,7 @@ You can securely publish internal tools and applications by adding Cloudflare Ac
 We recommend [creating an Access application](#1-add-your-application-to-access) before setting up the tunnel route. If you do not have an Access application in place, public hostname routes in Tunnel are available to anyone on the Internet.
 :::
 
-If your application is already publicly routable, a Tunnel is not strictly required. However, you will then need to protect your origin IP using [other methods](/fundamentals/basic-tasks/protect-your-origin-server/).
+If your application is already publicly routable, a Tunnel is not strictly required. However, you will then need to protect your origin IP using [other methods](/fundamentals/security/protect-your-origin-server/).
 
 ## 3. Validate the Access token
 
diff --git a/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx b/src/content/docs/dns/manage-dns-records/how-to/round-robin-dns.mdx
@@ -36,7 +36,7 @@ If all associated records were proxied, any request to Cloudflare's nameservers
 
 Each client (oftentimes a browser) would decide which Cloudflare IP address to send the request to. Cloudflare would then receive that request and — if Cloudflare needed to contact your origin server — we would pick one of the three IP addresses specified in your DNS records (either `192.0.2.1`, `192.0.2.2`, or `192.0.2.3`, using the example above).
 
-Beyond reducing requests to your origin server, this setup allows your application to take advantage of Cloudflare's [Zero downtime failover](/fundamentals/basic-tasks/protect-your-origin-server/#zero-downtime-failover). When a request to one IP address fails, Cloudflare automatically retries the request to other IP addresses associated with the same hostname. This behavior prevents end users from experiencing downtime.
+Beyond reducing requests to your origin server, this setup allows your application to take advantage of Cloudflare's [Zero downtime failover](/security/protect-your-origin-server/#zero-downtime-failover). When a request to one IP address fails, Cloudflare automatically retries the request to other IP addresses associated with the same hostname. This behavior prevents end users from experiencing downtime.
 
 ### Unproxied and proxied records
 
diff --git a/src/content/docs/fundamentals/concepts/cloudflare-ip-addresses.mdx b/src/content/docs/fundamentals/concepts/cloudflare-ip-addresses.mdx
@@ -35,7 +35,7 @@ To avoid blocking Cloudflare IP addresses unintentionally, review your external
 
 #### Further protection
 
-For further recommendations on securing your origin server, refer to our guide on [protecting your origin server](/fundamentals/basic-tasks/protect-your-origin-server/).
+For further recommendations on securing your origin server, refer to our guide on [protecting your origin server](/fundamentals/security/protect-your-origin-server/).
 
 ### Customize Cloudflare IP addresses
 
diff --git a/src/content/docs/fundamentals/index.mdx b/src/content/docs/fundamentals/index.mdx
@@ -15,7 +15,6 @@ As you get started with Cloudflare, explore the following resources:
 * [Concepts](/fundamentals/concepts/) explain the basic ideas behind how Cloudflare works and how you can work with Cloudflare.
 * [How to use Cloudflare](/fundamentals/setup/) gives step-by-step instructions on how to add your domain to Cloudflare.
 * [Subscriptions and billing](/fundamentals/subscriptions-and-billing/) help you set up your account profile, security, billing information, and more.
-* [Basic tasks](/fundamentals/basic-tasks/) provide guidance on how to perform common tasks with Cloudflare, particularly those related to new domains.
 * [Cloudflare's API](/fundamentals/api/) provides an overview of interacting with Cloudflare in a programmatic way.
 * [Reference topics](/fundamentals/reference/) offer technical details about different aspects of Cloudflare (common user agents, supported network ports, etc.).
 * [Getting started learning path](/learning-paths/get-started/concepts/) is a guided tutorial introducing you to Cloudflare. By the end of the learning path, you will have a live domain tuned for speed and security.
@@ -26,5 +25,5 @@ As you get started with Cloudflare, explore the following resources:
 
 :::note
 
-For additional resources, review [How to Interact with Cloudflare](/fundamentals/basic-tasks/interact-with-cloudflare/). 
+For additional resources, review [How to Interact with Cloudflare](/fundamentals/setup/interact-with-cloudflare/). 
 :::
diff --git a/src/content/docs/fundamentals/reference/scans-penetration.mdx b/src/content/docs/fundamentals/reference/scans-penetration.mdx
@@ -19,7 +19,7 @@ Targets like `*.cloudflare.com` or other Cloudflare-owned destinations are only
 - **Throttling**: Scans should be throttled to a reasonable rate to prevent disruptions and ensure stable system performance.
 - **Scope and intent**: Scans should identify the presence of vulnerabilities without attempting to actively exploit any detected weaknesses.
 - **Exclusions**: It is recommended to exclude [`/cdn-cgi/` endpoints](/fundamentals/reference/cdn-cgi-endpoint/) from scans to avoid false positives or irrelevant results.
-- **Compliance checks**: Customers may conduct [PCI compliance scans](/fundamentals/basic-tasks/pci-scans/) or verify that [known vulnerabilities](/ssl/reference/compliance-and-vulnerabilities/#known-vulnerabilities-mitigations) have been addressed.
+- **Compliance checks**: Customers may conduct [PCI compliance scans](/fundamentals/security/pci-scans/) or verify that [known vulnerabilities](/ssl/reference/compliance-and-vulnerabilities/#known-vulnerabilities-mitigations) have been addressed.
 
 ### Penetration testing
 
diff --git a/src/content/docs/fundamentals/setup/manage-domains/add-site.mdx b/src/content/docs/fundamentals/setup/manage-domains/add-site.mdx
@@ -38,6 +38,6 @@ If you do not already own a domain and plan to use Cloudflare for your [authorit
 
 To prevent insecure connections and visitor browser errors, [make sure you have SSL/TLS protection](/ssl/get-started/).
 
-## 4. Go beyond the basics
+Many Cloudflare services will automatically protect and speed up your web traffic once your nameservers are updated. 
 
-Many Cloudflare services will automatically protect and speed up your web traffic once your nameservers are updated. To customize how we process your traffic and to get more out of Cloudflare, refer to our [basic tasks](/fundamentals/basic-tasks/).
+To get more out of Cloudflare, refer to the [Security](/fundamentals/security/) and [Performance](/fundamentals/performance/) tasks. 
diff --git a/src/content/docs/learning-paths/get-started-free/onboarding/add-and-activate.mdx b/src/content/docs/learning-paths/get-started-free/onboarding/add-and-activate.mdx
@@ -53,7 +53,7 @@ If you already have a domain, the easiest way to get set up with Cloudflare is t
 If you cannot transfer your domain or want to keep your current registrar, your setup has a few more steps:
 
 1. [Add your site](/fundamentals/setup/manage-domains/add-site/).
-2. (*Optional*) If your domain is sensitive to downtime, you may have a [few additional steps](/fundamentals/basic-tasks/minimize-downtime/).
+2. (*Optional*) If your domain is sensitive to downtime, you may have a [few additional steps](/fundamentals/performance/minimize-downtime/ ).
 3. At your registrar (where you bought your domain name), disable DNSSEC. <br/> <Render file="dnssec-providers" product="dns" />
 4. (*For some*) At your origin server, [allow Cloudflare IP addresses](/fundamentals/concepts/cloudflare-ip-addresses/).
 5. Change your [domain nameservers](/dns/zone-setups/full-setup/setup/).
diff --git a/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx b/src/content/docs/reference-architecture/design-guides/extending-cloudflares-benefits-to-saas-providers-end-customers.mdx
@@ -60,7 +60,7 @@ The following products are used to deliver this solution.
 
 ## Cloudflare for SaaS examples
 
-The primary objective of using Cloudflare is to ensure that all requests to your application's custom hostname are routed through Cloudflare's security and performance services first to apply security controls and routing or load balancing of traffic. Since the origin server often needs to be publicly accessible, securing the connection between Cloudflare and the origin server is crucial. For comprehensive guidance on securing origin servers, please refer to Cloudflare's documentation: [Protect your origin server](/fundamentals/basic-tasks/protect-your-origin-server/).
+The primary objective of using Cloudflare is to ensure that all requests to your application's custom hostname are routed through Cloudflare's security and performance services first to apply security controls and routing or load balancing of traffic. Since the origin server often needs to be publicly accessible, securing the connection between Cloudflare and the origin server is crucial. For comprehensive guidance on securing origin servers, please refer to Cloudflare's documentation: [Protect your origin server](/fundamentals/security/protect-your-origin-server/).
 
 The diagrams below begin by illustrating the simplest approach to achieving this goal, followed by more complex configurations.
 
@@ -105,7 +105,7 @@ For enhanced security, rather than exposing your application servers directly to
 2. The regionalized SaaS hostname is set up as a CNAME record that directs traffic to the standard [Fallback Origin](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/#1-create-fallback-origin) of the SaaS provider (`fallback.myappexample.com`).
 3. The fallback origin is a CNAME DNS record that points to a [public hostname](/cloudflare-one/connections/connect-networks/routing-to-tunnel/) exposed by Cloudflare Tunnel. This public hostname should be configured to route traffic to your application, for example, `localhost:8080`.
 
-This setup is ideal for SaaS providers that do not need granular load balancing, such as [geo-based traffic steering](/load-balancing/understand-basics/traffic-steering/), across multiple origin servers. It's also well-suited for simple testing and development environments, where [protecting your origin server](/fundamentals/basic-tasks/protect-your-origin-server/) by only allowing requests through the Cloudflare Tunnel is sufficient. However, for distributed applications requiring load balancing at both global and local levels, we recommend using [Cloudflare's Load Balancer](/load-balancing/) with global and private network load balancing capabilities.
+This setup is ideal for SaaS providers that do not need granular load balancing, such as [geo-based traffic steering](/load-balancing/understand-basics/traffic-steering/), across multiple origin servers. It's also well-suited for simple testing and development environments, where [protecting your origin server](/fundamentals/security/protect-your-origin-server/) by only allowing requests through the Cloudflare Tunnel is sufficient. However, for distributed applications requiring load balancing at both global and local levels, we recommend using [Cloudflare's Load Balancer](/load-balancing/) with global and private network load balancing capabilities.
 
 ### Global Traffic Management (GTM) & Private Network Load Balancing as custom origin setup
 
diff --git a/src/content/docs/rules/reference/page-rules-migration.mdx b/src/content/docs/rules/reference/page-rules-migration.mdx
@@ -32,7 +32,7 @@ Improvements in modern Rules features include:
 
 - **New engine**: New Rules features are powered by the [Ruleset Engine](/ruleset-engine/), which offers versatile configuration with a robust language that supports many HTTP request and response fields.
 - **Improved scalability**: Thanks to the improved scalability, Cloudflare plans now have increased quotas.
-- **Easier troubleshooting**: Rule execution is more predictable, since each rule operates independently, simplifying troubleshooting. Additionally, [Cloudflare Trace](/fundamentals/basic-tasks/trace-request/) helps understand rule interactions.
+- **Easier troubleshooting**: Rule execution is more predictable, since each rule operates independently, simplifying troubleshooting. Additionally, [Cloudflare Trace](/fundamentals/security/trace-request/) helps understand rule interactions.
 - **Improved consistency**: New Rules features also ensure consistency, with common fields and capabilities shared across products, offering a seamless experience and predictable Terraform configurations.
 
 ## Key differences
diff --git a/src/content/docs/rules/transform/troubleshooting.mdx b/src/content/docs/rules/transform/troubleshooting.mdx
@@ -17,6 +17,6 @@ For more information on runtime errors related to Transform Rules configuration,
 
 Transform Rules performing request header modifications affect the HTTP headers sent by Cloudflare's network to your origin server. You will not find these headers in your browser request or response data, which can make it difficult to tell if the rule is working as intended.
 
-To check if a request header modification is taking effect, you can check the logs on your origin server or use [Cloudflare Trace](/fundamentals/basic-tasks/trace-request/) to check that the rule is matching traffic correctly. Since [Cloudflare Logpush](/logs/about/) only logs original request/response headers, Logpush logs will not include any header transformations done via Transform Rules.
+To check if a request header modification is taking effect, you can check the logs on your origin server or use [Cloudflare Trace](/fundamentals/security/trace-request/) to check that the rule is matching traffic correctly. Since [Cloudflare Logpush](/logs/about/) only logs original request/response headers, Logpush logs will not include any header transformations done via Transform Rules.
 
 To add HTTP headers that website visitors will receive in their browsers, you must [modify the response headers](/rules/transform/response-header-modification/) instead.
diff --git a/src/content/docs/rules/transform/url-rewrite/create-dashboard.mdx b/src/content/docs/rules/transform/url-rewrite/create-dashboard.mdx
@@ -70,6 +70,6 @@ Refer to [URL rewrite parameters](/rules/transform/url-rewrite/reference/paramet
 
 The **Request URL** value is only used to match the incoming request with a rule. It will not be used for capturing URL patterns for rewrites. If you are matching the URL path or query string in **Target path** or **Target query**, respectively, make sure that the **Request URL** pattern also matches the incoming request, or else the rule will not trigger.
 
-To validate rewrite URL rule matches, use [Cloudflare Trace](/fundamentals/basic-tasks/trace-request/). To validate rewritten URLs, check your origin server.
+To validate rewrite URL rule matches, use [Cloudflare Trace](/fundamentals/security/trace-request/). To validate rewritten URLs, check your origin server.
 
 :::
diff --git a/src/content/docs/rules/url-forwarding/bulk-redirects/faq.mdx b/src/content/docs/rules/url-forwarding/bulk-redirects/faq.mdx
@@ -16,7 +16,7 @@ Below you will find answers to the most commonly asked questions regarding Bulk
 To troubleshoot errors related to Bulk Redirects:
 
 * Refer to [Troubleshooting Cloudflare 10XXX Errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-10xxx-errors/) for more information on runtime errors.
-* Use [Cloudflare Trace](/fundamentals/basic-tasks/trace-request/) to determine if a rule is triggering for a specific URL.
+* Use [Cloudflare Trace](/fundamentals/security/trace-request/) to determine if a rule is triggering for a specific URL.
 
 ## What happens if the same source URL appears in two different Bulk Redirect Lists?
 
diff --git a/src/content/docs/rules/url-forwarding/bulk-redirects/index.mdx b/src/content/docs/rules/url-forwarding/bulk-redirects/index.mdx
@@ -25,4 +25,4 @@ Unlike dynamic URL redirects created in [Single Redirects](/rules/url-forwarding
 
 - [Availability](/rules/url-forwarding/#availability): Information on the Bulk Redirects quotas and features per Cloudflare plan.
 - [Execution order](/rules/url-forwarding/#execution-order): Execution order of the different Rules products.
-- [Trace a request](/fundamentals/basic-tasks/trace-request/): Use Cloudflare Trace to determine if a bulk redirect rule is triggering for a specific URL.
+- [Trace a request](/fundamentals/security/trace-request/): Use Cloudflare Trace to determine if a bulk redirect rule is triggering for a specific URL.
diff --git a/src/content/docs/rules/url-forwarding/single-redirects/index.mdx b/src/content/docs/rules/url-forwarding/single-redirects/index.mdx
@@ -23,4 +23,4 @@ Single Redirects allow you to create static or dynamic URL <GlossaryTooltip term
 
 - [Availability](/rules/url-forwarding/#availability): Information on the Single Redirects quotas and features per Cloudflare plan.
 - [Execution order](/rules/url-forwarding/#execution-order): Execution order of the different Rules products.
-- [Trace a request](/fundamentals/basic-tasks/trace-request/): Use Cloudflare Trace to determine if a redirect rule is triggering for a specific URL.
+- [Trace a request](/fundamentals/security/trace-request/): Use Cloudflare Trace to determine if a redirect rule is triggering for a specific URL.
diff --git a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/explanation.mdx b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/explanation.mdx
@@ -22,7 +22,7 @@ This block also applies for requests to [unproxied DNS records](/dns/manage-dns-
 
 Note that the certificate Cloudflare provides for you to [set up Authenticated Origin Pulls](/ssl/origin-configuration/authenticated-origin-pull/set-up/zone-level/) is not exclusive to your account, only guaranteeing that a request is coming from the Cloudflare network.
 
-For more strict security, you should set up Authenticated Origin Pulls with your own certificate and consider [other security measures for your origin](/fundamentals/basic-tasks/protect-your-origin-server/).
+For more strict security, you should set up Authenticated Origin Pulls with your own certificate and consider [other security measures for your origin](/fundamentals/security/protect-your-origin-server/).
 
 
 :::
diff --git a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/index.mdx b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/index.mdx
@@ -21,7 +21,7 @@ This authentication becomes particularly important with the [Cloudflare Web Appl
 
 ## Aspects to consider
 
-Although Cloudflare provides you a certificate to easily [configure zone-level authenticated origin pulls](/ssl/origin-configuration/authenticated-origin-pull/set-up/zone-level/), this certificate is not exclusive to your account and only guarantees that a request is coming from the Cloudflare network. If you want more strict security, you should consider [additional security measures for your origin](/fundamentals/basic-tasks/protect-your-origin-server/) and upload your own certificate when setting up Authenticated Origin Pulls.
+Although Cloudflare provides you a certificate to easily [configure zone-level authenticated origin pulls](/ssl/origin-configuration/authenticated-origin-pull/set-up/zone-level/), this certificate is not exclusive to your account and only guarantees that a request is coming from the Cloudflare network. If you want more strict security, you should consider [additional security measures for your origin](/fundamentals/security/protect-your-origin-server/) and upload your own certificate when setting up Authenticated Origin Pulls.
 
 Using a custom certificate is possible with both [zone-level](/ssl/origin-configuration/authenticated-origin-pull/set-up/zone-level/) and [per-hostname](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/) authenticated origin pulls and is required if you need your domain to be [FIPS](https://en.wikipedia.org/wiki/Federal_Information_Processing_Standards) compliant.
 
diff --git a/src/content/docs/ssl/troubleshooting/faq.mdx b/src/content/docs/ssl/troubleshooting/faq.mdx
@@ -36,7 +36,7 @@ This behavior occurs when all of the following conditions are true:
 
 Yes, Google announced that they use [HTTPS as a ranking signal for SEO](https://googleonlinesecurity.blogspot.co.uk/2014/08/https-as-ranking-signal_6.html).
 
-For further SEO tweaks, refer to our article on [improving SEO Rankings with Cloudflare](/fundamentals/basic-tasks/improve-seo/).
+For further SEO tweaks, refer to our article on [improving SEO Rankings with Cloudflare](/fundamentals/performance/improve-seo/).
 
 ***
 
diff --git a/src/content/docs/waf/rate-limiting-rules/index.mdx b/src/content/docs/waf/rate-limiting-rules/index.mdx
@@ -26,7 +26,7 @@ Refer to [How Cloudflare determines the request rate](/waf/rate-limiting-rules/r
 
 - Rate limiting rules are not designed to allow a precise number of requests to reach the origin server. In some situations, there may be a delay (up to a few seconds) between detecting a request and updating internal counters. Due to this delay, excess requests could still reach the origin server before Cloudflare enforces a mitigation action (such as blocking or challenging) in our global network.
 
-- Applying rate limiting rules to verified bots might affect Search Engine Optimization (SEO). For more information, refer to [Improve SEO](/fundamentals/basic-tasks/improve-seo/).
+- Applying rate limiting rules to verified bots might affect Search Engine Optimization (SEO). For more information, refer to [Improve SEO](/fundamentals/performance/improve-seo/).
 
 ---
 
diff --git a/src/content/docs/waf/reference/legacy/old-rate-limiting/index.mdx b/src/content/docs/waf/reference/legacy/old-rate-limiting/index.mdx
@@ -30,7 +30,7 @@ Are you trying to enable Rate Limiting? [Enable Rate Limiting](https://dash.clou
 
 ### Rate limiting and SEO
 
-Cached resources and known Search Engine crawlers are exempted from your rate limiting rules (previous version only). Therefore, they do not affect your website's [SEO ranking](/fundamentals/basic-tasks/improve-seo/).
+Cached resources and known Search Engine crawlers are exempted from your rate limiting rules (previous version only). Therefore, they do not affect your website's [SEO ranking](/fundamentals/performance/improve-seo/).
 
 ---
 
diff --git a/src/content/partials/dns/minimize-downtime-tip.mdx b/src/content/partials/dns/minimize-downtime-tip.mdx
diff --git a/src/content/partials/rules/troubleshoot-rules-with-trace.mdx b/src/content/partials/rules/troubleshoot-rules-with-trace.mdx
