What Cloudflare Pages actually is
Git-connected static hosting at the edge. Build command outputs HTML/CSS/JS; Pages serves it globally. No PHP runtime. Traditional WordPress doesn't run there without adaptation.
Common WordPress + Cloudflare setups
- WordPress on traditional host + Cloudflare CDN/proxy: most common, full compatibility
- Headless WordPress: WP as CMS API, Next.js/Astro front on Pages
- Static export plugins: generate HTML snapshots deployed to Pages—works for brochure sites, breaks dynamic features
- Cloudflare Workers + caching: advanced edge logic, not the same as Pages alone
When Pages makes sense for WordPress publishers
You've moved to headless for speed. You maintain a marketing landing site in static HTML while blog stays on managed WordPress. You're a developer team already using Git workflows and want preview URLs per branch.
When to skip Pages for WordPress
You need wp-admin plugin ecosystem, membership, WooCommerce, or dynamic comments without building custom APIs. You want one dashboard for non-technical editors. Static export forgot your search, forms, or e-commerce—that's painful.
Performance reality
Cloudflare's proxy in front of WordPress already improves TTFB and caches assets. Pages adds more when the front end is static. Measure before splitting stack complexity.
Security and AdSense
Cloudflare WAF and bot fight help hacked sites recover reputation. AdSense cares that final URLs serve consistent policy pages and quality content—whether origin is Kinsta or Pages + headless matters less than user experience.
Practical recommendation
Start with WordPress on quality hosting, orange-cloud DNS through Cloudflare, cache rules, and optional APO if on compatible plan. Explore Pages when you outgrow monolithic WordPress performance and have dev capacity—not because the name sounds modern.
Cloudflare APO vs Pages for typical blogs
Automatic Platform Optimization caches HTML at edge for WordPress on compatible plans—often the simpler win before headless migration. Measure TTFB with and without APO before rebuilding front end on Pages.
Workers for edge redirects and headers
Workers can add security headers or geo redirects without PHP. They're complementary: WordPress stays origin, Workers handle edge logic lighter than full static export.
Backup and rollback
Headless stacks multiply deploy points. Keep WordPress database backups independent of Pages git history. One bad deploy shouldn't leave you without rollback on both layers.
Cost reality
Pages free tier is generous; developer time isn't. Factor maintenance when editors expect wp-admin simplicity. Hybrid stacks suit teams with front-end dev capacity—not solo bloggers optimizing for AdSense approval alone.