One Website for Australia and New Zealand?

The pattern turns up constantly in audits. An Australian site with a New Zealand mobile number in the footer, a shipping page that mentions Auckland once, prices in AUD with 10% GST folded into them, and a steady trickle of New Zealand enquiries nobody planned for. The business serves two markets. The website serves one and hopes the other sorts itself out over email.

Often it does. Trans-Tasman buyers are patient. But patience isn't a conversion strategy, and the gap between "they'll work it out" and "the page answered it" is where a share of those enquiries quietly goes.

Our position, given nearly every time this comes up: one website, with a New Zealand section on a subfolder. Not two domains. Not a subdomain. And usually not hreflang either — not until the site genuinely has near-duplicate pages that need telling apart. The two-domain answer sounds thorough in a meeting and then becomes two of everything for the next five years.

The default architecture, and why it wins

There are four ways to structure a trans-Tasman site, and they are not equally sensible.

The reason the subfolder wins is unglamorous: consolidation. Whatever credibility your domain has accumulated — supplier links, trade press mentions, years of Google seeing it behave like a real business — attaches to the domain. A subfolder inherits all of it on day one. A second domain inherits none.

It's the same argument we make about subfolders versus separate sites for multi-location businesses, and it holds across the Tasman. Splitting a small site into two small sites gives you two weak sites.

The domain question isn't symmetrical

The rules don't run both ways, and the asymmetry matters before you plan anything.

To hold a .com.au or a direct .au domain you need an Australian presence — an ABN or ACN, or an Australian trade mark matching the name. That's set by auDA, the .au administrator, and it's enforced. A New Zealand company wanting a .com.au has to establish something real here first.

New Zealand runs the opposite policy. The Domain Name Commission imposes no local-presence requirement on .nz names — an Australian business can register its own .co.nz today, without an NZ entity, for roughly the price of a decent lunch.

Which makes one piece of advice easy: register the .co.nz version of your name regardless of what you build on it. It costs almost nothing and stops a competitor, or a speculator who noticed your Auckland enquiries, sitting on your name. Point it at your main site with a permanent redirect.

What you should not do is paste a copy of your Australian site onto it — that's a second site with none of your authority and all of your content, competing against you.

If the New Zealand side has grown enough to deserve its own build, the economics are a separate conversation; we've written about what a website actually costs in New Zealand, and the numbers aren't identical to the Australian ones.

hreflang in practice, and when it's overkill

hreflang tells Google that this page and that page are the same content for different audiences, so it can serve the right one to the right person. In a trans-Tasman setup the values are en-AU and en-NZ, with an x-default catching everyone else.

Three things about it get misunderstood.

It isn't a ranking boost. It influences which of two competing versions gets served, and helps Google see that a near-identical page is deliberate rather than sloppy. Google's documentation on localised versions treats it as a serving signal, not a lever on position.

The tags have to point both ways. Each page must reference every version, including itself. If your /nz/pricing page names the AU page as its Australian equivalent but the AU page says nothing back, Google treats the set as unreliable and ignores it. Broken return tags are the most common failure we see, and a half-implemented set does nothing.

It only earns its place when you have something to disambiguate. One pricing page and one contact page means no competing versions and nothing to resolve. It becomes useful the moment you have an AU pricing page in AUD and an NZ pricing page in NZD at parallel URLs — exactly the situation people worry is a duplicate content problem.

It usually isn't. Google doesn't penalise a business for having AU and NZ versions of the same page; it picks one as canonical and shows that. The risk is it picks the wrong one — which is what hreflang prevents, and why how duplicate content gets handled on Australian business sites applies here unchanged.

Nor is there still a country-targeting switch in Search Console to point a folder at New Zealand; that setting is gone. Your geographic signals are the domain, hreflang if you've implemented it, and the page itself — currency, address, phone format.

Currency, GST, and the pages that quietly lie

This is where most trans-Tasman sites lose people, and it isn't an SEO problem at all.

Australian GST is 10%. New Zealand GST is 15%. Both markets show consumers tax-inclusive prices — in Australia that's a legal requirement for consumer pricing under the Australian Consumer Law, not just habit — so an Australian price shown to a New Zealand buyer is wrong twice over: wrong currency, wrong tax treatment. The buyer can't tell how wrong without doing arithmetic you should have done for them.

The fix isn't a currency-switcher widget converting at yesterday's rate. It's deciding what you're quoting and saying so in plain words next to the number. Three honest positions:

• Prices in AUD, stated as AUD, with a line explaining what a New Zealand customer pays and who handles the tax.
• Separate NZD pricing on the NZ pages, set as real prices rather than live conversions, so they don't shift while someone's thinking about it.
• Quote-based pricing with the difference handled on the call — fine for services, hopeless with a cart.

For physical goods there's a compliance layer too. Australia applies GST to low-value imported goods sold to consumers once an overseas seller passes the registration threshold, and New Zealand runs an equivalent regime through Inland Revenue with different figures. Both get adjusted; the current positions live on the ATO's site and Inland Revenue's, and are worth checking with your accountant rather than a web studio's blog.

The related failure is service-area vagueness. If you don't ship to New Zealand, say so on the product page, not at checkout after someone's entered their address. If you serve NZ remotely but can't send a technician, say that too. Buyers forgive a limitation stated early, not one found at step four.

Search behaviour differs more than the spelling does

The instinct to "translate" for New Zealand is wrong. Both markets write the same English — colour, organise, enquiry — and the spelling conventions are effectively identical. What differs is the vocabulary for specific objects, the credentials that read as trustworthy, and the shape of the queries.

Vocabulary is the obvious one. Chilly bin, not esky. Jandals, not thongs — worth catching before it reaches a product page. If the everyday name of what you sell changes at the border, your NZ pages need the NZ noun or the product doesn't match what anyone typed.

Credentials matter more than most Australian businesses realise. A trust section built entirely on ABN registration, Australian Consumer Law and Australian industry bodies reads as foreign to a New Zealand buyer, because it is. NZBN, the Consumer Guarantees Act and the relevant NZ body are the local equivalents, and a page listing none of them asks for a leap of faith it hasn't earned.

Query shape is the one to verify rather than assume. Search Console will tell you, per country, which queries already bring New Zealand traffic — filter, sort by impressions, and read what people actually type before writing a single NZ page. That beats any generalisation we could offer, including the common claim that New Zealanders append "NZ" to searches more than Australians append "Australia".

If the New Zealand side is genuinely local — staff, an address, clients you can name — city pages earn their keep the way they do here, and we build them for Auckland and Wellington as readily as for Melbourne.

When a second domain actually earns its keep

The real cases share a property: the New Zealand operation is a business, not a market segment.

A separate legal entity with its own pricing, stock and support hours. A different brand name because yours was taken across the Tasman. Regulatory separation, common in financial services and health. An existing NZ brand you've acquired and shouldn't flatten into yours. A New Zealand team big enough that someone owns the site full-time.

If two or three of those describe you, build the second site. If none do, the second domain commits you to two content calendars, two link-building efforts, two analytics setups and two sets of legal pages to solve a problem a folder would have solved.

On cost: our custom builds start at $8,000 AUD, and a New Zealand section within that build is a scope line — extra pages, a currency decision, NZ-specific trust content. A genuinely separate New Zealand site is a second project, priced as one, because that's what it is. The ongoing difference is larger than the build difference, and it never stops.

FAQ

Do I need a .co.nz domain to rank in New Zealand?

No. A .com.au site can and does rank in New Zealand, particularly where the searcher isn't after a strictly local supplier. A .co.nz gives a stronger local signal but starts with no accumulated authority, so for most Australian businesses a New Zealand subfolder on the existing domain tends to be the stronger position for the first couple of years.

Register the .co.nz defensively anyway — the NZ registry has no local-presence requirement, so an Australian business can hold it.

Is hreflang worth it for a small Australian website?

Only if you have genuinely parallel pages for both markets. With one version of each page, hreflang has nothing to resolve. Once you have an AU pricing page and an NZ pricing page covering the same product at different prices, it earns its place — implemented properly, with every version referencing every other version, including itself.

Should I show prices in NZD or AUD?

Either, as long as the page says which and doesn't hide the difference. AUD with a clear note about what a New Zealand buyer pays is honest. Separate NZD prices are better for physical goods, because the buyer sees the number they'll actually be charged. Live conversion widgets are the weakest option — the price moves while they're deciding.

Will running AU and NZ versions of the same page hurt my rankings?

No. Google doesn't penalise near-duplicate regional pages — it picks one as canonical and serves that. The risk is it picks the version you didn't want shown in a given market, which is what hreflang and clear on-page geographic signals solve.

Where to start

If you're already taking New Zealand enquiries and doing nothing about it, the sequence is short.

Open Search Console, filter by country, and find out how much New Zealand traffic you get and on which queries. Ten minutes, and it decides everything downstream — there's no point building an NZ section for a market that turns out to be three visits a month.

Register your .co.nz and redirect it, whether or not you build on it.

Then, if the traffic justifies it, add a New Zealand section to the existing site: an NZ landing page, NZ pricing or shipping information, NZ credentials, a contact route with a local number. Leave hreflang until you have duplicated pages to reconcile.

If you're not certain your site even renders cleanly for a New Zealand visitor, run it through our free audit and start from the report rather than a hunch. Most trans-Tasman problems turn out to be one honest paragraph and a subfolder, not a second website.