What Is Hreflang?
Hreflang is an HTML link element attribute used in the head section of a webpage. It signals to search engines the language and, optionally, the geographic region that a page targets. The attribute uses ISO 639-1 language codes combined with ISO 3166-1 country codes.
For example, a page targeting South African English would use hreflang="en-ZA", while a page targeting British English would use hreflang="en-GB".
When a website has pages in multiple languages or regional variants, hreflang annotations help Google understand the relationship between those pages. Without hreflang, Google might treat translated or locally adapted pages as duplicate content. This can harm the SEO performance of both versions. With correct hreflang implementation, Google indexes each regional page and serves it to users in its intended market.
Hreflang can be implemented in three ways: directly in the HTML head as link elements, within the page's HTTP response headers, or in an XML sitemap. The HTML head approach is the most common and easiest to verify.
Each annotated page must include a reciprocal hreflang tag pointing back to every alternate version, including itself. Missing or unreciprocated tags are the most frequent implementation error.
South African businesses operating across multiple African markets or targeting both local and international customers should pay careful attention to hreflang. Take a South African e-commerce site that also serves Zimbabwean, Kenyan, or UK customers. Correctly implemented hreflang makes sure each market receives the right pricing, currency, and localised content in search results.
Hreflang In Practice
Consider a South African travel company that offers tour packages. They have an English site for South African customers and a separate Dutch site for European visitors. The South African homepage would include hreflang tags pointing to the Dutch version, and vice versa. It would also add an x-default tag to mark the fallback page for users in unsupported regions.
When a user in the Netherlands searches for African safari tours, Google reads the hreflang annotations and serves the Dutch version of the site in Netherlands search results. A South African user searching the same query sees the en-ZA version.
Without hreflang, Google might show the wrong version to both audiences, or merge both pages into a single result. Either way, the site reaches fewer people. Proper international SEO through hreflang is the foundation for any South African business expanding its digital reach into multiple markets.
What hreflang does
Hreflang is an HTML attribute (and equivalent sitemap or header signal) that tells search engines which language and, optionally, regional version of a page to show to which users, so that people searching in different languages or countries are served the appropriate version of your content. If you have the same page in multiple languages, or variants tailored to different countries (such as English for South Africa versus English for the United Kingdom), hreflang annotations link those versions together and specify the language and region each targets, helping search engines show the right one to the right user and avoid treating the variants as duplicate content. Each version references all the others (including itself) with hreflang values indicating language (and optionally region), forming a set of mutually-referencing pages. Hreflang is important for multilingual and multiregional sites because, without it, search engines may show the wrong-language version to a user, or may struggle to understand that the variants are alternatives rather than duplicates. It is a technical SEO signal specific to sites serving content in multiple languages or regional variants, ensuring the correct localised version reaches the correct audience.
Implementing hreflang correctly
Hreflang is powerful for multilingual and multiregional sites but is notoriously easy to get wrong, so correct implementation matters. The core rules are that annotations must be reciprocal, if page A points to page B as an alternative, B must point back to A, and that each set of alternatives should reference every version including itself, using correct language codes (and region codes where used) in the standard format. The values specify language (for example, en for English) and optionally region (for example, en-za for English targeting South Africa), and must use valid codes. Common mistakes that break hreflang include non-reciprocal or missing return links, incorrect or invented language and region codes, pointing to non-canonical or redirecting URLs, and conflicts with canonical tags. Because of this fiddliness, implementation should be checked with hreflang validation tools and Google Search Console's reporting, which flag errors. Hreflang can be delivered in the HTML head, in the XML sitemap, or via HTTP headers, whichever suits the site, applied consistently. It is worth stressing that hreflang is only needed when you genuinely have multiple language or regional versions, a single-language site does not need it, and adding it without real alternatives creates confusion rather than benefit. For sites that do serve multiple versions, careful, validated hreflang implementation ensures each user is served the correct localised page, which is its whole purpose.
FAQ
Does a South African website targeting only English users need hreflang?
If your website only targets South African English speakers and has no regional variants, hreflang is not required. However, if you have separate pages for en-ZA and en-GB audiences, or pages in Afrikaans or Zulu, hreflang tags help Google serve the correct version to each user.
What happens if hreflang tags are incorrect?
Incorrect hreflang implementation can lead to the wrong regional page appearing in search results, duplicate content signals, and reduced organic traffic from your target markets. Google may ignore malformed hreflang annotations entirely and revert to its own geo-targeting judgements.