Why this matters
Even static sites can ship broken links, bad metadata, or incorrect content. Rollback planning reduces recovery time.
Setup
Keep deployments tied to Git commits. Know how to revert a commit, rerun the workflow, and verify the restored production pages.
Implementation notes
For content-only mistakes, a corrective commit is often cleaner than a full rollback. For template mistakes affecting many pages, rollback quickly first.
Final checklist
- Deployments map to commits
- Revert workflow is understood
- Production URLs are rechecked