Translation Gets You Read.
Hreflang Gets You Found.
Your site exists in three languages. Google is still sending German visitors to your US store. Here is why that happens, what hreflang tags actually do, and where implementations silently break.
Why Translation Alone Is Not Enough
Translating content is a content decision. Hreflang is a technical signal. Without the latter, search engines guess — and they often guess wrong.
Translation vs. Targeting
A French translation tells visitors what language your content is in. It does not tell Google which country that page is meant to serve. These are separate signals that require separate implementation.
Silent Failures
Hreflang errors rarely throw a visible warning. A missing reciprocal link, a wrong locale code, or a URL mismatch will quietly cause Google to ignore the entire tag set while your analytics show nothing unusual.
English in Multiple Markets
English content targeting the US, UK, and Australia simultaneously is one of the most mishandled scenarios in international SEO. The language is the same; the targeting must differ. Hreflang makes this distinction possible.
<link rel="alternate"
hreflang="en-us"
href="https://example.com/en-us/" />
<link rel="alternate"
hreflang="en-gb"
href="https://example.com/en-gb/" />
<link rel="alternate"
hreflang="en-au"
href="https://example.com/en-au/" />
<link rel="alternate"
hreflang="x-default"
href="https://example.com/" />A Signal, Not a Rule
Hreflang tells search engines which version of a page is intended for which audience. It is a recommendation, not a command. Google weighs it alongside other signals like IP geolocation, browser language settings, and past search behavior.
Understanding that hreflang is advisory changes how you think about implementation. A correct tag set improves targeting significantly. An incorrect one can create confusion that is worse than having no tags at all.
- Correct locale codes (en-US, not en_US)
- Reciprocal links from every alternate page
- Absolute URLs, not relative paths
- Self-referencing hreflang on each page
The x-default Tag
When a visitor arrives from a locale that none of your hreflang tags address, x-default tells Google which page to serve. It is not a fallback for all unmatched users. It is a signal about your homepage or language-selector page.
Many implementations set x-default to the English homepage assuming it will cover everyone. But if your site has a language chooser, that is the correct target. If it has a regional landing page, x-default should point there. The tag has a specific meaning that is frequently misapplied.
Where Implementations Break
These are real patterns observed across international sites. Each one causes hreflang to fail silently.
Missing Reciprocal Links
Page A declares Page B as an alternate. Page B does not link back to Page A. Google requires every page in an hreflang set to acknowledge every other page. One missing link invalidates the group.
Underscore Instead of Hyphen
Using en_US instead of en-US is an extremely common error. The ISO standard uses a hyphen. The underscore variant is not recognized by Google and will be treated as an invalid locale code.
Relative URLs in Tags
Hreflang attributes must use fully qualified, absolute URLs including the protocol and domain. A relative path like /en-us/ is not valid and will be ignored during crawl processing.
Conflicting Sitemap and On-Page Tags
When hreflang is declared in both an XML sitemap and in page HTML, any discrepancy between the two creates a conflict. Google may disregard both sets, leaving targeting undefined.
Canonicals Pointing Away
A canonical tag that points to a different URL than the hreflang href creates a contradiction. The canonical effectively tells Google the hreflang target is not the preferred page, undermining the whole signal.
Reference Materials
Practical documents to keep nearby when working through hreflang implementation or auditing an existing setup.
Hreflang Checklist
A structured checklist covering every implementation requirement: tag format, reciprocal links, URL format, sitemap inclusion, and x-default placement. Work through it before and after any implementation.
View GuideLocale Code Reference
A reference covering the correct ISO 639-1 language codes and ISO 3166-1 region codes used in hreflang. Includes the most commonly confused entries and notes on case sensitivity requirements.
View ReferenceAudit Framework
A step-by-step framework for auditing existing hreflang implementations. Covers how to extract current tags, verify reciprocal links at scale, check canonical consistency, and identify sitemap conflicts.
View FrameworkLocal Business Guide
Specific guidance for physical businesses with a single location wondering whether hreflang applies to them, when it does, and how to handle multi-location scenarios across different countries.
View Guide
Frequently Asked
Questions that come up consistently when businesses first encounter hreflang and international targeting.
Yes, possibly more than you might expect. When the same language is used across multiple distinct markets like the US, UK, and Australia, Google needs explicit signals to serve the right version. Without hreflang, it will often consolidate these pages and serve whichever version it considers canonical to all three markets. Prices, spelling conventions, and product availability can all differ between these regions, so correct targeting matters.
You can, and for large sites it is often more practical. The sitemap approach uses the same logic as the HTML link element approach but declares all alternates inside the sitemap XML. The critical rule remains: every URL in the hreflang group must acknowledge every other URL in that group. The sitemap method does not remove that reciprocal requirement. Mixing both methods on the same site without keeping them synchronized will create conflicts.
There are several reasons. The most common is a missing reciprocal link somewhere in the tag set. Another is a conflict with the canonical tag on the same page. Google also weighs hreflang against other signals, so if the geolocation of your server, your domain structure, and your content all point toward one country while hreflang says another, the tag may be overridden. Hreflang is a strong signal but not the only one.
The x-default value in an hreflang tag designates the page that should be served when no other hreflang tag in the set matches the user's locale. It is not a generic fallback for all users. It is specifically for unmatched locales. If your site has a language-chooser page, that is the correct destination for x-default. If your site has a regional version for most major markets and an English homepage for the rest, the English homepage is appropriate. Pointing it to a country-specific page when you have an unmatched-locale scenario is a common misuse.
Hreflang is not a ranking factor in the traditional sense. It does not make a page rank higher for a given query. What it does is determine which version of your content appears in which country's search results. Correct implementation means the right page surfaces in the right market. This can significantly affect the organic traffic reaching each regional version of your site, which in turn affects conversions and overall performance in those markets.
Each structure has different implications. Country-code top-level domains like .co.uk or .com.au send strong geotargeting signals on their own but require separate link authority. Subdomains like uk.example.com are treated somewhat independently by Google. Subdirectories like example.com/en-gb/ inherit the root domain's authority and are easier to manage at scale. All three can work with hreflang, but subdirectories are often the most practical starting point for businesses adding international targeting to an existing site.