[Cache] SEO: cache-control header

src/content/docs/cache/concepts/cache-control.mdx

@@ -4,6 +4,7 @@ pcx_content_type: concept
 head:
   - tag: title
     content: Origin Cache Control
+description: Learn how the 'cache-control' header works with Cloudflare's Origin Cache Control feature, which ensures that Cloudflare respects caching directives from your origin server.
 
 ---
 
@@ -24,7 +25,7 @@ In the following sections, we will provide more details regarding:
 * How Origin Cache Control behaves with `Cache-Control` directives.
 * How other Cloudflare products interact with `Cache-Control` directives.
 
-## `Cache-control` directives
+## `Cache-control` header directives
 
 A `Cache-Control` header can include a number of directives, and the directive dictates who can cache a resource along with how long those resources can be cached before they must be updated.
 

src/content/docs/cache/concepts/cache-responses.mdx

@@ -47,7 +47,7 @@ The resource was served from Cloudflare's cache but was expired. Cloudflare coul
 
 ## BYPASS
 
-The origin web server instructed Cloudflare to bypass cache via a `Cache-Control` header set to `no-cache`, `private`, or `max-age=0` even though Cloudflare originally preferred to cache the asset. BYPASS is returned when enabling [Origin Cache-Control](/cache/concepts/cache-control/). Cloudflare also sets BYPASS when your origin web server sends cookies in the response header. If the Request to your origin web server includes an `Authorization` header, in some cases the response will also be BYPASS. Refer to [Conditions](/cache/concepts/cache-control/#conditions) in the Origin Cache-Control behavior section for more details.
+The origin web server instructed Cloudflare to bypass cache via a [`Cache-Control` header](/cache/concepts/cache-control/) set to `no-cache`, `private`, or `max-age=0` even though Cloudflare originally preferred to cache the asset. BYPASS is returned when enabling [Origin Cache-Control](/cache/concepts/cache-control/). Cloudflare also sets BYPASS when your origin web server sends cookies in the response header. If the Request to your origin web server includes an `Authorization` header, in some cases the response will also be BYPASS. Refer to [Conditions](/cache/concepts/cache-control/#conditions) in the Origin Cache-Control behavior section for more details.
 
 ## REVALIDATED
 

src/content/docs/cache/concepts/customize-cache.mdx

@@ -27,4 +27,4 @@ For example, add a `static=true` query string for resources at your origin web s
 * Using the Expression Builder: `Hostname contains "example.com" AND URI Query String contains "static=true"`
 * Using the Expression Editor: `(http.host contains "example.com" and http.request.uri.query contains "static=true")`
 
-Resources that match a Cache Everything Cache Rule are still not cached if the origin web server sends a Cache-Control header of `max-age=0`, `private`, `no-cache`, or an `Expires` header with an already expired date. Include the [Edge Cache TTL](/cache/how-to/cache-rules/settings/#edge-ttl) setting within the Cache Everything Cache Rule to additionally override the `Cache-Control` headers from the origin web server.
+Resources that match a Cache Everything Cache Rule are still not cached if the origin web server sends a [Cache-Control header](/cache/concepts/cache-control/) of `max-age=0`, `private`, `no-cache`, or an `Expires` header with an already expired date. Include the [Edge Cache TTL](/cache/how-to/cache-rules/settings/#edge-ttl) setting within the Cache Everything Cache Rule to additionally override the `Cache-Control` headers from the origin web server.

src/content/docs/cache/concepts/default-cache-behavior.mdx

@@ -12,7 +12,7 @@ import { FeatureTable } from "~/components"
 Cloudflare respects the origin web server’s cache headers in the following order unless an [Edge Cache TTL cache rule](/cache/how-to/cache-rules/settings/#edge-ttl) overrides the headers. Refer to the [Edge TTL](/cache/how-to/configure-cache-status-code/#edge-ttl) section for details on default TTL behavior.
 
 * Cloudflare **does not** cache the resource when:
-  * The `Cache-Control` header is set to `private`, `no-store`, `no-cache`, or `max-age=0`.
+  * The [`Cache-Control` header](/cache/concepts/cache-control/) is set to `private`, `no-store`, `no-cache`, or `max-age=0`.
   * The [Set-Cookie header](/cache/concepts/cache-behavior/#interaction-of-set-cookie-response-header-with-cache) exists.
   * The HTTP request method is anything other than a `GET`.
 * Cloudflare **does** cache the resource when:

src/content/docs/cache/how-to/cache-rules/examples/cache-ttl-by-status-code.mdx

@@ -24,7 +24,7 @@ import { Example, Render } from "~/components"
 * **Then**:
   * **Cache eligibility**: Eligible for cache
   * **Setting**: Edge TTL
-    * Use cache-control header if present, use default Cloudflare caching behavior if not
+    * Use [cache-control header](/cache/concepts/cache-control/) if present, use default Cloudflare caching behavior if not
     * **Status code TTL**:
       * **Scope**: *Range*
       * **From**: *200*