WordPress and platform choice for NZ small businesses: when it fits, and how to run it well
Who this is for. New Zealand owners evaluating WordPress against SaaS builders or custom development—and teams already on WordPress who want a sustainable operating model.
WordPress powers a huge share of the web because it is flexible and familiar. That flexibility is also a risk surface: plugins, themes, user roles, and hosting choices all affect security, speed, and maintainability.
1. When WordPress is a strong fit
- You need content publishing with roles (author, editor) and editorial workflows.
- You want WooCommerce for a store with extensible shipping, tax, and product modelling.
- You will invest in ongoing updates—either in-house discipline or a maintenance partner.
- You value data portability and open-source options over a fully closed SaaS.
2. When to reconsider WordPress
- The site is a single landing page with almost no updates—simpler stacks may cost less to run.
- You need highly bespoke application logic with minimal editorial content—a framework may be cleaner.
- Your team will install “a plugin for everything” without governance—expect instability.
3. Updates: a safe order of operations
Before you click “update all” on production:
- Take a fresh backup (files + database).
- Update on staging if available; smoke-test checkout, forms, and key templates.
- Update core, then trusted plugins, then theme—read changelogs for breaking changes.
- Clear relevant caches; verify front-end and admin.
4. Plugin hygiene
Each plugin is a dependency. Prefer maintained plugins with clear security history. Remove deactivated leftovers. Avoid overlapping SEO or caching plugins fighting each other.
5. User roles and least privilege
Editors should not be administrators. Use strong passwords and two-factor authentication for admin accounts. Retire accounts when staff leave.
6. WooCommerce on typical NZ hosting
Stores add database load, sessions, and admin AJAX. Plan for caching rules that exclude cart/checkout, adequate PHP workers, and monitoring during sales. Photography and variant counts affect performance as much as “theme choice.”
7. Page builders and long-term maintainability
Builders accelerate launches; they can also scatter styling across dozens of bespoke blocks. Document patterns, limit ad-hoc colours, and train editors on reusable components.
8. Security plugins vs good hosting practices
Security plugins help, but they do not replace patched PHP, sensible file permissions, WAF options where appropriate, and reliable backups. If compromised, sometimes a clean restore beats weeks of whack-a-mole.
9. Multisite and regional franchises
WordPress Multisite suits some NZ franchise models—shared users and updates—but adds architectural constraints. Decide centrally vs independently branded sites before you build.
10. Frequently asked questions
How many plugins are “too many”?
There is no magic number—quality and overlap matter more. Audit yearly: remove unused, consolidate duplicates, replace abandoned packages.
Should I allow automatic updates?
Minor core auto-updates can be fine for low-risk brochure sites; WooCommerce and complex stacks often benefit from staged testing.
Headless WordPress?
Powerful for developers; higher total cost of ownership for typical SMEs unless you have a clear omnichannel content strategy.
Related shorter guides. See the WordPress & platforms topic for platform comparisons, update habits, WooCommerce realism, and security thinking.