[Firewall] Add noindex to entire tile

src/content/docs/firewall/api/call-sequence.mdx

@@ -3,7 +3,7 @@ title: Call sequence
 pcx_content_type: reference
 sidebar:
   order: 4
-
+noindex: true
 ---
 
 import { Render } from "~/components"

src/content/docs/firewall/api/cf-filters/delete.mdx

@@ -6,7 +6,7 @@ sidebar:
 head:
   - tag: title
     content: DELETE examples - Filters
-
+noindex: true
 ---
 
 ## Delete multiple filters

src/content/docs/firewall/api/cf-filters/endpoints.mdx

@@ -6,6 +6,7 @@ sidebar:
 head:
   - tag: title
     content: Endpoints - Filters
+noindex: true
 ---
 
 To invoke a Cloudflare Filters API operation, append the endpoint to the Cloudflare API base URL:

src/content/docs/firewall/api/cf-filters/get.mdx

@@ -6,7 +6,7 @@ sidebar:
 head:
   - tag: title
     content: GET examples - Filters
-
+noindex: true
 ---
 
 ## Get all filters

src/content/docs/firewall/api/cf-filters/index.mdx

@@ -3,7 +3,7 @@ pcx_content_type: reference
 title: Cloudflare Filters API
 sidebar:
   order: 2
-
+noindex: true
 ---
 
 import { Render } from "~/components"

src/content/docs/firewall/api/cf-filters/json-object.mdx

@@ -6,6 +6,7 @@ sidebar:
 head:
   - tag: title
     content: Filter JSON object
+noindex: true
 ---
 
 import { Type } from "~/components";

src/content/docs/firewall/api/cf-filters/post.mdx

@@ -6,7 +6,7 @@ sidebar:
 head:
   - tag: title
     content: POST examples - Filters
-
+noindex: true
 ---
 
 This example creates several filters using a single API call.

src/content/docs/firewall/api/cf-filters/put.mdx

@@ -6,7 +6,7 @@ sidebar:
 head:
   - tag: title
     content: PUT examples - Filters
-
+noindex: true
 ---
 
 ## Update multiple filters

src/content/docs/firewall/api/cf-filters/validation.mdx

@@ -3,13 +3,11 @@ pcx_content_type: reference
 title: Expression validation
 sidebar:
   order: 8
-
+noindex: true
 ---
 
 The Cloudflare Filters API supports an endpoint for validating expressions.
 
-
-
 ## Examples
 
 ### Validate expression via query string

src/content/docs/firewall/api/cf-filters/what-is-a-filter.mdx

@@ -6,7 +6,7 @@ sidebar:
 head: []
 description: A filter is a way of setting up if (traffic matches certain
   criteria), then do something.
-
+noindex: true
 ---
 
 A filter is a way of saying:

src/content/docs/firewall/api/cf-firewall-rules/delete.mdx

@@ -6,6 +6,7 @@ sidebar:
 head:
   - tag: title
     content: DELETE examples - Firewall rules
+noindex: true
 ---
 
 :::note

src/content/docs/firewall/api/cf-firewall-rules/endpoints.mdx

@@ -6,6 +6,7 @@ sidebar:
 head:
   - tag: title
     content: Endpoints - Firewall rules
+noindex: true
 ---
 
 To invoke a Cloudflare Firewall Rules API operation, append the endpoint to the Cloudflare API base URL:

src/content/docs/firewall/api/cf-firewall-rules/get.mdx

@@ -6,7 +6,7 @@ sidebar:
 head:
   - tag: title
     content: GET examples - Firewall rules
-
+noindex: true
 ---
 
 ## Get all rules

src/content/docs/firewall/api/cf-firewall-rules/index.mdx

@@ -3,7 +3,7 @@ pcx_content_type: reference
 title: Firewall Rules API
 sidebar:
   order: 1
-
+noindex: true
 ---
 
 import { Render } from "~/components"

src/content/docs/firewall/api/cf-firewall-rules/json-object.mdx

@@ -6,6 +6,7 @@ sidebar:
 head:
   - tag: title
     content: Firewall rules JSON object
+noindex: true
 ---
 
 import { Type } from "~/components";

src/content/docs/firewall/api/cf-firewall-rules/post.mdx

@@ -6,17 +6,13 @@ sidebar:
 head:
   - tag: title
     content: POST examples - Firewall rules
-
+noindex: true
 ---
 
 This example creates several firewall rules using a single API call.
 
 :::note
-
-
 To create a firewall rule you need a [filter](/firewall/api/cf-filters/what-is-a-filter/) identifier (`id`). If you have not created a filter yet, refer to the [Cloudflare Filters API documentation](/firewall/api/cf-filters/).
-
-
 :::
 
 ```bash title="Request"

src/content/docs/firewall/api/cf-firewall-rules/put.mdx

@@ -6,6 +6,7 @@ sidebar:
 head:
   - tag: title
     content: PUT examples - Firewall rules
+noindex: true
 ---
 
 ## Update multiple rules

src/content/docs/firewall/api/index.mdx

@@ -6,7 +6,7 @@ sidebar:
 head:
   - tag: title
     content: Manage firewall rules via the APIs
-
+noindex: true
 ---
 
 import { Render } from "~/components"

src/content/docs/firewall/cf-dashboard/create-edit-delete-rules.mdx

@@ -3,7 +3,7 @@ title: Create, edit, and delete rules
 pcx_content_type: how-to
 sidebar:
   order: 1
-
+noindex: true
 ---
 
 import { Render } from "~/components"
@@ -16,10 +16,8 @@ When an incoming HTTP request matches a firewall rule expression, Cloudflare per
 
 :::note
 
-
 <Render file="max-expression-length" product="ruleset-engine" />
 
-
 :::
 
 ## Create a firewall rule

src/content/docs/firewall/cf-dashboard/create-mtls-rule.mdx

@@ -3,7 +3,7 @@ pcx_content_type: how-to
 title: Create a mTLS rule
 sidebar:
   order: 5
-
+noindex: true
 ---
 
 Use the [Mutual TLS](/api-shield/security/mtls/configure/) Rule interface in the Cloudflare dashboard to create an mTLS rule that requires requests to your API or web application to present a valid client certificate.

src/content/docs/firewall/cf-dashboard/index.mdx

@@ -6,7 +6,7 @@ sidebar:
 head:
   - tag: title
     content: Manage firewall rules in the Cloudflare dashboard
-
+noindex: true
 ---
 
 import { Render } from "~/components"

src/content/docs/firewall/cf-dashboard/rule-preview.mdx

@@ -7,13 +7,14 @@ sidebar:
 head:
   - tag: title
     content: Preview firewall rules
+noindex: true
 ---
 
 The expression of a firewall rule can become quite complex. In this situation, you should test your firewall rule before deploying it to ensure that the rule will behave as expected.
 
 Rule Preview helps you understand the potential impact of a firewall rule, by testing the rule against a sample drawn from the last 72 hours of traffic. Rule Preview is built into the firewall rules Expression Editor so that you can test a rule as you edit it.
 
-:::caution
+:::note
 Rule Preview is only available to customers on an Enterprise plan.
 :::
 

src/content/docs/firewall/cf-firewall-rules/actions.mdx

@@ -4,6 +4,7 @@ pcx_content_type: reference
 sidebar:
   order: 1
   label: Actions
+noindex: true
 ---
 
 import { Render } from "~/components";

src/content/docs/firewall/cf-firewall-rules/index.mdx

@@ -8,6 +8,7 @@ sidebar:
 head:
   - tag: title
     content: About Cloudflare Firewall Rules
+noindex: true
 ---
 
 import { Render } from "~/components";

src/content/docs/firewall/cf-firewall-rules/order-priority.mdx

@@ -3,6 +3,7 @@ pcx_content_type: concept
 title: Order and priority
 sidebar:
   order: 3
+noindex: true
 ---
 
 Cloudflare Firewall Rules, now deprecated, is part of a larger evaluation chain for HTTP requests, as illustrated in the diagram below. For example, Firewall Rules only evaluates requests that first clear IP Access rules. If a request is blocked by a rule at any stage in the chain, Cloudflare does not evaluate the request further.

src/content/docs/firewall/index.mdx

@@ -8,6 +8,7 @@ sidebar:
 head:
   - tag: title
     content: Cloudflare Firewall Rules (deprecated)
+noindex: true
 ---
 
 import { FeatureTable, Render } from "~/components";

src/content/docs/firewall/troubleshooting/index.mdx

@@ -5,6 +5,7 @@ sidebar:
   order: 5
   group:
     hideIndex: true
+noindex: true
 ---
 
 import { DirectoryListing } from "~/components";

src/content/docs/firewall/troubleshooting/required-changes-to-enable-url-normalization.mdx

@@ -2,6 +2,7 @@
 pcx_content_type: troubleshooting
 source: https://support.cloudflare.com/hc/en-us/articles/360057896851-Required-Firewall-Rule-changes-to-enable-URL-normalization
 title: Required firewall rule changes to enable URL normalization
+noindex: true
 ---
 
 import { Render } from "~/components";