Most NZ SME incidents trace to shared passwords, ex-contractors who still have FTP, or one Google account that controls everything with no backup MFA device.
Roles that should exist on a typical site
- Owner: billing, domain registrar, DNS, emergency admin—ideally two trusted people can reach these.
- Editor / Author: can publish content but not install plugins or change users.
- Developer: staging + production deploy access via keys, not shared root passwords.
Break-glass kit (store offline)
Registrar login, DNS provider, hosting panel, primary CMS admin, and recovery codes for MFA. Test recovery once a year—discovering stale phone numbers during a crisis is expensive.
Offboarding checklist
When someone leaves, revoke CMS users, rotate shared secrets they touched, and audit integrations (forms, email SMTP, payment gateways) for tokens tied to their email.
Frequently asked questions
Is a shared 1Password vault enough?
It helps—pair it with individual accounts where the platform supports it so audit logs show who acted.
Should the owner use the same login as the agency?
No. Agencies should have their own user with a documented role; shared owner credentials erase accountability.
Putting this into practice on your NZ website
This guide sits in our Security & maintenance collection. The goal is practical advice you can act on without a computer science degree. Start with one change, measure whether enquiries or usability improve, then tackle the next item. Small businesses across Auckland, Wellington, Hamilton, Christchurch, and regional New Zealand face the same constraints: limited time, real customers, and a website that must earn its keep.
For Least-privilege credentials and break-glass access for owners, the highest-leverage move is usually to align your live site with what the guide recommends, then fix anything that blocks Google from crawling pages or stops visitors from contacting you. If your site runs on WordPress, many of these tasks are configuration and content work rather than custom development.
Document your starting point: note current enquiry volume, average page speed from PageSpeed Insights, and any errors showing in Google Search Console. Without a baseline, improvements are guesswork. Revisit the same metrics after 90 days—SEO and UX changes rarely produce overnight miracles, but sustained progress should be visible in leads and user behaviour.
Share this guide with whoever maintains your site—an employee, a contractor, or your hosting support desk—so terminology and priorities align. The FAQ section on our main site answers common project questions if you are weighing a rebuild versus incremental fixes.
When to involve a web partner
Some tasks—migrations, checkout changes, security incidents, or a full redesign—benefit from experienced help. If you are comparing providers, look for clear scoping, realistic timelines, and measurement tied to business outcomes rather than vanity metrics. Our team builds and maintains business websites nationwide; explore relevant services below or request a quote when you are ready.
A good partner will ask about your customers, geography, and capacity to publish content—not only colour preferences. Review our recent website projects for examples of brochure, WordPress, and ecommerce work across New Zealand.
Related NZDH services
More guides in this topic
- Website maintenance and security basics for NZ small businesses
- Incident response basics: first steps if your site is compromised
- Suspicious files and permissions: what they can indicate
- Malware scans vs clean restores: picking the fastest recovery path
- Security headers beginners should know (high-level)
Browse the full Security & maintenance guide hub or return to the guides home.
Explore on NZDH.co.nz
- All practical guides
- Website design services
- SEO services
- Recent website projects
- Frequently asked questions
- Web hosting — NZ-friendly hosting with support that answers clearly
Authoritative further reading
These independent resources complement this guide. Search engines and customers both reward accurate, helpful information—we link out where official documentation or regulators explain the topic better than a generic blog post could.