Hreflang for multilingual affiliate sites tells Google which language or country version of a page to show each searcher, so your German review ranks in Germany and your English one in the UK. To set it up, every version of a page must list itself and all its alternates with valid language-region codes, using fully qualified URLs, and every alternate must link back. Add an x-default for everyone else, pick one method (HTML tags, HTTP headers or an XML sitemap) and audit it after every major content change.
That is the short version. Below is the step-by-step setup for a typical European affiliate site, plus the errors that most often cause the wrong version to rank.
What hreflang tags do for multilingual affiliate sites
Hreflang annotations are signals that link equivalent pages in different languages or for different regions. They help Google swap in the right URL for the searcher's language and location. According to Google's documentation on localised versions, they do not:
- Detect language. Google works out a page's language from its visible content, not from hreflang or the HTML lang attribute.
- Boost rankings. They help the right version appear where you already rank; they do not make a weak page rank.
- Merge duplicates on their own. Localised pages are only treated as duplicates if the main content is untranslated.
Other search engines treat language signals differently. Bing has historically recommended declaring language and region with the content-language meta tag, so if Bing traffic matters to you, consider adding that alongside hreflang.
Getting the language and country codes right
Each value is a language code (ISO 639-1), optionally followed by a region code (ISO 3166-1 Alpha-2). Values are case-insensitive, but uppercase regions are conventional.
| Audience | Correct value | Common mistake |
|---|---|---|
| English speakers in the UK | en-GB | en-UK (UK is a reserved code and has no effect) |
| English speakers in Ireland | en-IE | en-IR (IR is Iran) or ie alone (ie is Interlingue; Irish is ga) |
| German speakers anywhere | de | de-EU (EU is reserved) |
| German speakers in Switzerland | de-CH | ch (region alone is invalid) |
| French speakers in Belgium | fr-BE | be (be means Belarusian) |
| Dutch speakers in Belgium | nl-BE | vl or nl-VL (not valid codes) |
| Swedish speakers | sv | se (Northern Sami) |
| Danish speakers | da | dk (not a language code) |
| Norwegian Bokmål | nb or no | nn when you mean Bokmål (nn is Nynorsk) |
| Czech speakers | cs | cz (country code, not language) |
Watch out: a region code can never stand alone. "be", "ch", "dk" and "se" on their own are read as language codes, and three of those four point to the wrong language entirely.
Step 1: choose one implementation method
Google accepts three equivalent methods. Using more than one adds nothing and creates more places for conflicts.
| Method | Best for | Watch-outs |
|---|---|---|
| HTML link tags in the head | Small to mid-sized sites, CMS plugins | Adds weight to every page; templates must output the full set consistently |
| HTTP Link headers | Non-HTML files such as PDFs | Hard to audit without server access |
| XML sitemap | Large sites, programmatic pages, many languages | Must stay in sync with live URLs; a stale sitemap sends stale signals |
For most WordPress affiliate sites, a multilingual plugin that outputs head tags is the simplest route. For sites with thousands of comparison or review pages in five or more languages, a generated sitemap keeps page weight down and is easier to regenerate from your database.
Step 2: map every page to its equivalents
Before writing any tags, build a spreadsheet with one row per "content cluster" (the same page in every language) and one column per locale. This is where most affiliate sites go wrong: hreflang should only connect pages that genuinely serve the same purpose.
- A German review of a cam site and the English review of the same site belong together.
- A German "best dating sites" list and an English one belong together even if the featured programs differ by country, as long as the intent is the same.
- A page that exists only in one language gets no hreflang (or only a self-reference).
If you have both a language-level page (de) and country pages (de-DE, de-AT, de-CH), decide which is the catch-all. Google recommends providing a generic page for a language when several locales share it. Our guide to language vs country targeting helps you decide whether separate country versions are worth it, and hreflang for German variants covers the DACH case in detail.
Step 3: write the tags, including self-reference and x-default
Every version carries the same full set. For a review available in UK English, Irish English, German and French, the head of each of the four pages contains:
<link rel="alternate" hreflang="en-GB" href="https://example.com/uk/review/" />
<link rel="alternate" hreflang="en-IE" href="https://example.com/ie/review/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/testbericht/" />
<link rel="alternate" hreflang="fr" href="https://example.com/fr/avis/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/review/" />
Key rules:
- Self-reference: each page lists itself as well as the others.
- Return links: if page A points to page B, B must point back to A, or Google may ignore the pair.
- Fully qualified URLs: include https:// and the domain. Relative and protocol-relative URLs are not valid.
- Canonical URLs only: point to the indexable, canonical version of each page, never to a redirect, a noindexed URL or a parameter variant.
- x-default: use it for the page that should serve unmatched users, typically an English international version or a language-selector page.
Alternates can sit on different domains, so the same rules apply if you use country-code domains. If you have not yet chosen a structure, compare options in ccTLDs, subdomains or subfolders for European sites.
Optional: build an hreflang sitemap
In a sitemap, each URL gets its own url entry with a loc element and one xhtml:link child for every version, including itself. Declare the xhtml namespace at the top of the file. A trimmed example for one entry:
<url>
<loc>https://example.com/de/testbericht/</loc>
<xhtml:link rel="alternate" hreflang="de" href="https://example.com/de/testbericht/" />
<xhtml:link rel="alternate" hreflang="en-GB" href="https://example.com/uk/review/" />
<xhtml:link rel="alternate" hreflang="x-default" href="https://example.com/review/" />
</url>
The other versions each get their own url entry with the same set of children. Generate the file from the same data that builds your pages so the two never drift apart, and remove URLs promptly when a page is deleted or redirected.
Handling partial translations and phased launches
Few affiliate sites translate everything at once. You might launch German with your 40 strongest reviews, add French six months later and never translate low-value news posts. Hreflang copes with this, provided you are disciplined:
- Only annotate pages that exist in more than one version. An English-only news post needs no alternates. Do not point it at a German category page as a stand-in.
- Grow clusters, do not rebuild them. When you add a French version, update the tags on every existing member of that cluster in the same release, so return links are never missing for long.
- Prioritise the dominant version. If full bidirectional linking is hard during a migration, Google suggests at least linking new variants with the original or dominant language version first.
- Keep offers honest per country. If an Irish page features different programs from the UK page because some merchants do not accept Irish traffic, that is fine, but the page should still answer the same question. If it does not, it is a different page and should not share the cluster.
A practical way to manage this is a "translation status" field in your CMS or spreadsheet. Only pages marked as published and reviewed in a language should be output into the hreflang set, which stops half-finished drafts or machine-translated placeholders leaking into the cluster.
Common hreflang errors on affiliate sites
Canonical tags that point across languages
If your German page has a canonical pointing to the English page, you are telling Google the German page is a duplicate. Hreflang then fails. Each language version should be self-canonical.
Hreflang pointing to geo-redirected URLs
Many affiliate sites redirect visitors by IP. Googlebot mostly crawls from the US without an Accept-Language header, so if /de/ redirects US visitors to /en/, Google may never see the German page. Google advises against automatic redirection based on assumed language; see geo redirects and SEO in Europe for safer alternatives such as a suggestion banner.
Missing or one-way return links
Usually caused by adding a new language without updating the old pages, or by one template outputting tags and another not. Audit after every new locale launch.
Mismatched content
Linking a detailed English review to a two-paragraph German stub, or a review to a category page, confuses the cluster. If the German page is not ready, leave it out of the set.
Affiliate links and cloaked URLs in the set
Only include your own content pages. Never include redirecting /go/ links, tracking URLs or merchant pages in hreflang.
Mixing methods inconsistently
A plugin adding head tags while an SEO tool adds a sitemap with different values is a common source of conflicts. Choose one and disable the other.
Step 5: audit and maintain
Google retired the International Targeting report in Search Console in 2022, so you need other ways to check your setup:
- Crawl the site with an SEO crawler that reports missing return links, invalid codes and non-canonical targets.
- Check Search Console performance by country: if German queries in Germany show your English URL, your annotations or content are not doing their job.
- Use URL Inspection on key pages to confirm the canonical Google has chosen.
- Spot-check SERPs from each target country with a local VPN or SERP tool.
Make hreflang part of your publishing checklist: new page, new translation, deleted page or changed URL all mean the cluster needs updating. Hreflang sits within wider technical SEO; our guide to technical SEO for adult sites covers crawl, speed and indexing issues that affect it.
Frequently asked questions
Do I need hreflang if each language is on its own ccTLD?
It is still recommended where the pages are equivalents. A ccTLD signals country, but hreflang tells Google exactly which page on which domain is the alternate, which helps in shared-language situations such as German pages on .de, .at and .ch.
Should x-default point to my English page?
Often, yes, if English is your best fallback for visitors whose language you do not cover. If you have a language selector page, that is also a sensible x-default.
Can I use hreflang for pages that differ only by currency or offers?
Yes, as long as the pages target different regions with the same language and serve the same purpose, for example en-GB and en-IE versions with prices in pounds and euros. Make sure the differences are real, not just a changed currency symbol.
How long does hreflang take to work?
Google has to recrawl every page in the cluster before it can confirm the return links. On a small site that may take days; on a large site, weeks.
Next steps
Build your page-mapping spreadsheet first, then choose a method and implement for one content cluster before rolling out site-wide. If you need a plugin, crawler or translation management tool, compare options in our webmaster software and services directory.