LEYUN · SITE LAUNCH CHECKLIST独立站上线自查清单库

Cache and Response Header Baseline Configuration

Sections: Pages & Content · Reviewed: 2026-11-21 · 12 items

Key takeawayCaching decides how fast returning visitors load the site, and response headers decide how browsers treat the content. Both are low-level settings whose failures show up as broken styling, updates that never appear and security scan deductions.

Industries and use cases

  • After connecting a new server or CDN
  • When users still see the old page after a release
  • When a security scan flags missing headers
  • When static assets are re-downloaded and traffic looks abnormal

Checklist

Checklist: cache and response header configuration
Check itemPass criteriaRisk levelFix hint
Static asset cachingCSS, JS, fonts and images use long Cache-Control lifetimes of at least 30 daysHighFingerprinted filenames allow one year; without hashes, shorten to 7 days.
HTML cachingHTML responses use no-cache or a short lifetime so updates propagateHighLong HTML caching leaves visitors on an old version after release.
ETag and Last-ModifiedAt least one validator is configured and 304 responses carry an empty bodyMediumLet the server generate them instead of hard-coding timestamps.
CompressionText assets use gzip or brotli with at least 60% size reductionHighEnable it at server or CDN level and confirm the encoding header on CSS and JS.
HSTSStrict-Transport-Security is enabled with a max-age of at least six monthsMediumConfirm the whole site and its subdomains support HTTPS before extending the lifetime.
Content typeCorrect Content-Type is returned: text/html for HTML and application/xml for XMLMediumWrong types make browsers render as plain text or trigger a download.
Security headersX-Content-Type-Options, Referrer-Policy and X-Frame-Options are setLowInject them at one entry point rather than maintaining them page by page.
CSP policyContent Security Policy does not block first-party scripts or analyticsMediumRun in report-only mode for a week before switching to enforcement.
Server signatureResponses expose no exact version numbers or internal pathsLowDisable detailed version information to reduce targeted probing.
CDN hit rateStatic asset hit rate above 80% with stable origin trafficMediumReview cache keys so meaningless parameters do not fragment the cache.
Redirect caching301 responses may be cached while 302 responses are not given long lifetimesMediumPermanent redirects reduce requests, while temporary ones must stay reversible.
Post-release purgeThe release process includes purging HTML and CDN cachesHighWrite the purge step into the checklist instead of relying on memory.

Common misjudgements

  • Setting long cache lifetimes on everything: without hashed filenames, visitors never receive the new version.
  • Treating a 304 response as proof of correct caching, when it only shows validation works, not that the lifetime is sensible.
  • Enabling compression without verifying it, since some servers compress only certain types and the header reveals the truth.

How to use this checklist

  • Pair with the image and mobile sheets, as caching is the last step of performance work.
  • Check immediately after changing server or CDN and review headers quarterly.
  • Link with the release review sheet so cache purging is fixed inside the release process.

FAQ

What cache lifetime is appropriate?
A year for hashed static assets, and no caching or a few minutes for HTML.
Is server caching still needed with a CDN?
Yes. Two layers together balance hit rate and update speed.
Can caching cause indexing problems?
Rarely, but long HTML caching can serve stale content to crawlers, so set it carefully.
Version notes2026-11-21: first release, compiled from official Google documentation and public sources; updated as engine rules and regulations change.

If you prefer not to verify each item yourself, a pre-checked B2B template site package is available as an alternative.

Note: this checklist is a self-check reference only. Search-engine behaviour and regulations follow the latest official documentation of each provider and jurisdiction.