Hreflang Tags for German Pages: Why the Return Link Decides Everything
Hreflang tags tell Google which German page belongs to which English one, but only if both pages point at each other. Before you blame the translation, check these five spots.

Key takeaways
- Hreflang tags link language versions into pairs. They tell Google which German page is the twin of which English page, so the right one shows up for the right searcher.
- Both pages must link. If page X points to page Y, Y has to point back to X. Without the return link, Google ignores the annotations.
- Every version lists itself. The self-reference belongs to the set, not just the twin in the other language.
- Hreflang sorts pages, it does not improve them. A German version that only repeats the English text gains nothing from clean tags.
What are hreflang tags?
Hreflang tags are small annotations that tell Google which language version of a page belongs together. If your site exists in English and German, each English page names its German twin, and each German page names its English twin. Google then knows that these two URLs show the same content for different audiences and not two competing pages.
That matters more than it sounds. Without the pair, Google has to guess which version fits a searcher in Munich and which one fits a searcher in Manchester. Sometimes it guesses right. Sometimes your English page ranks in German results, or your German page never shows up where it should. Hreflang tags take the guessing out of it.
How hreflang tags work for German pages
The principle is simple and merciless. Every pair needs two links, there and back, and each page also names itself. On this site, the German article on content operations carries these two lines in its head:
<link rel="alternate" href="https://lukasthies.com/why-content-operations-fail-igaming-saas/" hreflang="en" />
<link rel="alternate" href="https://lukasthies.com/de/content-operations-igaming-saas/" hreflang="de" />
The English version contains exactly the same two lines. That way each page points to itself and to its twin, and Google can confirm the pair from both sides. If you pull one line out, the construction falls apart.
From Google’s documentation
If the return link is missing, the annotations are ignored. In Google’s words: “If two pages don’t both point to each other, the tags will be ignored.”
The reason is trust. If hreflang worked in one direction only, anyone could claim that their page is the twin of someone else’s. The return link proves that both sides agree.
Three ways to add hreflang tags
Google accepts hreflang in three places, and you should pick one and stay with it:
- Link elements in the head. The classic for normal web pages and the easiest method to check by eye, as in the example above.
- HTTP headers. Meant for files that have no head, such as PDFs.
- XML sitemap. Handy for large sites with many language versions, because all annotations live in one place.
For a blog with two languages, link elements in the head are the obvious choice. If you work with a multilingual plugin, it usually writes them for you, and that is exactly where the checking starts: the plugin only outputs what your setup tells it.
Checking hreflang: five spots where pairs break
Whether you work with an hreflang checker or open the page source yourself, tick off these five points in order:
- Return link. Does the English page point back to the German one? If not, the pair is dead.
- Self-reference. Each version names itself and all other versions.
- Language code. The first part is the language. A region on its own, such as “DE”, is invalid.
- Address. The URL in the tag is the full address the page really answers on, without a redirect in between.
- Canonical. Each language version has its own canonical URL. A canonical that points to the other language undoes the pair.
On the German article from above, for example, the canonical points to the German page itself. That is the right setup, because each version stands for itself and only the hreflang tags connect the two.
“Each language version must list itself as well as all other language versions.”
Google Search Central
Language codes and x-default
The code in the tag has two parts. The first one is the language, the optional second one is the region. “de” means German in general, “de-DE” means German for Germany, “de-AT” German for Austria. A region without a language, such as “DE”, is not valid. Add a region only if you really run separate versions for separate countries. For one German version aimed at the whole DACH region, “de” is the clean choice.
Then there is x-default. It is the fallback for visitors whose language matches none of your versions. It makes sense if you have a selector page or a default version for everyone else. If you have neither, you can leave it out. Two languages and no selector are a perfectly fine reason to skip it.
The mistake that cost me a pair
One mistake I have run into myself: a German version is saved without a language assignment. In a setup with a multilingual plugin, that means the post is treated as an English one and ends up at the root of the site instead of under the German path. It then never finds its English original. The tags look clean, nothing throws an error, and still the pair is simply missing.
The fix is dull but reliable. Assign the language when you create the German version, link it to its English twin, and look at the source of both pages once after publishing. Two minutes of checking beat weeks of wondering why the German page does not rank.
What hreflang tags cannot fix
Hreflang sorts pages, it does not improve them. Google states that localized versions only count as duplicates if the main content stays untranslated. A page that was pushed word for word out of English gains nothing from clean tags. It speaks German, but says nothing of its own.
Why that matters for AI answers is covered in this article on machine translation SEO. And how “Wicked Wednesday” becomes “Moneten-Mittwoch” is shown in this piece on transcreation. If your German archive has gone quiet altogether, a content audit shows where to start. How I set up language versions for clients is on my workflows page.
Frequently asked questions
What are hreflang tags?
They are small annotations that tell search engines which language or regional version of a page belongs to which URL. With them you link your German and English versions into one pair. Both pages have to carry the annotation, otherwise it does not work.
Where do I put hreflang tags?
Google accepts three places: link elements in the head of the page, an HTTP header for files that are not HTML, or an XML sitemap. Pick one method and keep it consistent. For a blog with a handful of language versions, link elements in the head are the easiest to check by eye.
When should I use hreflang x-default?
The value x-default is reserved for the case where no other language or region matches the user’s browser setting. It makes sense if you have a language selector page or a default version for all other visitors. It is optional, and it never replaces the language-specific tags.
Should I write “de” or “de-DE”?
The first part of the code is always the language. “de” covers every German speaker, “de-DE” only Germany. A region on its own is invalid. Add the region only if you really run separate versions for Germany, Austria or Switzerland.
How do I check hreflang tags?
Open the source of both pages and look for rel=”alternate” and hreflang. Each page has to name itself and its twin, with the full address. An hreflang checker automates this, but it does not replace your own look at the return link and the language code.
Work with me
Do your language pairs break somewhere?
In a free 30-minute call, we go through your language versions and I show you where the pairs break. No pitch deck, just your pages and a checklist.
