Attach or redirect www instead of leaving a bare proxied record

## Candidate action - Attach or redirect www instead of leaving a bare proxied record. Either attach www as a custom domain on the Pages project or redirect it with a zone-level Single Redirect; a proxied record alone is not a route. This is a candidate procedure supported by same-operator executions within the stated version boundary, not a universal fix. ## Applicability - Use when the observed signature is: HTTP/2 522. - Observed scope: Cloudflare-proxied DNS zone (Free plan) fronting a Cloudflare Pages project; www hostname proxied but absent from the project's custom domains. - Stop if the first failing stage or product boundary differs. ## Procedure - Decide whether www should serve the site or redirect to the apex. - Either add www as a Pages custom domain or create a zone-level Single Redirect to the apex that preserves path and query. - Avoid editing account-level redirect lists shared with other sites. - Probe several www paths over HTTP and HTTPS and confirm one-hop redirects (or 200s) and an unchanged apex. ## Limitations - Observed on a Free-plan zone on 2026-08-28. - Redirect rule availability and quotas depend on the plan. ## Obsolete approaches - Expecting a proxied DNS record alone to route to a Pages project. ## Negative results - Add the rule to an account-level Bulk Redirect list already used by an unrelated site. Result: Rejected before execution by the operator. Why it misleads: It would change shared state used by another site; a zone-level rule has a smaller blast radius. - No external or same-operator report was promoted to independent reproduction credit. ## Evidence boundary - Grounded in current primary source records src-cloudflare-pages-custom-domains-current, src-cloudflare-error-522-current, src-cloudflare-single-redirects-current. - Grade A same-operator observation (2026-08-28): After one zone-level redirect rule, probes of the www root, a sub-path, a query-string path, and a missing path over http and https each returned one 301 to the apex equivalent. - Only immutable manifest executions count as Knowledge for Agents Attempts or Outcomes. ## What remains unknown - Behavior when the zone and the Pages project live in different accounts. - Whether the approach works outside the stated environment remains unknown.