How to Use the Link Alternate Tag for International SEO

Businesses spend months building multilingual websites, investing heavily in translation and localization, only to watch Google serve the wrong language version to the wrong audience. Spanish speakers land on the English page. French users see the U.S. version. The traffic arrives, but the conversion never happens. The technical fix for this problem is the link alternate attribute, specifically, rel="alternate" used alongside hreflang, and the two are not the same thing. Understanding the distinction is what separates a setup that works from one that quietly fails.

At Brandleap Agency, international SEO configuration is part of every global optimization engagement we run. Hreflang implementation looks deceptively simple, but even a single missing reciprocal tag can cause Google to discard the entire language cluster, wiping out visibility across multiple markets. This guide walks through the correct setup, the canonical conflicts to avoid, and how to catch errors before they compound into ranking problems.

What rel=”alternate” actually does (and where hreflang fits in)

The “alternate” relationship in plain terms

rel="alternate" is a link relationship type that tells search engines the linked URL is a different version of the current page. By itself, it is a container relationship, it does not specify what kind of alternate version exists. That distinction depends on the additional attributes used alongside it: a type attribute might indicate an RSS feed, a media attribute might point to a mobile-optimized URL, and an hreflang attribute signals a localized language version.

Why hreflang cannot stand alone

hreflang is an attribute used with rel="alternate", not a standalone tag. Without the rel="alternate" relationship, the hreflang attribute has no defined link context for Google to act on. Think of them as a unit: rel="alternate" says “this is another version of this content,” and hreflang says “that version is intended for this specific language or region.”

The full anatomy of the tag

The complete tag structure looks like this: . The rel="alternate" defines the relationship type. The hreflang="fr" specifies the target language using the ISO 639-1 two-letter code. The href provides the absolute URL of that language version. Every part carries a specific job, and leaving any one out breaks the signal.

Alternate link tag implementation in the HTML head

The core implementation rule

The non-negotiable rule for HTML implementation is this: every page in a language cluster must carry the full set of link alternate tags, including a tag that points back to itself. If you have English, Spanish, and French versions of a page, each of those three pages must list all three URLs plus the x-default fallback. Missing even one page from the reciprocal link set causes Google to discard the entire cluster and treat each URL independently.

A working HTML example with multiple languages

Place the following block inside the element of every page in the language group. This example covers three language variants plus the x-default fallback for unmatched users:

This exact block must appear on the English page, the Spanish page, and the French page. The only thing that changes across pages is the URL in the browser address bar, not the tag set itself. Each page in the cluster references all the others, confirming the relationship for Google from every angle.

Language codes vs. language-region codes

There is an important difference between hreflang="en" and hreflang="en-US" or hreflang="en-GB". Language-region codes are only necessary when the same language has distinct regional versions with meaningfully different content. If you have one English page that serves all English speakers, hreflang="en" is correct. Adding en-US, en-AU, and en-GB when the content is identical creates maintenance complexity with no SEO benefit. Language codes follow ISO 639-1 format (two lowercase letters); region codes follow ISO 3166-1 alpha-2 format (two uppercase letters), joined with a hyphen: en-GB, not en_GB.

Sitemap and link alternate setup for large sites

When the sitemap approach makes more sense

For sites with hundreds or thousands of localized URLs, adding alternate link tags to every page’s HTML becomes impractical to manage and audit. The XML sitemap alternative consolidates all hreflang annotations into a single file, making it easier to update, audit, and hand off to new team members. Google treats both methods equally, so choosing one over the other is a maintenance decision, not an SEO preference.

How to write xhtml:link entries in an XML sitemap

The sitemap method requires declaring the XHTML namespace at the top of the file and using xhtml:link elements inside each block. Every URL in the cluster must appear as a separate block, and each block must carry the full set of alternates. Here is a working example for three language variants:

  
    https://example.com/en/
    
    
    
    
  
  
    https://example.com/es/
    
    
    
    
  
  
    https://example.com/fr/
    
    
    
    
  

The one rule both methods share

Regardless of whether you use HTML tags or an XML sitemap, the URL set must be identical across every member of the cluster. If the English page lists French and Spanish alternates, the French page must list English and Spanish, and the Spanish page must list English and French. There are no exceptions to this reciprocity requirement. Google uses it to confirm the cluster is intentional and consistent.

x-default and canonical tags: two signals that must not conflict

What x-default is actually telling Google

hreflang="x-default" signals the fallback page for users whose language does not match any defined alternate in the cluster. It typically points to a homepage, a language selector page, or the most commercially dominant language version. It carries no language code because it is explicitly language-neutral. A common misuse is assigning x-default to the English version of a page when a proper hreflang="en" tag already exists. These two values are not interchangeable: one targets English speakers, the other targets everyone else.

The canonical vs. alternate conflict to avoid

rel="canonical" answers one specific question: which URL should be indexed as the primary copy of this content? The link alternate attribute (rel="alternate") answers a different question: what other versions of this content exist for different audiences? These two signals serve separate jobs. The critical mistake is pointing a canonical tag from one language version to a different language version. Google ignores those canonical hints, and when that happens, the alternate annotations in the same cluster become unreliable.

The right pattern for each scenario

Each use case has a distinct answer, and mixing signals across them creates indexing problems that are difficult to diagnose. For language and regional variants, use rel="alternate" hreflang to connect the pages and let each page self-canonicalize. For true content duplicates within the same language, use rel="canonical" to point duplicates to the preferred URL. For separate mobile URLs on an m-dot subdomain, add rel="alternate" on the desktop page pointing to the mobile URL, then add rel="canonical" on the mobile page pointing back to the desktop version.

The mistakes that silently break your hreflang setup

Missing reciprocal links and incomplete URL sets

The most common error is a developer who adds alternate tags to the English page but forgets to mirror the full tag set on the Spanish and French pages. Google requires every page in a cluster to reference all other variants, including itself. A partial setup gets ignored entirely, which means the entire investment in localized pages delivers no international ranking benefit. This failure is silent: no crawl errors appear, the pages still index, but Google never connects them as a language group.

Wrong language codes and relative URLs

Using invented region codes, outdated codes, or incorrectly formatted combinations like en_US (underscore instead of hyphen) makes the annotation unreadable to Google. The correct format uses ISO 639-1 for language (two lowercase letters) and ISO 3166-1 alpha-2 for region (two uppercase letters), joined by a hyphen: en-US. Relative URLs are equally problematic: href="/en/" is not acceptable. Every href value must be a full absolute URL with the https:// protocol included, or search engines will misinterpret the path.

Noindex pages and irrelevant language mappings

Two less obvious errors regularly surface in audits. Adding alternate annotations to pages blocked from indexing sends contradictory signals: you are simultaneously telling Google “here is an alternate version to serve users” and “do not index this page.” The second error is mapping language alternates to pages that are not true content equivalents. If the English page covers one topic and the Spanish page linked as its alternate covers a different topic, Google’s understanding of your site structure degrades. Both errors quietly undermine international ranking performance without triggering obvious error messages.

How to validate your hreflang setup and catch errors early

Reading hreflang errors in Google Search Console

Google Search Console surfaces hreflang errors through its coverage and international targeting reports. The “No return tag” error signals missing reciprocal links: a page references an alternate, but the target URL does not link back. An unrecognized language code error means an invalid or malformed code was used in an annotation. An alternate URL not indexed error points to crawlability issues on the linked page. Knowing which error maps to which fix makes debugging faster than auditing code by hand.

Third-party validation tools worth using

Several tools catch hreflang conflicts that Search Console misses. Screaming Frog’s hreflang tab is a comprehensive option for site-wide audits: it crawls every URL in the cluster, maps all alternate relationships, and flags missing self-references, incorrect codes, and broken links in one report. For single-URL spot checks, Aleyda Solis’s validator at hreflang.es is fast and free. Both tools catch the missing self-referential tags and incorrect code formats that create indexing problems before those problems compound across language markets.

When the complexity warrants expert help

For sites targeting multiple countries and languages simultaneously, the annotation matrix grows fast. A 10-language site can require hundreds of individual alternate relationships maintained correctly across HTML and sitemaps, and that number multiplies with every new page added. This is where agency-managed international SEO removes the maintenance burden entirely. At Brandleap Agency, the technical implementation, ongoing validation, and monitoring of link alternate configurations are handled as part of every global optimization package, so business owners are not manually tracking an annotation matrix that scales into the thousands.

Getting your international setup right from the start

Once you understand what each signal contributes, the implementation hierarchy becomes clear. The rel="alternate" attribute establishes the relationship type. The hreflang attribute specifies the language or region target. Reciprocal link clusters confirm the relationship from every member of the group. The x-default value handles fallback routing for unmatched users. Canonical tags stay completely separate from link alternate signals, each answering its own distinct question.

The link alternate attribute is one of the most misunderstood technical SEO elements, but implemented correctly, it is one of the most powerful signals for international visibility. Before assuming your current setup is working, run your URLs through Search Console and a third-party validator. Errors in this system are rarely obvious until ranking data surfaces the damage, and by then, the fix requires rebuilding trust that took months to establish.

International SEO is only growing in importance for U.S. businesses expanding into global markets and for multilingual brands competing domestically. The businesses that get the technical foundation right early build a compounding advantage over competitors still serving the wrong content to the wrong audience. If you are ready to get your international setup audited and corrected, Brandleap Agency handles exactly this kind of work as part of a broader global SEO strategy.