Publishing your website in multiple languages is a big step. You spend time translating content, adapting product pages, and making sure visitors from different countries feel at home. Then something frustrating happens: a customer in Germany finds your English page, while someone in the United States lands on a version intended for the UK.
This is where hreflang comes in.
Hreflang helps Google understand which version of a page is intended for a particular language or region. It sounds straightforward, but small implementation mistakes can prevent Google from interpreting those relationships correctly.
The good news? Most hreflang problems are fixable once you know what to look for.
Here are seven mistakes worth checking before they affect your international SEO efforts.
1. Forgetting Reciprocal Hreflang Tags
Imagine you have two versions of a product page: one for American customers and another for British customers.
Your American page references the British version, but the British page doesn’t reference the American one.
That missing return link creates a problem.
Google expects hreflang relationships to work in both directions. Without reciprocal annotations, it may ignore the relationship between the affected pages.
How to fix it:
Make sure each localized version references the other relevant versions, including itself.
For example, if you have English pages for the United States and United Kingdom, both pages should contain the same set of hreflang annotations.
Whenever you launch a new translated page, update the annotations across its existing language alternatives.
2. Using Incorrect Language or Country Codes
This is one of those mistakes that can go unnoticed for months.
Suppose you’re targeting English-speaking visitors in the United Kingdom. You might assume en-UK is correct.
It isn’t.
The correct hreflang value is en-GB.
A few common examples:
Target audience
Correct hreflang
English speakers in the USA
en-US
English speakers in the UK
en-GB
English speakers in Australia
en-AU
French speakers in Canada
fr-CA
German speakers in Germany
de-DE
The first part identifies the language. The optional second part identifies the region.
How to fix it:
Check your codes against the supported language and region standards.
Don’t assume a country’s familiar abbreviation is the correct technical code.
Google’s official hreflang documentation explains the supported formats and provides examples.
3. Leaving Out Self-Referencing Hreflang Tags
Here’s a detail that’s surprisingly easy to miss.
Your English page points to its French and Spanish alternatives, but it doesn’t include its own URL in the hreflang set.
Google recommends that every localized version include a reference to itself.
For example, a US English page should contain an en-US annotation pointing to its own URL, alongside annotations for the other versions.
How to fix it:
Check the hreflang annotations on every localized page.
Each page should reference itself and the other relevant language versions.
If you’re generating tags manually, this is an especially useful item to include in your pre-publication checklist.
4. Pointing Hreflang Tags to Broken or Redirected URLs
A translated page might have worked perfectly when you first published it.
Six months later, someone changes its URL, deletes it, or adds a redirect.
The original hreflang annotation is still there, pointing to an outdated destination.
Now Google has to interpret an international page relationship that no longer matches the current website structure.
How to fix it:
Review your hreflang destinations after migrations, redesigns, and URL changes.
As a practical rule, alternate URLs should point directly to the intended, accessible localized pages rather than relying on redirect chains.
Check that those pages are indexable and haven’t been accidentally blocked.
This is particularly important for large ecommerce websites, where product URLs can change frequently.
5. Confusing Canonical Tags With Hreflang Tags
Canonical and hreflang annotations solve different problems.
A canonical tag identifies the preferred URL among duplicate or similar pages.
Hreflang identifies language or regional alternatives.
Problems arise when site owners assume that every translated page should have a canonical pointing to one main-language page.
For genuinely distinct translated pages, this can send conflicting signals about which URLs should be indexed.
How to fix it:
For separately indexable translated pages, use appropriate canonical URLs and connect the localized versions with hreflang.
Regional pages containing substantially duplicate content require more careful canonical decisions.
Don’t apply one universal canonical rule to every international website.
Google provides additional guidance in its documentation on managing multilingual and multiregional websites.
6. Ignoring the X-Default Hreflang Value
What happens when someone visits your international website from a country you haven’t specifically targeted?
Perhaps you have versions for the United States, Germany, and France, but no dedicated version for visitors elsewhere.
The x-default annotation can identify a fallback URL for users who don’t match your specified language or regional alternatives.
It’s particularly useful when your website has a language selector or an international landing page.
How to fix it:
If your website needs a fallback experience, choose an appropriate default page and include it in your hreflang configuration.
You don’t need to create a separate page for every country.
A well-designed language selection page may be more helpful than sending visitors to a region that doesn’t match their needs.
Remember that x-default is a fallback annotation, not a replacement for properly configured language-specific tags.
7. Generating Hreflang Tags Without Checking Them
Generating hreflang code is only the beginning.
A perfectly formatted tag can still point to the wrong page. Likewise, a correct list of URLs can fail because one localized page is missing its reciprocal annotations.
This is why international SEO needs a validation process, not just a code-generation process.
How to fix it:
Before publishing your hreflang configuration:
Confirm that every localized URL is correct.
Check the language and region codes.
Include self-referencing annotations.
Verify reciprocal relationships.
Check the destination pages for redirects and indexing problems.
Review canonical compatibility.
Test the implementation again after major website changes.
You can use the free Hreflang Tag Generator by Degates to prepare hreflang markup for your international pages.
Once you’ve generated the tags, review the actual implementation on your website. Generating code and validating live pages are separate tasks.
Should You Use HTML Tags or an XML Sitemap?
There isn’t one universal answer.
Google supports three methods for communicating localized page relationships:
HTML link elements
HTTP response headers
XML sitemaps
For a small multilingual website, HTML annotations may be convenient.
For a larger website with hundreds or thousands of localized URLs, XML sitemap annotations may be easier to manage centrally.
HTTP headers can be useful for non-HTML resources, including PDFs.
Google treats these methods as equivalent for hreflang purposes. Implementing all three doesn’t provide an additional search benefit and can make maintenance more complicated.
Choose the method that fits your website’s technical setup and that your team can maintain accurately.
How Often Should You Audit Hreflang?
There’s no mandatory audit schedule.
A small website with five translated pages might only need periodic reviews and checks after changes.
An international ecommerce store with constantly changing inventory may need automated monitoring.
At a minimum, revisit your implementation whenever you:
Publish a new language version.
Change a localized URL.
Remove a translated page.
Migrate your website.
Modify canonical settings.
Change your international site structure.
The important thing is to treat hreflang as an ongoing part of website maintenance.
Frequently Asked Questions
Does hreflang improve Google rankings?
Hreflang is not a direct ranking boost. Its primary purpose is to help Google show an appropriate language or regional version of a page. Correct implementation can improve the relevance of the search experience for international visitors.
Can I use hreflang on an English-only website?
Yes, if you maintain separate regional versions, such as pages for the United States, United Kingdom, and Australia. You don’t need multiple languages to use hreflang.
Is hreflang required for multilingual SEO?
No. Google can discover language variations without it. However, hreflang provides explicit information about relationships between localized pages and is recommended when applicable.
Can hreflang be added through an XML sitemap?
Yes. Google supports hreflang annotations in XML sitemaps. Each localized URL needs the appropriate alternate-language references.
What happens if hreflang tags are incorrect?
Google may ignore affected annotations or fail to associate localized pages as intended. This can result in visitors encountering a less appropriate language or regional version in search results.
Final Thoughts
International SEO involves more than translating a website.
You need to make sure search engines understand how your localized pages relate to one another.
The most common hreflang mistakes aren’t necessarily complicated technical failures. They’re often small oversights: a missing return link, an incorrect region code, an outdated URL, or a canonical configuration that doesn’t match the site’s international structure.
Start with the basics. Keep your localized URLs organized, verify reciprocal annotations, and review your setup whenever your website changes.
If you’re preparing hreflang markup for a new multilingual project, try the Degates Free Hreflang Tag Generator and check the generated code before adding it to your website.
Getting hreflang right won’t replace high-quality translations or a solid international SEO strategy. But it can help Google understand which version of your content belongs in front of the right audience.
Leave a Reply