Changing a public website is often treated as a visual task. In an organization, it is also an operations task: a domain may carry web traffic, email delivery, verification records, subdomains, and services owned by different teams.
The safest release is not the one with the fewest changes. It is the one whose changes are explicit, tested, and easy to undo.
Map the boundary before touching it
Begin by separating the service you intend to change from the services that merely share the same domain. Record the web route or host, the intended origin, the expected redirects, and the records that must not change. Email routing and domain-verification records deserve their own checklist rather than becoming incidental details in a web deployment.
Prefer exact routing rules over broad catch-alls. An exact route makes it clear which traffic the release owns; a wildcard can silently take over unrelated services.
Treat rollback as a release artifact
Before the change, capture the previous state in a small, readable rollback note. It should include the route or record being changed, its former value, where the change was made, and the checks that show the old path has returned.
This is not a substitute for a complete infrastructure backup. It is a focused operational record for the change at hand. Its purpose is to let a teammate reverse a release safely under time pressure.
Verify the path people actually use
A successful build or deployment message is only one signal. Verify the real public behaviour:
- the primary HTTPS page returns the intended response;
- HTTP and alternate-host redirects preserve the path and query when expected;
- a representative static asset loads;
- the contact or form path handles invalid and valid input correctly; and
- adjacent services that were deliberately out of scope remain unchanged.
When a nearby service is already unhealthy, record it as a separate observation unless there is evidence that the release caused it. This avoids “fixing” an unrelated system during an urgent web change.
Reversible delivery is a small discipline with a large payoff: it gives the team confidence to ship, because the route back is as clear as the route forward.