Hreflang Tags Explained: A Practical Guide for Multi-Region Australian Sites

Category: Technical SEO

Hreflang is the HTML attribute that tells Google which version of a page to show to which audience. For Australian businesses serving New Zealand, the UK, the US or non-English-speaking markets from the same domain or a network of domains, hreflang is the difference between Google showing the right page to the right user and showing the wrong country’s page to everyone. This guide covers what hreflang is, when to use it, the three implementation methods, the common mistakes that wreck implementations, and the simplest path for an Australian site.

What Is Hreflang?

Hreflang is an HTML attribute (rel="alternate" hreflang="...") that tells search engines a page has alternate versions for different languages or regions. When Google indexes a site with proper hreflang, it serves the right version based on the user’s language and country. So an AU shopper sees the .com.au site with AUD pricing, an NZ shopper sees the .co.nz site with NZD, and a UK shopper sees the .co.uk site with GBP, even if they search the same product.

Without hreflang, Google guesses, and the guesses are often wrong. Common symptoms: AU site ranking in NZ but showing AUD prices, US shoppers landing on UK pages, or worse, multiple country versions cannibalising each other because Google sees them as duplicate content.

When Do You Need Hreflang?

You need hreflang when any of the following are true:

  • The site serves multiple countries with the same language (AU + NZ + UK + US English).
  • The site has translated versions for non-English speakers.
  • The site has region-specific landing pages (Australian shipping rates, NZ contact details).
  • You operate multiple TLDs (.com.au, .co.nz, .co.uk) with similar content.

You do not need hreflang if you serve a single country and language. For most Australian SMBs targeting AU only, hreflang is irrelevant: the country targeting in Search Console plus the .com.au TLD handle it.

How Hreflang Works

Each version of a page references itself and every other language/region version. The references use ISO 639-1 language codes (en, fr, ja) optionally combined with ISO 3166-1 Alpha 2 country codes (AU, NZ, GB, US). Examples for an AU + NZ + UK English site:

  • hreflang="en-AU": English for Australia
  • hreflang="en-NZ": English for New Zealand
  • hreflang="en-GB": English for United Kingdom
  • hreflang="x-default": fallback when no language/region matches

Per Google’s international SEO documentation, the x-default tag is critical: it tells Google which page to show when no specific match exists. Most AU-first sites set en-AU as both en-AU and x-default.

The Three Implementation Methods

There are three ways to deliver hreflang to Google, in descending order of practicality for most sites:

  • HTML <link> tags in the <head>: most common method. Each page contains a link tag for itself and every alternate version. Works well for static or small dynamic sites. Becomes unwieldy on sites with hundreds of pages and many regions.
  • HTTP headers: useful for non-HTML files (PDFs) and sites with limited HTML editing access. Same logical structure as HTML tags, delivered via HTTP response headers.
  • XML sitemap: the recommended method for large multi-region sites. One sitemap entry per URL with nested xhtml:link children listing every alternate. Easier to maintain centrally and does not bloat page HTML.

For most AU sites of fewer than 200 pages with two or three region variants, HTML link tags in the head are the simplest and most reliable. For ecommerce or large content sites, the XML sitemap approach is the only sustainable option.

Hreflang Example for an Australian Site

For a service business with an Australian primary site and a New Zealand sister site, each page on each site needs the following inside the <head>:

<link rel="alternate" hreflang="en-AU" href="https://www.example.com.au/services/widgets/" />
<link rel="alternate" hreflang="en-NZ" href="https://www.example.co.nz/services/widgets/" />
<link rel="alternate" hreflang="x-default" href="https://www.example.com.au/services/widgets/" />

Both pages need both references. The AU page references itself and the NZ version; the NZ page references itself and the AU version. This is called the “return tag” requirement and is one of the most common implementation failures.

The Five Most Common Hreflang Errors

  • Missing return tags. Page A references Page B, but Page B does not reference Page A back. Google ignores the entire relationship. This is the single most common hreflang implementation failure.
  • Incorrect language or country codes. Using “en-UK” instead of “en-GB” (United Kingdom is GB in ISO 3166), “uk” instead of “ua” for Ukrainian, or invalid combinations.
  • Hreflang pointing to non-200 URLs. Referencing a page that 404s or redirects breaks the relationship.
  • Hreflang conflicting with canonical tags. Canonical points to one URL, hreflang references the same URL under a different region, so Google picks one and ignores the other.
  • Forgetting x-default. Without x-default, users in countries not specifically targeted get unpredictable results.

Validate every hreflang implementation with the Aleyda Solis hreflang generator and verify in Google Search Console under the International Targeting report.

Hreflang and Canonical Tags: How They Work Together

Each language/region version should self-canonical (its canonical tag points to itself). The hreflang tags then reference all the alternate versions. Common mistake: canonicalising every regional version to the primary AU version, then adding hreflang. Google treats that as “all these pages are duplicates of the AU one”, which defeats the purpose of having regional sites. Self-canonical + bidirectional hreflang is the correct pattern.

Hreflang on Shopify, WordPress and Other Platforms

Implementation differs by platform:

  • Shopify Markets handles hreflang automatically when you enable multiple markets. The native implementation is generally clean and correct.
  • WordPress with WPML, Polylang or TranslatePress generates hreflang automatically for translated content. For multi-region sites on separate WP installs, use plugins like Hreflang Tags Lite or manual implementation.
  • Custom sites require developer implementation, ideally via XML sitemap for maintainability.

When Not to Use Hreflang

  • If you only serve one country, do not add hreflang. It is unnecessary and adds maintenance overhead.
  • If your country variants have very different content (different products, services, branding), hreflang may not be the right pattern: separate domains targeted individually in Search Console may serve better.
  • If your translations are machine-generated and low quality, fix the translation quality before adding hreflang. Google may treat low-quality translations as thin content regardless of hreflang.

Frequently Asked Questions

What is hreflang used for?

Hreflang tells search engines which version of a page to serve to users in different countries or who speak different languages. Without it, search engines may serve the wrong country version, causing pricing, shipping or language mismatches.

Does Google still use hreflang in 2026?

Yes. Hreflang remains the official signal Google uses to understand multi-region site relationships. Bing also uses it. AI search engines vary in how they use hreflang, but Google’s reliance has not changed.

Do I need hreflang if my site only targets Australia?

No. Hreflang is only needed if your site has multiple language or country variants. AU-only sites should use the .com.au TLD plus country targeting in Search Console.

What does “en-AU” mean in hreflang?

It means “English language, Australia region”. The first part is the ISO 639-1 language code (en for English), the second is the ISO 3166-1 Alpha 2 country code (AU for Australia). For language only without region, use just “en”.

Can I use hreflang on a single-domain site with country subfolders?

Yes. Hreflang works equally well with separate ccTLDs (.com.au, .co.nz), subdomains (au.example.com, nz.example.com), or subfolders (example.com/au/, example.com/nz/). The choice between these structures is a separate decision driven by branding, hosting and authority considerations.

What is the x-default hreflang tag?

x-default specifies the fallback page Google should serve when no other hreflang version matches the user’s language and country. Always include x-default, because without it users in unspecified regions get unpredictable results.

Need Multi-Region SEO Help?

Hreflang is one piece of international SEO; the bigger picture includes domain structure, currency handling, country-specific content, and Search Console region targeting. Rank Haus has implemented hreflang and multi-region setups for AU businesses serving NZ, UK and US markets. Get in touch for an international SEO consultation.

Our Services

Similar Posts