International SEO: Hreflang for Multi-Country English Sites
Hreflang tells Google which version of a page to show searchers in different countries or languages, using values like `en-US`, `en-GB`, `en-CA` and `en-AU`. For sites targeting multiple English-speaking markets with the same language but different regions, the three requirements that matter most are: self-referencing canonicals on every page, fully reciprocal tags across the whole cluster, and genuinely differentiated content per market — get any one of these wrong and the setup fails silently.
Choosing a URL structure
Country subfolders (`/us/`, `/uk/`, `/ca/`, `/au/`) — consolidates domain authority on one site, the most operationally efficient option for a new domain without strong local entities in each market. This is what we use ourselves.
ccTLDs (`.com`, `.co.uk`, `.ca`, `.com.au`) — the strongest local-trust signal, but starts each domain's authority at zero and multiplies hosting, SSL and maintenance overhead.
Subdomains (`us.example.com`) — a middle option Google generally treats similarly to subfolders for authority-sharing purposes, though subfolders are typically simpler to manage.
For most new multi-country sites, subfolders are the right default — but the execution details below matter more than the structural choice itself.
The five rules that actually matter
1. Self-referencing canonicals. Every regional page must canonical to itself. If `/uk/pricing/` canonicals to `/us/pricing/`, you're telling Google to never index the UK version — a mistake that silently removes half your site from search.
2. Fully reciprocal hreflang. If `/us/x/` lists `/uk/x/` as an alternate, `/uk/x/` must list `/us/x/` back. One-way hreflang tags are functionally ignored by Google.
3. Valid language-region codes. Use `en-GB`, not `gb`. A country code without a language prefix is invalid and provides no benefit.
4. Include x-default. This tells Google (and other search engines) which version to show a searcher who doesn't match any of your specified region/language combinations — required if you have a global or unmatched-market fallback.
5. Only reference indexable, 200-status pages. Never hreflang to a redirect, a noindex page, or a broken URL — Google will discard the whole cluster's tags if the target isn't cleanly indexable.
The mistake that undoes everything else
Getting hreflang perfectly correct doesn't help if the four country pages contain near-identical content with only the currency symbol changed. Google's own guidance is explicit that hreflang doesn't fix duplicate content — it just tells Google which duplicate to consider showing to which searcher, and if the underlying content is genuinely thin or repetitive, index quality systems can still suppress most of the cluster regardless of correct tagging. Real differentiation — local case examples, region-specific regulatory notes, genuinely different pricing context — is what makes the technical setup worth doing at all.
A minimal example
```html <!-- On /us/pricing/ --> <link rel="canonical" href="https://example.com/us/pricing/" /> <link rel="alternate" hreflang="en-US" href="https://example.com/us/pricing/" /> <link rel="alternate" hreflang="en-GB" href="https://example.com/uk/pricing/" /> <link rel="alternate" hreflang="en-CA" href="https://example.com/ca/pricing/" /> <link rel="alternate" hreflang="en-AU" href="https://example.com/au/pricing/" /> <link rel="alternate" hreflang="x-default" href="https://example.com/pricing/" /> ```
Each of the other three pages needs the mirror image of this block, each with its own self-referencing canonical.
Search Console setup
Set up each subfolder as its own property (or use directory-level configuration within one property) so you can read performance and set any manual geotargeting per market separately, rather than blended together.
See this in practice on our own site →
Written technical findings by senior strategists. Published transparent pricing.