Deploy a static WordPress site
Before you start
In this tutorial, you will migrate a WordPress site to Cloudflare Workers, making use of . Serving a static version of your WordPress site has many advantages over directly exposing your WordPress site. While WordPress is extremely powerful and easy to use, the consistent discovery of new vulnerabilities make it an obvious target for hackers to attack. Because WordPress is built on PHP, each incoming request to your site regenerates a new response on the server – for most websites this is not necessary, and leads to scaling issues when your site receives a lot of traffic.
This tutorial assumes that you are:
- The Administrator account on your WordPress site.
- Able to install WordPress plugins on the site.
To start, install the plugin to export your WordPress site to a ZIP file. In your WordPress admin, navigate to the Add Plugins page, by default at
/wp-admin/plugin-install.php. In the search bar, search for
WP2Static and confirm that the resulting plugin that you will be installing matches the plugin below.
Select Install on the plugin. After it has finished installing, select Activate.
Export your WordPress site
When your application refreshes, you should see a new section in your sidebar called WP2Static. Navigate to that section to begin your first static WordPress export.
From the Where will you host... dropdown on the page, select ZIP archive (.zip). WP2Static supports a number of different export types, including manual and automated exports. To make deployment easier, select Allow offline usage – this will make all the URLs in your WordPress export relative:
https://mysite.com/logo.png, and will reduce the number of asset errors that could occur depending on your theme and WordPress setup.
To do your first export, select Start static site export (this operation may take a while), and when it completes, save the ZIP file somewhere you can easily find it later.
Creating the Workers project
With an export ready of your site, it is time to get to work deploying it. To do this, use , the command-line tool for Cloudflare Workers. If you have not yet installed and configured Wrangler, refer to the guide.
Once Wrangler is installed and configured, we can create a new project for deploying your static WordPress site to Workers. To generate a new project run:
Generate a new project
$ wrangler generate --site wp-static
Port the WordPress Site
The newly generated
wp-static directory will contain three components:
publicdirectory, representing the site you want to deploy to Workers. This will be the location of your WordPress site.
workers-sitedirectory, which contains the Workers script that will serve your website content. In this tutorial, you will not change anything in this folder.
wrangler.tomlfile, which contains the configuration details for your
wp-staticdirectory. You will populate this file with some information before the project is deployed.
public folder mentioned above.
Open the ZIP file downloaded from your WordPress static export, and extract the contents of the ZIP into the
Copy files into the public directory
$ cp -R ~/Downloads/wp-static-html-output-<some-tag>/ ./public
Your directory structure should look something like this:
Listing the files in wp-static
$ tree wp-static├── public│ ├── 2018│ ├── 2019│ ├── 404.html│ └── # More exported WordPress files├── workers-site│ ├── index.js│ ├── node_modules│ └── # More Workers script files└── wrangler.toml
Using Wrangler’s preview feature, you can quickly upload a version of your site to the Cloudflare Workers preview service and review that the static export looks as expected. Running
wrangler dev will upload your static site and preview it in a browser window.
There are some features available in WordPress sites that will not be supported in a static site environment:
- WordPress Forms
- WordPress Comments
- Any links to
/wp-adminor similar internal WordPress routes
Deploying your WordPress site to Workers has benefits for your site’s performance, security, and cost. With a static version of your site being served, you can do a number of things with your live WordPress installation:
- Move your WordPress install to a private URL or subdomain, and serve the static version of your site by deploying the Workers application to your domain. Refer to to learn more.
- Run your WordPress instance locally, or put your now-hidden WP instance behind something like to only give access to your contributors. This has a dramatic effect on the number of attack vectors for your WordPress site and its content.
- Downgrade your WordPress hosting plan to a cheaper plan. Because the memory and bandwidth requirements for your WordPress instance are now much smaller, you can often host it on a cheaper plan, or moving to shared hosting. Your Cloudflare Workers plan is priced per-request, and because you can host up to thirty sites on your account, serving a high number of static WordPress sites can be an order of magnitude cheaper on Workers.