Getting Started
Install the plugin, turn static mode on, and your visitors get static pages instead of a rebuild on every visit.
From install to your first static page
Your WordPress is dynamic: it builds each page again for every visit. MyStaticWP turns your pages into static ones: it builds each page once, saves it as a file, and hands that static file to visitors. Once the plugin is active, you choose a generation style, turn static mode on and let it build a static copy of each page. From then on, visitors who are not logged in receive that static copy, while you keep editing the live, dynamic site in the same WordPress admin as usual. The steps below take about ten minutes, and you only do them once.
At the end of this page you will have:
- a static copy of every public page of your site;
- a check that visitors really receive it;
- a first measurement, on your own server, of the difference between dynamic and static;
- a clear way back if anything looks wrong.
Nothing here changes your content. Static files live in their own folders, and deactivating the plugin returns the site to plain, dynamic WordPress.
Check what you need
MyStaticWP checks its own environment and tells you on the Overview screen if something blocks it. Three things can block it; the others only change how fast static pages are served.
| Requirement | Why | If it is missing |
|---|---|---|
| WordPress and PHP | WordPress 6.0 or higher and PHP 7.4 or higher are the minimum versions the plugin is built for. | Blocked: the plugin will not run. |
| Pretty permalinks | Static files are stored under the address of each page. Plain permalinks (?p=123) cannot be mapped to files. |
Blocked. Go to Settings → Permalinks and choose any structure other than Plain. |
| Uploads folder | It must be writable: the Hybrid style stores its static files in wp-content/uploads/mystaticwp. |
Blocked. Ask your host to make the folder writable. |
| Apache or LiteSpeed | With a writable .htaccess, the web server hands out the static file itself, before WordPress starts (the server-level bypass). |
Not blocking. Static pages are then served through PHP: still no rebuild, but WordPress starts for each visit. |
| wp-content folder | It must be writable for the Strict style (wp-content/mystaticwp-strict) and for per-page plugin blocking (wp-content/mu-plugins). |
Only those two features are unavailable. |
Install and activate
- In your WordPress admin, go to Plugins → Add New → Upload Plugin.
- Choose the MyStaticWP
.zipfile you downloaded from your RemotelyLicense account, then click Install Now. - Click Activate.
A MyStaticWP entry appears in the admin menu, with six screens:
| Screen | What it is for |
|---|---|
| Overview | The dashboard: mode, static pages in cache, last regeneration, speed, alerts, and a getting-started checklist. |
| Switch | Turns static mode on or off, chooses the generation style, and rebuilds the static files. |
| Pages | Sets a different style for a category or a single page, or keeps a page fully dynamic. |
| Plugins | Chooses which plugins run on which page, and measures what each one costs. |
| Export | Exports the site as portable static files for another host. |
| License | Your license key and what happens when you uninstall. |
Activating the plugin changes nothing for your visitors. Your site stays dynamic until you turn static mode on.
Activate your license
Open MyStaticWP → License and paste the key from your RemotelyLicense account. This step is optional for using the plugin: no feature is locked without a key. The key is what allows one-click updates.
The license check runs in the administration only. It sends the license key, your site address and the product name to the licensing server, and nothing about your visitors. Nothing is sent on a visitor’s request.
Read the Overview
Open MyStaticWP → Overview. A Getting started checklist follows your site’s real state and ticks itself:
- Environment — ticked when nothing blocks the plugin (see the requirements above).
- Static mode — ticked when the switch is on.
- Pages generated — ticked when at least one static page exists.
- Speed measured — ticked after your first measurement.
You can hide the checklist at any time, and it disappears by itself when every step is done. An alert strip appears on the Overview only when something needs your attention.
Choose a generation style
Open MyStaticWP → Switch. The Generation style decides what a static page contains. It is independent of the on/off switch.
| Style | What the static copy is | Choose it when |
|---|---|---|
| Hybrid (default) | The page exactly as WordPress rendered it. Forms and interactive elements keep working. | Your pages contain forms or scripts that need WordPress behind them. |
| Strict | A true HTML, CSS and JS mirror of the page, in its own folder (wp-content/mystaticwp-strict), separate from your media library. Menus, sliders and styling keep working. Each form is replaced by a message with your contact address. |
The page needs no live backend and you want a fully standalone static copy. |
If you choose Strict, fill in the Contact address field. It appears as a mail link wherever a form was replaced. Leave it empty to show the message without a link.
The style you pick applies to the whole site. You can set a different one for a category or a single page later, on the Pages screen. Changing the style rebuilds the static files by itself.
Turn static mode on
Still on the Switch screen, click Turn static mode on. Visitors are not affected yet: until static files exist, they still see the live, dynamic site. The screen says so with this message:
Static mode is on, but no static files exist yet — visitors are still seeing the dynamic site. Click “Regenerate all” below.
While you are logged in, you always see the live site, whatever the mode.
Generate your static pages
Click Regenerate all. MyStaticWP visits each public page once, as an anonymous visitor would, and saves the result as a static page.
- A small site (up to about 30 items) is rebuilt in one go.
- A larger site is rebuilt in batches, with a progress bar. You can leave the page: the rebuild carries on in the background.
- Static pages already in place keep being served while the rebuild runs. Nothing is emptied first.
When it finishes, the Last regeneration journal lists every page with its result and its timing. Only the latest run is kept. A page can end in one of three states:
| Result | Meaning |
|---|---|
| Regenerated | The static copy was written. |
| Skipped | On purpose, with the reason: a WooCommerce system page (cart, checkout, account) is always served live; a page marked always dynamic; a page that is not published; or an address that redirects elsewhere. |
| Failed | The page could not be captured. The reason and the HTTP code are shown. |
Skipped pages are not errors. A “skipped” WooCommerce cart is exactly what you want.
Check that it works
- Open your site in a private window, or log out. Static copies are only served to visitors who are not logged in.
- Browse a few pages. They should look exactly like the live site.
- On the Switch screen, read the status line under the generation style. On Apache and LiteSpeed it should say Server-level bypass active — matching pages are served without WordPress running at all.
If you want proof from the browser, open the developer tools, go to the Network tab and reload a page:
- With the server-level bypass active, the response comes from the web server and carries no MyStaticWP header. That is normal.
- When static pages are served through PHP (no bypass), the response carries
X-MyStaticWP-Cache: hit.
A page is never served statically when its address contains a query string (?s=, ?utm_source=…), when you are logged in, or when it is listed as skipped. Those always reach the live, dynamic WordPress.
Measure the difference
On the Overview, the Speed card compares your home page built dynamically by WordPress with the same page served from its static copy: one warm-up, then five interleaved requests of each, medians shown.
Read the figures with their limits in mind:
- It is a measurement, on your own server, of the server’s response time. It is not a page-load score and it does not include the browser’s rendering.
- It runs from the server itself, without the network between you and your visitors. Visitors see a smaller gain than this card shows, because the network is the same for both.
- If the static copy is answered through PHP rather than directly by the web server, the card says so.
Optional: choose which plugins run on each page
Once static mode works, the Plugins screen lets you decide, page by page, which active plugins are allowed to run. It is independent of static mode and applies when WordPress builds a page: pages left dynamic, and the moment a static copy is generated.
Every plugin is active everywhere by default, exactly as WordPress does. Nothing is suggested to you: you untick, you preview, you save. Read Plugins, page by page before you use it, and keep the Reset button in mind: one click makes every plugin active again everywhere.
What happens next
You do not have to regenerate by hand after each change.
| Event | What MyStaticWP does |
|---|---|
| Page change | Saving, updating or deleting a page rebuilds its static copy. |
| Shared change | Changing the theme, a menu, the site identity, a Bricks template or the Bricks global styles, or updating a plugin or a theme, rebuilds the whole site once, about a minute later, however many changes came in. |
| Nothing | The site is rebuilt every day, so form security tokens on pages nobody edits do not expire. |
The Regenerate outdated or missing pages only button on the Switch screen rebuilds just what is stale. See Regeneration & rebuilds for the details.
If something looks wrong
- A page looks different from the live site. Open the Pages screen and set that page to stay dynamic, or try the other generation style for it.
- A form no longer works on a static page. Use the Hybrid style for that page, or keep it dynamic.
- A static page is stale. Click Regenerate all, or regenerate outdated pages only.
- You want to stop. Click Turn static mode off. Visitors receive the live, dynamic site again at once. Deactivating the plugin also removes its server rules and returns the site to plain WordPress.
More help is on the Troubleshooting page and in the FAQ.