Michael D. Wandzilak
Cloudflare Pages is a hosting platform that serves your website from Cloudflare’s global edge network — over 300 cities worldwide — instead of from one server in one place. For static sites it is, remarkably, free: unlimited bandwidth, unlimited requests, free SSL, no metering. We run dozens of production client sites on it. This is the plain-English version of what it is, why it’s fast, and what it can’t do.
How it works
Traditional hosting parks your site on a single server; every visitor, wherever they are, makes the round trip to it. Pages takes a different approach: your site’s files are distributed to Cloudflare’s entire network, and each visitor is served from the node nearest them. A visitor in Sydney gets the site from Sydney; one in Chicago gets it from Chicago. That’s the core reason edge-hosted sites feel instant everywhere — the speed isn’t a tuning trick, it’s geography. (If Cloudflare itself is new to you, start with What Is Cloudflare?)
Deploying is equally simple in practice: connect a Git repository (or upload directly), Pages builds and distributes the site, and every update rolls out globally in seconds. Each deploy also gets a private preview URL — which is how our clients review changes before anything goes live.
What it costs
For a static site: nothing. The free tier includes unlimited bandwidth and requests, 500 builds per month, custom domains, and automatic SSL. That's not a promotional teaser — it's the standing deal, and it's why a small-business site that once cost $30–60/month on managed WordPress hosting can run on Pages for $0. Cloudflare can afford this because static files are extraordinarily cheap to serve from a network they already operate at planetary scale.
Compare that honestly with what traditional hosts charge — we did the line-item math in Cloudflare Pages vs Traditional Hosting — and the recurring-cost argument for most business sites simply ends.
What it's ideal for
- Business and marketing sites. Services, portfolio, about, contact — the classic small-business site is the perfect Pages workload. Most of our WordPress migrations land here.
- Sites that get traffic spikes. No bandwidth bill, no server to fall over. A page that goes viral costs you exactly what a quiet Tuesday costs: nothing.
- Anything security-sensitive. A static site has no database to inject, no admin login to brute-force, no plugins to exploit. Most of the WordPress attack surface simply doesn’t exist.
- Documentation, landing pages, campaign sites. Fast to deploy, free to leave running forever.
What it can't do (and the honest workarounds)
Pages serves files; it doesn’t run PHP or a database. That means:
- It can’t run WordPress itself. A WordPress site has to be rebuilt as (or exported to) a static site first — that’s the migration work.
- Dynamic features need a companion. Contact forms, search, payments and logins are handled with small serverless functions — Cloudflare Workers — that live on the same network. Every client site we deploy gets its contact form this way: a tiny Worker validates the submission, checks a bot challenge, and emails it on. The visitor never notices the difference; the owner notices there’s nothing to maintain.
- Content editing is a workflow question. There’s no built-in admin panel. Owners either send us changes, or we wire a lightweight CMS in front for sites that need frequent self-service editing.
One more thing worth knowing: Cloudflare has been converging Pages and Workers into a single platform — new capabilities land on the Workers side first, and static-asset hosting is now native to Workers too. Practically, nothing changes for site owners: same network, same economics, and existing Pages projects keep working. It’s simply where the platform is heading, and a good developer picks the right entry point per project.
Getting a site onto Pages
The short version of every migration we do: capture or build the site as static files, wire the forms and any dynamic pieces as Workers, stage it on a preview URL for review, then point the domain at Cloudflare and go live — with every old URL 301-redirected so search engines follow. Email stays wherever it lives today; DNS just needs moving carefully. Done right, the cutover is invisible except for the speed.
Frequently asked questions
Is Cloudflare Pages really free?
For static sites, yes — unlimited bandwidth and requests, 500 builds a month, custom domains and SSL included. Paid plans exist for teams that need more concurrent builds or advanced features, but a typical business site runs comfortably on the free tier indefinitely.
Can Cloudflare Pages run WordPress?
Not directly — Pages doesn’t run PHP or MySQL. A WordPress site is first converted to a static build (which is a service we provide end-to-end), and dynamic pieces like contact forms are rebuilt as Cloudflare Workers.
Do I need to know how to code to use it?
To host something already built, no — you can upload files directly. To build and maintain a real business site on it, you’ll want a developer in the loop, the same way you would for any hand-built site.
Is Cloudflare Pages good for SEO?
The platform itself gives you the raw ingredients Google rewards: excellent Core Web Vitals, global speed, and clean HTML you fully control. Rankings still depend on your content and links — but the technical foundation starts ahead of most CMS hosting.