Hreflang for US, UK, Canada and Australia Sites

If your business sells into the United States, the United Kingdom, Canada and Australia, you may be running separate pages or sites for each market in the same language. Hreflang annotations tell Google which version is intended for which country, so a UK searcher sees prices in pounds and British spelling while a US searcher sees the US version. Without hreflang, Google may show the wrong version, or treat the pages as duplicates and index only one.

Hreflang is only needed when you genuinely have localised versions. Many businesses serving several English-speaking countries are better off with a single international site. This guide covers both the decision and the implementation.

Do you actually need separate country versions?

Separate versions make sense when the content genuinely differs: prices and currencies, product availability, shipping, legal requirements, contact details, regulations or terminology that changes the meaning of the page. An ecommerce store with different pricing and stock by country is a clear case.

They make less sense when the only difference is spelling, or when you would copy the same pages four times with minor edits. Each country version then needs its own links, maintenance and attention, and thin near-duplicates rarely perform well. A single site in one variety of English, with country-specific information where needed, is often more effective for service businesses and SaaS companies.

How hreflang works

Each localised page lists all of its alternates, including itself, using language and optional country codes. For English markets, typical values are:

• en-us for the United States
• en-gb for the United Kingdom (not en-uk, which is invalid)
• en-ca for Canada
• en-au for Australia
• x-default for the fallback version shown to users who match none of the above

Language codes use ISO 639-1 and country codes use ISO 3166-1 alpha-2. A country code cannot be used on its own; “gb” without “en-” is not valid.

Implementation methods

Hreflang can be added in three places. Choose one method and use it consistently.

HTML link tags in the page head. The most common method. Each page includes a set of link elements pointing to every alternate.

HTTP headers. Used for non-HTML files such as PDFs.

XML sitemaps. Useful for large sites, since annotations can be managed centrally without changing page templates.

Rules that cause most errors

Return links are required. If the US page points to the UK page, the UK page must point back to the US page. Missing return links cause Google to ignore the annotation.

Each page must reference itself. Every version should include a self-referencing hreflang entry.

Annotations must point to canonical, indexable URLs. Pointing hreflang at redirected, noindexed or canonicalised URLs breaks the set. Each country page should usually have a self-referencing canonical, not a canonical pointing to another country’s version.

Use consistent URL formats. Mixing trailing slashes, HTTP and HTTPS, or www variants creates mismatches.

Do not auto-redirect by IP. Forcing visitors to a country version based on location can stop Googlebot, which mostly crawls from the US, from reaching other versions. A suggestion banner that lets users switch is safer.

URL structure for country versions

The three common options are country-code domains (example.co.uk), subdirectories (example.com/uk/) and subdomains (uk.example.com). Subdirectories are usually the simplest to manage and allow all versions to benefit from the main domain’s authority. Country-code domains send a strong local signal but require building authority for each domain separately.

Localise properly, not superficially

Hreflang tells Google which page to show, but the page still needs to earn its ranking. Localisation should include currency, pricing, spelling, terminology, local contact details, relevant regulations and examples that make sense to that market. “Zip code” versus “postcode” or “cell phone” versus “mobile” may seem small, but they signal whether a page was written for the reader.

Checking your setup

Crawlers such as Screaming Frog and Sitebulb can audit hreflang for missing return links, invalid codes and non-canonical targets. Search Console no longer has the old International Targeting report, so third-party tools and manual checks are the main way to validate. Test a sample of pages after any template change, because hreflang errors often appear site-wide from a single change.

Expanding into new English-speaking markets

Hreflang solves a specific problem: showing the right country version of a page. It works when the versions are genuinely different and correctly linked, and it creates maintenance work that should be weighed against the benefit.

If you are planning to expand from one English-speaking market into others, or your existing country versions are cannibalising each other, our technical SEO service can help decide on the right structure and implement hreflang correctly.