Hreflang has a reputation as the hardest tag in SEO, and plenty of businesses either fear it or add it to sites that never needed it. The truth is simpler on both counts. The tag exists for exactly one situation: your site publishes alternate versions of the same page for different languages or regions, and you want Google to show each searcher the right one. This guide explains what hreflang does, a plain test for whether you need it, how to implement it without the classic errors, and why most Australian businesses can happily skip it.
What hreflang actually does
Hreflang is an annotation, added as link tags in a page's head, in HTTP headers or in a sitemap, that tells Google which language and region each version of a page is meant for, and where all the other versions live. When a page has an Australian, a US and a German edition, the hreflang set connects the three, and Google uses it to swap the right URL into results for each searcher: the German page for searchers in Germany, the Australian page for searchers here.
Two boundaries keep expectations honest. First, hreflang is about serving the right version, not about ranking harder; Google describes it as a signal for language targeting, not a ranking boost. Think of it as language targeting for the result slot, not a lever on the ranking itself. Second, it is a hint rather than a directive, so Google can ignore annotations that conflict with other signals. It also does not solve duplication by itself: localised alternates are expected to exist, and hreflang is precisely how you tell Google they are deliberate variants rather than accidental duplicate content.
Do you need hreflang? A simple test
Ask one question: does the same page on your site exist in more than one language, or in more than one regional edition? If the answer is no, you do not need hreflang, full stop. A Melbourne trades business with one English website serving all of Australia has nothing to annotate. Adding the tags to a single-version site does nothing except create maintenance work. The lang attribute in your HTML and ordinary local signals already tell Google what language a page is in; the annotations only add value once alternates exist to point at.
If the answer is yes, the tag earns its keep. That covers translated sites, English in multiple regions, think an Australian, a US and a UK store with different currencies, spelling and shipping, and mixed setups where some pages are translated and others are not. Same-language regional variants are the sneaky case: without hreflang, Google can pick the US page for Australian searchers, showing prices in dollars you do not sell in. This is bread-and-butter enterprise SEO territory, but any store expanding overseas hits it eventually, often during a site migration that splits one domain into regional folders.
How the codes work
Each value is a language code, optionally followed by a region code: en for English anywhere, en-AU for English in Australia, en-US for the United States, de-DE for German in Germany. The language part uses ISO 639-1 codes and the region part uses ISO 3166-1 Alpha 2 codes, and the region is always optional. There is one special value, x-default, which marks the fallback page for searchers who match none of your versions; a global homepage or country selector is the usual choice.
Precision beats ambition here. Only annotate versions that genuinely differ for the audiences involved; en-AU and en-NZ pages that are word-for-word identical add complexity without helping anyone. And resist inventing codes: the values are checked against the ISO lists, and anything unrecognised is simply dropped.
The classic trap: hreflang must be reciprocal. If your Australian page points to the US page, the US page must point back. Google says annotations without these return links can be ignored, which is why one-way tags are the most common reason the setup silently fails.
Three ways to implement it
Google supports three placements, and you should pick one rather than mixing them. Link elements in the HTML head are the simplest and suit smaller sites: one line per alternate version, on every page in the set, including a self-reference. HTTP headers do the same job for non-HTML files such as PDFs. And an XML sitemap can carry the annotations for every URL centrally, which is far easier to maintain once a site has thousands of pages, because each new market means regenerating one file instead of editing every template.
Whichever route you take, each version should also keep its own self-referencing canonical tag. Pointing every regional variant's canonical at one master version tells Google to index only that one, which quietly undoes the international setup; hreflang and canonical tags have to agree. On international SEO projects, this pairing is where most of the debugging time goes.
Testing is not optional at this scale. A desktop crawler such as Screaming Frog will report missing return links, invalid codes and non-indexable alternates across the whole set in one crawl, and Search Console's Pages report will show whether the intended version of each page is the one being indexed. Re-run the checks after any template or platform change, because that is when sets quietly break.
The mistakes that break it
The failure patterns are consistent. Missing return links, as above. Invalid codes, with en-UK instead of en-GB the perennial favourite, since region codes follow the ISO country list rather than intuition. Annotating pages that redirect, 404 or carry noindex, so the alternate Google is sent to cannot be indexed at all. Forgetting x-default, which leaves unmatched searchers to luck. And automatically redirecting visitors by IP address instead of letting the annotations work, which Google advises against because it hides your variants from crawlers and users alike.
None of this is hard once it is systematic, but it punishes ad-hoc edits: one template change can strip the tags from a whole section without anyone noticing. If your site serves more than one market, an international-aware technical SEO review will verify the whole set, return links, codes and canonicals together, in one pass.
Selling into more than one country? We build and audit hreflang setups as part of our technical work for multi-market sites. Talk to us before you launch the next region, not after the traffic goes sideways.
