Cloudflare Pages migration: switch without downtime
An executable path for moving an existing project to Cloudflare Pages, with a rollback plan.
On this page
Quick answer
How do I pin Cloudflare Pages and Workers runtime versions?
Use compatibility_date in wrangler.toml to lock the runtime behavior. Validate any bump on a Preview branch first so breaking changes never reach production.
Machine-readable page data: /data/cloudflare-migration.json
In-depth analysis
Cloudflare Pages watches your Git branch, builds on every commit, and atomically publishes the result to the global edge — zero-ops static hosting. Migration runs in parallel with validation and gradual cutover — keep a switch that rolls back in seconds so business never breaks.
# 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-originCloudflare Pages Migration · Key takeaways
- Full branch build passes
- All 8 Preview drills green
- Production and Preview KV isolated
- Rollback switch ready
FAQ & pitfalls
How do I precisely invalidate Cloudflare edge cache?
Static assets get immutable with a long max-age, HTML gets must-revalidate. Change the filename, change the URL — Cloudflare picks up the new version automatically.
Explore the hub
See all 5 guides in Edge ArchitectureSame category as this article, sorted across the codebase.
AI Search migration: switch without downtime
An executable path for moving an existing project to AI Search, with a rollback plan.
Astro migration: switch without downtime
An executable path for moving an existing project to Astro, with a rollback plan.
Cloudflare Pages deployment guide
A hands-on, zero-ops edge deployment using Git-driven Cloudflare Pages.
GEO migration: switch without downtime
An executable path for moving an existing project to GEO, with a rollback plan.
Share & save
What readers are asking
Questions that keep coming back in reader feedback, already answered.
- 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 → - 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 → - 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 →