cacheable-matchers

To make pages cacheable at the CDN edge, audit loader cache declarations and enforce cacheable flags on matchers. This ensures deterministic results are cached while preventing foreign cookies or personalization from breaking cacheability.

A cacheability gate is a condition that determines if a page can be stored at the CDN edge. You need to evaluate cacheability gates when using matchers and loaders to identify no-store requirements, cookies, and user segments that block caching.

Auditing loader cache declarations involves checking if public, static data is marked for caching and identifying loaders that must be set to no-store. This separates cacheable assets from dynamic, uncacheable user data.

Foreign Set-Cookie headers break HTML cacheability by injecting dynamic user state into responses. Moving personalization client-side and preventing foreign cookies ensures compliant, cacheable outputs at the edge.

Matcher-enabled pages using query params or geo-based variants require specific caveats for cacheability. You must enforce cacheable equals true for deterministic results while carefully handling variant-specific routing and user segments.

Edge caching limitations occur when user-based personalization requires foreign cookies or dynamic data. Loaders must be declared no-store for user-specific segments, and personalization should be moved client-side to maintain cacheability.