Zen Site Security
Zen Site Security migrates your WordPress site to HTTPS safely and keeps it there. One-click activation The plugin first verifies that a valid SSL certificate is actually installed for your domain — activation is blocked until one is found, so you can never lock yourself out by accident. Activation
Zen Site Security migrates your WordPress site to HTTPS safely and keeps it there.
One-click activation
The plugin first verifies that a valid SSL certificate is actually installed for your domain — activation is blocked until one is found, so you can never lock yourself out by accident. Activation then:
- switches your WordPress Address and Site Address to https,
- 301-redirects every HTTP request (pages, REST API) to HTTPS,
- fixes mixed content on your pages on the fly.
HTTP to HTTPS redirect, your way
- PHP 301 redirect (default) — works on every server and disappears automatically when the plugin is deactivated.
- .htaccess 301 redirect (advanced, Apache/LiteSpeed) — redirects at server level before WordPress loads, with the PHP redirect kept as a safety net. The rules are placed above the WordPress block, wrapped in clear markers, and removed on deactivation.
- On nginx the plugin shows you the exact server snippet to copy instead.
Mixed content fixer
Insecure http:// references to your own site (including www/non-www variants and JSON-escaped URLs), plus common src , href , action , og:image , url() and srcset patterns, are rewritten to https:// just before the page is sent to the browser. Feeds, sitemaps and JSON responses are left untouched. An optional fixer for the WordPress admin is available too.
Certificate monitoring
The dashboard shows the certificate issuer, expiry date, and whether it covers your domain (wildcards included). When SSL is active and the certificate is about to expire (or already has), administrators see a warning.
HTTP Strict Transport Security (HSTS) — opt-in
Once your site runs reliably on https, you can send the Strict-Transport-Security header. Max-age starts at one day for safe testing; the preload-eligible configuration (1 year + includeSubDomains) requires explicit opt-in, because it is hard to undo.
Security hardening — XSS, CSRF, and injection defense in depth (all opt-in)
- Security headers : X-Content-Type-Options: nosniff , X-Frame-Options (clickjacking), Referrer-Policy (keeps tokens out of cross-site referrers), a conservative Permissions-Policy , and CSP upgrade-insecure-requests . Every header stands down automatically if another plugin already sends it.