Statixly

Statixly helps you create a static copy of your WordPress website, facilitating faster content delivery and reducing the security risks on production hosting.

The admin screen provides the following capabilities:

• Start a static export job
• Monitor live export status in real time
• Pause, resume, or abort the export
• Download the generated static site as a ZIP file
• Download or delete export logs
• Delete temporary export directories

Statixly systematically crawls website URLs, renders content, rewrites links for static output, and packages the results for deployment.

Typical workflow

1. First, build and set up your site as you normally do in WordPress. Make sure all content and settings are finalized before exporting.
2. Next, open the Statixly admin screen and select the Generate/Export Static Site button to start the export process.
3. After the export finishes, download the generated ZIP file containing your static website.
4. Extract the files from the ZIP archive. Upload the extracted files to your chosen static hosting provider. For example, use your website’s document root on a web hosting server, Cloudflare Pages, GitHub Pages, AWS S3, etc.

Important Requirements

• If the current WordPress website is on example.com and you want to make the static website available on example.com as well, move the WordPress website to a subdomain and protect it with HTTP Basic Auth, or move it to your localhost computer using a backup and migration plugin such as Duplicator.
• Permalink structure must not be set to Plain.
• Keep the Statixly export tab open while export is running.

Not for e-commerce, etc.

Statixly will not work on any WordPress website that generates content dynamically based on user interaction, e.g., an e-commerce or subscription-based website.

Contact forms will not work. The contact form requires immediate backend processing upon submission by the user. However, this is on our roadmap.

Advanced Opt-In Options

Statixly includes two optional safety/compatibility flags (both disabled by default):

• statixly_prefer_temp_storage_above_document_root Set to true (in the options table) only if you explicitly want Statixly working directories outside wp_upload_dir(). By default, Statixly uses WordPress uploads paths.

• statixly_allow_insecure_local_http_fetch Set to true (in the options table) only for local/self-signed certificate environments where same-site HTTPS fetches fail TLS verification. This disables SSL verification for local same-site fetches.

Need Help?

If you face any issues after installing the Statixly plugin, please open a support ticket with detailed information, and we will be happy to fix the issue.