Skip to content
SEO & GEO

Hreflang: A Practical Guide for B2B Multilingual Sites

When is hreflang needed, which method to pick, in what order to fix errors and how to check the result? A practical guide for B2B companies with several languages or markets.

Louis Mauclair · CEO

Updated November 2026 · 8 min read

Marketing and sales team reviewing a revenue presentation

TL;DR Hreflang tells Google which pages are language or country variants of the same page. Google recommends signaling them as soon as two versions of the same content exist, for example English and French, or English for the US and the UK. For a B2B site, we recommend tags in the head: one method, every version lists itself and all the others, with absolute URLs that return a 200. Fix errors in a set order and check the result in the page source, then with a crawl.

Louis Mauclair, CEO of Klickbee, an SEO, GEO and Google Ads agency for B2B and ecommerce companies. Before Klickbee, he co-⁠founded an ecommerce business that grew past 13,000 customers.

You launch a French version of your site, or you open a second market, and someone says you "just need hreflang." It is an easy tag to get wrong in technical SEO: simple on paper, fragile the moment a plugin gets involved.

This guide is for B2B companies with more than one language or market. The rules come from Google's documentation, read on November 20, 2026.

What hreflang does, and when you need it

Hreflang is an attribute that links the versions of the same page in different languages or for different countries. Google can sometimes work out these versions on its own, but its documentation recommends that you signal them.

One point prevents false hopes: Google does not use hreflang or the HTML lang attribute to detect a page's language. It relies on its own algorithms. Hreflang routes the right version to the right visitor, it does not declare a language. And a translated page is not a duplicate: Google only treats localized versions as duplicates if the main content stays untranslated.

  • It is recommended when the same page exists in several languages, or in one language with content adapted to several countries (offer, legal notices, currency).
  • You can skip it on a site in one language for one market.

Hreflang implementation: head, sitemap or HTTP header

Google accepts three channels and treats them as equivalent. Using all three gives no benefit in Search and makes maintenance harder.

  • Tags in the head: one link element per version, with rel set to alternate, the hreflang attribute and the absolute URL, the current page included. This is the default for a B2B site: everything is readable in the page source.
  • XML sitemap: the alternates are declared in the sitemap, with the xhtml namespace. Useful when the head is hard to edit. The sitemap can only contain URLs in its own directory or below, and nothing shows on the page, so you need a tool to check it.
  • HTTP headers: useful for non-⁠HTML files such as PDFs.

Our firm view: pick one channel per site and write it into the spec. Stacking a plugin, a theme and a sitemap multiplies the places where annotations drift apart.

Reciprocity, self-⁠reference and hreflang canonical: the core rules

  1. Reciprocity. If the French page points to the English page, the English page must point back. Otherwise, per Google, the tags are ignored.
  2. Self-reference. Each version lists itself, and the set of annotations is identical on every version.
  3. Absolute URLs, with the protocol (https://example.com/page), never a relative path.
  4. 200 and indexable URLs. Screaming Frog treats non-200 URLs as errors and warns that a noindex return page can make the relationship ignored.
  5. Self-canonical. With hreflang, Google asks for a canonical in the same language (or the best substitute), and says it prefers URLs that belong to an hreflang cluster for canonicalization.

Language and country codes, and the hreflang x-⁠default tag

The format is an ISO 639-1 language code, optionally followed by an ISO 3166-1 alpha 2 region code: en, en-⁠US, fr-⁠CA. A country code alone is not valid. Google lists the traps itself:

  • be is the code for Belarusian, not Belgium. For French in Belgium, use fr-⁠BE.
  • UK, EU and UN as a region have no effect in Search. For the United Kingdom, the ISO region code is GB, so en-⁠GB.
  • Language only, or language and country? Add the country only when the content really differs. For a language targeted at several countries, Google suggests adding a generic page: its example combines en-⁠IE, en-⁠CA and en-⁠AU with an en page for everyone else.

The x-default value marks the fallback page for visitors whose language matches no version, mainly on a language or country selector. Google recommends including it, but Screaming Frog describes a missing one as optional and not necessarily an error. Our rule: add it whenever an obvious fallback exists, because it is the cheapest tag you will ever write.

What klickbee.com declares (read on November 20, 2026)

We read the klickbee.com page source that day.

  • Home page and technical SEO service page: five tags, en, en-⁠AE, fr, fr-⁠AE and x-⁠default, identical across the four versions of the site (the root, /fr, /en-ae and /fr-ae), each with a canonical pointing to itself.
  • Blog post (example: Google Ads management): three tags, en, fr and x-⁠default, identical on the English and French versions.
  • Codes: language only for the general versions. A region appears only on the two versions built for the UAE. The x-⁠default points to the English version of each page.
  • One method: tags in the head, and no hreflang annotations in the 294 sitemap URLs we read that day.

This is a setup, not a result: we promise no traffic gain.

Common hreflang mistakes, in the order to fix them

This order is ours, not a Google ranking.

  1. Cluster URLs in error: redirected, 404, blocked by robots.txt or noindex. Fix these first. For pages that are not indexed, see crawled, currently not indexed.
  2. Automatic redirects by language or country: Google advises against them, because they can keep users and search engines from seeing every version.
  3. Missing return links or self-⁠reference.
  4. Invalid codes: be for Belgium, UK, a country alone.
  5. Contradictory canonical, or one pointing to another language.
  6. Duplicate annotations: a plugin and a theme each output their own set.
  7. Missing x-⁠default: last, because it is optional.

Not sure what Google actually reads on your two versions? Get your free action plan.

International SEO: what hreflang does not fix

Hreflang assumes translated pages in a readable structure, a design decision best made when you build a B2B website. Google compares four URL structures:

  • Subdirectory (example.com/fr/): simple, low maintenance, but a single server location. It is our default for a B2B company, and the one klickbee.com uses.
  • Country-⁠code domain (example.de): clear geotargeting, but costly, sometimes unavailable, and one country only.
  • Subdomain (de.example.com): simple, but the targeting is not readable from the URL alone (is "de" the language or the country?).
  • URL parameter (?loc=de): Google does not recommend it.

Another limit: a page where only the template is translated. Google says this can create a bad user experience if the same content appears several times in results.

If you add a language during a redesign, put hreflang on your site migration SEO checklist: a URL that changes can break reciprocity.

Hreflang checker: how to test your tags, step by step

  1. Read the page source. Search for hreflang in the head of each version: same set everywhere, valid codes.
  2. Inspect the URL in Search Console. View crawled page shows the raw HTML and headers Google received. Search Console does not replace this check: the old International Targeting report is deprecated, although Google keeps supporting hreflang.
  3. Crawl the site. Screaming Frog's hreflang audit tutorial describes a Hreflang tab and its filters: missing return links, non-200 URLs, noindex return links, incorrect codes, pages not using the canonical.
  4. Use an online hreflang checker for a single page: TechnicalSEO.com says it checks HTML, HTTP headers and sitemaps, and DomScan checks return links and codes.
  5. Re-⁠check after every change: new language, redesign, URL change.

Tools described from their official pages, read on November 20, 2026. We did not test them.

Hreflang for B2B sites: what to remember

Hreflang is mostly about organization: one channel, clean URLs, reciprocal links, valid codes. Check what is actually published, fix in order, and re-⁠check whenever the site changes.

To see where your site stands, Get your free action plan: it reviews, among other things, indexation and site structure, with no commitment.

FAQ

What is a hreflang tag used for?

It tells Google the language (and optionally the country) of a page version and the URLs of its equivalents. It routes the right version to the right visitor. It does not tell Google which language a page is in.

Where should I put hreflang tags?

In the page head, in the XML sitemap or in HTTP headers: Google treats the three as equivalent. For a B2B site, the head is the easiest to control.

How do I add hreflang tags in HTML?

Put one link element per version in the head, with rel set to alternate, an hreflang attribute and the absolute URL. Include the current page, and repeat the same set on every version.

Do I need an x-⁠default tag?

No, it is optional, but Google recommends it for the fallback page, especially with a language selector. Screaming Frog describes a missing one as optional and not necessarily an error.

How do hreflang and canonical tags work together?

Each version carries a canonical pointing to itself and appears in the hreflang set. Google asks for a canonical in the same language. A French page canonicalized to the English page is a contradiction to fix.

Is hreflang enough for international SEO?

No. It replaces neither the URL structure, nor translation of the main content, nor indexing of each version. Without truly localized pages, it has nothing to link.

Sources

Share

LinkedInX

Louis Mauclair

Louis leads growth and digital acquisition for B2B and e-⁠commerce companies in France and the UAE. Before Klickbee, he co-⁠built and sold an e-⁠commerce business that served more than 13,000 customers. He moved to Dubai in 2026 to work with companies across the GCC.

Free action plan

Want more leads from your traffic?

Get your 6-page action plan within 48 hours.

Get my free action plan

Related articles

All articles

Free action plan

Grow faster. Get your free action plan.

A tailored plan to generate more leads and sales from your existing traffic.

  • Built for B2B & e-⁠commerce teams
  • No commitment
  • A 15-minute call, then your plan within 48 hours
  • ★ 5.0 on Google · 22 reviews
  • Senior experts + in-⁠house AI
  • Founders of a 13,000-customer e-⁠commerce

Your action plan

6 pages · 3 priority levers · within 48 h

Free

Step 1 of 2 — Your business

Got a question first? Message us on WhatsApp
Get my free action planWhatsApp