Before you start
You need website editing permission, the matching accepted staging save, the intended production environment and the existing production WordPress page number. This workflow applies only when its native integration and required review evidence are available.
What to do
- In the matching release, choose Check review evidence. Inspect the observations for block validity, editing, visual fidelity, responsive behaviour, functionality, accessibility, updates and recovery. Missing or mismatched evidence must be resolved for the exact staged design.
- Choose Prepare review when all required categories are available. Read the observations and current review result before recording acceptance with the offered review action.
- After the review is accepted, choose Prepare publication. Check the production domain and page number, then choose deliberately whether to preserve the page status or set it to Published, Private or Draft.
- Continue the existing publication request and read its proposed change before committing it. Use Open WordPress when offered for the exact prepared production page. Check the saved result and record acceptance only when it confirms the change was applied.
- To continue earlier work, use request history with the correct environment and page number. After an uncertain save, reconcile the existing request before retrying; retry requires a confirmed unapplied result.
- If an accepted publication needs restoration, use Prepare rollback from that publication. Review the restoration proposal and its exact page predecessor, then use the separate restore action and verify the saved result and public page.
What happens next
An accepted publication or restoration records the verified outcome for the selected page. The actual WordPress visibility still determines whether ordinary visitors can read it.
If something goes wrong
An accepted staging save is insufficient without matching review evidence. A prepared proposal or opened editor is not proof of a saved production change. Stop on a divergent result, wrong page, changed predecessor or unavailable permission and contact the project administrator. Do not replace an entire database or assume a rollback may overwrite later editorial work.
