# Static site: one-release acceptance checklist

Life Linked Lab | practical worksheet | 2026-11-07
Not a deployment script. Fill private copies with actual results.

## Build and scope

- [ ] Give the candidate a unique release ID.
- [ ] List public files and hashes, added/changed/removed paths and expected counts.
- [ ] Exclude private source settings, credentials, logs and customer data.
- [ ] Check HTML metadata, same-page/cross-page fragments, assets, downloads,
      sitemap and RSS; keep tests relevant to the changed behavior.
- [ ] Check desktop, narrow viewport and keyboard behavior; retain limitations.

## Prepare a recoverable change

- [ ] Identify the current live release and compare all expected old file hashes.
- [ ] Verify archive contents and paths, including symlinks and duplicate names.
- [ ] Keep the preceding static release and a guarded recovery procedure.
- [ ] Check unrelated service health without changing those services.

## Verify actual responses

- [ ] Origin HTTPS returns the intended release ID with normal certificate checks.
- [ ] Public HTTPS returns the intended release ID and changed-file bytes.
- [ ] Content hashes match the expected candidate, not just HTTP 200.
- [ ] A real missing path returns the intended missing-page response, not a
      generic home page that masks a broken URL.
- [ ] Public article, stylesheet/script and downloads have suitable content types.
- [ ] Check relevant root/host redirects and cache behavior separately.
- [ ] Open the public result in a real browser, including the changed interaction.
- [ ] Recheck unrelated service health and monitored configuration boundaries.

## Close the record

- [ ] Record time, candidate ID, previous ID, paths, observed bytes and errors.
- [ ] If acceptance failed, verify guarded recovery; never overwrite later work.
- [ ] Keep technical acceptance separate from traffic, indexing, ads and sales.

Release / previous release:
Changed paths / expected hashes:
Origin result / public result / browser evidence:
Recovery state / unresolved checks / next action:

Guide: https://lab.life-linked.com/articles/static-site-release-checks/
Historical example: https://lab.life-linked.com/downloads/static-release-acceptance-2026-11-07.json

One success is not continuous monitoring, all-CDN consistency or a business result.