The hreflang basics in one sentence: hreflang is an annotation that tells Google which pages are localised versions of the same content, so it can show each searcher the right version. It belongs in your wider SEO in South Africa plan only when you actually run more than one version of a page, for example a UK-priced copy of your store or an Afrikaans translation of your service pages.

If you are still deciding whether to sell abroad at all, start with selling internationally from South Africa. This post covers hreflang basics for exporters, the narrow technical piece that comes after that decision: when the tags are needed, how they are written, the one condition under which Google's documentation says they are ignored, and the requirements around it.

Quick Answer

The hreflang basics are simple: each localised version of a page lists itself and every other version, using a language code (en) or a language-plus-country code (en-ZA, en-GB), with absolute URLs. If two pages do not point at each other, Google's documentation says the tags are ignored. A single English site selling to South Africa only does not need them.

Planning a UK or Australian version of your site?

Send us the URLs you plan to duplicate and we will tell you whether they need these tags and which method fits.

Send us your site plan

Hreflang Basics: What the Annotation Does and Does Not Do

Hreflang is a signal that links equivalent pages across languages or regions, and its job is to swap the URL Google shows, not to lift a page's position. Google's documentation on localised versions describes it as a way to tell Google about variations of your content so that it can understand the pages are localised variations of the same content. It says Google Search then points users to the most appropriate version by language or region.

Two misunderstandings cost owners time. First, hreflang does not tell Google what language a page is in. Google says it does not use hreflang or the HTML lang attribute to detect page language and relies on algorithms reading the visible content instead. So the tag cannot rescue a page that is half translated.

Second, hreflang does not replace translation. Google's multi-regional guidance warns against translating only the boilerplate of a page while the bulk of the content stays in one language. A page with a translated menu and an English body gives the searcher a poor result, tags or no tags.

Key Takeaway

Hreflang connects pages that already exist as genuine localised versions. It does not detect language, translate anything or create a ranking advantage on its own. It tells Google which of your equivalent pages to show to which searcher.

Which of Your Sites Actually Needs These Tags?

A site needs hreflang when it publishes more than one version of the same page for different languages or regions. Google's wording is direct: if you have multiple versions of a page for different languages or regions, tell Google about them. It names two cases, content with small regional variations in a single language, and content fully translated into several languages.

The table below turns that into the situations a South African operator is likely to be in. The verdict column is our reading of Google's two cases, not a Google ruling on each scenario.

Your situationNeeds the tags?Why
One English site, sold to South African customers onlyNoThere is only one version of each page, so nothing to connect
One English site that also ships abroad, same pages for everyoneNoStill one version of each page; the choice is whether to build a second version
A separate English version for the UK or Australia with its own prices, spelling and shipping termsYesThis is the "small regional variations in a single language" case in Google's list
Service pages translated in full into another languageYesThis is the "fully translated" case
Same content on a .co.za and a .com domainYesTwo domains carrying near-identical pages are exactly what the tags connect
Menu and buttons translated, body text still EnglishFix the content firstGoogle warns against translating only boilerplate; the tags do not repair a half-translated page

The expensive mistake is not forgetting the tags. It is building a second version of the site to chase export demand you have not tested. The tags are a small job once a version exists, so let the business case for the version come first.

How Are Language and Country Codes Written?

Hreflang codes are a language code, optionally followed by a country code, and the language always comes first. Google specifies the language in ISO 639-1 format and the optional region in ISO 3166-1 Alpha 2 format, giving values such as en-GB or de-CH. A region on its own is invalid: Belgium is written de-BE, nl-BE or fr-BE, never just be.

ValueMeaningUse it for
en-ZAEnglish, South AfricaYour South African pages
en-GBEnglish, United KingdomA UK-specific copy with its own prices and delivery terms
en-USEnglish, United StatesA US-specific copy
enEnglish, any countryA general English page for everyone not matched above
x-defaultNo other value matches the visitorOptional: a language selector page or your general fallback, which Google recommends for unmatched visitors

Google says the value is case-insensitive, though uppercase region codes follow the ISO convention. Region spelling still matters. Google ignores codes reserved for something else, and its own example is UK, so en-UK would not target the United Kingdom. The correct ISO region is GB, which gives en-GB.

Where Do You Put the Tags: HTML, Header or Sitemap?

You can declare the tags in the page's HTML head, in HTTP headers, or in your XML sitemap, and Google says the three methods are equivalent. Choose by what your platform makes easy, not by what looks most technical.

  • HTML head. A link element per version in every page. It suits small sites and platforms that generate the tags for you.
  • HTTP header. A Link header sent with the response. It is set on the server rather than in the page. In our view, most small business sites will not need it.
  • XML sitemap. The same links inside the sitemap entries. It keeps the maintenance in one file, which matters once the catalogue grows.

A South African store with South African, UK and US versions of a product page would put these four lines in the head of all three pages. The domain is a placeholder:

<link rel="alternate" hreflang="en-ZA" href="https://example.co.za/product/" />
<link rel="alternate" hreflang="en-GB" href="https://example.co.za/en-gb/product/" />
<link rel="alternate" hreflang="en-US" href="https://example.co.za/en-us/product/" />
<link rel="alternate" hreflang="x-default" href="https://example.co.za/product/" />

Why the method matters: the tag arithmetic

Because each version must list itself and all the others, the number of lines grows faster than the number of markets. The sample above has three versions plus x-default, which means 4 tags on each page, so 3 pages x 4 tags = 12 lines for one product. A fourth version makes 5 tags on each of 4 pages, which is 20 lines, 8 more than before. On an assumed catalogue of 100 products, that is 1,200 lines becoming 2,000, an extra 800. Hand-edited tags on that scale are where mistakes creep in, and that is the argument for sitemap or platform-generated tags.

Not sure which method suits your platform?

Tell us what the site runs on and how many versions you plan, and we will recommend where the tags should live.

Ask which method fits

What Makes a Tag Set Valid or Ignored?

Google documents one condition under which the tags are ignored, a missing return link, and states two requirements for a valid set: every version lists itself, and every URL is fully qualified. A fourth item, the fallback value, is recommended rather than required. If two pages do not both point to each other, Google's documentation says the tags will be ignored.

  1. Hreflang return links (the documented ignore condition). If the South African page points to the UK page, the UK page must point back. A one-way pointer is an easy mistake when a second version is built later and the original pages are never edited.
  2. Self-reference (required). Google says each version must list itself as well as all other versions. In the code above, the en-ZA page carries an en-ZA line pointing at itself.
  3. Absolute URLs (required). Use the full address with https and the domain. Google's documentation asks for fully qualified URLs, so a relative path such as /en-gb/product/ does not meet it.
  4. x-default (optional fallback). Google says this value is used when no other language or region matches the visitor's browser setting, and recommends it for the fallback page. It was designed for language selector pages, and it is a fallback, not a version.

One related rule is about behaviour, not tags. Google advises against automatically redirecting users from one language version to another, because that can stop users and search engines seeing every version. Offer a visible selector instead of redirecting by guessed location.

Diagnosing a version that does not show

When the wrong version appears for a searcher, treat it as a set of hypotheses to check, not one cause. Several of the checks below are practitioner habits rather than Google-documented steps.

SymptomPossible causesCheck that tells them apart
UK searchers still see your South African pageA missing return link or a code that Google ignores (documented); the new page not yet crawled or indexed (our hypothesis, not a Google statement); the two pages not being close enough equivalents (our hypothesis)Open both pages, view source, and confirm each lists itself and the other with correct codes; then confirm the new page is reachable and indexed
Tags present but a version seems to be droppedRelative URLs (documented requirement); a version that redirects elsewhere (our hypothesis); a platform and a plugin both writing tags (Shopify documents the duplicate-tag risk)Check every href is a full address that loads directly, and look for duplicate hreflang blocks in the source
Traffic from one country dipped after launchSeasonality; a change in the mix of queries; the tags working as intended and moving visitors to the other versionCompare the same weeks last year and the same queries, and check which version those visitors now land on

Key Takeaway

The hreflang basics checklist has four items to check on every version: each other version points back (the documented ignore condition), it lists itself, every address is absolute, and an optional x-default fallback is set if you have a selector or general page. When a market is added later, re-check the existing pages as well as the new one.

What Does Shopify Markets Do About Hreflang?

Shopify generates hreflang tags for you when a market has its own domain, subdomain or subfolder, so a store on that platform usually does not need hand-written tags. Shopify's help centre says the tags are generated automatically from your market and language configuration, and only for markets that have a distinct domain, subdomain or subfolder.

The warning from the same page is the part owners miss: to avoid duplicate tags, use either your own tags or the automatic ones, not both. If an earlier developer or app already wrote hreflang into the theme, check for double blocks before adding a second market. Our Shopify SEO guide for South Africa covers the wider store settings, and the translation workload behind a second language is priced in translation services cost in South Africa.

Where the version lives also shapes the work. Google's URL guidance lists subdirectories as easy to set up with low maintenance, and subdomains as easy to set up, while country-specific domains give clear geotargeting but are expensive and limited to a single country. For a small exporter, our own judgement, not a Google recommendation, is that a subfolder is the lighter option, though the ccTLD route can make sense if you already own the domain.

For international hreflang basics on Shopify, that choice also decides whether the platform writes the tags for you. Broader market-selection trade-offs sit in our guide to international SEO from South Africa.

Why South African Businesses Choose Growth Pulse Media

Growth Pulse Media is a Johannesburg agency run by Dirk van Greuning, who built and scaled a large South African ecommerce business before founding it. All work is executed in-house and the client load is limited, so a senior person looks at your site. We are a Registered Shopify Partner.

If you want someone to check your setup before you commit to a second version, our SEO service in South Africa starts with a free audit or consultation. No obligation, and we will get back to you within 24 hours.

Who This Is Not For

This guide covers hreflang basics for SMEs, so it is not for sites that run a single version of each page or that only have a translated menu.

You sell to South African customers only. One English site, one version of each page. There is nothing to connect, and adding tags would only add something to maintain.

Your second language is a plugin overlay. If only the menu and buttons are translated, finish the translation of the content before thinking about tags. Google's own guidance warns against the half-translated pattern.

You want a rankings guarantee. Hreflang chooses which of your pages is shown to whom. It does not make a weak page rank, and nobody can promise that it will.

Want a second pair of eyes before you launch a new market?

Send us your current site and the markets you have in mind, and we will review it with you in a free audit.

Request a free audit

Frequently Asked Questions

These are the questions South African owners most often type when they are weighing up a second version of a site.

What is hreflang in simple terms?

Hreflang is an annotation that links equivalent versions of a page written for different languages or regions. According to Google's documentation, it helps Google understand that the pages are localised variations of the same content and point users to the most appropriate one. It is not a ranking booster.

Do I need hreflang if my site is only in English?

Not if you run one English version for one audience. Google frames the annotation for sites with multiple versions of a page, including small regional variations in a single language. A UK-priced copy of your store would qualify, while a single South African site does not.

What is the hreflang code for South Africa?

English for South Africa is en-ZA: the language code en followed by ZA, the ISO 3166-1 Alpha 2 country code. Google's documentation specifies ISO 639-1 for the language and ISO 3166-1 Alpha 2 for the optional region. Google says the value is case-insensitive, though uppercase region codes follow the ISO convention.

What does x-default mean in hreflang?

According to Google's documentation, x-default is the reserved value used when no other language or region matches the visitor's browser setting. The same page says it was designed for language selector pages. It is recommended as the fallback page, but optional.

Why is Google ignoring my hreflang tags?

The most documented cause is a missing return link, because Google says that if two pages do not both point to each other, the tags will be ignored. Also check that each page lists itself, that every URL is absolute, and that a plugin and your platform are not both writing tags. Shopify, for example, advises using its automatic tags or your own, not both.

Get Your International Setup Checked Before You Build

Send us the site and the markets you are considering. We work with Shopify, GA4 and Search Console, and will tell you whether you need a second version at all. No obligation. We will get back to you within 24 hours.

Contact Growth Pulse Media

Dirk van Greuning — Founder, Growth Pulse Media
Dirk van Greuning Founder, Growth Pulse Media

Founder of Growth Pulse Media and a specialist in South African search dominance. Dirk translates his experience in scaling South African businesses into high-velocity digital strategies for B2B and retail leaders. He writes about SEO, lead generation, and paid media from an operator's perspective — prioritising pipeline value over impressions.

Connect on LinkedIn