# Static business-site deployment checklist

Researched 2026-10-14. Record actual evidence; these unchecked items are not test results.

- [ ] Approve facts, photo rights and a real contact route; remove fictional content.
- [ ] Review phone/desktop, keyboard, enlarged text, images, links and 404.
- [ ] Confirm dist is static and contains no secrets or internal material.
- [ ] Record the intended Cloudflare account and isolated project privately.
- [ ] Confirm Free plan/limits; no model API, Functions, database or paid widget.
- [ ] Choose Direct Upload deliberately; later Git integration needs another project.
- [ ] Operator authorizes Wrangler login OR protected token with Account / Cloudflare Pages / Edit for the intended account, short expiry. This can affect other Pages projects in the account.
- [ ] Never paste token values into chat or commit them; never use Global API Key.
- [ ] Create project: npx wrangler pages project create (production branch main).
- [ ] Preview: npx wrangler pages deploy dist --project-name=YOUR_PROJECT --branch=review
- [ ] Inspect the returned public-safe preview; record URL, checks and human approval.
- [ ] Publish same reviewed dist: npx wrangler pages deploy dist --project-name=YOUR_PROJECT --branch=main
- [ ] Read back live URL and deployment identifier; check contact destination again.
- [ ] Retain reviewed source/assets and previous deployment reference for recovery.
- [ ] Revoke temporary token; assign maintenance owner and next fact-review date.
- [ ] If adding a domain, separately approve actual first-year/renewal costs and DNS changes without disturbing mail.

Preview URL: __________________
Review date/owner: __________________
Production URL/deployment identifier: __________________
Actual checks/blockers: __________________
