14 min read · Technical SEO · Last updated July 2026
Quick answer: International SEO requires two decisions: (1) which URL structure to use (ccTLD, subdomain, or subdirectory), and (2) how to implement hreflang to signal language/region targeting. Subdirectories are the default recommendation for most sites (consolidates authority). hreflang requires a return tag from every targeted page — missing return tags cause Google to ignore the entire hreflang cluster.
Introduction
International SEO is where technical complexity and strategic decision-making collide. A business expanding into Australia, UK, UAE, and US faces genuine architectural choices: one domain or many? Shared content or localised? One GSC property or four?
Getting the technical foundation right determines whether Google serves users in Sydney the Australian page or the global US-default page. On a site with 50,000 products across 8 markets, wrong geo-targeting can waste millions of potential impressions on the wrong audiences.
What you’ll learn:
– The difference between multiregional and multilingual SEO and why it matters for architecture
– How to choose between ccTLD, subdomain, and subdirectory for international URLs
– How hreflang works and how to implement it correctly at scale
– The most common hreflang errors and how to audit for them
Table of Contents
- Multiregional vs Multilingual: Two Different Problems
- URL Structure Options for International Sites
- hreflang: What It Is and How It Works
- Implementing hreflang Correctly
- hreflang at Scale: XML Sitemap Approach
- Common hreflang Errors
- Content Strategy for International Pages
- Setting Up International GSC
- Frequently Asked Questions
Multiregional vs Multilingual: Two Different Problems
These terms are often conflated, but they represent different technical and content challenges.
Multiregional: same language, different country targets. A site targeting both the US and Australia in English. The content may be nearly identical, with minor differences (pricing, contact details, local references). The primary SEO challenge is geo-targeting — making sure users in each country see the relevant version.
Multilingual: different languages. A site serving English, French, and Spanish speakers. The content is fundamentally different (different language). The challenge is both language targeting and geo-targeting.
Both at once: an enterprise site might serve English (US), English (AU), French (FR), French (CA), Spanish (ES), and Spanish (MX). This is the most complex scenario — six combinations of language and region.
The distinction matters for architecture:
– For multiregional (same language, different country): geo-targeting signals are your priority. URL structure and hreflang x-default tags matter most.
– For multilingual (different languages): language detection and content separation matter most. Serve the right language without relying solely on user preference settings.
– For both: you need both language and region attributes in your hreflang tags.
International URL Structure Decision Tree
Find the right URL structure for your international expansion.
URL Structure Options for International Sites
ccTLD (Country Code Top-Level Domain)
Examples: .com.au (Australia), .co.uk (UK), .co.nz (New Zealand), .com.np (Nepal), .ae (UAE)
The strongest geo-targeting signal available to Google. Country targeting is unambiguous. Users in that market may have higher trust in a local TLD.
The trade-offs: each ccTLD builds authority independently. 8 ccTLDs means 8 separate link building programmes. Management complexity scales with the number of domains. GSC verification and monitoring required per domain.
Subdomain
Examples: au.example.com, uk.example.com
Moderate geo-targeting signal. Less authority consolidation than subdirectory but more than entirely separate domains. Simpler content management than ccTLDs. Still requires separate Googlebot crawl schedules per subdomain.
Subdirectory (recommended default)
Examples: example.com/au/, example.com/uk/
Best authority consolidation. All link equity flows to the root domain. One GSC domain property covers all regional subdirectories (use geotargeting in GSC per subfolder). Easier to manage content and SEO from a single team.
GSC geotargeting: in Google Search Console, you can set a geographic target for a subdirectory. Go to Legacy Tools → International Targeting → Country, and assign a target country to each regional subdirectory. This reinforces the geo-targeting signal.
hreflang: What It Is and How It Works
hreflang is an HTML attribute that tells Google which language and/or region a page is intended for, and what the equivalent pages are in other languages/regions.
The basic structure:
<link rel="alternate" hreflang="en-AU" href="https://example.com/au/page/" />
<link rel="alternate" hreflang="en-US" href="https://example.com/us/page/" />
<link rel="alternate" hreflang="en-GB" href="https://example.com/uk/page/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/page/" />
Language codes: use ISO 639-1 two-letter codes (en, fr, de, es, zh, ja, etc.)
Region codes: use ISO 3166-1 Alpha-2 country codes (AU, US, GB, NZ, NP, AE, etc.)
Combined: en-AU means English as used in Australia. zh-Hant means Traditional Chinese (no specific country).
The x-default tag: points to the fallback page — the version shown to users whose language/region does not match any of your specific hreflang targets. Typically your main global or English-US page.
Implementing hreflang Correctly
hreflang is one of the most error-prone SEO implementations because it requires bidirectional tagging. Every page in the cluster must reference every other page in the cluster.
The return tag requirement: if Page A (English AU) hreflang-points to Page B (French FR), then Page B must also hreflang-point back to Page A. If the return tag is missing, Google ignores the entire hreflang cluster.
For a site with 5 language versions of 1,000 pages each:
– 5,000 pages total
– Each page needs 5 hreflang tags (one per language version, including itself)
– Total hreflang tags: 25,000
– Every single return tag must be correct
This is why manual implementation does not scale. You need CMS-driven, programmatic hreflang generation.
Implementation method 1: HTML head tags
<!-- en-AU page -->
<link rel="alternate" hreflang="en-AU" href="https://example.com/au/about/" />
<link rel="alternate" hreflang="en-US" href="https://example.com/us/about/" />
<link rel="alternate" hreflang="en-GB" href="https://example.com/uk/about/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/about/" />
<!-- Same tags MUST appear on en-US, en-GB, and default pages -->
Implementation method 2: HTTP header (for PDFs and non-HTML)
Link: <https://example.com/au/doc.pdf>; rel="alternate"; hreflang="en-AU",
<https://example.com/us/doc.pdf>; rel="alternate"; hreflang="en-US"
Implementation method 3: XML sitemap (preferred for large sites)
hreflang at Scale: XML Sitemap Approach
For large international sites, the XML sitemap is the most manageable place to implement hreflang. It centralises all hreflang declarations in one file rather than spreading them across thousands of HTML pages.
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xhtml="http://www.w3.org/1999/xhtml">
<url>
<loc>https://example.com/au/products/shirts/</loc>
<xhtml:link rel="alternate" hreflang="en-AU" href="https://example.com/au/products/shirts/"/>
<xhtml:link rel="alternate" hreflang="en-US" href="https://example.com/us/products/shirts/"/>
<xhtml:link rel="alternate" hreflang="en-GB" href="https://example.com/uk/products/shirts/"/>
<xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/products/shirts/"/>
</url>
<url>
<loc>https://example.com/us/products/shirts/</loc>
<xhtml:link rel="alternate" hreflang="en-AU" href="https://example.com/au/products/shirts/"/>
<xhtml:link rel="alternate" hreflang="en-US" href="https://example.com/us/products/shirts/"/>
<xhtml:link rel="alternate" hreflang="en-GB" href="https://example.com/uk/products/shirts/"/>
<xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/products/shirts/"/>
</url>
</urlset>
Each URL entry must appear once per regional version, and each must contain the complete set of hreflang tags for the cluster. This is why programmatic generation is essential — build this from your CMS or URL mapping spreadsheet.
hreflang Implementation Validator
Audit your hreflang setup against the most common error patterns.
Common hreflang Errors
Error 1: Missing return tags (most common)
If /au/page/ has hreflang pointing to /uk/page/, but /uk/page/ does not have hreflang pointing back to /au/page/, Google ignores the cluster. Screaming Frog’s hreflang report flags this as “Missing Return Tag.”
Error 2: hreflang pointing to non-200 URLs
A 301 redirect in a hreflang tag is technically invalid. Google may follow it, but it is better practice to update the tag to point directly to the final 200-status URL. After any migration, always audit your hreflang tags for redirected URLs.
Error 3: Incorrect language/region codes
Common mistakes:
– en-UK (should be en-GB — Great Britain, not UK)
– zh-CHT (should be zh-Hant for Traditional Chinese)
– en-AUS (should be en-AU)
– en for all English variants (correct, but less specific — cannot differentiate AU from US with just en)
Error 4: hreflang on paginated pages without proper handling
If /au/products/page/2/ has hreflang tags, those tags must point to the equivalent paginated page in each language version — not to the category root. A common mistake is hreflang pointing page 2 in English to page 1 in French.
Error 5: Cross-region canonical conflicts
If your Australian page has rel="canonical" pointing to your US page (perhaps to consolidate content), the hreflang on the AU page is ignored — Google treats it as a duplicate of the US page. Canonical tags take precedence over hreflang when they conflict. Each regional page should canonical to itself.
Key takeaway: Run your hreflang through Screaming Frog’s hreflang audit report after every template change. A single broken return tag can silently invalidate hundreds of pages’ geo-targeting.
Content Strategy for International Pages
URL structure and hreflang handle the technical signals. Content handles the user experience and relevance signals.
Truly localised vs translated: translation alone is not enough for competitive markets. A page translated word-for-word from US English to Australian English is technically multilingual but practically the same content. Genuine localisation includes:
– Local terminology (car “boot” in AU/UK, “trunk” in US)
– Local pricing and currency
– Local regulatory or compliance references
– Local testimonials and case studies
– Local contact information and business hours
The thin content risk: international sites with 10+ regional versions and identical content across all versions are at risk of being treated as duplicate content. Make sure each regional version has at least some genuinely unique content elements — even if the core content is the same.
Content gaps by market: keyword research in each target market often reveals different search behaviours. Australians searching for “home loan” vs Americans searching for “mortgage” vs Brits searching for “mortgage” — same intent, different terminology. Research and write for each market’s actual search language.
Setting Up International GSC
Domain property vs URL prefix property:
– Domain property (example.com): covers the entire domain including all subdomains and protocols (http, https). Ideal for sites with subdomains.
– URL prefix property (https://example.com/): covers only the exact protocol and domain specified. Use separate properties for each regional subdirectory to enable geotargeting.
Geotargeting in GSC:
For subdirectory-based international sites, set a geotarget per subdirectory:
1. Add a URL prefix property for each regional subdirectory (e.g., https://example.com/au/)
2. Go to Legacy Tools → International Targeting → Country
3. Select the target country for that property
This gives Google an additional signal that /au/ targets Australia — supplementing your hreflang implementation.
Separate GSC properties for ccTLDs:
Each ccTLD requires its own GSC property verification and monitoring. Set up coverage monitoring, keyword tracking, and Core Web Vitals monitoring per property.
Frequently Asked Questions
Do I need hreflang if all my international pages are in English?
Yes, if you are targeting different English-speaking regions. en-AU and en-US tell Google which English page to serve to which audience. Without hreflang, Google may serve your AU users the US page or vice versa, especially if both pages have similar content.
How does Google determine which version to show a user if hreflang is correct?
Google uses hreflang as a strong signal, combined with the user’s browser language settings, IP address, and search query context. hreflang is not a directive — it is a signal. Google may occasionally override it, especially if one version has significantly more authority than others.
Can I use hreflang with pagination?
Yes, but every paginated page in each language cluster must have complete hreflang tags pointing to all equivalent paginated pages. This is one of the most complex hreflang implementations. For very large paginated catalogues, the sitemap method is more manageable than HTML tags.
What happens if I have hreflang errors — will my rankings drop?
hreflang errors cause Google to ignore the cluster, which means users in the wrong region may see the wrong version — potentially lower CTR or conversion rate. They do not typically cause ranking penalties, but they cause geo-targeting to fail, which means traffic goes to the wrong page or is split across pages when it should be consolidated.
How do I handle content that only exists in one market?
If a page only exists for Australia (no US equivalent), you do not need hreflang on that page. Add x-default if you have a global fallback, but do not create empty or thin redirect pages in other markets just to satisfy hreflang symmetry. Hreflang is only necessary for pages with genuine regional/language variants.
Conclusion
International SEO’s technical foundation — URL structure, hreflang, and GSC setup — determines whether Google serves users the right version of your site. The implementation details matter: a missing return tag, a wrong ISO code, or a canonical conflict can silently break geo-targeting across hundreds of pages.
The return on getting this right is substantial. A properly geo-targeted site in five markets serves each market the locally relevant content, earns better click-through rates, and accumulates country-specific relevance signals that improve rankings in each market over time.
Let Ignited Nepal Handle This
Our team implements international SEO for clients serving Australia, UK, UAE, US, Nepal, and other markets — from URL structure decisions to hreflang implementation at scale to GSC setup and monitoring.
→ Request a Free Technical SEO Audit
Written by the Ignited Nepal SEO team. We build organic search systems for businesses across Nepal, Australia, UAE, USA, UK, and beyond. ignitednepal.com