This runbook defines how WordPress, plugins, themes, and builders are updated in a controlled, repeatable manner over the life of the site.
Updates are treated as operational events. They are planned, sequenced, verified, and documented to prevent regressions, drift, or unintended side effects.
Checklist Objective
Apply updates safely while preserving site stability, configuration integrity, and recoverability.
Scope Boundary
This runbook covers:
- WordPress core updates
- Plugin and theme updates
- Bricks Builder updates
- Change documentation and validation
This runbook does not cover:
- Server provisioning or operating system updates
- Infrastructure tuning or hosting internals
- Feature experimentation or plugin evaluation
Preconditions
- Site is in a stable, known‑good state
- Operations 02 — Backups & Recovery readiness is confirmed
- No active troubleshooting is in progress
Checklist Steps — Update Preparation
1. Review pending updates
- Navigate to Dashboard → Updates
- Review available updates for WordPress, plugins, and themes
- Do not apply updates blindly
2. Confirm update scope
- Identify what components will be updated
- Confirm updates do not conflict with active work
- Defer updates if major content or layout changes are planned
3. Confirm recovery readiness
- Confirm a recent backup exists
- Confirm restore procedures are known
- Do not proceed without recovery options
Checklist Steps — Apply Updates
4. Apply updates in controlled order
- Apply WordPress core updates first
- Apply plugin updates next
- Apply theme updates last
- Apply Bricks Builder updates after core and plugins
5. Avoid partial or interrupted updates
- Do not navigate away during updates
- Allow each update to complete fully
- Resolve any update errors before proceeding
Checklist Steps — Post‑Update Validation
6. Validate site behavior
- Confirm frontend loads correctly
- Confirm WP‑Admin loads without errors
- Navigate key pages and templates
7. Verify Bricks and templates
- Open the Bricks editor
- Confirm templates and components render correctly
- Confirm no warnings or compatibility notices appear
8. Verify SEO visibility settings
- Confirm indexing and visibility settings remain unchanged
- Avoid unintended sitemap or indexing changes
Checklist Steps — Change Documentation
9. Document the change
- Record what was updated
- Note the date and reason for the update
- Document any observed issues or follow‑ups
Required Output
- Updates applied in correct order
- Site behavior validated
- Configuration and templates verified
- Change documented and traceable
Pause & Lock
Each update cycle ends with a locked, known‑good state. Do not proceed with additional changes until the site is verified as stable.
Proceed to: Operations 02 — Backups & Recovery