A WordPress site is never finished. Core, plugins and themes release updates all year, and each one can close a security hole or open a compatibility problem. Skip them and the site gets slower, easier to hack and more likely to break at the worst moment. This WordPress website maintenance checklist shows what to do and how often: backups and monitoring daily, updates and backup checks weekly, form tests and Site Health monthly, restore tests quarterly, and domain, SSL and hosting renewals yearly. Two 2026 changes need attention too. PHP 8.2 loses security support on 31 December, and SSL certificates now last 200 days at most.
What WordPress website maintenance includes
WordPress maintenance is the recurring work that keeps a site updated, backed up, monitored, secure and working for visitors. It covers core, plugin and theme updates, tested backups, uptime and security alerts, form and email checks, and yearly renewals.
It isn't the temporary maintenance mode page visitors see while a site is being changed. That's a screen, not a routine. Nor does a host's automatic backup count on its own: a copy stored on the same server can vanish with the site, and nobody has checked it restores. The tasks start with the ones that run without you.
Daily WordPress maintenance tasks
Nothing here needs a person unless an alert fires, so set these up once and let them run. Alerts only help when the security settings behind them are right, so learn how to secure a WordPress site before you rely on them. One catch: alerts sent to an unread inbox are worthless, so name an owner.
- An off-site backup runs every day and is stored somewhere other than the web server.
- An uptime monitor, such as UptimeRobot or Jetpack's downtime monitor, emails you if the site goes down.
- Security alerts from a tool like Wordfence or Patchstack reach a named person.
- Any overnight alert gets read and answered the same day.
Weekly WordPress maintenance tasks
Weekly work is about keeping software current and proving nothing broke afterwards. You apply updates, test the live site, confirm the latest backup and leave a short record of what changed.
- Apply updates. Install security releases within days. The Australian Signals Directorate's Essential Eight uses two weeks as its benchmark for internet-facing services, or 48 hours when a vendor rates a flaw critical or an exploit exists. It's guidance for organisations, not a legal rule for your site. Test page builder, form, checkout and SEO plugin updates on a staging copy first, and take a fresh backup before you start, because a rollback is only as good as the copy behind it.
- Check the live site. Open the homepage and a service page, then submit your contact form. WordPress 6.6 added automatic rollback for plugin auto-updates, but it only catches PHP fatal errors. A broken layout or a dead form stays live. Check on a phone as well as a desktop, and view the site logged out, because administrators often see a page visitors don't.
- Confirm the last backup finished. It should hold both files and the database. Glance at the date and file size too, since a sudden drop in size is worth a look.
- Hold big updates before peak trading. The end of the financial year on 30 June, Black Friday and Boxing Day are poor times to find a bug.
- Log what changed. One line per update is enough: the date, the plugin and the version. When something breaks, that line saves an hour.
Monthly WordPress maintenance tasks
Monthly checks catch the problems weekly updates can't see: contact forms that fail silently, drops in search visibility and plugins that have been quietly abandoned.
- Submit your own enquiry form. Send it from a different address than the one that receives it, then confirm the email lands in an inbox, not spam. When it doesn't, the cause is usually SMTP settings or missing SPF and DKIM records, and proper business email hosting fixes most of it.
- Open Tools > Site Health. Work through the critical issues first. Recommended items can wait. Note the PHP and database versions it reports, because you'll need them for the quarterly check.
- Review Search Console. Check indexing errors, pages that dropped out of the index since last month, and Core Web Vitals. Field data comes from real visitors, lab data from a test run. Google's good thresholds on web.dev are LCP at 2.5 seconds or less, INP at 200 milliseconds or less and CLS at 0.1 or less. Smaller Australian sites often lack the traffic for field data, so you'll only see lab figures.
- Check for abandoned plugins. Look at each plugin's last-updated date on WordPress.org, and whether it's been closed. Delete what you don't use rather than just deactivating it. A plugin untouched for a long stretch needs a replacement plan, especially if it handles forms or payments.
- Fix worthwhile broken links. Start with your highest-traffic pages. Redirect only where a real replacement page exists. Otherwise leave the 404.
Quarterly WordPress maintenance tasks
Quarterly work moves from checking to proving. You restore a backup, review who has access, confirm your PHP version, and tidy up plugins, themes and the database.
- Run a full restore test on staging. A backup you've never restored is a hope. We recommend confirming completion weekly, restoring fully each quarter, and monthly for online stores. After restoring, check that the site loads, you can log in and a test enquiry arrives.
- Audit user accounts. Remove former staff and contractors, and switch on two-factor authentication for every admin. Replace shared logins with individual accounts so you can see who changed what.
- Check your PHP version with your host. According to php.net, PHP 8.2 loses security support on 31 December 2026 and 8.3 follows on 31 December 2027. WordPress.org recommends 8.3 or newer. Update plugins first, then switch versions on staging. Record the date of the switch in your change log.
- Audit plugins, themes and licences. Cancel what nobody uses and renew what you rely on before it lapses. Watch for overlap, such as two SEO plugins or two caching tools.
- Clean the database, after a fresh backup. Old revisions and expired transients are safe to trim once the backup is verified. On a live store, take that backup the same day.
- Re-read key pages. Check prices, phone numbers and opening hours, then compare GA4 enquiries with last quarter.
Yearly WordPress maintenance tasks
Yearly work protects the foundations: your domain, SSL certificate and hosting. Let any one of them lapse and the whole site can go offline.
- Renew your domain early. Confirm the ABN or ACN behind a .com.au is current, and check auDA for the renewal windows that apply to you. Put the expiry date in two calendars, and make sure the registrant email goes to someone who reads it.
- Check SSL auto-renewal. Under the CA/Browser Forum schedule, certificates last 200 days at most, falling to 100 days from 15 March 2027 and 47 days from 15 March 2029. Manual renewal won't keep up.
- Review your hosting. Look at the PHP versions offered, backup retention, staging access and support hours in Australian time zones. Ask whether the plan still fits your traffic and storage.
Then ask one honest question: does the site still earn its keep?
DIY or professional WordPress maintenance
A site owner can usually manage the weekly tasks in 15 to 30 minutes, plus one to two hours a month and a half day a quarter. Those are typical published ranges, not promises. DIY works when one person owns the job and the site is simple: a brochure site, a handful of plugins, no payments. Hand it off when nobody owns it, past updates have broken the site, there's no tested restore, you take payments or bookings, or the plugin stack is long. Any task can have an owner who isn't you.
Write the routine down as a one-page checklist so anyone covering for you can follow it. If you'd rather not carry it, WordPress maintenance help is a sensible place to start. Sometimes the answer is the platform. If upkeep eats more time than the site earns, look at alternatives to WordPress. Moving costs time and money, so weigh it honestly.
WordPress maintenance checklist FAQs
How often should WordPress be maintained?
Apply updates and check backups weekly, review forms and Site Health monthly, test a full restore quarterly, and renew domain, SSL and hosting yearly. Alerts and off-site backups run daily without you. Stores and booking sites should tighten every step, especially restore tests.
How long does WordPress maintenance take?
Typically 15 to 30 minutes weekly, one to two hours monthly and half a day quarterly, based on published ranges. A neglected site takes longer the first time, because months of updates and untested backups have to be cleared before the routine settles.
Does my host already handle WordPress maintenance?
Usually only part of it. Hosts commonly cover server updates, SSL and backups. They rarely handle plugin updates, form and email tests, user audits or restore tests. Ask your host which tasks are covered, and get the answer in writing.
Is WordPress still worth maintaining in 2026?
Often, yes. A well-run WordPress site with a clear owner works fine. If upkeep keeps slipping, or you want simpler publishing, moving can cost less than maintaining.
WordPress maintenance help from EffektivWeb
If WordPress upkeep keeps sliding to the bottom of the list, we can look at your routine with you, or at whether another platform suits the site better. There's no pressure either way.