Katsushi Kawamori

<h4>Requires</h4>
<ul>
<li>This plugin only supports execution from the command line using <a href="https://wp-cli.org/" rel="nofollow ugc">WP-CLI</a>.</li>
</ul>
<h4>Generate</h4>
<ul>
<li>Generated static site with WP-CLI command.</li>
<li>Replaces URLs or strings in content.</li>
<li>Supports custom post types.</li>
<li>Outputs the archive page for the year, month, and day.</li>
<li>Outputs category archives.</li>
<li>Outputs tag archives.</li>
<li>Outputs author archives.</li>
<li>Outputs feed.</li>
<li>Outputs categories feed.</li>
<li>Outputs tags feed.</li>
<li>Sitemap by default in WordPress.</li>
<li>Generates a file from a specified URL.</li>
</ul>
<h4>Copy</h4>
<ul>
<li>Copy the files that the following tags in the html read to the static site.</li>
</ul>
<pre><code><a href="...">
<img src="...">
<img srcset="...">
<video src="...">
<audio src="...">
<link href="...">
<script src="...">
<iframe src="...">
<source src="...">
<track src="...">
<object data="...">
<embed src="...">
<script>...</script>
CSS
</code></pre>
<h4>WP-CLI</h4>
<ul>
<li>1st argument(string) : <code>/home/www/localhost.test</code> : output path of full path</li>
<li>2nd argument(string) : <code>https://localhost.test</code> : url of output homepage</li>
<li>optional argument1(string) : <code>--cb1="site.com" --ca1="localhost.test"</code> : <code>cb1</code> -> Original string | <code>ca1</code> -> Changed string</li>
<li>optional argument2(string) : <code>--cb2="/wordpress" --ca2="/"</code> : <code>cb2</code> -> Original string | <code>ca2</code> -> Changed string</li>
<li>optional argument3(bool) : <code>--s</code> : Only arguments 4-7, which directly specify the URL and file name, are executed.</li>
<li>optional argument4(string) : <code>--file1="ja/feed/index.xml" --orgurl1="https://site.com/ja/feed/"</code> : <code>file1</code> -> Output filename | <code>orgurl1</code> -> Original url</li>
<li>optional argument5(string) : <code>--file2="ja/category/whatsnew-ja/feed/index.xml" --orgur2="https://site.com/ja/category/whatsnew-ja/feed/"</code> : <code>file2</code> -> Output filename | <code>orgurl2</code> -> Original url</li>
<li>optional argument6(string) : <code>--file3="feed/googleimagesitemap/index.xml" --orgurl3="https://site.com/feed/googleimagesitemap/"</code> : <code>file3</code> -> Output filename | <code>orgurl3</code> -> Original url</li>
<li>optional argument7(string) : <code>--file4="feed/googlevideossitemap/index.xml" --orgur4="https://site.com/feed/googlevideossitemap/"</code> : <code>file4</code> -> Output filename | <code>orgurl4</code> -> Original url</li>
<li>
<p>optional argument8(bool) : <code>--c</code> : Outputs file copy status to the console.</p>
</li>
<li>
<p>Example1 <code>wp static /home/www/localhost.test https://localhost.test</code></p>
</li>
<li>
<p>Example2 <code>wp static /home/www/localhost.test https://localhost.test --cb1="site.com" --ca1="localhost.test" --cb2="/wordpress" --ca2="/"</code><br />
In the html or xml, the original home page is converted to “https://localhost.test”, “site.com” is converted to “localhost.test”, and “/wordpress” is converted to “/”.</p>
</li>
</ul>


Static Site Generator

kryptonmediagroup

<p>Cyclone Static generates fully-rendered static HTML files for every page on your WordPress site and instructs Apache to serve them directly — bypassing PHP, WordPress, and the database for anonymous visitors.</p>
<p>When a static file exists for a requested URL, Apache reads it from disk and sends it without starting PHP or querying the database. The visitor receives a complete HTML page. Their browser runs your JavaScript, plays your audio, renders your animations — everything works as it did before, because the static file contains the same HTML WordPress would have generated.</p>
<p>Logged-in users, POST requests, query strings, and administrative paths bypass the static cache and receive live WordPress as normal.</p>
<h4>Key features</h4>
<ul>
<li><strong>Static file serving</strong> — Apache serves files directly from disk. PHP and the database are not involved in serving anonymous page requests.</li>
<li><strong>Automatic regeneration</strong> — When you publish or update a post or page, it is automatically queued for regeneration. You do not need to do anything.</li>
<li><strong>Reduced attack surface</strong> — Static HTML files do not execute PHP or query a database. Common WordPress-targeted attack vectors that require a live PHP process — such as SQL injection via PHP, PHP code execution, and xmlrpc.php abuse — do not apply to anonymous page requests served as static files.</li>
<li><strong>CDN integration</strong> — Works alongside W3 Total Cache. Direct integration with Bunny.net, Cloudflare, KeyCDN, and Amazon CloudFront is available in Cyclone Static Pro.</li>
<li><strong>W3 Total Cache compatible</strong> — Installs its .htaccess rules before W3TC rules. Works alongside or without W3TC.</li>
<li><strong>Non-destructive</strong> — Deactivating the plugin removes the .htaccess rules and WordPress resumes normal operation. Your cached files are not deleted without your explicit consent — a prompt appears when you deactivate, asking whether to keep or delete them.</li>
<li><strong>Free and open</strong> — No license required. Support via the WordPress.org community forums.</li>
</ul>
<h4>System requirements</h4>
<ul>
<li>WordPress 6.0 or later</li>
<li>PHP 8.0 or later</li>
<li><strong>Apache web server</strong> with mod_rewrite enabled</li>
<li>.htaccess support enabled (AllowOverride All or equivalent)</li>
<li>WordPress Multisite is not supported in this version — Multisite support is available in Cyclone Static Pro</li>
</ul>
<p><strong>Nginx users:</strong> Cyclone Static manages .htaccess automatically on Apache. If your server runs Nginx, the Settings page includes a ready-to-paste Nginx server block under <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Nginx Configuration</strong>.</p>
<h4>CDN support</h4>
<p>The free version works automatically alongside W3 Total Cache — CDN purges are routed through W3TC when it is active.</p>
<p>Direct API integration with Bunny.net, Cloudflare, KeyCDN, and Amazon CloudFront is available in Cyclone Static Pro.</p>
<h4>Privacy</h4>
<p>Cyclone Static does not collect, transmit, or store any personal data. The queue table stores only URLs. No external service is contacted except the CDN purge APIs you explicitly configure.</p>
<h3>Support</h3>
<p>Support is provided via the WordPress.org community forums. Post your question there — answers are public, so search first as your question may already be answered. For private inquiries, you can reach us at support@kryptonmediagroup.com. Confirmed bugs are addressed through plugin updates. Private one-on-one support is not offered via the forums.</p>
<h3>External Services</h3>
<p>Cyclone Static can optionally connect to the following third-party services to purge cached content from your CDN. These connections are only made when you configure a CDN provider under <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> CDN Integration</strong> and a purge is triggered. No data is sent to these services unless you explicitly configure them.</p>
<h4>Bunny.net</h4>
<p>Used for CDN cache purging. Your Bunny.net API key and Pull Zone ID are sent to the Bunny.net API.<br />
* Service: https://bunny.net/<br />
* API documentation: https://docs.bunny.net/reference/purgepublicpullzone<br />
* Privacy policy: https://bunny.net/privacy/</p>
<h4>Cloudflare</h4>
<p>Used for CDN cache purging. Your Cloudflare API token and Zone ID are sent to the Cloudflare API.<br />
* Service: https://www.cloudflare.com/<br />
* API documentation: https://developers.cloudflare.com/api/resources/cache/methods/purge/<br />
* Privacy policy: https://www.cloudflare.com/privacypolicy/</p>
<h4>KeyCDN</h4>
<p>Used for CDN cache purging. Your KeyCDN API key and Zone ID are sent to the KeyCDN API.<br />
* Service: https://www.keycdn.com/<br />
* API documentation: https://www.keycdn.com/api<br />
* Privacy policy: https://www.keycdn.com/privacy</p>
<h4>Amazon CloudFront</h4>
<p>Used for CDN cache invalidation. Your AWS Access Key, Secret Key, and CloudFront Distribution ID are sent to the Amazon CloudFront API.<br />
* Service: https://aws.amazon.com/cloudfront/<br />
* API documentation: https://docs.aws.amazon.com/cloudfront/latest/APIReference/API_CreateInvalidation.html<br />
* Privacy policy: https://aws.amazon.com/privacy/</p>


Cyclone Static

Serve static HTML files directly from disk — no PHP, no database queries for anonymous visitors.

Static Site Generator vs Cyclone Static