Every Cloudflare (CDN/proxy used with any platform) fix we catalog

SEOLZ catalogs 1 fixes for Cloudflare (CDN/proxy used with any platform) across 1 areas — SEO, answer-engine readiness, accessibility, security and site-health. Each lists the exact steps for Cloudflare (CDN/proxy used with any platform), with a link to the official docs.

Scan my Cloudflare (CDN/proxy used with any platform) store free

Security (OWASP) · 1 fixes

Hsts max age too shortQuick win

Increase your HSTS max-age directive to at least 31536000 seconds (1 year) so browsers enforce HTTPS connections for a meaningful period.

On Cloudflare (CDN/proxy used with any platform)

  1. Log in to Cloudflare → select your domain.
  2. Go to SSL/TLS → Edge Certificates.
  3. Scroll to 'HTTP Strict Transport Security (HSTS)' and click 'Enable HSTS'.
  4. In the dialog, set Max Age Header to '12 months (31536000)', toggle 'Include Subdomains' on (if all subdomains use HTTPS), then click Save.
  5. Note: Do NOT enable 'Preload' until you have verified your entire domain and all subdomains are permanently on HTTPS — preload list inclusion is very difficult to reverse.
  6. Verify with securityheaders.com.
Code · Generic HTML (http)
Strict-Transport-Security: max-age=31536000; includeSubDomains

This is an HTTP response header — it must be sent by your server, NOT as an HTML meta tag. The meta tag is not supported for HSTS.

Full guide →