What to do before a big update
A pre-update checklist for WordPress site owners — everything to do before applying a major WordPress, plugin, or theme update.
Routine plugin updates are generally low-risk. But major updates — a new version of WordPress core, a major plugin version jump, or a theme overhaul — deserve a little preparation. This guide gives you a clear checklist to follow.
Quick summary
Before a major update: back up your site, check for known issues, test on a staging site if possible, update one thing at a time, and check the site right after. If something breaks, restore the backup.
What counts as a "big" update?
Not all updates need this level of care. Reserve the full checklist for:
- WordPress core major releases (e.g., version 6.4 → 6.5)
- Plugin major version jumps (e.g., WooCommerce 8.x → 9.x, Elementor 3.x → 4.x)
- Theme major updates, especially if you have a premium theme with heavy customization
- Multiple updates applied at once on a business-critical site
Routine minor updates (e.g., 6.5.1 → 6.5.2, or a plugin going from 2.3.1 → 2.3.2) can usually be applied without the full process — though a backup is still good practice.
The pre-update checklist
1. Take a fresh backup
This is the most important step. A backup is your "undo button." If anything goes wrong after the update, you restore the backup and you're back to exactly how things were.
Your backup should include:
- All WordPress files
- The database (where your content lives)
If you use a managed host like Flywheel, WP Engine, or Kinsta, you can trigger a manual backup from your hosting dashboard. Alternatively, use your site's backup plugin. Full details at How WordPress backups work.
Don't skip the backup
Updates occasionally cause problems. Without a backup, you may have no way back. A backup that takes two minutes to create can save hours of work.
2. Check for known compatibility issues
Before updating, do a quick check:
- Visit the plugin's or WordPress's changelog (the list of what changed in the new version).
- Search online for "[plugin name] [version number] issues" or "problems."
- Check the plugin's support forum on WordPress.org for recent posts.
If many people are reporting a specific problem with the new version, it may be worth waiting a day or two for a patch.
3. Test on a staging site (recommended for major updates)
A staging site (also called a test site) is a private copy of your website where you can make changes without affecting what visitors see. Most managed hosts offer this.
Create or refresh your staging site from your hosting dashboard.
Apply the update on staging first. Let it run.
Test your key pages: homepage, contact form, any store or booking features.
If staging looks good, proceed with the live site.
See What is a staging site? for more information.
4. Do the update
Apply the update during a low-traffic time — evenings or weekends are good for most business sites. Update one major thing at a time rather than everything at once.
Keep the update page open while it runs. Don't navigate away or close the browser.
5. Check the site immediately after
Right after updating, visit:
- Your homepage
- Your main service or product pages
- Any forms (try submitting a test entry)
- Your store (if you have one)
- The WordPress dashboard itself
A quick walkthrough takes two minutes and catches most issues before any visitor notices.
6. If something breaks
Don't panic. You have a backup.
Identify what changed. If you updated one thing, that's likely the cause.
Deactivate the newly updated plugin to test if that fixes it. See Deactivating vs deleting plugins.
If the site is completely broken, restore your backup from your hosting dashboard or backup plugin.
Contact us. We can help diagnose compatibility issues and find a path forward.
Common questions
Related guides
- WordPress updates explained
- Why updates matter
- How to update plugins safely
- How WordPress backups work
- What is a staging site?
Need a hand?