Publish, Launch QA, and Rollback

Step 1: Confirm the Intended Change
Before publishing, confirm the page or template title, status, mode, assignment, global-change state, and save revision. Read the change summary and resolve any conflict from another editor instead of overwriting it. A global style save and a page content save have different reach and should be reviewed separately.

Step 2: Keep a Recovery Point
Verify the recent page history and the wider site recovery artifact before a major launch. Record the current public layout hash or other known-good identity. The recovery target must be complete and readable, and the person running the launch should know the exact command or control used to restore it.

Step 3: Run Prelaunch Checks
Review one page heading, title, description, canonical, robots, social image, schema, sitemap status, links, forms, analytics intent, consent, accessibility, cold and warm performance, security headers, and mobile containment. Test important anonymous, signed-in, customer, and editor states without using a production payment or private record unnecessarily.

Step 4: Verify Public and Monitor
Publish once, purge only the affected cache, and open the public page in a clean session at desktop, tablet, and mobile. Confirm content, styles, media, menus, forms, and calls to action. Inspect fresh browser and PHP logs, then keep the rollback package until the update remains healthy after a warmed request and a second independent check.
