Anindya Sundar Mandal

<p>Statixly converts your WordPress site into a fully static HTML website — eliminating PHP, databases, and server-side dependencies from your production host. The result: faster load times, a reduced attack surface, and the freedom to deploy on any web server or CDN.</p>
<p>⚡ Benefits: Why Statixly?</p>
<ul>
<li>🚀 <strong>Faster page loads:</strong> Static websites load 3 to 5 times faster than WordPress sites by serving pre-rendered HTML without PHP execution or database queries.</li>
<li>🔒 <strong>Reduced attack surface:</strong> Static sites have no login page, database connection, or server-side code on your production host. This eliminates primary attack vectors such as SQL injection and brute-force attacks.</li>
<li>🌍 <strong>Deploy anywhere:</strong> Host on Cloudflare Pages, GitHub Pages, AWS S3, or any standard web server. No PHP, MySQL, or WordPress dependency is required in production.</li>
<li>💰 <strong>Lower hosting costs:</strong> Static files can be served from free or low-cost CDN-based hosts instead of a PHP-capable server. Managed WordPress hosting typically costs $25 to $100 or more per month, while static hosting is often free or very affordable on platforms like Cloudflare Pages or Netlify, which offer unmetered bandwidth on their free tiers.</li>
<li>🛠️ <strong>Zero production maintenance:</strong> Your live site is pure HTML. With no WordPress running in production, there are no security patches, plugin updates, or server-side dependencies to manage on your public host.</li>
<li>🎛️ <strong>Live export control:</strong> Start, pause, resume, or abort the export from the admin screen and monitor progress in real time.</li>
<li>📦 <strong>One-click download:</strong> The entire static site is packaged as a ZIP file, ready for extraction and upload.</li>
<li>🔄 <strong>Auto-resume on interruption:</strong> If internet connectivity drops during export, the job resumes automatically once the connection is restored.</li>
</ul>
<p>🔍 SEO Benefits</p>
<ul>
<li>📊 <strong>Better Core Web Vitals scores:</strong> Static HTML loads faster, directly improving Time to First Byte (TTFB) and Largest Contentful Paint (LCP), which are metrics Google uses as ranking signals.</li>
<li>🤖 <strong>Improved crawl efficiency:</strong> Search engine bots fetch plain HTML instantly, with no server-side rendering delay. This signals high crawl health and allows engines to index content more effectively.</li>
<li>⏱️ <strong>Higher uptime reliability:</strong> Static files served from a CDN experience near-zero downtime, helping avoid Google ranking penalties for frequently unreachable URLs.</li>
<li>🧹 <strong>No WordPress footprint in production:</strong> Common WordPress paths such as /wp-admin and /wp-login.php are removed from the live site, reducing spam crawling and preserving crawl budget.</li>
</ul>
<p>The admin screen provides the following capabilities:</p>
<ul>
<li>Start a static export job</li>
<li>Monitor live export status in real time</li>
<li>Pause, resume, or abort the export</li>
<li>Download the generated static site as a ZIP file</li>
<li>Download or delete export logs</li>
<li>Delete temporary export directories</li>
</ul>
<p>Statixly systematically crawls website URLs, renders content, rewrites links for static output, and packages the results for deployment.</p>
<h4>Typical workflow</h4>
<ol>
<li>First, build and set up your site as you normally do in WordPress. Make sure all content and settings are finalized before exporting.</li>
<li>Next, open the Statixly admin screen and select the <strong>Generate/Export Static Site</strong> button to start the export process.</li>
<li>After the export finishes, download the generated ZIP file containing your static website.</li>
<li>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.</li>
</ol>
<h4>Important Requirements</h4>
<ul>
<li>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.</li>
<li>Permalink structure must not be set to <strong>Plain</strong>.</li>
<li>Keep the Statixly export tab open while export is running.</li>
</ul>
<h4>Not for e-commerce, etc.</h4>
<p>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.</p>
<p>Contact forms will not work. The contact form requires immediate backend processing upon submission by the user. However, this is on our roadmap.</p>
<h4>HTTP Basic Authentication</h4>
<p>If your WordPress install is protected with HTTP Basic Auth (for example, a staging or subdomain install), enter your credentials under <strong>Statixly <span aria-hidden="true" class="wp-exclude-emoji">→</span> Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Security</strong> so Statixly can authenticate during export.</p>
<p>Credentials are encrypted before storage and never exposed in logs or diagnostics output.</p>
<h4>Advanced Opt-In Options</h4>
<p>Statixly includes two optional safety/compatibility flags, both disabled by default and configurable from the <strong>Statixly <span aria-hidden="true" class="wp-exclude-emoji">→</span> Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> General</strong> screen.</p>
<ul>
<li>
<p><strong>Allow insecure local HTTP fetch</strong><br />
Enable this only for expired, invalid, or self-signed certificate environments where same-site HTTPS fetches fail TLS verification. This turns off SSL verification only for local same-site fetches.</p>
</li>
<li>
<p><strong>Prefer temporary storage above document root</strong><br />
Enable this only if you explicitly want Statixly working directories outside <code>wp_upload_dir()</code>. By default, Statixly uses WordPress uploads paths. Please note that this option works only if the intended directory is readable and writable by the web server user.</p>
</li>
</ul>
<p>Both flags can also be set directly in the options table if preferred.</p>
<h4>Need Help?</h4>
<p>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.</p>


Statixly – Static Site Generator

Convert your WordPress site into a blazing-fast, static HTML site and deploy anywhere — no PHP, no database, reduced attack surface in production.

StaticWeb.io

<p>Turns your WordPress site into a secure, lightning-fast static website.</p>
<h4>Features</h4>
<ul>
<li>Deploy website directly to S3 and CloudFront</li>
<li>Export website to a directory that can be served by your web server</li>
<li>Full WP-CLI support</li>
</ul>
<h4>Speed</h4>
<p>Static websites are many times faster than a normal WordPress server.<br />
A simple S3 + CloudFront setup can easily serve millions of users.<br />
The greatly increased speed generally improves SEO performance.</p>
<h4>Security</h4>
<p>Making the public version of your website a static website allows you to restrict access to your WordPress server.<br />
This dramatically reduces the attack surface of your website and makes expensive WAF services unnecessary.</p>


StaticWeb Deploy

Generate static sites for deployment as files or S3-compatible storage.

Statixly – Static Site Generator vs StaticWeb Deploy