WordPress updates: a safe order of operations for non-developers
Short answer: Update in a safe sequence: backup first, staging test, then core → plugins → theme—watch the site and have a rollback path.
NZ SMEs often click “update all” on a Friday without backups. One incompatible plugin can blank the homepage or break checkout until someone restores files.
Order of operations
- Backup files + database and verify you can restore.
- Read release notes for breaking changes—especially WooCommerce + payment gateways.
- Update plugins in small batches on staging; retest critical paths.
- Core last or per vendor guidance if your stack is sensitive.
After updating
Smoke-test homepage, a service page, contact form, and admin login. Clear caches if you use page caching or a CDN.
When to pause
During a major sale, invoice run, or if you lack backups—delay until you have cover.
Frequently asked questions
Should I enable auto-updates?
Security auto-updates for minor core releases help many sites—pair with monitoring and backups.
What if the site whitescreens?
Restore backup or disable the last plugin via filesystem/host tools—know the procedure before panic.