Hreflang correctly implemented on multilingual websites means clearly assigning language- and country-specific versions of a page. If you maintain multilingual websites properly from a technical point of view, the risk of assignment errors caused by incorrect language or country signals falls.
Above all, what matters is a consistent implementation in the HTML head, in sitemaps or via HTTP headers. Regular technical checks help you spot deviations early.
For classifying such signals, it is also important to understand that rankings are not a fixed value: they depend on language, region, device and search context. You should therefore not set hreflang once and then forget about it, but see it as part of ongoing technical maintenance. When checking international pages, Rank Tracking, Search Console data and a technical site audit can also help together.
Why hreflang exists
On multilingual websites, a search engine must be able to recognise which URL is intended for which language or region. Otherwise, a suitable page may be available, but appear in the wrong version.
hreflang is a hint for this. It does not change the content itself, but supports the assignment between language and country variants. A language or country signal is a hint that supports search engines in selecting the right URL.
This is particularly important when you publish content in several language versions or in regionally adapted versions. Then it is not only about translations, but also about which version is intended for the respective target audience.
Which URL is ultimately considered the right one can also depend on the search query, device, language and region. That is why rank positions are not fixed, but change with time and context. For technical checks, a project dashboard can help to view the associated SEO signals together.
When checking international pages, you should always look at hreflang in connection with other signals, such as the canonical tag and Search Console.
Syntax and return links
You always set hreflang annotations per language or country URL. Each URL then points to the respective matching alternative version so that search engines can recognise the relationships between the variants.
There are three common ways to implement the markup:
- in the page’s HTML head
- in XML sitemaps
- in the HTTP header for non-HTML files
It is important that you use language codes and, optionally, country codes consistently and uniformly. The assignment of the URLs must also be unambiguous: one language version should be clearly assigned to one target URL, without contradictory signals.
A return link means that every linked language version also links back to the other matching versions. These reciprocal links must be complete and mutual so that the assignment remains understandable. If a return link is missing, the relationship between the variants is often not clearly recognisable.
In practice, you should always plan hreflang together with canonical tags. The canonical tag is the hint for the preferred URL for a page. If canonicals and hreflang do not match, signals can conflict and the technical classification becomes unnecessarily unclear. The canonical tag in combination is the relevant background here.
For the content planning of language variants, keyword research can also help, because it allows you to identify which terms make sense in which language or region. If you also compare international pages against similar pages in the market, competitor analysis can be a useful point of reference.
Common hreflang mistakes
A common mistake is missing or only partially set return links. If one language version links to another, but the other does not link back, the relationship between the variants quickly becomes unclear.
Confusing language and region is also often a problem. This happens, for example, when language and country variants are not clearly separated or when the same URL is meant to stand for different target audiences.
Inconsistent URLs also lead to errors. This is the case, for example, when a page redirects to another target URL or when canonicals point to a different version than hreflang. Such signals should not work against each other.
You should also not set hreflang on pages that are blocked by robots directives or that cannot sensibly be indexed. If search engines are not meant to, or cannot, crawl a page, it is generally not suitable as a target for language assignment.
Other technical weaknesses also put extra strain on an international website. These include:
- duplicate or missing titles
- duplicate or missing meta descriptions
- unclear status codes
- faulty internal links
- slow loading times
A technical site audit checks exactly these points. The severity of findings can vary. In practice, you should first fix the clear errors, then the unclear issues, and only then the less urgent hints.
If you want to record such findings in a structured way, a site audit helps you collect the technical topics in an orderly fashion and work through them one by one. SerpDash is an SEO tool from ballmüller solutions, Berlin, which is first used for the publisher’s own websites; individual functions are still being developed.
Using x-default sensibly
x-default is intended for a general or language-neutral target page when none of the specific language or country variants fits. This can be, for example, a homepage, a selection page or a neutral entry page.
Not every international website needs x-default. It is particularly useful when users from different regions are to be sent first to a shared page and only there choose the right language or region.
It is important that the x-default URL is also consistently taken into account in the other hreflang entries. It should therefore be clearly part of the same assignment system and not stand as a special case outside the other variants.
In practice, the actual selection by search engines may depend on the search query and the context. This is an observation from practice and not a fixed rule. You should therefore understand x-default as a supporting signal, not as a directive that forces the same output in every case.
Frequently asked questions about hreflang
Is hreflang in the HTML head enough?
Yes, that can be enough if your website is set up cleanly in that way. The HTML head is one of the usual places for hreflang entries. What matters, however, is not only the location, but the complete and consistent implementation across all affected language or country URLs.
In some cases, XML sitemaps or HTTP headers are the more suitable solution, for example for non-HTML files or if you want to maintain international signals centrally. The key point is that search engines can clearly recognise the assignment.
Must every language version point to itself?
Yes, that is part of a clean implementation. Each language version should not only point to the alternative variants, but also clearly include itself. This keeps the assignment complete and understandable.
If a page only points to other variants, part of the signal is missing. That can make technical checking unnecessarily difficult.
What is the difference between hreflang and canonical?
hreflang describes which language or region a URL is intended for. The canonical tag, by contrast, names the preferred URL for content that is similar or duplicated.
So both fulfil different tasks:
hreflangsupports selection between language and country versions.- Canonical consolidates signals on a preferred URL.
If both are used together, the signals should match each other. Otherwise, contradictory hints arise.
How do I check whether the implementation is technically sound?
First check the basics:
- Are all language and country URLs present?
- Do the pages point to each other correctly and reciprocally?
- Are language and country codes consistent?
- Do
hreflang, canonical and redirects fit together? - Are the target pages indexable and not blocked by
robots?
A technical site audit also helps. It checks typical points such as status codes, titles, meta descriptions, canonicals, internal links and loading times as well. If you find errors, fix those first and then work through the less urgent hints.
What does Google Search Console show for rankings?
Google Search Console shows clicks, impressions, click-through rate and average position for the verified own website. This average position is a mean across impressions, not a fixed ranking number.
This is especially important for international pages: a single position can differ depending on language, region, device and search context. Search Console therefore mainly helps you observe developments and signals for your own website, not a single rigid rank.
If you want to bring such signals together, SerpDash can help as an SEO tool with Rank Tracking, Search Console data and site audit; some functions are still being developed.
Next step
Always check hreflang together with the other technical signals on your page. These include the target URLs themselves, canonicals, internal linking and accessibility for search engines. If these building blocks do not fit together, the assignment quickly becomes unclear.
For the technical workflow, a simple sequence is sensible:
- first fix errors
- then clarify contradictory signals
- finally check the details
Positions in search results can also change depending on the context. So monitor the development of your own pages regularly. SerpDash is an SEO tool from ballmüller solutions, Berlin; some functions are still being developed.