Description
Staatic lets you create and deploy a streamlined static version of your WordPress site, enhancing performance, SEO, and security simultaneously.
Features of Staatic include:
- Powerful Crawler to transform your WordPress site quickly.
- Supports multiple deployment methods, e.g. GitHub, Netlify, AWS (Amazon Web Services) S3 or S3-compatible providers + CloudFront integration, or even your local server (dedicated or shared hosting).
- Very flexible out of the box (allows for additional urls, paths, redirects, exclude rules, etc.).
- Supports HTTP (301, 302, 307, 308) redirects, custom “404 not found” page and other HTTP headers.
- CLI command to publish from the command line.
- Compatible with WordPress MultiSite installations.
- Compatible with WPML (multilingual) installations.
- Supports HTTP basic auth protected WordPress installations.
- Various integrations to improve compatibility with popular WordPress plugins.
Depending on the chosen deployment method, additional features may be available.
Staatic Premium
In order to support ongoing development of Staatic, please consider going Premium. In addition to helping the authors maintain Staatic, Staatic Premium adds additional functionality.
For more information visit Staatic.
Screenshots
Installation
Installing Staatic is simple!
Install from within WordPress
- Visit the plugins page within your WordPress Admin dashboard and select ‘Add New’;
- Search for ‘Staatic’;
- Activate ‘Staatic’ from your Plugins page;
- Go to ‘After activation’ below.
Install manually
- Upload the ‘staatic’ folder to the
/wp-content/plugins/
directory; - Activate the ‘Staatic’ plugin through the ‘Plugins’ menu in WordPress;
- Go to ‘After activation’ below.
After activation
- Click on the ‘Staatic’ menu item on the left side navigation menu;
- On the settings page, provide the relevant Build & Deployment settings;
- Start publishing to your static site!
FAQ
-
How will Staatic improve the performance of my site?
-
Staatic transforms your dynamic WordPress site into a streamlined static site. Starting at the homepage or a designated URL, Staatic uses a web crawler to methodically navigate through every link, post, and page. As it moves through the site, dynamically generated content is captured and converted into static HTML files, while simultaneously fetching related assets like images and scripts.
By eliminating both WordPress and PHP from the delivery process, pages from your site are served instantly, bypassing the delay of on-the-fly generation. This guarantees the quickest possible load times and significantly reduces the time to first byte (TTFB), offering an unparalleled browsing experience for your visitors and enhancing your site’s SEO positioning.
-
Why not use a caching plugin?
-
Caching plugins boost site performance by storing data for quicker access, yet they don’t fully bypass WordPress, introducing some latency. Additionally, after every update, these plugins need cache prewarming to serve the first requests quickly. In contrast, static sites are always ‘warmed up’, ensuring consistently rapid load times.
Furthermore, with Staatic, you gain the flexibility to host your site on any platform of your choice. This means you could opt for an ultra-fast cloud provider or a robust content delivery network, further amplifying your site’s performance and ensuring optimal user experience.
-
Will the appearance of my site change?
-
No, it shouldn’t. However, if there is a difference in the static version of your site, it might be due to invalid HTML in your original WordPress site that couldn’t be accurately converted. In such instances, consider checking your HTML’s validity using services like the W3C Markup Validation Service.
-
How will Staatic improve the security of my site?
-
By converting your site into static HTML pages, you substantially minimize the potential attack surface. This strengthens your website’s security and reduces the ongoing need to update WordPress, its plugins, and themes constantly. As a result, you can enjoy greater peace of mind, knowing your site is resilient to most threats.
-
Is Staatic compatible with all plugins?
-
Not entirely. When your site undergoes conversion to a static format, dynamic server-side functionalities become unavailable. As a result, plugins relying on these features – such as those processing forms or fetching external data – might not function immediately or might be unsupported altogether.
To accommodate such features, adjustments or alternatives may be necessary. Alternatively, you can opt for Staatic Premium, which seamlessly integrates some of these functionalities. For detailed insights, visit staatic.com.
-
Staatic offers broad compatibility, only requiring the permissions to write to the working directory and to initiate an HTTP connection with your dynamic WordPress installation.
-
Where can I get help?
-
If you have any questions or issues, please have a look at our documentation and FAQ first.
If you cannot find an answer there, feel free to open a topic on our Support Forums.
Want to get in touch directly? Please feel free to contact us. We will get back to you as soon as possible.
Reviews
Contributors & Developers
“Staatic – Static Site Generator” is open source software. The following people have contributed to this plugin.
Contributors“Staatic – Static Site Generator” has been translated into 2 locales. Thank you to the translators for their contributions.
Translate “Staatic – Static Site Generator” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.10.6
Release date: October 4th, 2024.
Improvements
- Adds publication type to the publication list table and detail pages.
- Extends support for relative file paths in selective publication with examples.
- Introduces
--merge
option for thestaatic publish
command. - Expands MIME type support for optimizing generated web server configurations.
- Updates external dependencies.
1.10.5
Release date: September 16th, 2024.
Features
- Releases SFTP Server deployment method.
Improvements
- Enhances compatibility of the “Downgrade HTTPS to HTTP” setting with Local.
- Adds warnings for publication entry URLs that result in HTTP redirect responses.
- Clarifies actions when site health checks fail due to loopback request issues.
- Includes
X-Staatic-Request
header in crawler requests. - Updates external dependencies.
Fixes
- Resolves issues with WP-CLI
staatic
command registration.
1.10.4
Release date: July 25th, 2024.
Improvements
- Enhances support for lazy-loaded assets.
Fixes
- Fixes a PHP scoping issue that prevented successful SFTP deployments.
1.10.3
Release date: July 4th, 2024.
Fixes
- Fixes PHP scoping issue which may cause fatal errors.
1.10.2
Release date: July 4th, 2024.
Improvements
- Enforces a publication time limit, which is set to four hours by default.
- No longer automatically retries failed HTTP requests due to time-outs.
- Shows sensitive publication log details only to users with settings permissions.
- Halts publication immediately if the entry URL fails during crawling.
- Updates external dependencies.
1.10.1
Release date: May 14th, 2024.
Improvements
- Improves XML sitemap recognition.
- Updates external dependencies.
Fixes
- Restores global support for the
data-srcset
HTML attribute.
1.10.0
Release date: April 17th, 2024.
Improvements
- Enhances the presentation of publication logs.
- Improves overall compatibility with FlyingPress plugin.
- The “Netlify” deployment method now waits for deploy to finish and provides deploy URL.
- Expands HTTP client retry to include 502 Bad Gateway errors alongside 503 and 429 statuses.
- Introduces
staatic_publication_tasks
filter hook to customize the publication process. - Various performance optimizations.
- Updates external dependencies.
Fixes
- Tightens fallback URL extraction to ignore adjacent non-URL characters.
- Prevents the fallback URL extractor from clearing content upon encountering invalid unicode data.
- Properly handles unexpected Guzzle HTTP exceptions.
Earlier releases
For the changelog of earlier releases, please refer to the changelog on staatic.com.