Keep the artefact identifiable
A release label should identify the bytes being served. Record the artefact digest alongside the build inputs and store it with the release. A rebuild from the same branch can pick up a different toolchain or dependency.
For a static platform the rehearsal can be simple. Extract the package into an empty directory, start a file server and open a nested page directly. This catches a surprisingly important class of routing mistakes.
Trace what persists
List the files and data that live longer than a release. Uploads, certificate challenges and configuration often sit close to the material being replaced. Give each an owner and an explicit preservation rule.
Exercise the procedure against a temporary document root with representative persistent files. Verify both the new content and the continued presence of those files before considering the rehearsal complete.
Test the way back
Choose a failure that matters to a visitor, such as an unavailable stylesheet. Restore the previous artefact, then request both the page and its resources. A successful copy command alone is a poor recovery signal.
Record the observations needed to decide whether to continue or roll back. Keep the runbook short enough to follow under pressure and specific enough that a second person can reproduce the result.