What NZ businesses usually hire a WordPress developer for
Almost every WordPress enquiry from New Zealand falls into one of three jobs: rebuild, repair or retail. Naming which one you need is the quickest way to a sensible quote.
Rebuild
The site was built years ago on a page builder and a theme that no longer gets updates. It looks dated on phones, staff are scared to edit it, and nobody remembers the hosting password. A rebuild keeps your domain, content and search history but replaces the theme and most plugins.
Repair
The design is fine, but the site is slow, throws a critical error after an update, or has been hacked. Repairs are targeted: find the cause, fix it, stop it happening again.
Retail
You want to sell online through WooCommerce, or your current WooCommerce shop charges the wrong freight, fumbles GST or loses orders. Retail work is mostly configuration and testing, with a little code.
Many sites need two of the three: a café that wants online gift vouchers probably needs a repair and a small retail job. Tell us which one hurts most and we will start there. If you are unsure whether to stay on WordPress at all, our NZ ecommerce design guide compares platforms for stores.
Should you rebuild your WordPress site or repair the one you have?
Repair the site if the theme is still maintained and the problems are specific; rebuild it if the theme is abandoned, the page builder generates heavy code on every page, or the site needs changes in more than half its templates.
Some decision rules we use when auditing NZ sites:
- Theme last updated years ago and flagged by security scanners: rebuild.
- Fewer than about fifteen plugins, most actively maintained, and only a few slow pages: repair.
- Staff edit through a builder that breaks layouts whenever they touch it: rebuild with block patterns.
- Site is fine but hacked once: repair, harden and move to a care plan.
- Brand refresh planned in the next year anyway: rebuild now rather than paying twice.
A rebuild is not a re-platform. Your posts, pages, media and URLs can stay where they are; we replace the parts that cause trouble. For very small sites a rebuild often costs less than a long run of repairs, and the starting plan is US$150.
How much does a WordPress developer cost in NZ?
WordPress developer costs in NZ swing widely because "WordPress work" can mean a two-hour fix or a two-month store build. The honest way to compare is by job: our rebuilds start at US$150, content sites of 299+ pages at US$300, WooCommerce stores at US$750, and care plans at US$120/mo.
What moves a WordPress quote up or down:
- How many unique page templates you need, not just how many pages.
- Whether content can be migrated automatically or has to be rewritten and restructured.
- The number of plugins that must be replaced with something lighter or custom.
- Forms, bookings, member areas and integrations with Xero or a CRM.
- WooCommerce product count, variations and shipping complexity.
- Hosting migration and email DNS work, if the site is moving providers.
NZ studios and freelancers each price differently, so ask every candidate for an itemised quote and compare the lines. For a wider view across site types, our NZ website cost guide lays out typical scopes side by side.
Why is my WordPress site slow, and can a developer fix it?
Most slow WordPress sites are slow because of what was added to them, not because WordPress itself is slow. A developer can usually fix it by removing weight rather than adding another optimisation plugin on top.
Google's Core Web Vitals give a clear target. Google's web.dev guidance treats a page as good when Largest Contentful Paint happens within 2.5 seconds, Interaction to Next Paint is 200 milliseconds or less, and Cumulative Layout Shift stays at 0.1 or below, measured at the 75th percentile of real visits.
The culprits we find most often on NZ business sites:
- Page builders loading their full CSS and JavaScript on every page, even simple ones.
- Sliders and background videos on the homepage that push the main heading below the fold.
- Five or six plugins doing overlapping jobs: two SEO plugins, three form plugins, several analytics scripts.
- Uncompressed photos straight from a phone or camera, often several megabytes each.
- Cheap shared hosting with slow server response, located far from New Zealand visitors.
- Chat widgets, review badges and booking embeds loading before the page content.
We measure before and after with PageSpeed Insights and Search Console's Core Web Vitals report, so you see what changed rather than taking our word for it.
Cutting plugin bloat without breaking the site
Plugin clean-up is careful subtraction: list every plugin, find out what it actually does on the live site, then remove, replace or merge until each job is done once. We always do it on a staging copy first.
Our audit sorts each plugin into one of four groups:
- Keep: maintained, lightweight, doing something the site needs.
- Replace: does a needed job but is heavy, abandoned or insecure; swap for a lighter plugin or a few lines of theme code.
- Merge: several plugins covering one job, such as forms or SEO; keep the best one.
- Remove: installed for a campaign years ago, or never actually used.
Removal leaves traces, so we also clean orphaned database tables, scheduled tasks and shortcodes left behind in old pages. Then we retest forms, checkout and any logged-in areas. You get the spreadsheet of what changed, including anything we recommend you pay for, such as a licence renewal for a premium plugin that is still worth keeping.
NZ or Australian hosting for a WordPress site?
Host in New Zealand if most visitors are Kiwis and you want your data kept onshore; Australian hosting in Sydney or Melbourne is also a reasonable choice for NZ audiences, and a content delivery network narrows the gap further for images and static files.
The main things to weigh:
- Latency: servers close to your visitors respond faster; a CDN helps with files but not with uncached pages or checkout.
- Data location: some clients, especially in health or government-adjacent work, prefer customer data to stay in New Zealand. Check your own obligations with your adviser.
- Support hours: a host whose support team works NZ hours can matter at 8 am on a Monday.
- Cloud options: AWS opened its Asia Pacific (New Zealand) region in Auckland in September 2025, which gives cloud-hosted WordPress an onshore option alongside NZ-owned hosts.
Whichever you choose, the hosting account should be in your business name and paid by you. We set up the server, SSL, caching and backups, then hand over the credentials. Hosting moves are quoted per task and include checking email DNS records, which is where most migrations go wrong.
WooCommerce for New Zealand: payments, NZ Post and GST
A WooCommerce store in New Zealand needs three things set correctly before it takes its first order: GST-inclusive pricing at 15%, shipping rates that reflect NZ carriers, and payment options Kiwi buyers trust. Our WooCommerce builds start at US$750.
Payments
Most NZ stores offer a local card gateway through its official WooCommerce plugin, plus WooCommerce's built-in direct bank transfer option for customers who prefer paying from internet banking. Trade customers can be offered invoice terms through a small custom rule. Your gateway account is always opened by you.
Shipping
The New Zealand Post extension listed on the WooCommerce marketplace can calculate live NZ Post rates at checkout; other stores prefer simple zone-based rates for urban, rural and island addresses. We test with real addresses before launch.
GST
Inland Revenue sets GST at 15% on most taxable supplies. We configure WooCommerce's tax tables so prices display inclusive of GST and invoices show the tax line, then your accountant confirms the settings.
If your catalogue is large or you want less maintenance, Shopify may suit you better; our Shopify developer NZ guide sets out that side of the choice.
Keeping a NZ WordPress site secure
Most WordPress hacks come through outdated plugins, reused passwords or abandoned admin accounts, not through WordPress core. Security is mostly routine done consistently.
What we set up on every site we build or take over:
- Unique admin accounts for each person, with two-factor sign-in and no shared logins.
- Plugins trimmed to what is maintained and needed, so there are fewer doors to lock.
- Automatic minor core updates left on, with major updates tested on staging first.
- Daily off-site backups stored separately from the host, and a restore actually tested.
- File editing disabled in the dashboard and sensible permissions on the server.
- Form spam protection that does not rely on annoying puzzles for real visitors.
If your site has already been hacked, we clean it, find how the attacker got in, close that path and give you a written summary. We do not claim any security certification, and for regulated data you should involve your own security or legal adviser.
WordPress maintenance retainers: what NZ clients get for the money
A WordPress care plan pays someone to keep the site updated, backed up and working, so problems are caught on a Tuesday afternoon instead of during your busiest weekend. After the two free months that follow launch, our plans start at US$120/mo, quoted in USD.
A typical month includes:
- Plugin, theme and core updates applied on staging, checked, then pushed live.
- Backup checks and a periodic test restore.
- Uptime monitoring and a look at any errors in the logs.
- A quick speed check against the Core Web Vitals baseline set at launch.
- Small content edits within the allowance written in your quote.
The exact allowance, what counts as a new project, and how requests are raised are all written into your quote rather than a generic policy. You can pay by Wise or bank wire each period. If you prefer to run updates yourself, we will show you how and stay on call for the tricky ones.
Handover: making sure you can edit pages yourself
A good WordPress handover means your team can add a staff profile, change opening hours or publish a news post without messaging a developer. We design the editing experience as deliberately as the public site.
On rebuilds we use the block editor with locked patterns: pre-designed blocks for things like service panels, testimonials you actually received, team cards and call-to-action strips. Editors choose a pattern, type into it and cannot accidentally break the layout. Roles are set so a staff writer can draft posts while only the owner can publish or install plugins.
Handover includes:
- Short screen recordings for the five or six tasks your team does most.
- A one-page guide listing every login, where it lives and who pays for it.
- Admin access for you, with our account easy to remove.
- The theme and any custom plugin code in a repository or archive you hold.
After that, whether you keep us on a care plan is entirely your choice.
Page builders, block themes or custom themes: which should a NZ developer use?
For most business sites we recommend a block theme with custom patterns; page builders suit teams that already know one well, and fully custom themes suit sites with unusual layouts or strict performance targets.
Block theme with patterns
Uses WordPress's own editor, adds very little extra code, and keeps editing consistent. Best default for service businesses, community organisations and clinics.
Page builder
Familiar drag-and-drop editing, but heavier pages and more to update. Reasonable if your marketing person already builds landing pages in one and speed is secondary.
Custom classic or hybrid theme
Written for your site only, very light, and ideal for complex listings or directories. Needs a developer for layout changes later.
Headless WordPress
WordPress as a content backend feeding a separate front end. Fast, but costs more to build and run; worth it for larger publishers, rarely for small NZ businesses.
If your team is weighing WordPress against a hosted builder, the trade-offs are covered in Webflow vs WordPress.
How to choose a WordPress developer in NZ you will not regret
Choose the developer who asks the most specific questions about your current site and explains what they would remove, not the one with the longest list of plugins they love.
Useful questions for any WordPress developer NZ businesses are considering:
- Will you work on a staging copy and show me before anything goes live?
- Which plugins would you remove from my site, and why?
- Where will the site be hosted, and whose name is the account in?
- How will you keep my current Google rankings during a rebuild?
- What will my team be able to edit without calling you?
- What happens if I stop paying for maintenance?
Warning signs: a developer who insists on hosting the site in their own account, will not hand over admin access, or promises a guaranteed ranking. You can read more general advice in our guide to hiring a WordPress developer.
WordPress SEO and AI answers for NZ searches
WordPress is a solid base for SEO when the theme outputs clean headings, the site is fast, and each page answers one clear question. A rebuild is also the riskiest moment for rankings, so we treat URL changes carefully.
What we do on every WordPress project:
- Crawl the old site and map every URL to its new home with 301 redirects.
- Keep titles and descriptions that already rank, and improve the weak ones.
- Add LocalBusiness or Organization schema, plus FAQ content written as direct answers.
- Submit the new sitemap in Google Search Console and watch coverage for the first weeks.
- Write service pages that name your NZ towns and suburbs naturally, which helps both Google and AI Overviews match you to local questions.
Nobody can promise a ranking on google.co.nz. If you want ongoing growth after launch, monthly SEO starts at US$150/mo; the NZ SEO services page explains the month-by-month work.
Every contact form, booking widget and newsletter sign-up on your WordPress site collects personal information, so it should collect only what you need and say what you do with it.
On builds we set forms to ask for the minimum, store entries securely or send them straight to your inbox without keeping a copy, and add a link to your privacy statement next to the submit button. For newsletter sign-ups we add an unticked consent checkbox rather than assuming consent.
If a developer outside New Zealand can see your form entries, information privacy principle 12 of the Privacy Act 2020 is relevant; the Privacy Commissioner's guidance on IPP12 explains when information may be disclosed offshore. We work on staging copies with test entries wherever we can and do not export your enquiry data. Your privacy statement and any decisions about offshore disclosure are yours to confirm with your own adviser; we build what you decide.
Worked example: a hypothetical Dunedin consultancy's slow WordPress site
Picture a twelve-person engineering consultancy in Dunedin whose WordPress site takes ages to load on mobile, and whose office manager is afraid to update the team page. This is an illustrative scenario, not a real client.
Our audit finds forty-one plugins, a page builder loading everywhere, a homepage video and US-based shared hosting. The theme has not been updated in years. Using the decision rules above, it is a rebuild, not a repair.
The itemised quote starts from the US$150 rebuild plan. It lists a block theme with eight patterns, migration of sixty pages and their images, a redirect map, a hosting move to Australian servers in the client's own account, and a Search Console check two weeks after launch.
Over roughly two weeks the office manager reviews staging each morning, NZ time, and records questions as voice notes. Plugin count ends at nine. Before launch we run PageSpeed Insights on the same pages as the original audit and share both reports. Afterwards the consultancy has two months of free care, then chooses whether to continue from US$120/mo.
Hiring a WordPress developer in India from NZ: how the first fortnight runs
From New Zealand, our working day starts around your lunchtime, since India sits six and a half to seven and a half hours behind depending on NZ daylight saving. Calls work best in the NZ afternoon; written updates arrive while you are offline.
Payments are straightforward: quotes and invoices are in USD from India, and you pay by Wise or bank wire from your NZD account, usually split into milestones. Your accountant can tell you how GST treats services bought from overseas; we do not advise on tax.
First two or three days
You send the site URL and a temporary admin login or a staging copy. We audit plugins, theme, hosting and speed and reply with findings and questions.
End of week one
You receive the itemised quote, approve it in writing, and share hosting access in your own account. A staging site is created.
Week two
Rebuild or repair work happens on staging. You review each NZ morning, reply in writing, and we adjust during the Indian day.
There are no site visits; everything is online. Contract basics are in our terms and your written quote. More on how we work with Kiwi clients is on the New Zealand hub.
WordPress developer NZ checklist: before, during and after the job
Use this list to keep any WordPress project on track, whoever you hire.
- Before: collect hosting, domain and admin logins; list the pages staff edit most; note which forms bring real enquiries.
- Before: export Search Console data so you know which pages already bring traffic.
- During: review on staging only; keep feedback in one written thread; test forms with your own email.
- During: check the redirect map covers every page that gets visits.
- Launch day: confirm SSL, email delivery, analytics and the sitemap submission.
- After: compare Core Web Vitals against the baseline; watch Search Console coverage for new errors.
- After: store the handover guide somewhere your whole team can find it.
Send us whatever you have from the first two lines and we can start the audit.