Static Publication
Edit in WordPress. Publish a static site.
Keep your WordPress editor and deliver completed pages through Cloudflare Pages. Static Publication builds, uploads and checks the public copy after your content changes.
One editing source. A separate public copy.
WordPress renders the pages; the plugin gathers their HTML and referenced images, stylesheets, scripts and fonts. It sends those files to your Cloudflare Pages project, then checks that the new generation is visible at your live address.
For example, changing a service page schedules publication in the background. Your save finishes without waiting for the upload. The plugin reuses the last verified inventory for local changes; global changes and manual publication rebuild the complete site.
A saved edit is not yet a delivered edit. Check Current state under Settings → Static Publication to see whether the matching revision has reached the public site.
The editor stays in WordPress. The publishing step produces the pages visitors receive; it does not move the WordPress application into their browsers.
Check the parts that cannot become static
Public articles, service pages and their assets are suitable starting points. A static copy does not execute WordPress PHP or query its database when someone visits.
Forms, site search, logins, baskets and personalised pages need a compatible server-side service or a separate dynamic route. Test each interaction before switching the public hostname. A form that looks correct is not proof that submissions arrive.
The plugin preserves individual page exclusions and canonical targets. Its generated sitemap includes eligible canonical routes, not every file in the deployment. Publishing a page does not guarantee that a search engine will index it.
Prepare WordPress and Cloudflare
- WordPress: version 6.5 or later, PHP 8.0 or later with OpenSSL, and an enabled sitemap on the same origin.
- Cloudflare: a Pages project, account ID, zone ID, production branch and HTTPS live address.
- API access: a bearer token restricted to the required account and zone, with Cloudflare Pages edit and cache-purge permissions. Legacy Global API Keys are not supported.
The build runs in PHP inside WordPress. You do not need a separate build service, command-line tool or editorial workflow plugin. Cloudflare Pages is required for delivery; check its Direct Upload documentation and current deployment limits before choosing this setup.
Make the first publication a checked change
- Back up the site and test the setup on a staging copy.
- Install and activate the ZIP through Plugins → Add Plugin → Upload Plugin.
- Open Settings → Static Publication. Enter the Cloudflare values, live URL, sitemap URL and token. Choose the required search visibility.
- Select Publish site now for the initial complete build.
- Check Current state for the delivered revision and live receipt. Then inspect the public pages, navigation, images and any interactive functions.
If delivery fails, inspect the reported error and correct its cause. Pending work is retained when WordPress or Cloudflare is temporarily unavailable. Deleting or unpublishing content starts a complete inventory build so retired routes can disappear from the next deployment.
Keep the editor. Deliver the finished pages.
Download the GPL-licensed plugin, test your site’s dynamic features and verify the first publication before changing the live setup.