When You Need International SEO
Not every business needs international SEO. If you're a plumber in Auckland, you don't need to rank in Germany. But if any of these apply, you do:
- You serve customers in multiple countries
- Your website has content in multiple languages
- You have country-specific versions of your site (different pricing, products, or regulations)
- You're expanding into a new market and want organic visibility there
- Google is serving your NZ page to Australian searchers (or vice versa)
International SEO ensures that Google shows the right version of your content to the right audience in the right country. Without it, you risk duplicate content issues, confused rankings, and users landing on pages meant for a different market.
URL Structure: The Foundation Decision
The first and most consequential decision is how you structure your international URLs. There are three main options.
Option 1: Country-Code Top-Level Domains (ccTLDs)
example.co.nz (New Zealand)
example.com.au (Australia)
example.co.uk (United Kingdom)
Pros:
- Strongest geo-targeting signal to search engines
- Users trust local domain extensions
- Clear separation between markets
Cons:
- Most expensive (separate domains to purchase and maintain)
- Domain authority doesn't transfer between domains
- Each domain builds authority from scratch
- More complex to manage technically
Best for: Large businesses with significant resources and strong brand presence in each market.
Option 2: Subdirectories
example.com/nz/ (New Zealand)
example.com/au/ (Australia)
example.com/uk/ (United Kingdom)
Pros:
- All authority consolidates on one domain
- Easiest to manage technically
- Cheapest option (one domain)
- Simple analytics setup
Cons:
- Weaker geo-targeting signal than ccTLDs
- Less obvious to users which version they're on
Best for: Most businesses. This is the recommended approach for small to medium companies expanding internationally.
Option 3: Subdomains
nz.example.com
au.example.com
uk.example.com
Pros:
- Can be hosted on different servers in different regions
- Some authority inheritance from root domain
- Easier to manage than separate domains
Cons:
- Google may treat subdomains as separate sites
- Authority splitting between subdomains
- More complex than subdirectories
Best for: Businesses that need separate hosting infrastructure per region.
The Recommendation
For most businesses: subdirectories. You get one domain building authority, simple management, and straightforward hreflang implementation. Use ccTLDs only if you have the resources to build authority on multiple domains simultaneously.
Hreflang: Telling Google Which Page Is for Which Audience
Hreflang is an HTML attribute that tells search engines which language and country a specific page targets. It's the core technical mechanism of international SEO.
How It Works
You place hreflang tags in the <head> of each page (or in your XML sitemap) to declare: "This page is for [language]-[country] audiences, and here are the equivalent pages for other audiences."
<link rel="alternate" hreflang="en-nz" href="https://example.com/nz/services/" />
<link rel="alternate" hreflang="en-au" href="https://example.com/au/services/" />
<link rel="alternate" hreflang="en-gb" href="https://example.com/uk/services/" />
<link rel="alternate" hreflang="en-us" href="https://example.com/us/services/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/services/" />
The Syntax
hreflang="[language]-[country]"
- Language: ISO 639-1 code (en, fr, de, es, zh, ja)
- Country: ISO 3166-1 Alpha 2 code (NZ, AU, GB, US, DE, FR)
- Language only:
hreflang="en"— English, no specific country - Language + country:
hreflang="en-nz"— English for New Zealand - x-default: The fallback page for users who don't match any specified version
Critical Rules
1. Every page must reference itself AND all alternates. The NZ page must include hreflang tags pointing to itself, the AU page, the UK page, and every other version.
2. Hreflang must be reciprocal. If Page A says "my AU version is Page B," then Page B must say "my NZ version is Page A." Non-reciprocal hreflang is the most common error and causes Google to ignore the tags entirely.
3. Use absolute URLs.
href="https://example.com/au/services/" — not /au/services/.
4. Always include x-default. This is your fallback for users who don't match any specific country/language version.
5. URLs must return 200 status codes. Don't point hreflang tags at pages that redirect, 404, or are noindexed.
Implementation Methods
HTML <head> tags: Best for sites with a manageable number of pages. Place the tags in the head section of each page.
XML Sitemap: Better for large sites with many pages. Add hreflang annotations to your sitemap. Easier to maintain at scale.
<url>
<loc>https://example.com/nz/services/</loc>
<xhtml:link rel="alternate" hreflang="en-nz" href="https://example.com/nz/services/" />
<xhtml:link rel="alternate" hreflang="en-au" href="https://example.com/au/services/" />
<xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/services/" />
</url>
HTTP headers: For non-HTML files (PDFs, documents). Less common.
Content Localisation vs. Translation
This is where many businesses cut corners — and pay for it.
Translation
Converting text from one language to another. Necessary for multilingual sites (English to French, Spanish, etc.).
Machine translation (Google Translate) is not enough. Google has explicitly stated that auto-translated content that isn't reviewed by humans provides a poor user experience and can be treated as spam.
If you're translating, use professional translators or high-quality AI translation with human review.
Localisation
Adapting content for a specific market's culture, norms, and expectations. This goes beyond language.
For English-speaking markets (NZ, AU, UK, US), localisation includes:
- Spelling: colour vs. color, optimise vs. optimize, organisation vs. organization
- Currency: NZD, AUD, GBP, USD — with correct symbols and formatting
- Units: metric vs. imperial
- Cultural references: Local examples, local businesses, local regulations
- Legal compliance: Privacy laws (GDPR for UK/EU, Privacy Act for NZ/AU), industry regulations
- Seasonal references: Summer in December (NZ/AU) vs. June (UK/US)
- Local phone numbers and addresses
- Pricing: Localised pricing, not just currency conversion
- Testimonials: From local customers where possible
The Duplicate Content Question
If you have English content for NZ, AU, UK, and US — all written in English — isn't that duplicate content?
No, if hreflang is implemented correctly. Hreflang tells Google these are intentional regional variations, not duplicates. Google will serve the right version to the right audience.
But: If the content is truly identical across all versions (same text, no localisation), you're wasting an opportunity. Even minor localisation — currency, local examples, spelling conventions — improves user experience and conversion rates.
Google Search Console for International SEO
International Targeting Report
Search Console shows you:
- Which hreflang errors exist on your site
- Which pages have hreflang issues
- Return tag errors (non-reciprocal tags)
Check this report regularly. Hreflang errors are silent — they don't break your site visually, but they prevent correct geo-targeting.
Performance by Country
Filter your Performance report by country to see:
- Which countries drive organic traffic
- Which queries perform in which markets
- Whether the right pages are ranking in the right countries
If your NZ page is ranking in Australia instead of your AU page, your hreflang implementation needs attention.
Technical Considerations
Server Location and CDN
Server location is a minor ranking factor for geo-targeting. More importantly, it affects page speed for users in different regions.
Solution: Use a CDN (Content Delivery Network) to serve content from servers close to users in each target market. Cloudflare, AWS CloudFront, and Fastly all handle this well.
IP-Based Redirects
Don't do this. Automatically redirecting users based on their IP address is problematic:
- Googlebot crawls primarily from the US — you might be redirecting the crawler away from your other country pages
- Users with VPNs get sent to the wrong version
- It prevents users from choosing their preferred version
Instead: Show a banner suggesting the local version ("It looks like you're in Australia. View our AU site?") but let the user choose.
Internal Linking
Within each country version, internal links should point to pages within the same country version.
Your NZ services page should link to your NZ blog posts, not your AU blog posts. Cross-linking between country versions confuses the geo-targeting signals.
XML Sitemaps
Create separate sitemaps per country version or one comprehensive sitemap with hreflang annotations. Submit all sitemaps to Search Console.
Common Hreflang Mistakes
75% of hreflang implementations contain errors. Here are the most frequent:
- Missing self-referencing tags — every page must include a hreflang tag pointing to itself
- Non-reciprocal tags — if Page A references Page B, Page B must reference Page A
- Wrong language/country codes —
en-UKis wrong. It'sen-GB(Great Britain, not United Kingdom).en-NZis correct. - Relative URLs — use absolute URLs with the full domain
- Pointing to redirected or 404 pages — all hreflang URLs must return 200
- Missing x-default — always include a fallback
- Conflicting signals — hreflang says one thing, canonical tags say another
- Mixing implementation methods — don't use both HTML tags AND sitemap annotations for the same pages
Validation Tools
- Google Search Console — International Targeting report
- Ahrefs Site Audit — hreflang validation
- Screaming Frog — crawl and validate hreflang tags
- hreflang.org — free hreflang tag generator and validator
- Merkle hreflang tag testing tool — check individual pages
The NZ-AU Scenario
For New Zealand businesses expanding to Australia (or vice versa), this is the most common international SEO scenario in the region.
Unique considerations:
- Same language but different spelling conventions (minor — both use British English)
- Different currencies (NZD vs. AUD)
- Different regulatory environments
- Different local competitors
- Cultural similarities but distinct local references
- Different Google market (google.co.nz vs. google.com.au)
Minimum localisation for NZ→AU expansion:
- Currency updated to AUD
- Phone numbers and addresses updated
- Local testimonials and case studies
- Regulatory references updated (e.g., different privacy laws, industry bodies)
- Correct hreflang implementation (en-nz and en-au)
- Google Business Profile for Australian locations
Getting Started
- Decide your URL structure (subdirectories recommended for most)
- Create your target market page structure
- Implement hreflang tags (start with HTML head tags for smaller sites)
- Localise content for each market (don't just duplicate)
- Validate hreflang with Search Console and Screaming Frog
- Submit country-specific sitemaps
- Set up Search Console properties for each country version
- Monitor Performance reports by country monthly
International SEO is detail-oriented work. One missing reciprocal tag can break geo-targeting for an entire section of your site. But done right, it opens your business to organic traffic from markets you've never reached before — without paying for a single click.