aicode8
Edge ArchitectureUpdated: 2026-09-08

Cloudflare Pages deployment guide

A hands-on, zero-ops edge deployment using Git-driven Cloudflare Pages.

On this page

Quick answer

Does Cloudflare Pages require any server maintenance?

None — it is a pure serverless static hosting service.

Machine-readable page data: /data/cloudflare-pages-deploy.json

In-depth analysis

Cloudflare Pages offers native Git integration: every commit builds in a sandbox and atomically publishes to every global edge node.

Cloudflare Pages · Config example
# public/_headers — security headers ride with static assets (Cloudflare convention)
/*
  X-Content-Type-Options: nosniff
  Strict-Transport-Security: max-age=63072000; includeSubDomains
  X-Frame-Options: DENY
  Referrer-Policy: strict-origin-when-cross-origin
Best practices:Commit-to-build and atomic publish. Preview branches bind their own KV namespace so canary data never leaks into production.
Pitfalls:_headers and _redirects must live in the output root (e.g. dist/) — placing them under src/ means they never ship. Pure static projects should not add _worker.js either, or you lose the zero-cold-start advantage. Preview branches must bind their own KV namespace — sharing production will poison canary data.

Cloudflare Pages Deployment Guide · Key takeaways

  • astro.config has a single source-of-truth site value
  • public/_headers declares nosniff and HSTS
  • 404 returns a real 404
  • Preview passes all 8 edge drills

Share & save

My shelf0
← Back to homeTopic: Cloudflare Pages deployment guide

What readers are asking

Questions that keep coming back in reader feedback, already answered.

  1. 01
    Why are _headers / _redirects not taking effect?

    Both files must sit at the root of the output directory (dist/); anything under src/ is never uploaded. A purely static project should not add _worker.js either — that gives up the zero-cold-start advantage.

    See the full guide →
  2. 02
    How do I invalidate the Cloudflare edge cache precisely?

    Give static assets a long immutable max-age and serve HTML with must-revalidate. Changing a filename changes the URL, so Cloudflare fetches the new version automatically.

    See the full guide →
  3. 03
    Why is my Astro component's interactivity not working?

    Components ship as zero-JS HTML by default, so an interactive one needs a client:* directive (client:load, client:visible, …). Without it the script is never bundled into the page.

    See the full guide →
All questions →

Follow along as I build with AI

Get the honest, real-time record: what I build, what breaks, and what I learn — from a non-technical founder. No jargon, no fluff.

We respect your inbox. One click to unsubscribe, anytime.