What WordPress maintenance actually covers for a small NZ business
A lot of Auckland small businesses treat "the site is online" as the same thing as "the site is looked after". Hosting keeps the server answering. WordPress maintenance is different: it's the regular work inside the site so updates, backups and login hygiene don't get left for a quiet Friday that never comes.
I'm not talking about redesigns or new features here. This is the unglamorous checklist that stops a brochure site or a WooCommerce store from quietly drifting into an unsafe, hard-to-fix state.
What "maintenance" actually means
In practice it's a short loop, repeated on a schedule you can stick to:
- Update WordPress core, plugins and themes — especially when a security release lands. WordPress.org's own hardening guidance is blunt: older versions do not receive security updates, so staying current is the baseline, not a nice-to-have. Security releases still arrive regularly (for example WordPress 7.1.4 on 28 October 2026); treat those as "do soon", not "next quarter".
- Take a backup you could actually restore — files and database, kept off the server. "There's a backup somewhere" is not the same as knowing you can put the site back.
- Check the site after updates — home page, a couple of key inner pages, contact forms, and for WooCommerce the cart and checkout. An update that "succeeded" can still break a payment gateway or a booking form.
- Remove what you don't use — inactive plugins and leftover admin accounts from freelancers who finished months ago. Every unused plugin is another thing that can age out of support.
- Keep logins boring and strong — unique passwords, and two-step authentication on admin accounts where you can. WordPress.org recommends both for the same reason: a guessed admin password is still one of the fastest ways into a small site.
Use plugins and themes from places you trust (the WordPress.org directory, or vendors you recognise). Random ZIP files from search results are how a lot of "we got hacked" stories start.
Hosting is not maintenance
Your host looks after the machine: uptime, disk, often PHP version and server patches. They are rarely responsible for which plugins you installed, whether those plugins still get updates, or whether yesterday's backup restores cleanly.
Managed WordPress hosting covers more of the stack than cheap shared hosting, but the application layer — WordPress itself, your theme, your plugin set — is still mostly yours unless the plan says otherwise. Read the host's support scope once. It saves an awkward conversation later.
DIY is fine — until it isn't
For a simple brochure site with a handful of plugins, a careful owner can own the checklist: backup, update one thing at a time, click around, done. That works when someone actually does it.
It stops being fine when:
- The site takes money or bookings. A broken checkout on a Friday afternoon costs more than a careful update routine.
- Nobody has a staging copy. Clicking "update all" on a live store is gambling with today's orders.
- Plugins conflict after an update and the homepage whitescreens. You need a restore path, not a guess.
- Nobody remembers what's installed or why. That's when "quick maintenance" turns into archaeology.
If you DIY, keep two clocks: security releases as soon as you reasonably can; everything else on a weekly or monthly round. Never leave it for months and then update twelve things at once.
A routine that fits a small NZ business
Weekly or monthly, depending on how painful a break would be:
- Confirm the latest backup finished, and that you've restored once to a staging copy so you know the restore works.
- Apply due updates (core first if needed, then plugins/themes), ideally on staging for a store.
- Spot-check forms, login, and checkout.
- Glance at Users → Administrators. Remove accounts that shouldn't be there.
- Note anything odd: unfamiliar plugins, sudden "update available" storms, emails about failed logins.
None of that makes a site "hack-proof". Risk goes down; it doesn't hit zero. The goal is a site you can keep running without a crisis every time WordPress ships a fix.
Where I fit in
I fix WordPress and WooCommerce sites and build small custom plugins when nothing off the shelf fits, and I also take on ongoing care — updates, backups, security patches and small changes — so you're not the person remembering to click Update at midnight. If an established plugin or a settings change does the job, I'll say so before writing any code.
If your WordPress site has been coasting without a maintenance routine, send me a short note with the URL and what's worrying you. I'll tell you what I'd check first.