en
English Español Deutsch Français Italiano Português (Brasil) Русский 中文 日本語
Submit post
Go to Blog
updated

7 Common Hreflang Mistakes (and How to Fix Them) + Bonus Tip

Kaitlin McMichael updated
7 Common Hreflang Mistakes (and How to Fix Them) + Bonus Tip

It is surprising how often I hear about international SEO discussed without any mention of “hreflang.” If anything, because it is such a tricky subject, it should be discussed more often in conjunction with helping SEO specialists understand how to target international web audiences more accurately.

Not only is it difficult to implement correctly on your geo-targeted sites, but the purpose of hreflang is also commonly misunderstood. It has been around for a few years but SEOs who target international audiences still struggle to figure out how to use this attribute correctly. These are misconceptions even among advanced SEO experts, so make sure you understand how to correctly use it to set up your international sites for success.

The Purpose of Hreflang

Hreflang annotations are meant to cross-reference pages that are similar in content but target different audiences. You can target different audiences with href lang attribute according to their language and/or their country. This ensures that the correct pages will be shown to the correct users when they search on the versions of Google search that you are targeting.

Here is an example of two tags that target English speakers in the USA and English speakers in Canada:

<link rel="alternate" hreflang="en-us" href="http://www.example.com/usa/" />
<link rel="alternate" hreflang="en-ca" href="http://www.example.com/ca/" />

Both of these tags would appear on both pages. This would ensure that Canadians searching on google.ca would find the page targeting Canadians, and Americans searching on google.com would find the page targeting Americans.

Preview: The Ultimate Site Audit With SEMrush

Regular site audits are an integral part of maintaining a healthy website. However a comprehensive site audit (particularly on a large website) isn’t easy, with every technical aspect of a site requiring meticulous attention, with the list of potential problems huge. Frequently, the same mistakes and issues raise their head time and time again. That’s why we analysed 100,000 sites and 450...

Get Free PDF

So that’s the purpose of this tag, but often I come across hreflang mistakes and misconceptions. Here are some of the most common:

Common Mistakes in Implementing Hreflang

Return Tag Errors

Return Tag Errors” are the result of hreflang annotations that don’t cross-reference each other. These can be found within Google Search Console under the International Targeting tab. If your website has hreflang annotations, either via the page tagging method or the XML sitemaps method, there will be data reported on how many tags were found, and how many errors were found. If there are errors, oftentimes those errors are “return tag errors.” Here’s an example of a site that has 412 hreflang tags with errors – all due to “no return tags”):

Return Tag Errors

Your annotations must be confirmed from the other pages. If page A links to page B, page B must link back to page A, otherwise, your annotations may not be interpreted correctly.

Often times, the “missing link” is because the tags do not include a reference to the page itself. Your annotations should be self-referential. Page A should use rel-alternate-hreflang annotation linking to itself.

Using the Wrong Country or Language Codes

When you are adding hreflang codes to your webpages, you need to be absolutely sure that you are using the correct country and language codes. According to Google, “The value of the hreflang attribute must be in ISO 639-1 format for the language, and in ISO 3166-1 Alpha 2 format for the region. Specifying only the region is not supported.”

One of the most common mistakes is using “en-uk” to specify English speakers in the United Kingdom. However, the correct attribute for the UK is actually “en-gb.”

You can use hreflang generator tools like this one to figure out which values you should be using.

Combining Hreflang Sitemaps and Page Tagging Methods

There is no need to use multiple methods for implementation. Google recommends against it, since it would be redundant. You certainly can use both methods, and there is no clear advantage of one method over the other. Here are some considerations for when you are deciding whether to use the XML sitemaps or page tagging methods:

  • Hreflang XML sitemaps can be difficult to create and update. You can use online tools or create it in Excel, but it is difficult to automate the process. If you have sitemaps that your CMS updates for you automatically, it would be better to continue to use those rather than creating separate, static hreflang XML sitemaps.
  • Page tagging leads to code bloat, especially when you are targeting several countries/languages. That can mean an additional 10+ lines of code to each geo-targeted page.
  • Some content management systems, such as WordPress and Drupal, offer automatic page tagging solutions.

Believing That hreflang Annotations Will Consolidate Link Authority

This is another common misconception that can trip up even advanced SEO experts. There have been articles published that seem to show that, once hreflang is correctly implemented across multiple top-level domains or sub-domains, the most authoritative domain gains in link authority. This has not been verified with other international SEO experts, and I have no evidence to believe this is the case either.

The best way to build link authority and consolidate it across your geo-targeted web pages is to keep your content all on one domain. Use a generic, top-level domain such as a .com, and use the sub-folder method to create your country- or language-targeted content. Here is a snapshot of a conversation I had with Gianluca Fiorelli and Martin Kura about this subject:

Twitter Conversation Hreflang

Fixing Duplicate Content Issues

This is another tricky subject that deserves some nuance. Duplicate content itself is often misunderstood, and throwing hreflang into the mix makes it even more difficult to understand. This approach will not “fix” duplicate content issues, per se. For example, when you add hreflang tags to your site, they will appear in the International Targeting tab of Google Search Console (so Google does indeed recognize and understand them), but you will still continue to see Duplicate Title Tags and Duplicate Meta Description warnings in the HTML Improvements tab (if you have pages with duplicate titles and descriptions across your geo-targeted webpages). So if you have two pages in the same language targeting different regions, such as English in the USA and Canada, the content of those two pages may be so similar that they are considered duplicates. Adding multi-language tags will not change that. It is still possible that your American page may outrank your Canadian page, if the American page has significantly more link authority, and especially if it has links from Canadian sources.

However, hreflang tags will help to alleviate this issue. This is why adding these tags is not enough. They provide a technical structure that helps Google sort out and understand your content, but to have a full-fledged international site(s), you need a holistic international marketing strategy that includes building link authority to your site(s) from the relevant countries/languages that you are targeting.

Hreflang is very effective at handling cross-annotations among different languages, but when it comes to same language, different regions, you can get mixed results.

Here is a snapshot of a conversation I had on Twitter with Aleyda Solis about this issue:

hreflang will not eliminate duplicate content

Not Using Canonical Tags and Hreflang Tags Together Correctly

The hreflang tag also can be used along with rel="canonical" annotations, but multi-language tags need to reference self-referential canonical URLs. For example, page A should have a canonical tag pointing to page A, page B should have a canonical tag pointing to page B, and page C should have a canonical tag pointing to page C. All three pages should have hreflang tags that mention all three of the pages in the group. You do NOT want to canonicalize only one version of a page in a page grouping.

Here is a more visual example:

For the United States page (http://www.example.com/usa/), the right usage of the hreflang and canonical tags must be next:

<link rel="alternate" hreflang="en-us" href="http://www.example.com/usa/" />
<link rel="alternate" hreflang="en-ca" href="http://www.example.com/ca/" />
<link rel="Canonical" href="http://www.example.com/usa/" />

And on the Canadian page (http://www.example.com/ca/), the hreflang tags would remain the same, but the canonical tag would be:

<link rel="alternate" hreflang="en-us" href="http://www.example.com/usa/" />
<link rel="alternate" hreflang="en-ca" href="http://www.example.com/ca/" />
<link rel="Canonical" href="http://www.example.com/ca/" />

Not Using Absolute URLs

This one is a heartbreaker because often everything is correct except for the simple fact that the hreflang link referenced is relative rather than absolute. There really is no margin for error with these tags so make sure you are always using absolute URLs. For example, here is what NOT to do:

<link rel="alternate" hreflang="en-us" href="/usa/" />
<link rel="alternate" hreflang="en-ca" href="/ca/" />

Google wants to be able to crawl the entire URL path, especially since many times hreflang tags reference separate ccTLDs or sub-domains.

Adding hreflang tags to noindexed pages

If you have hreflang tags that point to a page that is noindexed, either with a meta-robots noindex tag or blocked in robots.txt, then Google will report that tag as an error. Google will not be able to follow the return link from that blocked page back to the originating link, so it will report a return tag error. It's important to note that this does not mean ALL your multi-language tags in a page group will suddenly stop working; it means ONLY the pages that are blocked, and their return links, will stop working. As a general rule of thumb, just don't create hreflang tags that point to pages that are blocked from Google's indexing. 

These tips should be enough to get you started with trouble-shooting your international rankings issues. Hopefully, this has been helpful, and feel free to check out my previous blog post on SEMrush about how to choose the right site structure for your international sites.

Find out more about hreflang implementation issues from SEMrush Study: 13 Most Common Hreflang Mistakes

Get a free 7-day trial

Start working on your online visibility

Please specify a valid domain, e.g., www.example.com

Kaitlin McMichael
Pro

Asks great questions and provides brilliant answers.

Kaitlin McMichael specializes in SEO and has a blog at Kate Ideas Marketing. She has been working in the digital marketing sphere since 2010, and has written on SEO, travel, music, and the arts for dozens of websites and magazines. Follow her on Twitter.

Send feedback

Your feedback must contain at least 3 words (10 characters).

We will only use this email to respond to you on your feedback. Privacy Policy

Thank you for your feedback!