説明
Staatic turns WordPress into a practical static site generator. Keep editing posts, pages, menus, media, and settings in WordPress, then publish a static copy made of HTML, images, CSS, JavaScript, and other assets.
The public site can be served without WordPress, PHP, or a database in the visitor request path. That can improve performance, reduce origin load, and shrink the public attack surface while preserving the familiar WordPress editing workflow.
This is especially useful for a private-origin, public-static setup: WordPress remains available for editors and publication work, while visitors receive prebuilt files from your chosen hosting target.
Staatic includes the publication workflow and deployment methods needed to run a self-hosted static WordPress site.
Staatic の機能は次のとおりです:
- Crawls your WordPress site and builds a static publication from the pages and assets it discovers.
- Publishes from WordPress Admin, with publication status, logs, resource details, and downloadable output.
- Deploys to Local Directory, Amazon S3 or S3-compatible storage, GitHub, Netlify, SFTP, or a zip archive.
- Supports redirects, custom 404 pages, additional URLs and paths, exclude rules, and HTTP headers.
- Includes a WP-CLI command for command-line publication workflows.
- Works with WordPress Multisite, WPML, and HTTP Basic Auth protected WordPress origins.
- Helps separate the public site from WordPress admin, plugin runtime, and database-backed page generation.
- Provides integration hooks and compatibility improvements for common WordPress setups.
Staatic Premium and Staatic Cloud add features such as forms integration, search integration, scheduled publications, change-based publications, and managed static WordPress hosting. The Community edition remains suitable when you want to generate and deploy a static version of a WordPress site yourself.
Staatic プレミアム
Staatic Premium supports ongoing development and adds functionality for teams that need more than the Community edition.
Premium features include forms integration, search integration, scheduled publications, change-based publications, additional automation, and Staatic Cloud deployment options.
詳細については、Staaticをご覧ください。
スクリーンショット
インストール
Staatic のインストールは簡単です !
WordPress からインストール
- WordPress 管理者ダッシュボード内のプラグインページにアクセスし、「新規追加」を選択します;
- 「Staatic」を検索してください;
- プラグインページから「Staatic」を有効化します;
- 下記の「有効化後」に進んでください。
手動でインストール
- 「staatic」フォルダーを
/wp-content/plugins/ディレクトリにアップロードします; - WordPressの「プラグイン」メニューから「Staatic」プラグインを有効化します;
- 下記の「有効化後」に進んでください。
有効化後
- 左側のナビゲーションメニューにある「Staatic」メニューをクリックしてください;
- 設定ページで、関連するビルド & 展開設定を指定します;
- 静的サイトへの公開を開始しましょう !
FAQ
-
Staatic はサイトのパフォーマンスをどのように向上させますか ?
-
Staatic crawls your WordPress site like a visitor, starting from the site’s front page or configured Custom Origin URL, plus any additional URLs or paths you provide. It captures the generated HTML and related assets, then stores them as a static publication.
When that publication is deployed, visitors receive prebuilt files instead of waiting for WordPress, PHP, plugins, and the database to build each page on demand. This usually improves time to first byte, reduces server load, and gives you a simpler public delivery path.
-
なぜキャッシュプラグインを使わないのですか ?
-
Caching plugins can be useful, but the public request still usually reaches WordPress infrastructure. Cache misses, cache purges, plugin behavior, and origin capacity can still affect visitors.
Staatic changes the architecture: the public site is a deployed set of static files. You can host those files on your own server, object storage, a static hosting provider, or a CDN-backed setup, depending on the deployment method you choose.
-
サイトの外観は変わりますか ?
-
No, it should not. Staatic publishes the output that WordPress already renders for visitors.
If the static version differs, the cause is usually frontend behavior that depends on server-side requests, invalid HTML, blocked assets, authentication, or plugin/theme output that behaves differently while being crawled. The publication resources and logs can help identify what was captured and what failed.
-
Staatic はサイトのセキュリティをどのように向上させますか ?
-
Static delivery reduces the amount of WordPress infrastructure exposed to public visitors. Your public site can be served as files, while WordPress remains the authoring environment behind the publication workflow.
In a private-origin, public-static setup, visitors do not hit
wp-login.php, plugin PHP code, or database-backed page generation on the public site. This reduces the blast radius of many common WordPress risks, including plugin runtime vulnerabilities, automated login probing, and server-side behavior that only exists while WordPress is serving each request.You still need to maintain your WordPress origin, themes, plugins, accounts, and deployment credentials. The main security benefit is architectural: fewer dynamic systems are involved in serving anonymous public traffic.
-
Staatic はすべてのプラグインと互換性がありますか ?
-
Not entirely. Static sites do not run WordPress, PHP, or database queries for each visitor request. Plugins that depend on server-side processing on the public site may need changes or alternatives.
Common examples include native comments, some search implementations, forms that post back to WordPress, eCommerce flows, membership areas, and plugins that fetch personalized server-side data.
For forms and search, Staatic Premium provides ready-made integrations. For other dynamic features, use a static-compatible service, client-side integration, or a hybrid architecture where needed.
-
Staatic is designed to work on typical WordPress hosting, including many shared hosting environments. The server must be able to write to the configured work directory and make HTTP requests to the WordPress site being published.
Large sites, slow origins, strict firewalls, disabled loopback requests, or very limited PHP execution time can require tuning. The Site Health checks, publication logs, and advanced settings are the best starting points if a publication does not start or takes too long.
-
どこでサポートを受けられますか ?
-
ご質問や問題がある場合は、まずドキュメントと FAQ から始めてください。
そこで答えが見つからない場合は、お気軽にサポートフォーラムでトピックを開いてください。
商用サポート、Staatic Premium、またはStaatic Cloudに関するご質問は、お問い合わせからご連絡ください。
評価
貢献者と開発者
変更履歴
1.13.2
Release date: September 27th, 2026.
Features
- Introduces the
staatic_origin_rule_pathsfilter to supply origin rule paths from code. - Defers WordPress background updates while a publication of the main site runs, so an update does not put the site in maintenance mode mid-crawl.
- Introduces the
staatic_defer_automatic_updatesfilter to turn off deferring background updates. - Introduces the
staatic_automatic_updates_deferredaction, fired with the publication ID and site ID each time an update run is deferred. - Introduces the
staatic_http_retry_optionsfilter to adjust how failed HTTP requests are retried.
Improvements
- Excludes paths that Staatic Cloud origin rules forward to your origin from publications.
- Caps the pause between crawler retries at 30 seconds and gives up retrying a URL after about two minutes, so a site that is briefly in maintenance mode no longer holds up a publication for 10 minutes per attempt.
1.13.1
Release date: September 23rd, 2026.
Features
- Adds a Publication Retention Count setting under Advanced settings.
- Introduces the
staatic_publication_tickaction during crawling. - Adds Site Health advice for persistent object caches on large sites and crawl queue indexes stored in ascending order.
Improvements
- Speeds up crawling on large sites with batched crawl queue dequeues and discovered URL writes.
- Keeps the crawl pool fed with time-budgeted batches, so publications started from the WordPress admin run as fast as WP-CLI.
- Corrects the primary key order of the results deployment table on existing installs and indexes publication logs by date.
Bug Fixes
- Prevents wp-admin fatal errors when packaged plugin files are missing.
1.13.0
Release date: September 8th, 2026.
Features
- Adds a Publication Time Limit setting under Advanced settings, so publications on large sites can be given more than the default four hours before they are canceled.
Improvements
- Speeds up result lookups by build and URL with a new database index, benefiting redirect and configuration post-processing as well as registering uploads on sites with many media files.
- Replaces the publication test task with a bounded backend-worker survival diagnostic that reports disabled, running, complete, incomplete, and stale states, without claiming to test proxy responses or CPU capacity.
Bug Fixes
- Prevents an HTTP Concurrency of zero from being saved, which stalled the crawl batch size.
- Prevents duplicate publication diagnostics, delays the first recurring run after the initial dispatch, and removes the Site Health status test when diagnostics are intentionally disabled.
- Prevents large publications from failing when the deployment is initiated from the WordPress admin, by building the deployment manifest in bounded steps that resume across background runs.
- Gives additional redirects precedence over generated results for the same address on every deployment method, instead of silently dropping the redirect or uploading the generated page alongside it; the publication log now names each result a redirect replaced.
- Prevents a publication from removing the only remaining version of a page when two addresses that differ by a trailing slash redirect to each other.
- Removes redirect results that point at their own address instead of publishing them as pages.
Earlier releases
For the changelog of earlier releases, please refer to the changelog on staatic.com.