International Link Building

Hreflang and Link Building for Multilingual Sites

By BacklinkPrice Team · Nov 22, 2026 · 6 min read
Illustrated cover for Hreflang and Link Building for Multilingual Sites

Hreflang decides which language version Google shows; links decide how strong each one is. Here's how to plan both for a multilingual site.

On a multilingual site, hreflang tells Google which language or regional version of a page to show, while links decide how strong each version is. Build links to each language version from sites in that language and market, link the versions to each other internally, and keep hreflang annotations complete and reciprocal so value isn't lost to misdirected pages.

Hreflang and link building are often handled by different teams. When they're planned together, each local version of a page can rank in its own market instead of competing with its siblings.

Key takeaways

  • Google uses hreflang to understand that pages are localized variations of the same content.
  • Localized versions are only treated as duplicates if the main content stays untranslated.
  • The x-default value names a fallback page for languages and regions you don't target, and Google says hreflang URLs may be used for URL discovery.
  • Hreflang doesn't pass link value between versions. Each version needs its own relevant links.
  • Links from sites in the same language and market usually help a localized page most.
ElementWhat it doesWhat it doesn't do
hreflang annotationsTell Google which version suits which language or regionPass link value between versions
Canonical tagsPick the preferred URL among duplicatesShould not point all languages to one version
Internal links between versionsHelp crawling and let users switch languageReplace hreflang
External links to each versionBuild each version's authority in its marketChoose which version Google shows
x-defaultSets a fallback for unmatched usersRank anything by itself

What hreflang actually does

It groups versions of the same page.

Google's documentation on localized versions says hreflang helps it understand that pages are localized variations of the same content. It can then show the right version to each searcher.

The same guide notes that localized versions are only considered duplicates if the main content remains untranslated. Properly translated pages are separate pages in their own right.

Our guide on whether links from foreign-language sites help explains how relevance works across languages, which shapes where each version's links should come from.

Hreflang values and syntax

Language first, region optional.

Each annotation uses a language code and, optionally, a region code, such as "es" for Spanish or "es-MX" for Spanish in Mexico. Wikipedia's hreflang article notes that values follow language tag rules, including script variations such as zh-Hant and zh-Hans.

The underlying standard is RFC 5646, which defines language tags. The W3C's guide to choosing language tags is a friendlier introduction if you're unsure which code to use.

You can add hreflang in the HTML head, in HTTP headers for files like PDFs, or in an XML sitemap. Pick one method and use it consistently.

The x-default value

A fallback for everyone else.

Google's post on how x-default can help explains that x-default marks the language- and region-neutral URL when you don't support a searcher's language or region.

The same post notes that URLs listed in hreflang annotations, including x-default, may be used for URL discovery. That makes complete annotations useful for crawling as well as targeting.

Point x-default at a country selector or your main international version. Don't leave it pointing at a page that redirects or returns an error.

Hreflang doesn't share authority.

Hreflang tells Google which version to show. It doesn't move link value from your strongest version to the others. A Spanish page with no links can still struggle in Spain, even if the English version is well linked.

That's why international link building should be planned per market. A link from a respected Spanish site to your Spanish page is more relevant to Spanish searchers than another link to your English page.

Our guide on topical relevance of links covers why matching the linking site's subject and audience matters.

Think in markets, not translations.

Start with each market's own media, associations, universities and directories. Local press covers local data, local experts and local events, so give them something with a local angle.

Translate your best linkable assets, such as data studies or tools, and adapt them with local figures. A survey of German consumers will earn more German links than a translated US survey.

Recruit native speakers for outreach. A pitch with awkward grammar is easy to ignore, and local editors respond better to people who know their market.

Link versions to each other and keep paths clear.

Add a visible language switcher that links each page to its equivalents. This helps users and gives crawlers another route between versions.

Within each language, link pages to each other in that language. A Spanish guide should link to related Spanish pages, not jump back to English pages mid-paragraph. Our guide on building internal links covers structure within a single site.

Canonicals pointing to one language.

If every language version canonicalises to the English page, Google may ignore the other versions. Each version should usually have a self-referencing canonical and hreflang pointing to its siblings.

Missing return links. Google's guidelines call for each version to list all the others, including itself. If page A points to page B but B doesn't point back, Google may ignore the pair.

Automatic redirects by IP or browser language. Forced redirects can stop crawlers reaching some versions. Offer a choice with a banner or selector instead.

Mixing languages on one URL. A page with half-translated content is harder to rank anywhere. Translate the main content fully before launching a version.

Ideally, yes.

When you earn a link from a French site, ask for it to point to your French page. That builds authority where you want it and sends visitors to content they can read.

If a site links to the wrong version, a polite correction request is reasonable. When that isn't possible, good internal links and hreflang will still help Google and users find the right page. Our comparison of 301 redirects and canonicals for links explains how consolidation affects link value.

A sample rollout for a new language

Weeks 1 to 2: translate and localise key pages fully, add self-referencing canonicals, and add complete hreflang sets with x-default.

Weeks 3 to 4: add a language switcher, build internal links within the new language, and submit the updated sitemap.

Months 2 to 3: localise one linkable asset with market data, and pitch it to local media and trade sites through a native speaker.

Check the setup in Search Console and track rankings in each target country separately. Our guide on building topical authority with links helps plan which pages to support first.

Frequently Asked Questions

No. It tells Google which version to show to which users. Each version builds authority from its own links.

Yes, ideally. Links from sites in the same language and market are the most relevant to each localized page.

What should x-default point to?

Usually a country or language selector, or your main international page. It should be a live page, not a redirect.

Can I use hreflang and canonical tags together?

Yes. Each version should normally have a self-referencing canonical and list its alternates with hreflang.

No. Those links still help. Ask for links to the matching language version when you can, so value and visitors reach the right page.

Sources

BacklinkPrice Team
Written by
BacklinkPrice Team
Link building and backlink pricing research

The BacklinkPrice Team researches backlink prices, publisher sites and link building tools. We check prices and plans against each provider's own pages and date them, so you know how current the numbers are.

More from BacklinkPrice Team

Related guides