Title: Static Porter Author: Kayıhan Turgutoğlu Published: 18 janvier 2026 Last modified: 10 octobre 2026 --- Recherche d’extensions ![](https://ps.w.org/static-porter/assets/banner-772x250.jpg?rev=3653630) ![](https://ps.w.org/static-porter/assets/icon-256x256.png?rev=3442842) # Static Porter Par [Kayıhan Turgutoğlu](https://profiles.wordpress.org/kturgutoglu/) [Télécharger](https://downloads.wordpress.org/plugin/static-porter.4.2.0.zip) * [Détails](https://fr-ca.wordpress.org/plugins/static-porter/#description) * [Avis](https://fr-ca.wordpress.org/plugins/static-porter/#reviews) * [Installation](https://fr-ca.wordpress.org/plugins/static-porter/#installation) * [Développement](https://fr-ca.wordpress.org/plugins/static-porter/#developers) [Support](https://wordpress.org/support/plugin/static-porter/) ## Description **Static Porter** turns your WordPress site into pre-built HTML files, so visitors get instant page loads without your server ever touching PHP or a database. Most caching plugins just speed up WordPress. Static Porter goes further: it generates a real, physical copy of your site that can be served on its own — from your own server via Apache, from Cloudflare’s global edge network, from an AWS S3 bucket behind CloudFront, or as a downloadable ZIP you can host anywhere. Your live WordPress site stays completely private and secure behind the scenes; only the static HTML is ever exposed to visitors. Built with shared and budget hosting in mind: a live « Peak Memory » monitor, a one-click « Stop Crawl » safety switch, and sensible defaults mean you’re never one crawl away from taking your server down. ### Automated Maintenance (Smart Refresh) Never worry about stale content. When you publish or update a post, Static Porter quietly regenerates that post, your homepage, and its category and tag archives in the background, without slowing down the editor. Unpublish, trash, or rename a post and its old static file is removed automatically, so visitors never get served a page that no longer exists. ### Why choose Static Porter? * **Deploy anywhere:** Not locked into one platform. Serve statically from your own Apache server, push to Cloudflare Workers, upload to AWS S3 with automatic CloudFront cache invalidation, or export a portable ZIP — pick whichever fits your infrastructure. * **Built for real-world WordPress:** Works with page builders, shortcodes, and JavaScript-driven widgets. A built-in Documentation tab explains exactly what works out of the box and what needs a small adjustment first (forms, WooCommerce checkout, etc.). * **Tells you what won’t work before you crawl:** A built-in Compatibility check tests your real site for blocked crawling, plain permalinks, form and shop plugins, and pages that contain forms or checkout content, and can add the right exclusions for you. * **Safe by default:** Every feature that could meaningfully change your site’s output — Cloudflare deployment, S3 deployment, asset mirroring — is hidden until you explicitly turn it on. Nothing surprises you. ### Key Features **Static generation & speed** * **One-Click Full Crawl:** Generate a static version of your entire site in one click. * **Server-Safe Crawling:** A real-time « Peak Memory » monitor and an emergency « Stop Crawl » button, designed for budget shared hosting where resources are limited. * **Smart Refresh:** Publishing or updating a post regenerates that page, your homepage, and its archives in the background. Unpublished, trashed, and renamed posts have their old files removed. * **Crawl Health Report:** After every crawl, see exactly how many pages were cached and which failed, with the reason for each (timeout, HTTP 500, HTTP 403) and one-click Retry. Error pages are never saved as static files. * **Orphan File Cleanup:** Finds static files whose source page was deleted, unpublished, renamed, or excluded, explains why, and removes them manually or automatically after each crawl. * **Advanced Optimization:** Built-in HTML minification and Gzip compression. * **Security & Caching:** Automatically configures .htaccess with security headers and browser caching rules. * **NGINX Support:** Detects NGINX and generates the exact server rule your site needs, with a copy button. The Dashboard status is honest about whether pages are actually being served. **Deploy anywhere** * **Cloudflare Deployment:** Push your static files straight to a Cloudflare Worker, serving your site from Cloudflare’s global edge network. Hidden until you enable it. * **AWS S3 + CloudFront Deployment:** Upload directly to an S3 bucket, with automatic CloudFront cache invalidation on every deploy. Hidden until you enable it. * **Asset Mirroring:** Optionally copy your CSS, JavaScript, images, and fonts locally too, so a deployed or exported site works completely standalone— no dependency on your WordPress server staying online. * **Download as ZIP:** Export your entire static site as a single ZIP file — perfect for local browsing, migrating hosts, or keeping an offline snapshot. **Visibility & control** * **Persistent Cache Table:** See every cached page with five independent actions per row: View, Recrawl, Copy URL, Exclude, and Delete — each with clear confirmation and feedback. * **File Storage Location:** See exactly where your static HTML files live on disk, with a one-click « Copy path » button and a writable/not-writable status check. * **Compatibility Check:** A dedicated tab that scans your site before the first crawl and flags anything that behaves differently as static pages, with a one-click button to add suggested exclusions.*** Built-in Documentation:** A dedicated Documentation tab covers every feature — how it works, file locations, compatibility, deployment options, and FAQs — without ever leaving wp-admin. ## Captures d’écran [⌊One-click static generation with real-time progress bar.⌉⌊One-click static generation with real-time progress bar.⌉[ One-click static generation with real-time progress bar. [⌊Precise control: Delete or recrawl specific pages without clearing the whole cache.⌉⌊ Precise control: Delete or recrawl specific pages without clearing the whole cache .⌉[ Precise control: Delete or recrawl specific pages without clearing the whole cache. [⌊Visualize your efficiency: See exactly how much database load you are bypassing.⌉⌊ Visualize your efficiency: See exactly how much database load you are bypassing.⌉[ Visualize your efficiency: See exactly how much database load you are bypassing. [[ [[ ## Installation 1. Upload the `static-porter` folder to the `/wp-content/plugins/` directory. 2. Activate the plugin through the ‘Plugins’ menu in WordPress. 3. Go to the ‘Static Porter’ menu in your sidebar. 4. Open the ‘Compatibility check’ tab to see whether anything on your site needs attention. 5. Configure your excluded paths and click ‘Start full crawl’. 6. On NGINX, add the server rule shown on the Dashboard (Apache and LiteSpeed work automatically). ## FAQ ### Will Static Porter really make my site faster? Yes! Traditional WordPress pages require the server to process PHP and query a MySQL database every time a visitor arrives. Static Porter converts these into flat HTML files. Your server can then deliver these files instantly, bypassing the «  heavy lifting » entirely. This often results in a nearly instant Time to First Byte( TTFB). ### Will my URL structure or permalinks change? No. This is one of the core strengths of Static Porter. The plugin generates a static mirror of your site that follows your existing WordPress permalink structure perfectly. Your visitors (and search engine bots) will continue to see the same clean URLs they always have, but the pages will simply load much faster. ### Do I have to manually recrawl my site every time I write a post? No. Smart Refresh automatically regenerates the post, your homepage, and its category and tag archives when you publish or update it, and removes the old file if you unpublish, trash, or rename it. A full crawl is only needed after changes it can’t see, such as menus, widgets, your theme, or permalinks. The Dashboard shows a banner when that happens. ### Can I use this on a low-resource budget server? Absolutely. Static Porter is designed to be resource-efficient and includes a built- in « Peak Memory » monitor in the dashboard so you can track its impact. If the crawl is too heavy for your server, you can use the « Stop Crawl » safety button at any time to immediately halt the process. ### Does this plugin improve my site’s security? Yes. In addition to serving static files (which are inherently more secure than dynamic PHP), Static Porter automatically injects security headers into your .htaccess file. This includes protection against clickjacking (X-Frame-Options) and MIME-type sniffing (X-Content-Type-Options). ### Will this help my Google search rankings (SEO)? Speed is a major ranking factor for Google, especially with Core Web Vitals. By serving ultra-fast static HTML and enabling Gzip compression and browser caching automatically, your site will likely see improved performance scores, which can lead to better visibility in search results. ### What happens if I want to remove a single page from the cache? Unlike simple « purge all » plugins, Static Porter gives you a persistent cache table. You can view a list of every cached URL and use individual « Delete » or« Recrawl » buttons for precise control without affecting the rest of your static site. ### Can I choose which parts of my site to make static? Yes. The dashboard allows you to toggle the crawling of Posts, Pages, Categories, and Tags independently. You can also use the « Excluded Paths » box to prevent specific directories from ever being turned into static files. ### How do I know if it’s working? Enable the « HTML Attribution » setting. View your website’s source code, and you will see a comment at the top confirming the page is being served as static HTML. ### Does this work with WooCommerce? It is recommended to exclude checkout, cart, and account pages using the « Excluded Paths » setting to ensure dynamic functionality remains intact. ### Can I deploy my static site to Cloudflare or AWS? Yes. Both are optional, hidden-by-default features. Cloudflare deployment pushes your static files to a Cloudflare Worker, serving your site from Cloudflare’s global edge network. AWS S3 + CloudFront deployment uploads directly to your own S3 bucket, with automatic CloudFront cache invalidation on every deploy. Enable whichever fits your infrastructure from the dashboard settings. ### Do I need my WordPress site to stay online after deploying to Cloudflare or S3? By default, yes — only your HTML is deployed, so CSS, JavaScript, images, and fonts still load from your live WordPress site. Turn on Asset Mirroring if you want a fully standalone deployment that doesn’t depend on WordPress staying online. ### What is Asset Mirroring? An optional setting that copies your CSS, JavaScript, images, and fonts locally alongside your static HTML, instead of leaving them to load from your live WordPress site. It’s useful before deploying to Cloudflare, S3, or exporting a ZIP, since it makes the result fully self-contained. It’s off by default because it increases crawl time and disk usage. ### Do I need a new sitemap.xml after using Static Porter? No. Static Porter only crawls your posts, pages, categories, tags, and 404 page — it never generates or touches sitemap.xml itself. Since no static copy of your sitemap exists, the .htaccess rule finds nothing to serve for that path and simply passes the request through to WordPress as normal. Your existing sitemap (from Yoast, RankMath, or whichever SEO plugin you use) keeps generating itself dynamically and staying current, completely independent of Static Porter. ### Does Asset Mirroring affect my sitemap or its image links? No. Asset Mirroring only rewrites the src/href references inside your crawled static HTML pages, pointing them at locally mirrored copies of your CSS, JS, and images. It does not modify your sitemap file, and the live image URLs your sitemap already lists continue to work exactly as before on your WordPress server, whether or not mirroring is enabled. ### Will using Static Porter affect my SEO rankings? Static Porter’s main SEO benefit is indirect but real: faster page loads improve your Core Web Vitals, which is a direct Google ranking factor, and you get that automatically just from running a crawl — no extra configuration needed. Your URLs, permalinks, and sitemap are unaffected either way. Two things worth checking after your first crawl: 1. Browse your site logged out (or in an incognito window), since that’s exactly what Googlebot sees. Confirm nothing looks broken or missing compared to the logged- in, dynamic version. 2. Make sure anything duplicate, private, or irrelevant (like WooCommerce cart or checkout pages) is listed in « Excluded Paths, » so it’s never accidentally served as a static page to search engine crawlers. ### Does Static Porter work on NGINX? Yes, with one extra step. NGINX ignores .htaccess, so Static Porter detects it and shows an equivalent server rule on the Dashboard, generated for your site’s real paths, with a copy button. Add it to your NGINX configuration (or send it to your host’s support on managed hosting) and static files are served exactly as they are on Apache. Until then your files are still generated, and the status badge says « Generated » rather than claiming the site is being served statically. ### What happens if a page fails during a crawl? Nothing is silently lost. The crawl report lists every failed page with the reason( a timeout, HTTP 500, HTTP 403, and so on) and a Retry button for each, plus Retry all failed. A page that returns an error is never saved as a static file, and if a refresh fails, the previous good copy is kept. ### What are orphaned files? Static files that your site wouldn’t produce any more: a page you deleted, unpublished, or renamed, or a path you excluded after it was cached. Static files are served before WordPress runs, so an orphan keeps showing visitors stale content. The Orphan File Cleanup card lists them with the reason, and can remove them automatically after each crawl. Pages that still exist are never deleted this way. ### How do I know if my site is compatible? Open the Compatibility check tab. It tests that your site can crawl itself, checks your permalinks and server type, detects form, shop, and membership plugins, and scans your actual pages for forms and checkout content (including Divi and Elementor forms). It changes nothing unless you click the button to add its suggested exclusions. ## Avis ![](https://secure.gravatar.com/avatar/6dd4aa6b8330a3187d1ba2ceb85d104903ea2b1cdf7a15b492b94e7a971d614e? s=60&d=retro&r=g) ### 󠀁[Fully automates static HTML site generation](https://wordpress.org/support/topic/fully-automates-a-site/)󠁿 [ricardosimoes](https://profiles.wordpress.org/ricardosimoes/) 13 avril 2026 Just had to do a 1st full cache generation, and from then on the cache is auto-generated on each "publish" button click! Static site generation is fully automated! [ Lire l’avis ](https://wordpress.org/support/plugin/static-porter/reviews/) ## Contributeurs & développeurs « Static Porter » est un logiciel libre. Les personnes suivantes ont contribué à cette extension. Contributeurs * [ Kayıhan Turgutoğlu ](https://profiles.wordpress.org/kturgutoglu/) [Traduisez « Static Porter » dans votre langue.](https://translate.wordpress.org/projects/wp-plugins/static-porter) ### Le développement vous intéresse ? [Parcourir le code](https://plugins.trac.wordpress.org/browser/static-porter/), consulter le [SVN dépôt](https://plugins.svn.wordpress.org/static-porter/), ou s’inscrire au [journal de développement](https://plugins.trac.wordpress.org/log/static-porter/) par [RSS](https://plugins.trac.wordpress.org/log/static-porter/?limit=100&mode=stop_on_copy&format=rss). ## Historique des changements #### 4.2.0 * **New:** Crawl health report. When a crawl finishes you see pages cached, pages failed, and duration, with every failure listed alongside its reason (timeout, HTTP 500, HTTP 403) and a Retry button, plus Retry all failed. The report is saved, so it is still there after a reload. * **New:** Orphan file cleanup. Detects static files whose source was deleted, trashed, unpublished, scheduled, made private, renamed (shown with the new URL), excluded, or switched off under Content to crawl. Delete or Ignore each one, Delete all, or tick « Auto-delete orphans after each crawl ». Deletion is re- verified on the server and empty folders are removed. * **New:** NGINX support. NGINX is detected, and a ready-to-copy server rule equivalent to the .htaccess rule is generated for your site’s real paths, including subdirectory installs. The status badge now reads « Generated » instead of « Active » on NGINX, because nothing is served statically until the rule is added. * **New:** Compatibility check tab. Tests that crawling works (and explains HTTP 401 and 403 blocks), flags plain permalinks, checks the server type, cache folder, and .htaccess rules, detects form, shop, membership, and competing page-cache plugins, and scans your pages for forms, cart, checkout, and login content, including Divi and Elementor forms. One click adds the suggested exclusions. The homepage is never suggested for exclusion. * **Improved:** Smart Refresh now also regenerates the posts page and the post’s category and tag archives, removes the old file when a post is unpublished, trashed, deleted, or its URL changes, refreshes a post when a comment is approved, handles scheduled posts going live, and runs after the editor has saved so you never wait on it. It respects Content to crawl and Excluded paths. A « full crawl recommended» banner appears when menus, widgets, the theme, permalinks, or active plugins change, since Smart Refresh can’t see those. * **Fix:** Pages that return an HTTP error (404, 500, and so on) are no longer saved as static files. Previously an error page could be cached and served to visitors. If a refresh fails, the existing good copy is now kept. * **Fix:** Deploying to Cloudflare or S3 with Asset Mirroring on now actually uploads the mirrored CSS, JavaScript, images, and fonts, not just the HTML, and sends each file with the correct content type instead of labeling everything as HTML. * **Fix:** Asset Mirroring now also covers responsive images (srcset), no longer skips re-downloading assets after the cache is purged, and no longer logs a PHP warning on every asset. * **Security:** Every crawl, delete, and stats request now checks administrator capability as well as the nonce, and file paths from the browser are validated to stay inside the cache folder. * **Requirement:** Smart Refresh relies on a hook introduced in WordPress 5.6, so the minimum WordPress version is now 5.6. #### 4.1.0 * **Redesign:** Cloudflare deployment is no longer shown as an always-visible settings card. It now appears as a compact « Enable » card by default, and only expands into the full account ID / API token / worker name settings — and only shows the « Deploy to Cloudflare » button in the actions row — once you explicitly enable it. Existing Cloudflare credentials are preserved if you disable and later re-enable it. * **New:** Added a Cloudflare-branded icon to the deployment card in place of the generic cloud icon. * **New:** Added a « Documentation » tab directly on the plugin’s own dashboard page (next to « Dashboard »), covering how the plugin works step by step, exact file storage locations, a compatibility guide (shortcodes, forms, sliders, WooCommerce, NGINX), and frequently asked questions — no need to leave wp-admin to understand what the plugin does. * **Redesign:** The Cached pages table’s single Delete/Recrawl toggle button has been replaced with five independent row actions: View (opens the generated static file directly), Recrawl (regenerates that page without deleting it first), Copy URL, Exclude (adds the page’s path to Excluded Paths and removes its static file in one step), and Delete. Delete now shows an inline « Delete this static file?» confirmation in place of the row instead of deleting immediately, Recrawl shows a spinning icon and briefly disables the row while it runs, and Copy/Exclude flash a green checkmark to confirm the action completed. * **Expanded:** The Documentation tab now covers every feature in the plugin across nine sections — How it works, Crawling and content, Performance and output, File locations, Cached pages actions, Cloudflare deployment, Download ZIP, Compatibility, and FAQ — instead of the original four thin sections. * **New:** Added a red « New » badge on the Documentation tab, and a dismissible callout banner on the Dashboard pointing new users to it. Both automatically stop showing once you’ve visited the Documentation tab at least once, or if you dismiss the banner directly. * **New:** Added optional AWS S3 + CloudFront deployment. Enable it from a collapsed settings card (matching the Cloudflare card’s pattern, but visually distinct with an AWS-branded bucket icon and navy color treatment) to reveal fields for your AWS Access Key ID, Secret Access Key, S3 bucket name, region, and an optional CloudFront distribution ID. Deploying uploads your static files to S3 using hand- implemented AWS Signature Version 4 request signing (no AWS SDK dependency), and automatically invalidates your CloudFront cache afterward if a distribution ID is set. * **New:** Added optional Asset Mirroring. When enabled, Static Porter downloads a local copy of every CSS, JavaScript, image, and font file a page references— including assets referenced inside CSS via url() and @import — and rewrites the page to point at those local copies. This makes ZIP exports and Cloudflare/S3 deployments fully standalone, no longer dependent on your WordPress site staying online to serve styling and images. A separate sub-option extends mirroring to external, third-party assets like Google Fonts. A warning banner appears near the deploy and download buttons whenever this is off and a deployment feature is active, so you know before you deploy rather than after. * **Fix:** The « Download ZIP » button is now disabled and labeled « Crawl first to download as ZIP » until at least one page has been crawled, instead of being clickable and failing with an error afterward. * **Docs:** Expanded the Documentation tab with two new sections, Asset Mirroring and S3 + CloudFront, and corrected the Cloudflare and Download ZIP sections to reflect that assets can now be included when Asset Mirroring is turned on. * **Docs:** Added a new SEO section to the FAQ answering whether a new sitemap. xml is needed (no — Static Porter never touches it), whether Asset Mirroring affects sitemap image links (no), and what to check for SEO after using the plugin. #### 4.0.0 * **New:** Added a « File storage location » settings card showing the full server path and browser-accessible URL of the static file cache, a writable/not-writable status indicator, a one-click « Copy path » button, and a direct « Open in browser» link. * **New:** Added a « Download ZIP » button that packages your entire static HTML output into a single ZIP file and triggers an automatic browser download. Useful for local site browsing, migrating to a different host, or sharing a snapshot of the static output. Requires PHP’s ZipArchive extension (available on all major hosts). #### 3.5.9 * **New:** Added a « Deploy to Cloudflare » option that uploads your generated static HTML files to a Cloudflare Worker, so they can be served entirely from Cloudflare’s global edge network. Configure your account ID, API token, and worker name in the new « Cloudflare deployment » settings card. * **Layout:** Moved Start full crawl and Stop crawl next to Purge cache in the main action row, instead of the page header. * **Security:** The Cloudflare API token field no longer echoes the saved token back into the page source; leave it blank to keep the existing value. #### 3.5.8 * **Redesign:** Rebuilt the dashboard with a clearer status header, grouped settings cards (Content to crawl, Excluded paths, Performance & caching, HTML attribution), and icon-labeled toggles in place of the old stacked gray boxes. * **No more page reloads:** Replaced the post-crawl countdown/reload with a « Refresh stats » action that updates the coverage, requests-avoided, memory, and disk- size figures in place via AJAX, with no full page reload at all. * **Cached pages table:** Added a live search box to filter cached URLs, and fixed a bug where the « Start full crawl » button could stay stuck on « Crawling… » after a natural completion. #### 3.5.7 * **Bug Fix:** Fixed an infinite reload loop on the dashboard after a crawl completed. The post-crawl countdown timer was never stopped, so once it reached zero it kept counting into negative numbers and repeatedly tried to reload the page, leaving the browser stuck refreshing with no way to stop it short of closing the tab. The countdown now stops itself after triggering a single, clean reload. #### 3.5.6 * **UX Improvement:** Dashboard now clearly indicates active/inactive status with a « reassurance » message for new users. * **Workflow:** Removed automatic page reload after crawling to allow reading of statistics. * **Privacy:** HTML attribution comment is now opt-in by default. #### 3.5.5 * **HTML Attribution Fix:** Correctly outputs the verification message as an HTML comment on the first line of static pages. #### 3.5.4 * **New Icon:** Updated plugin branding to a professional « Porter/Package » box icon. * **UI Refresh:** Restored sidebar labels and updated dashboard header icons. * **Timer Update:** Reduced post-crawl auto-refresh from 10 seconds to 5 seconds for a faster workflow. #### 3.4.7 * Major fixes * Added Stop Crawl functionality. * Added individual row Delete and Recrawl buttons. * Added 10-second auto-refresh after crawl. ## Méta * Version **4.2.0** * Last updated **il y a 6 jours** * Active installations **100+** * WordPress version ** 5.6 ou plus ** * Tested up to **7.1.3** * PHP version ** 7.0 ou plus ** * Language * [English (US)](https://wordpress.org/plugins/static-porter/) * Tags * [amazon s3](https://fr-ca.wordpress.org/plugins/tags/amazon-s3/)[cdn](https://fr-ca.wordpress.org/plugins/tags/cdn/) [cloudflare](https://fr-ca.wordpress.org/plugins/tags/cloudflare/)[performance](https://fr-ca.wordpress.org/plugins/tags/performance/) [static site generator](https://fr-ca.wordpress.org/plugins/tags/static-site-generator/) * [Vue avancée](https://fr-ca.wordpress.org/plugins/static-porter/advanced/) ## Notes 5 out of 5 stars. * [ 1 5-star review ](https://wordpress.org/support/plugin/static-porter/reviews/?filter=5) * [ 0 4-star reviews ](https://wordpress.org/support/plugin/static-porter/reviews/?filter=4) * [ 0 3-star reviews ](https://wordpress.org/support/plugin/static-porter/reviews/?filter=3) * [ 0 2-star reviews ](https://wordpress.org/support/plugin/static-porter/reviews/?filter=2) * [ 0 1-star reviews ](https://wordpress.org/support/plugin/static-porter/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/static-porter/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/static-porter/reviews/) ## Contributeurs * [ Kayıhan Turgutoğlu ](https://profiles.wordpress.org/kturgutoglu/) ## Support Erreurs résolues ces deux derniers mois : 1 sur 2 [Voir le forum de support](https://wordpress.org/support/plugin/static-porter/)