The 12-Page NZ Business Website: When Less Is More
Most NZ business sites should be smaller, not bigger. Why 12 focused pages outperform 50 thin ones — and exactly which pages every NZ business actually needs.
TL;DR
Most NZ business sites we audit are oversized — 30-80 pages, half of them thin, contradictory, or duplicate. The instinct to 'add a page for everything' destroys site authority because Google increasingly demotes thin content. The right answer for most NZ SMBs is a tightly-focused 12-page site that covers every essential commercial query without diluting authority across pages that shouldn't exist.
- →Google increasingly demotes thin-content pages — and thin pages drag down rankings of good pages on the same domain.
- →Most NZ SMB sites have 30-80 pages but only 8-12 carry real commercial intent. The rest leak authority.
- →A tightly-focused 12-page site with deep content per page consistently outranks 50-page sites with shallow content per page.
- →When in doubt: cut. A page should exist because customers search for it, not because the business wants to talk about it.
- →Blog articles are different — they should be additive, indexed separately, and not counted against the core site page budget.
The thin-content problem most NZ sites have
Google's recent updates have repeatedly penalised thin content — pages with under 300 words of meaningful unique copy, pages that duplicate other pages on the same domain, pages that exist purely for keyword targeting without real customer-intent. The penalty isn't just on the thin page; it drags down the perceived authority of the whole domain. A 50-page site where 35 pages are thin scores worse overall than a 12-page site where every page is deep.
The 12 pages every NZ business actually needs
Home, About, Contact, Services (overview), one page per major service (typically 3-5), one page per key location served (typically 2-4), FAQ, and a free-resource or audit landing page. Total: 11-13 pages depending on services + locations. Every page should answer a specific customer intent that drives commercial value. Pages that exist only to "make the site look bigger" — generic blog category pages, empty tag archives, "About our process" pages that nobody reads — are net negative.
When more pages are justified
Three legitimate reasons to go bigger than 12. First: real city/area expansion — if you genuinely serve 15 NZ cities, dedicated /areas pages for each rank. Second: industry vertical depth — if you serve trades + tourism + hospitality with meaningfully different propositions, separate vertical pages help. Third: ecommerce or directory-style content where each entry is a distinct query target. For most SMB service businesses, none of these apply at scale, and 12 pages is sufficient.
Blog vs core site
Blog articles are a separate budget. Each post should target a specific informational or commercial query, be 800+ words of meaningful content, and have its own indexable URL. A 12-page core site + 25 deep blog posts outranks a 50-page core site + zero blog. Treat them as separate inventories — the core site is for high-intent commercial conversion; the blog is for top-of-funnel research traffic and topical authority.
How to cut without losing traffic
Audit Google Search Console for the actual queries each page ranks for, then traffic-weight the page list. Pages ranking for nothing valuable + getting no traffic are deletion candidates. Pages ranking for valuable queries are keepers — even if you think the content is weak. Cuts should be 301-redirected to the closest live page (consolidates link equity); orphaned pages should be removed cleanly from the sitemap. Done right, a 50-to-15 page cut typically lifts overall rankings, not drops them.
FAQ
Frequently asked.
What if I have 30 service variations? Do I really need to consolidate to 12 pages?
If each service genuinely has distinct search intent (different keywords, different customer types), 30 service pages can be justified. The test: does each page rank for a distinct commercial query that drives real revenue? If yes, keep it deep. If not, consolidate into parent pages with subsection content.
Will deleting pages tank my SEO?
Done wrong, yes. Done right — 301 redirecting deleted pages to the closest live page, keeping the cuts targeted at pages with zero traffic, and consolidating before removing — overall rankings typically lift. We see this routinely in client work: a 50-to-15 cut adds 20-40% organic traffic within 90 days.
What about local/area pages? Do those count against my budget?
If you genuinely serve those areas with distinct customer demand, area pages are legitimate — each ranks for a distinct local-pack query. The threshold: at least 10+ inbound search queries per area page per month. Below that and the page is probably not paying for the authority cost.
How long does it take to see results from a site cut?
30-60 days for ranking stabilisation, 60-120 days for organic traffic recovery and lift. Faster if the cut was a major thin-content issue Google was actively demoting; slower if the cuts are marginal pages that Google was already mostly ignoring.
More from the blog
Browse the Strategy hubNZ Business Schema.org Cheat Sheet for 2026
Practical schema.org reference for NZ businesses — which schema types matter for which business type, what to include, what to skip.
Google's March 2026 Update — What Changed for NZ
Google's March 2026 core update reshuffled NZ local-pack rankings and shifted AI Overviews coverage. The changes that matter and what to action now.
AI in Web Design: Where It Helps and the New Agency
AI is changing what a web agency can do — but only when used in meaningful ways. The honest read on what works, what's hype, and how Webgun uses it.
Apply this to your site.
Free audit, no commitment. We'll show you which of these wins are sitting on the table for your business right now.
Get a Free Audit