To rank in both Australia and New Zealand with English pages that are almost identical, give each market its own URL, make every page canonical to itself, and connect the pairs with reciprocal hreflang en-AU / en-NZ annotations plus an x-default. Then make the New Zealand pages genuinely different where a buyer would notice (NZ$ prices, 15% GST, shipping, NZ contact details and consumer law), because Google treats same-language regional pages as duplicates and can fold your NZ page into your Australian one.
This guide covers the part generic hreflang tutorials skip: two English-speaking markets that share most of their spelling, so the usual "localise the language" advice does not apply. You get a structure decision table, copy-paste link-tag and sitemap examples, the canonical mistakes that collapse NZ into AU, a localisation table built from Australian and New Zealand government sources, how to monitor each market now that Search Console's country targeting is gone, and an honest account of what is and is not known about how AI search engines treat regional variants. Google documentation and all government pages were checked on 2 November 2026.
Key takeaways
- Google says localised pages "are only considered duplicates if the main content of the page remains untranslated". An Australian and a New Zealand English page are, by that definition, duplicates unless you make them differ.
- hreflang does not stop duplication. It tells Google which URL to show in which country, and it is ignored if the two pages do not point to each other.
- Never point the NZ page's canonical at the AU page. Each regional URL should be self-canonical and list itself, its twin and an x-default.
- Spelling is not a differentiator between AU and NZ English. Prices, GST (10% vs 15%), shipping, business numbers, regulators and local proof are.
- Search Console's International Targeting report is deprecated. Monitor each market with the Country filter, URL Inspection and the Generative AI performance report's Countries view.
- No AI engine other than Google documents how it handles en-AU vs en-NZ pages. Make every regional page say which country it serves in plain text, so the signal survives even where hreflang is not read.
Why are Australian and New Zealand pages the hardest hreflang case?
Because nothing about the language separates them. Most hreflang guides use English and German, or at least US and UK English, where spelling and vocabulary differ. Australian and New Zealand English share the same broadly British spelling conventions, so a page written for Brisbane reads perfectly well in Christchurch. To Google, that makes them near-duplicates.
Google is explicit about this. Its guide to telling Google about localised versions of your page says: "Localized versions of a page are only considered duplicates if the main content of the page remains untranslated." An AU page and an NZ page in English are untranslated by definition. For that situation, Google's guide to managing multi-regional sites says to "pick a preferred version and use the rel="canonical" element and hreflang tags to make sure that the correct language or regional URL is served to searchers."
The risk shows up in Search Console. If Google decides two pages are duplicates, the Page indexing report files one under "Duplicate, Google chose different canonical than user" or "Duplicate without user-selected canonical", and Google "will not serve this page in Search". Google's own fix for a page that is not really a duplicate is blunt: "you should ensure that the content differs substantially between the two pages." The rest of this guide is about doing both jobs at once: the markup that tells Google which URL belongs to which country, and the content differences that make the two URLs worth keeping.
Which site structure should you use for Australia and New Zealand?
The short answer: separate country domains (.com.au and .co.nz or .nz) give the strongest country signal, subfolders on one generic domain (/au/ and /nz/) are the easiest to run, and one shared site with no regional versions is fine only when your offer and price are the same in both countries. Google describes country-code domains as providing "a strong signal to both users and search engines" that a site "is explicitly intended for a certain country".
| Structure | Example | Strengths | Weaknesses | Best for |
|---|---|---|---|---|
| Separate country domains | example.com.au + example.co.nz | Strongest country signal; easy to separate reporting; local trust in the URL | Two domains to build links and authority for; more infrastructure; .com.au needs an Australian presence | Brands with real operations, stock or staff in both countries |
| Subfolders on a generic domain | example.com/au/ + example.com/nz/ | One domain's authority; low maintenance; easy to add more markets later | Country not obvious from the URL; relies on hreflang and on-page signals | SaaS and online stores planning further markets |
| Subdomains on a generic domain | au.example.com + nz.example.com | Easy to host separately; easy to separate | Google notes users may not know whether "au" means a language or a country | Teams that need separate platforms per market |
| NZ folder inside an Australian domain | example.com.au/nz/ | Keeps existing AU domain equity; cheapest to test NZ demand | The .com.au suffix signals Australia; Google does not document how a /nz/ folder inside it is weighed; NZ buyers may assume AU pricing and shipping | Short-term tests before committing to NZ |
| One site for both, no regional versions | example.com.au (serves both) | No duplication; all links and signals on one URL | Cannot show NZ$ prices or NZ GST on a crawlable URL; Google warns against adapting content by IP | Services with identical offers and prices in both countries |
Two practical constraints shape the choice. A .com.au name requires a verifiable Australian presence such as an ABN or ACN, or an exactly matching Australian trade mark, as Sprintlaw's summary of the auDA licensing rules explains. The .nz space is more open: the Domain Name Commission says anyone over 18 can register a .nz name and you do not have to be in New Zealand. So a New Zealand business expanding west often has to choose subfolders or an Australian entity, while an Australian business expanding east can simply register a .co.nz or .nz.
A quick decision matrix
| Your situation | Recommended structure | Why |
|---|---|---|
| Established in both countries, separate pricing, stock and teams | Separate country domains | Strongest signal, clean reporting, the URL itself tells buyers you are local |
| Australian business testing NZ demand | /nz/ folder first, move to .co.nz or .nz if it works | Cheap to start; plan the redirect map from day one |
| NZ business entering Australia without an Australian entity | Subfolders on a generic domain | .com.au eligibility may rule out a country domain |
| Ecommerce on Shopify, WooCommerce or similar with markets | Subfolders (/en-au/, /en-nz/) generated by the platform | Platform handles currency per URL; you still need to check the hreflang output |
| B2B service with one price and one offer for both | One site, clearly naming both countries | Two near-identical URLs add risk without adding value |
How do you write hreflang for en-AU, en-NZ and x-default?
Use the language code en plus the country codes AU and NZ, list every version on every version (including the page itself), and use full absolute URLs. Google supports three equivalent methods: HTML link tags, HTTP headers and XML sitemaps. Pick one and use it everywhere.
The rules from Google's hreflang documentation that matter most here:
- Language codes are ISO 639-1 and region codes are ISO 3166-1 Alpha 2, so
en-AUanden-NZ. "You can't specify the country code by itself", sohreflang="NZ"is invalid. - The value is case-insensitive:
en-nzanden-NZare equivalent. - "Each language version must list itself as well as all other language versions." And "If two pages don't both point to each other, the tags will be ignored."
- URLs must be fully qualified with https://. Relative paths such as
/nz/pricing/are not valid. x-defaultis the fallback "when no other language/region matches the user's browser setting". For a trans-Tasman site it usually points to your main market's page or a country selector.
Option 1: link tags in the head (separate domains)
On the Australian page:
On the New Zealand page, the alternates are identical but the canonical points to itself:
Option 2: XML sitemap (subfolders)
Sitemaps are easier to maintain on large sites because the annotations live in one file. Add the xhtml namespace and give every URL its full set of alternates:
https://www.example.com/au/pricing/
https://www.example.com/nz/pricing/
https://www.example.com/pricing/
Here the x-default URL is a country-selector page, so it carries the same set of alternates. If your x-default is simply the Australian page, drop the third block. Our free sitemap generator will build the base URL list for you; it does not add hreflang, so add the xhtml:link lines yourself or from your CMS.
Option 3: HTTP headers (PDFs and other non-HTML files)
For a price list or product brochure in PDF, send the annotations in the response header, listing every variant including the one requested:
Link: ; rel="alternate"; hreflang="en-AU",
; rel="alternate"; hreflang="en-NZ" What should x-default point to?
Point x-default at the page you want shown to English searchers outside Australia and New Zealand, such as a visitor in Singapore or the UK. Most Australian-led businesses point it at the Australian page; businesses with a global offer point it at a country selector or a generic page. Google treats x-default as optional, but leaving it out means Google picks for those visitors.
Canonical and hreflang mistakes that collapse NZ into AU
The most common reason an Australian URL shows in google.co.nz instead of the New Zealand page is a contradiction between canonical and hreflang signals. Google's guide to consolidating duplicate URLs calls rel="canonical" "a strong signal that the specified URL should become canonical", and notes that "for canonicalization purposes Google prefers URLs that are part of hreflang clusters". Ahrefs' hreflang guide describes canonical tags that point away from an hreflang page as attributes that "contradict each other and confuse search engines", and reports that 67% of hreflang implementations in its 374,756-domain study had at least one issue.
| Mistake | What Google sees | Fix |
|---|---|---|
| NZ page has a canonical pointing to the AU page | "The NZ page is a copy, index the AU one." The NZ URL drops out. | Every regional page is canonical to itself |
| AU page lists the NZ page, but the NZ page does not list AU back | A one-way annotation. Google ignores the pair. | Generate both sets from one source (CMS field or sitemap) |
| hreflang points at URLs that redirect, are noindexed or blocked in robots.txt | Annotations to pages that cannot be indexed | Point only at the final, indexable, canonical URL |
| Visitors and crawlers are auto-redirected by IP from /nz/ to /au/ (or the reverse) | Google may never see one version. Google advises: "Don't use IP analysis to adapt your content." | Show a "Looks like you're in New Zealand" banner and let people choose |
| Currency switches by cookie or script on a single URL | One URL, one price. No crawlable NZ version exists. | Give NZ prices their own URL if NZ is a real market |
Codes such as NZ, en-NZL or nz-en | Invalid values, ignored | Use en-NZ and en-AU |
| Relative or http:// URLs in annotations | Not fully qualified, ignored | Absolute https:// URLs only |
| Sitemap and on-page tags disagree after a migration | Conflicting clusters | Use one method and remove the other |
| NZ page is the AU page with "A$" swapped for "NZ$" | Near-duplicate. Google may still fold it. | Make the content differ where it matters (next section) |
One more point about Google's wording. "Pick a preferred version" in the multi-regional guide describes how to handle content you cannot or will not differentiate. If you want both pages to rank on their own, the safest set-up is self-referencing canonicals plus reciprocal hreflang, with content that gives Google a reason to keep both.
What should you actually localise between AU and NZ pages?
Localise everything a buyer uses to decide or to trust you: price, tax, delivery, legal terms, business identifiers, contact details and proof. Spelling is not on the list, because Australian and New Zealand English already match on almost every word you will write. Google's multi-regional guide lists "local addresses and phone numbers on the pages, the use of local language and currency" among the signals it uses to understand which country a page serves.
| Element | Australia | New Zealand | Why it matters |
|---|---|---|---|
| Currency | A$ (AUD) | NZ$ (NZD) | A named country signal in Google's guide; the first thing a buyer checks |
| GST rate | 10% (business.gov.au) | 15% (Inland Revenue) | The NZ price is not just an exchange-rate conversion |
| Price display | Total price, including GST, shown as a single figure and as prominent as any part price (business.gov.au) | Make clear whether the price includes GST; prices must not mislead under the Fair Trading Act (Consumer Protection) | Copying AU price wording to NZ can mislead |
| Business identifier | ABN / ACN | NZBN (nzbn.govt.nz) | Footer, invoices and Organization schema; a trust signal |
| Phone and address | +61, Australian address | +64, NZ address if you have one | Named country signal; do not invent an NZ address you do not have |
| Shipping and returns | AU carriers, delivery times, return address | Trans-Tasman delivery times, duties if shipping from AU, NZ returns process | The most visible practical difference for ecommerce |
| Consumer law and regulators | Australian Consumer Law; ACCC; OAIC for privacy | Consumer Guarantees Act and Fair Trading Act; Commerce Commission; Privacy Commissioner | Warranty and refund wording differs |
| Examples, case studies, reviews | Australian customers, cities, suppliers | NZ customers, cities, suppliers | The cheapest way to make main content differ substantially |
| Vocabulary | thongs, esky | jandals, chilly bin | Matters for consumer and retail pages; rarely for B2B |
| Place names | States and territories | Regions; te reo Māori names where your audience uses them | Local relevance; check usage with NZ customers |
How different do the two pages need to be?
Google does not publish a threshold, so anyone quoting a percentage is guessing. What Google does say is that pages it treats as duplicates should "differ substantially" if you want both served. In practice, prioritise the main content rather than the footer: a New Zealand section on delivery and returns, NZ$ pricing with GST explained, NZ customer examples and NZ-specific FAQs change what the page is about for a New Zealand buyer. A different phone number in the footer does not. If you cannot justify those differences for a page, consider not creating an NZ version of it at all and let the AU page (or a shared page) serve both countries.
How do you monitor each market in Search Console now?
Search Console no longer lets you set a target country. Google's help page states that the International Targeting report has been deprecated, that country targeting is no longer supported, and that Google continues to support hreflang. With that report gone there is also no dedicated hreflang error list in Search Console, so monitoring is now a mix of Search Console filters and your own crawling.
- Set up properties that match your structure. One Domain property per country domain, or URL-prefix properties for
https://www.example.com/au/andhttps://www.example.com/nz/alongside the domain property. - Filter Performance by Country. Set Country = New Zealand and check the Pages tab. If Australian URLs collect New Zealand impressions for queries where an NZ page exists, Google is serving the wrong version.
- Inspect the NZ URLs. URL Inspection shows the user-declared canonical and the Google-selected canonical. If Google selected the AU URL, the pages are being folded together.
- Read the Page indexing report. Watch for NZ or AU URLs under "Duplicate, Google chose different canonical than user".
- Check AI feature impressions per country. The Generative AI performance report (announced June 2026, available to all sites from 31 August 2026) shows which of your URLs appeared in AI Overviews and AI Mode, with a Countries view. It reports impressions only, with no query dimension. We cover it in detail in our guide to the Search Console generative AI report.
- Crawl the hreflang clusters. Use a crawler that reports missing return links, non-canonical targets and invalid codes, and re-run it after every template or platform change.
Do ChatGPT and Google AI Overviews respect hreflang for regional pages?
For Google, AI Overviews and AI Mode are built on the normal Search index, so the same hreflang and canonical choices feed them. For ChatGPT, Claude, Perplexity and Gemini, nobody has published how they treat en-AU versus en-NZ pages, and none of them documents support for hreflang. What follows separates what is documented from what is not.
Google says a page only needs to be "indexed and eligible to be shown in Google Search with a snippet" to appear in its AI features, and that there are no other special optimisations (AI features and your website). AI Mode is available in both Australia and New Zealand in English. So if Google folds your NZ page into your AU page for classic results, expect the AU URL to be the one grounding AI answers in New Zealand too.
The best public test so far is Glenn Gabe's December 2025 study of how AI search platforms handle hreflang and multilingual queries. Google's blue links, AI Mode, Bing and Copilot generally returned the correct-language URL. AI Overviews usually did, but one French query surfaced the US English page. ChatGPT, Perplexity and Claude most often returned US English URLs even when they answered in the searcher's language. His test was about language, not country, and it used a small set of queries, so it does not tell you what happens with two English regional versions.
| Engine | What is documented | What is not known |
|---|---|---|
| Google AI Overviews and AI Mode | Grounded in the Search index; same indexing and snippet requirements; AI Mode live in AU and NZ; Countries view in the Generative AI performance report | Whether AI features pick the hreflang-matched regional URL as reliably as blue links do |
| ChatGPT search | OpenAI's help centre says ChatGPT may use a general location based on your IP address and share it with search partners, and rewrites queries before sending them; the API web search tool accepts an approximate user location (country, city, region) | Whether hreflang is read at all; how it chooses between same-language regional pages |
| Claude | Anthropic says Claude may use your IP address to set a coarse city or region location for features such as web search (March 2026) | Whether hreflang is read; regional URL choice |
| Perplexity | No public documentation on regional page variants that we could find | Everything beyond Gabe's language test |
| Gemini app | No public documentation on regional page variants that we could find | Gabe saw inconsistent sourcing; no country-level test |
Location is clearly an input for ChatGPT and Claude, but location only helps if the engine can tell which of your pages belongs to New Zealand. If an engine does not read hreflang, the only signal left is what is visible on the page. That leads to three practical steps:
- Make each regional page self-describing. Put the country in the title and H1 where it reads naturally ("Solar batteries in New Zealand"), state NZ$ prices with GST, and name NZ delivery and contact details in the body text, not only in the footer.
- Earn country-specific mentions. AI answers lean on third-party sources. NZ directories, NZ media and NZ partner sites linking to your NZ URL make the association explicit. Our guide to entity SEO for AI search covers how engines connect a brand to places and facts.
- Measure from each country separately. Run the same queries with the location set to Australia and then New Zealand, and compare which URL is cited. Disclosure: AI Rank Lab is our product. Its AI Overview tracker and AI Mode tracker take a country and language per query, so you can check whether Google cites your .co.nz or your .com.au page in each market. Its ChatGPT, Claude, Gemini and Perplexity prompt runs do not emulate a location, so they cannot show you the NZ-versus-AU view for those engines.
If you are also expanding into non-English markets, our study roundup on multilingual SEO for AI search covers the language side, which behaves differently from the same-language case here.
Trans-Tasman hreflang testing checklist
Run this before launch and after any CMS, theme, platform or domain change. Each row is a pass/fail check.
| Check | How | Pass condition |
|---|---|---|
| Self-referencing canonical | View source on an AU and an NZ page | Each canonical equals its own URL |
| Full cluster on every page | View source or the sitemap entry | en-AU, en-NZ and x-default present on both versions |
| Return links | Crawler hreflang report | Zero missing return links |
| Valid codes | Crawler or manual check | Only en-AU, en-NZ, x-default (any case) |
| Absolute https URLs | Crawler | No relative or http:// targets |
| Targets return 200 and are indexable | Crawler status and robots checks | No redirects, 404s, noindex or robots.txt blocks |
| No forced geo-redirect | Load the NZ URL from an Australian connection (and the reverse) | Page loads; a banner may suggest the other site |
| Prices on the right URL | View the NZ page with cookies cleared | NZ$ prices with GST wording visible in the HTML |
| Main content differs | Side-by-side review of the AU and NZ versions | NZ-specific delivery, pricing, examples or FAQs in the body |
| Google's chosen canonical | URL Inspection on 5-10 NZ URLs | Google-selected canonical = the NZ URL |
| Right URL in the right country | Performance report, Country = New Zealand, Pages tab | NZ URLs, not AU URLs, take NZ impressions |
| AI features by country | Generative AI performance report, Countries view; AI Overview/AI Mode checks per location | NZ URLs appear for New Zealand where an AI feature shows |
Tools that help with trans-Tasman hreflang
Disclosure: AI Rank Lab is our product. We list it first because this is our site, and we've kept the same criteria for every tool below: does it help you verify the markup, the canonical Google chose, or the URL that actually shows in each country?
- AI Rank Lab - checks Google AI Overviews and AI Mode with a chosen country and language, so you can compare the URL cited in Australia with the one cited in New Zealand; also audits SEO, AEO and GEO readiness. Priced in USD. It does not validate hreflang clusters, and its LLM prompt runs are not location-specific.
- Google Search Console - the only source for the canonical Google actually selected (URL Inspection) and for per-country impressions, including AI features. Free. No hreflang error report since the International Targeting report was retired.
- A site crawler with hreflang reporting (for example Screaming Frog SEO Spider or Ahrefs Site Audit) - the practical way to find missing return links, non-canonical targets and invalid codes across thousands of URLs.
- Your CMS or ecommerce platform's market settings - Shopify Markets and multilingual plugins such as WPML can create regional URLs, and many output hreflang automatically. Check what they output; do not assume the defaults include x-default or the right canonicals.
If you are still deciding whether New Zealand is worth the effort, our guide to SEO in New Zealand covers the market, and what SEO costs in Australia helps you budget the Australian side.
The bottom line
Trans-Tasman SEO fails in a predictable way: two near-identical English pages, conflicting canonicals, and a New Zealand page Google decides it does not need. Separate URLs, self-referencing canonicals and reciprocal hreflang en-AU / en-NZ annotations fix the markup; real differences in price, GST, delivery, legal terms and local proof give Google a reason to keep both pages. For AI engines outside Google, assume nothing reads your hreflang and make the country obvious on the page itself.
Want to see which of your regional URLs Google's AI features cite in each country? Run an AI Overview check for Australia and New Zealand with AI Rank Lab.
Get a free AI ranking consultation
Want your brand to show up when ChatGPT, Gemini and Perplexity answer questions in your market? Tell us about your site and our team will send a personalized strategy.
