How to fix hsts disabled on Webflow
Enable HTTP Strict-Transport-Security (HSTS) by setting a max-age of at least 31536000 seconds (one year) so browsers always use HTTPS when visiting your store.
Steps for Webflow
- Webflow automatically provisions SSL and sets HSTS headers for all sites published to Webflow Hosting — no manual action is needed for webflow.io or connected custom domains.
- Ensure your site is published to Webflow Hosting (not self-hosted export): Webflow Designer → Publish → Webflow subdomain or your custom domain.
- For custom domains, go to Webflow Dashboard → Project Settings → Publishing → Custom Domain, confirm SSL is active (green padlock shown).
- If you export and self-host Webflow code on your own server, add the HSTS header in your Nginx or Apache config as described in the WooCommerce server steps above.
Strict-Transport-Security: max-age=31536000; includeSubDomainsWhat is hsts disabled?
HTTP Strict-Transport-Security (HSTS) is a security header your web server sends to a visitor's browser. It tells the browser: "For the next X seconds, never connect to this site over plain HTTP — always use HTTPS, no exceptions." When HSTS is disabled or set to `max-age=0`, that instruction is removed and the browser is free to make unencrypted HTTP requests. HSTS is a one-line server response header, not a code change, but it has a significant impact on how securely shoppers connect to your store.
Without HSTS, even if your store has an SSL certificate, a customer could still land on an unencrypted HTTP version of your site — either by typing your address without "https://" or by following an old link. That window is enough for an attacker on the same network (e.g. a coffee-shop Wi-Fi) to intercept login credentials, session cookies, or payment-related data in a "man-in-the-middle" attack. Google treats HTTPS as a ranking signal and flags insecure sites in Chrome, so a missing or zeroed-out HSTS header can hurt both your search rankings and customer trust. Regulations such as PCI-DSS (required for stores handling card data) explicitly expect transport-layer protections like HSTS to be in place, and failure to comply can result in fines or loss of the ability to accept card payments.
See the complete Hsts disabled guide for every platform and the full background.
Not sure if your Webflow store has this?
Run a free SEOLZ audit — we’ll find hsts disabled and every other issue across your whole site.
Scan my site free