On this page
Hreflang matters the moment you sell in more than one market. Without it, Google may show the wrong language, or treat your country versions as rivals for the same query. One line in the head of a page looks like this:
<link rel="alternate" hreflang="en-GB" href="https://www.example.com/uk/">
Google introduced the markup in December 2011 and added x-default in 2013: the page for anyone who fits none of your versions, often a language picker or your main market. The code is a two-letter language (en, de, fr), optionally followed by a two-letter country (en-GB, en-US, de-AT). Language always comes first. You can put the lines in the head of each page, in an HTTP header for PDFs, or in your XML sitemap. Our hreflang tag generator writes the lines for you, and international SEO strategy shows where they fit in a plan for several countries.
Same language, different countries
The hardest case is not translation but one language across several markets. An English page for the UK, Ireland and the US, or a German page for Germany, Austria and Switzerland; or a Dutch page in two versions, for the Netherlands and for Flanders, as in Dutch vs Flemish. Prices, VAT, spelling, delivery and legal details differ, but the text is mostly the same. Hreflang tells Google which one belongs to which country, so a searcher in Dublin gets euro prices rather than dollars. Without it, Google sees near-identical pages and picks one, which is duplicate content by another name.
| Setup | Example | Fits when |
|---|---|---|
| Country domains | example.de, example.co.uk | Separate teams and strong local brands per market |
| Folders on one domain | example.com/de/, example.com/uk/ | One team, shared authority, simplest to run |
| Subdomains | de.example.com | Separate systems per market |
All three work with hreflang. Folders on one domain are usually the easiest to maintain and pool your links in one place.
Every version names every version, itself included
As on business-centrum.be. A missing cell is a missing return link, and Google ignores that pairing.
A four-language site, line by line
The site we built for Business Centrum runs in Dutch, French, English and Turkish. The head of the Dutch home page carries five lines: one per language plus x-default pointing at the Dutch version. Each language version carries the same five lines and a canonical tag pointing at itself. The figure shows that as a grid: only when every cell is filled does Google trust the pairing. In its first weeks the site also reached page one for French and English searches such as "secretariat social horeca" and "social secretariat belgium", which only happens when Google shows each version to the right searcher.
The mistakes that hide a market
- No return linkIf the German page points to the English one, the English page must point back, and every page must name itself. Otherwise Google ignores the pairing. Translation plugins are the usual culprit.
- Every version canonical to the main languageYou have just told Google the other languages are copies, and they drop out.
- Codes the wrong way round or inventeden-UK is not valid; the country code for Britain is GB. Language first, country second.
- Redirecting by browser languageGooglebot crawls mostly from the US and only ever sees one version. Let visitors choose instead.
- Pointing at addresses that redirect or return errorsGoogle skips those lines.
To see what your own pages declare, run the SEO checker; for the bigger picture of building for several markets, see multilingual website development and, for Belgium specifically, a website in French and Dutch.
Hreflang links intent, not identical text
Your German page does not have to be a word-for-word translation of your English one. Hreflang pairs pages that serve the same purpose. Buyers in each market search with their own words, so the best version for each is written for them.
What owners of multilingual sites ask
Is hreflang a ranking factor?
No. It does not lift your position; it makes sure the right version appears at that position.
Do I need hreflang with only one language?
Only if you serve the same language to several countries with different content, such as en-GB and en-US pages.
Should x-default point to English?
Point it to whatever serves an unmatched visitor best: a language picker, or the version most of your international buyers use.