Hreflang for multilingual B2B websites: the mistakes that stop the right page ranking

What hreflang does and does not do

Hreflang annotations connect equivalent pages in different languages or for different regions. When a German-speaking searcher looks for a service, the annotations help search engines show the German page instead of the English one. When the same language serves several countries, such as German for Germany, Austria and Switzerland, annotations can indicate which version is intended for which country.

Hreflang does not translate pages, does not make thin pages rank and does not override other signals such as canonical tags, content quality or internal links. It is a signal about equivalence. If the pages are not genuinely equivalent, or if technical signals contradict each other, search engines may ignore it.

Choose the URL structure first

Before implementing hreflang, decide how language and country versions will be organised. Common options are subdirectories such as /de/ and /es/, subdomains, or separate country domains. For most B2B companies, subdirectories on one domain are easiest to maintain and benefit from the authority of the main site.

The important thing is consistency. Every language version should have a predictable, stable URL, and equivalent pages should be easy to map. A structure where some pages are translated, some are redirected and some are generated by browser language detection creates problems quickly.

Subdirectories

For example /de/ and /es/. Usually simplest for B2B sites on one domain.

Subdomains

For example de.example.com. Workable, but often more complex to manage.

Country domains

For example example.de. Strong country signal, but separate authority and maintenance.

The rules that break most often

Every page in a hreflang set should reference every version, including itself, and every referenced version should link back. Missing return links are the most common error. If the English page points to the German page but the German page does not point back, the relationship may be ignored.

Codes must be valid. Language codes use the ISO 639-1 format, such as de, es or sq, and optional region codes use the ISO 3166-1 alpha-2 format, such as de-AT or es-ES. Using a country code alone, or an invented code, breaks the annotation. An x-default version can indicate the page to show when no language version matches.

Each URL in the annotations should be the canonical, indexable version. Pointing hreflang at redirected pages, pages blocked from indexing or URLs with tracking parameters undermines the signal.

Translation equivalence matters

Hreflang works best when pages cover the same topic and intent. A detailed English service page connected to a short German summary is technically annotated, but not truly equivalent. Searchers landing on the thin version may leave, and search engines may prefer the stronger page in another language.

Localisation should reflect the market. A German page for Austrian or Swiss audiences may need different examples, regulations, currencies or contact details. A Spanish page for Spain should use Spanish conventions rather than Latin American terminology if Spain is the target market. For languages such as Albanian, native review is essential because automated translation often misses tone and terminology.

Implementation options

Hreflang can be implemented in HTML link elements in the page head, in HTTP headers for non-HTML files, or in XML sitemaps. For static and generated websites, head annotations are easy to inspect, while sitemap annotations keep page markup cleaner and can be generated centrally. Either works if consistent.

The best implementations generate hreflang from a single content model that knows which pages are translations of each other. Hand-maintained annotations drift as pages are added, renamed or removed.

Testing and maintenance

After launch, crawl the site to check that every hreflang target returns a successful response, is indexable, is canonical and links back. Search Console and crawling tools can reveal errors, but they are most useful when paired with a build process that prevents mistakes before deployment.

Maintenance rules matter as much as initial setup. When a page is removed in one language, the annotations in other languages must change. When a new translation is added, all existing versions must reference it. When URLs change, redirects and annotations must be updated together.

Multilingual SEO is ultimately a content and governance project. Hreflang only helps search engines understand a structure that should already make sense to people.

Where this sits in what we do

This article covers one decision inside a wider engagement. The solution page sets out how that engagement runs, what it includes and what it costs to find out.

• Digital Growth — The ongoing programme — strategy, content, paid, organic and reporting — run as one thing that answers to pipeline rather than to channel dashboards.
• Quote to cash without re-keying: where the handoffs break
• Product data is the e-commerce growth lever nobody budgets for
• Selling insurance online in the EU: how distribution rules shape digital journeys
• An AI knowledge base for company documents: permissions, sources and the content nobody owns
• All insight articles