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.

Gareth Bult

<p>Welcome to the Make Me Static Plugin for WordPress. This plugin is a static site generator and aims to create and maintain a static copy of your WordPress website within a Git repository. This version includes automatic access to a free Git solution and Page provider platform. (so no setup or credentials are necessary)</p>
<p>Alternatively the static site can be generated and stored in a GitLab Git Repository that can be used as a source for a static page platform such as CloudFlare Pages. The plugin provides customised sitemap and change tracking which connects to an external crawling service which does all the heavy lifting.</p>
<p>We have made great efforts in this version to minimise the configuration required to get going, if you have any problems (with anything) please let is know and we’ll do our best to help. Check out this YouTube video for an introduction to static front-ends and a walk-through of converting a pre-existing WordPress site into a WordPress site with a static front-end.</p>
<p><span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/ZJ5IDgZ9u-Q?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span></p>
<h3>How the service works</h3>
<p>The plugin connects to a directory service on the Internet at one of the directory URL’s listed below. This in turn will point the plugin to a ‘crawler’ that has been allocated to your site.<br />
When you ask the plugin to make a static copy of your site, it will instruct the crawler to visit all the pages on your site to determine which have changed since it’s last visit. Any changed pages will be copied to a Git repository, which in turn can publish pages directly to a page hosting service.</p>
<p>The default option is to use a Git account hosted by MadPenguin, and to publish the site on MadPenguin’s page hosting platform. As a result the default options do not require any specific Git or Page hosting configuration to get going. If on the other hand you choose to use a hosted Git service such as GitLab, you will need to enter some credentials for your online account, and from there configure your GitLab account to publish to a page hosting service.</p>
<p>Once you have successfully published a static copy of your site, all you need to do is point your domain at the address of the page hosting service, and asssuming your domain matches the one you<br />
entered when setting up your profile within the plugin, you should be up and running.</p>
<p>The service retains a metadata database for the site which includes file names, sizes and modification times, together with any credentials that have been added when creating a profile. (Sensitive credentials and other information is encrypted at rest).  The external service is responsible for all scanning and processing activities to mitigate strain on the WordPress server.<br />
The only private data transferred to the external service is the information you enter when creating a profile. All other information is obtained via an anonymous external scan, hence publically available. If you have selected the default Git option, then the service will also retain a static copy of the site.</p>
<h3>Useful references</h3>
<ul>
<li><a href="https://makemestatic.com/" rel="nofollow ugc">The service product page</a></li>
<li><a href="https://makemestatic.com/terms-and-conditions/" rel="nofollow ugc">Terms and Conditions of Service</a></li>
<li><a href="https://makemestatic.com/privacy-policy/" rel="nofollow ugc">Privacy Policy</a></li>
<li><a href="https://makemestatic.com/getting-started/" rel="nofollow ugc">Getting Started</a></li>
<li><a href="https://makemestatic.com/service-status/" rel="nofollow ugc">Service Status</a></li>
<li><a href="https://github.com/oddjobz/make_me_static/issues" rel="nofollow ugc">Support Forum</a></li>
</ul>
<p>Make me static directory service URL’s;</p>
<ul>
<li>https://mms-directory-1.madpenguin.uk</li>
<li>https://mms-directory-2.madpenguin.uk</li>
<li>https://mms-directory-3.madpenguin.uk</li>
</ul>
<p>Other URL’s used to load code;</p>
<ul>
<li>https://assets.makemestatic.com, source for stage-2 crawler UI</li>
<li>https://status.makemestatic.com, endpoints that indicate the currently deployed version of a site</li>
<li>https://weblogs.makemestatic.com, source for dynamically loaded weblogs data / websockets</li>
<li>https://mms-crawler-*.madpenguin.uk, location of the actual crawlers (via websocket)</li>
</ul>
<p>Note that this in an integrated solution, the 3rd party crawling service is owned and operated by the plugin authors on a combination of cloud hosted and on premesis equipment.</p>
<h3>Live Web Statistics (<em>experimental</em>)</h3>
<p>If you opt to use the integrated Pages platform, this also provides a live WebStats option that uses the following URL;</p>
<ul>
<li>https://weblogs.makemestatic.com</li>
</ul>
<p>This allows live webstats to be seamlessly delivered into your control panel and updated in real-time via a websocket connection. Do not use this URL directly!<br />
This URL is only referenced once you click on the webstats icon next to your profile.</p>
<h3>How Does it work?</h3>
<p>The WordPress site is scanned by the MMS service under direction from the WordPress plugin. This off-loads the scanning process to specialised software which aims to minimise the loading on the WordPress server while scans are in progress.</p>
<p>There are three types of scan that can be performed;</p>
<ul>
<li>
<p>An “update”, which literally only looks at entries with changed sitemap timestamps<br />
(this is very quick and great for typo’s and any changes that only affect a single page)</p>
</li>
<li>
<p>A “synchronise”, typically this will scan every asset on the WordPress site and compare a checksum of each asset against it’s database to see if it’s changed since the last scan. Any changes are then transferred to the connected Git repository.</p>
</li>
<li>
<p>A “Git verification”, this is like a “synchronise”, but also scans the Git repository for assets that are no longer referenced by the site (and removes them).</p>
</li>
</ul>
<p>As the site is scanned “from the outside” there should be no risk of the plugins actions exposing any data that isn’t already public. By the same token the external service has no ability to modify WordPress so the security footprint of the plugin is tiny.</p>
<h3>Feature bullet points</h3>
<ul>
<li>The plugin provides a way to produce a static copy of your website in a git repository</li>
<li>The result is compatible with both Github pages and CloudFlare pages for automatic publication</li>
<li>Multiple profiles are supported for (A+B_…) testing</li>
<li>Various scan rates are supported from one page per 5s to 7 cores flat out</li>
<li>Scheduled updates are supported and automated scanning</li>
<li>Currently “Gitlab” is supported with plans for GitHub and on-prem Gitlab</li>
<li>Support push services (WebPushr) to automatically notify subscribers on scan completion</li>
<li>Issue tracker for each profile to diagnose problems
<ul>
<li>Handles current and historical issues</li>
<li>Ability to acknowlede or delete issues when resolved</li>
</ul>
</li>
<li>GUI access to the internal asset database
<ul>
<li>Search as you type filtering</li>
<li>Pinning (force assets to be scanned regardless of perceived change)</li>
<li>Selective / manual queueing of assets for testing</li>
</ul>
</li>
<li>Ability to include manual / static assets in the scan (in the WP tree but unmanaged by WP)</li>
<li>Ability to exclude specific files and folders</li>
<li>Setup Wizard is included for a guided profile creation</li>
</ul>
<h3>The Technology</h3>
</p>
<ul>
<li>The Plugin presents as a WordPress Admin / plugin page</li>
<li>Backend connections are made over websockets using PKI</li>
<li>The crawler respects Robots.txt, (make sure the “MMSbot” agent is allowed on your site)</li>
<li>MMS Javascript runs in an isolated module and CSS “plays nice” with WordPress</li>
<li>Global CSS and theming is partitioned and user editable (if you feel the need …)</li>
<li>All of the front-end JS code and PHP is either GPL2 or MIT licensed</li>
<li>Backend-code is all based on the Orbit Framework (the framework and DB are all MIT licensed)</li>
<li>Orbit is a ‘real time’ framework, so the admin panel is 100% reactive.
<ul>
<li>Progress bar updates are typically “per percent” granularity</li>
<li>All statuses, totals, etc, are updated as they happen</li>
<li>Unless you’ve hit a bug, there is no mileage in reloading the MMS plugin page</li>
<li>If you change your license information, it will change in real-time</li>
<li>If the crawler allocated to your site changes (perhaps due to a license upgrade) then the<br />
appropriate version of the crawler UI will be uploaded “into” the page from the new<br />
crawler.</li>
</ul>
</li>
</ul>


Make Me Static, Static Site Generator, Git, Pages and Live Stats

Static site generator using Git for storage. Comes with free integrated Git + Pages solution including Live WebStats.

Statixly – Static Site Generator vs Make Me Static, Static Site Generator, Git, Pages and Live Stats