29 Oct 2026 · 4 min read · Lunor Medya · Updated 20 Nov 2026
A WordPress maintenance routine: weekly, monthly and yearly tasks
A practical WordPress maintenance calendar that groups updates, backups, security and performance checks by frequency and makes clear who does what.
Most problems on WordPress sites are not sudden; they are the result of neglect piling up: a plugin not updated for months, a backup nobody has ever tried to restore, an error log no one reads. This article turns maintenance from something done “when we remember” into a routine split by frequency.
Before you start: three prerequisites
- A staging copy: trying major updates on a copy of the live site lets you catch problems before visitors see them.
- Off-site backups: backups should not live only on the same server; keep a copy in separate storage.
- A maintenance log: a simple list of what was updated when and what went wrong. It is the first place to look when something breaks.
Weekly tasks
- Review pending core, theme and plugin updates, and apply minor security releases promptly.
- Check that recent backups actually ran and that their file sizes look reasonable.
- Send a test submission through the contact and quote forms and confirm the email arrives.
- Check that the site is reachable and key pages load without errors.
Monthly tasks
- Try major version updates on staging and push them live if nothing breaks.
- Deactivate and delete unused plugins and themes; inactive code can still carry vulnerabilities.
- Review the user list: remove accounts of people who have left and reduce unnecessary admin rights.
- Look through server and PHP error logs; recurring warnings often precede bigger issues.
- Check Search Console for crawl errors and security notices.
- Measure load times of important pages and compare them with last month.
Quarterly tasks
- Do a test restore from a backup. A backup that cannot be restored is not a backup.
- Scan for broken links and 404 pages, and add redirects where needed.
- Clean up revisions, drafts and transient records piling up in the database.
- Check expiry dates of paid plugin and theme licences; an expired licence means no more updates.
Yearly tasks
- Confirm the server’s PHP version is still supported and plan an upgrade if needed.
- Re-evaluate the plugin list: is each still needed, is its developer active, is there a simpler alternative?
- Put domain, SSL certificate and hosting renewal dates in the calendar.
- Update the record of who holds access to the admin panel, hosting and domain accounts.
Should automatic updates be on?
WordPress installs minor maintenance and security releases of core automatically by default, and automatic updates can be switched on per plugin and theme. A practical approach: keep security and minor releases automatic, and update plugins that directly drive how the site works (ecommerce, forms, translation, page builders) by hand after testing on staging. Even with auto-updates on, do not skip the weekly check; the only way to know an update really succeeded is to look at the site.
Security measures to add to the routine
- Use two-step verification on admin accounts and avoid guessable usernames such as “admin”.
- Limit failed login attempts.
- Disable theme and plugin file editing in the dashboard; code changes should be made in a controlled way, not from the panel.
- Give each user only the role they need; someone entering content does not need administrator rights.
Who does what?
| Task | Site owner | Technical team |
|---|---|---|
| Form and content checks | Yes | Supports |
| Updates and testing | Is informed | Yes |
| Backups and restore tests | Sees the result | Yes |
| User and permission clean-up | Reports who has left | Applies it |
| Licence and renewal tracking | Approves payment | Sends reminders |
If an update breaks the site
No need to panic; this is what the routine is for. First find the latest change in the maintenance log. If the problem started with a specific plugin, deactivating it often brings the site back. If not, restore the pre-update backup and investigate the update on staging. Record the cause so the same step is taken more carefully next time.
A smooth routine also depends on the environment the site runs on; we cover that on our hosting and infrastructure page. If you would rather hand this list to a team on a regular basis, see our maintenance and support service and the website maintenance package.