Cloudflare Pages excels at static sites. WordPress runs PHP and MySQL—so "WordPress on Cloudflare Pages" usually means something hybrid, not a one-click host replacement. Understanding the split saves months of wrong architecture.
What Cloudflare Pages actually does
Git-connected static hosting at the edge. Build output is HTML, CSS, and JS—no PHP runtime. Traditional WordPress doesn't run there without adaptation.
Common WordPress + Cloudflare setups
- WordPress on host + Cloudflare proxy: most common, full compatibility
- Headless WordPress: WP as CMS API, Next.js front on Pages
- Static export plugins: HTML snapshots—brochure sites only
- Workers at edge: redirects and headers, not full CMS replacement
When Pages fits WordPress publishers
You've gone headless for speed. Marketing landings are static while blog stays on managed WordPress. Your team already uses Git previews per branch.
When to skip Pages
You need the full plugin ecosystem, memberships, WooCommerce, or native comments without custom APIs. Non-technical editors expect wp-admin simplicity. Static export breaks search, forms, and carts painfully.
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 first.
Security and AdSense
Cloudflare WAF and bot fight help recover hacked sites. Reviewers care that final URLs serve consistent policy pages and quality tutorials—origin host matters less than user experience.
Practical recommendation
Start WordPress on quality hosting, orange-cloud DNS through Cloudflare, tune cache rules, add APO if eligible. Explore Pages when you outgrow monolithic performance and have dev capacity—not because the name sounds modern.
Backup across hybrid stacks
Headless setups multiply deploy points. Keep WordPress database backups independent of Pages git history. One bad deploy shouldn't leave you without rollback on both layers.