[Fundamentals & Rules] Moved Trace Request & added redirects (cloudflare#22719)

dcpena · pedrosousa · sdnts · commit 1e9afc3aa286 · 2025-07-24T16:05:59.000-04:00
* Moved Trace Request &amp; added redirects

* Fixed yaml for changelog

* Fixed broken links

* Update src/content/release-notes/trace.yaml

Co-authored-by: Pedro Sousa &lt;680496+pedrosousa@users.noreply.github.com&gt;

---------

Co-authored-by: Pedro Sousa &lt;680496+pedrosousa@users.noreply.github.com&gt;
diff --git a/public/__redirects b/public/__redirects
@@ -698,7 +698,10 @@
 /fundamentals/subscriptions-and-billing/delete-account/ /fundamentals/setup/account/delete-account/ 301
 /fundamentals/subscriptions-and-billing/ /fundamentals/setup/account/ 301
 /fundamentals/api/building-custom-dashboards/ /fundamentals/api/ 301
-
+/fundamentals/trace-request/ /rules/trace-request/ 301
+/fundamentals/trace-request/how-to/ /rules/trace-request/how-to/ 301
+/fundamentals/trace-request/limitations/ /rules/trace-request/limitations/ 301
+/fundamentals/trace-request/changelog/ /rules/trace-request/changelog/ 301
 
 # gateway
 /gateway/about/ /cloudflare-one/policies/gateway/ 301
diff --git a/src/content/changelog/rules/2025-01-09-rules-overview.mdx b/src/content/changelog/rules/2025-01-09-rules-overview.mdx
@@ -15,6 +15,6 @@ What you can do:
 - **See all your rules in one place** – No more clicking around.
 - **Find rules faster** – Search by name.
 - **Understand execution order** – See how rules run in sequence.
-- **Debug easily** – Use [Trace](/fundamentals/trace-request/) without switching tabs.
+- **Debug easily** – Use [Trace](/rules/trace-request/) without switching tabs.
 
 Check it out in [Rules > Overview](https://dash.cloudflare.com/?to=/:account/:zone/rules/overview).
diff --git a/src/content/changelog/rules/2025-04-09-snippets-ga.mdx b/src/content/changelog/rules/2025-04-09-snippets-ga.mdx
@@ -17,7 +17,7 @@ What's new:
 - **Snippets are now GA** – Available at no extra cost on all Pro, Business, and Enterprise plans.
 - **Ready for production** – Snippets deliver a production-grade experience built for scale.
 - **Part of the Cloudflare Rules platform** – Snippets inherit request modifications from other Cloudflare products and support sequential execution, allowing you to run multiple Snippets on the same request and apply custom modifications step by step.
-- **Trace integration** – Use [Cloudflare Trace](/fundamentals/trace-request/) to see which Snippets were triggered on a request — helping you understand traffic flow and debug more effectively.
+- **Trace integration** – Use [Cloudflare Trace](/rules/trace-request/) to see which Snippets were triggered on a request — helping you understand traffic flow and debug more effectively.
 
   ![Snippets shown in Cloudflare Trace results](~/assets/images/changelog/rules/snippets-ga-trace.gif)
 
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/trace-request/) helps understand rule interactions.
+- **Easier troubleshooting**: Rule execution is more predictable, since each rule operates independently, simplifying troubleshooting. Additionally, [Cloudflare Trace](/rules/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/trace-request/changelog.mdx b/src/content/docs/rules/trace-request/changelog.mdx
diff --git a/src/content/docs/rules/trace-request/how-to.mdx b/src/content/docs/rules/trace-request/how-to.mdx
diff --git a/src/content/docs/rules/trace-request/index.mdx b/src/content/docs/rules/trace-request/index.mdx
@@ -2,7 +2,7 @@
 pcx_content_type: concept
 title: Trace a request
 sidebar:
-  order: 5
+  order: 14
   badge:
     text: Beta
 head:
diff --git a/src/content/docs/rules/trace-request/limitations.mdx b/src/content/docs/rules/trace-request/limitations.mdx
diff --git a/src/content/docs/rules/transform/troubleshooting.mdx b/src/content/docs/rules/transform/troubleshooting.mdx
@@ -16,6 +16,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 transform rule is taking effect, you can check the logs on your origin server or use [Cloudflare Trace](/fundamentals/trace-request/) to check that the rule is matching traffic correctly. Since [Cloudflare Logpush](/logs/about/) only logs original HTTP request/response headers, Logpush logs will not include any header transformations done via Transform Rules.
+To check if a request header transform rule is taking effect, you can check the logs on your origin server or use [Cloudflare Trace](/rules/trace-request/) to check that the rule is matching traffic correctly. Since [Cloudflare Logpush](/logs/about/) only logs original HTTP 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 URL rewrite rule matches, use [Cloudflare Trace](/fundamentals/trace-request/). To validate rewritten URLs, check your origin server.
+To validate URL rewrite rule matches, use [Cloudflare Trace](/rules/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
@@ -15,7 +15,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/http-status-codes/cloudflare-10xxx-errors/) for more information on runtime errors.
-- Use [Cloudflare Trace](/fundamentals/trace-request/) to determine if a rule is triggering for a specific URL.
+- Use [Cloudflare Trace](/rules/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/trace-request/): Use Cloudflare Trace to determine if a bulk redirect rule is triggering for a specific URL.
+- [Trace a request](/rules/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/trace-request/): Use Cloudflare Trace to determine if a redirect rule is triggering for a specific URL.
+- [Trace a request](/rules/trace-request/): Use Cloudflare Trace to determine if a redirect rule is triggering for a specific URL.
diff --git a/src/content/partials/rules/troubleshoot-rules-with-trace.mdx b/src/content/partials/rules/troubleshoot-rules-with-trace.mdx
@@ -7,4 +7,4 @@ import { Markdown } from "~/components";
 
 ## Troubleshooting
 
-When troubleshooting {props.rulesFeatureName}, use [Cloudflare Trace](/fundamentals/trace-request/) to determine if a rule is triggering for a specific URL.
+When troubleshooting {props.rulesFeatureName}, use [Cloudflare Trace](/rules/trace-request/) to determine if a rule is triggering for a specific URL.
diff --git a/src/content/release-notes/trace.yaml b/src/content/release-notes/trace.yaml
@@ -1,7 +1,7 @@
 ---
-link: "/fundamentals/trace-request/changelog/"
+link: "/rules/trace-request/changelog/"
 productName: Trace
-productLink: "/fundamentals/trace-request/"
+productLink: "/rules/trace-request/"
 productArea: Core platform
 productAreaLink: /fundamentals/reference/changelog/platform/
 entries:
