preview deployment

A preview deployment is a working copy of a site, built from a specific change, and published to a private link instead of the real address. It looks and behaves exactly like the live site would, because it is built from the same code the same way. The only difference is where it lives: an unlisted address that nobody stumbles across, instead of the domain your customers use.

It exists to answer one question before a change goes live: does this actually look and work the way it was meant to. Without one, checking a change would mean either testing it on the real site, where visitors might see a half-finished update, or trusting that it will be fine once it deploys, which is a bad habit for anything that matters.

Why it matters to you

Mistakes happen most often at the moment a change goes from “written” to “live.” A typo, a broken link, a form that stopped working because of an unrelated edit nearby: all the kinds of things that are obvious the instant you look at the actual page, and easy to miss when reading code. A preview deployment gives a real page to look at, before any customer sees it.

It also means you can review a change yourself. If I am building a new page or updating copy, I can send you the preview link, and you can read it exactly as it will appear, on your own phone or laptop, and tell me to fix something before it is public.

How I set it up

Every change to a site’s code, tracked through version control, can trigger its own preview build through Cloudflare Pages, separate from the live deploy. That preview gets its own private address automatically, with no extra setup needed for each individual change. Once the change is reviewed and confirmed, the same code is deployed to the site’s real domain, and the preview link is no longer needed.

One thing I am careful about on projects with a database attached: a preview deployment can share the same underlying data as the live site, depending on the setup. When that is the case, I treat any data written through a preview as real, not as a disposable test, and I say so up front rather than let a client assume a preview is a sandbox with no consequences.

What it looks like in practice

You get a link, you open it on whatever device you would normally browse on, and you see the actual change: new page, new wording, a fixed form, whatever it was. If it looks right, it goes live. If something is off, it gets fixed and a new preview replaces the old one, all before your customers see any of it.