{"id":2574,"date":"2022-12-02T07:30:55","date_gmt":"2022-12-02T07:30:55","guid":{"rendered":"http:\/\/www.rebelytics.com\/?p=700"},"modified":"2025-11-26T10:05:43","modified_gmt":"2025-11-26T10:05:43","slug":"hreflang-canonical","status":"publish","type":"post","link":"https:\/\/www.searchviu.com\/en\/hreflang-canonical\/","title":{"rendered":"How to use hreflang and canonical tags together"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

When you use hreflang as well as canonical tags on your website, you have to be careful not to send confusing signals to Google. Here’s how to implement hreflang when you already have a canonical tag solution on your website.<\/strong><\/p>

Note: This article was first published on rebelytics.com in 2015 and has since then been updated several times and moved to this blog.<\/em><\/p>

hreflang and canonical tags both have similar functions: They suggest to search engines which URLs to index or to show to users in search results. If you already have a canonical tag solution on your website, which asks Google not to include certain URLs, and you then add hreflang tags to all of your URLs, you will most likely confuse Google. You will be asking Google to show and not to show certain URLs to users at the same time.<\/p>

Let’s have a look at what URLs with canonical tags or hreflang annotations “say” to Google:<\/p>

What do URLs with canonical tags want?<\/h2>

A URL that has a canonical tag pointing to another URL says to Google:<\/p>

“Hey Google, how’s it going? I don’t want to be indexed. But you can index my twin sister here instead of me?”<\/em><\/p>

A URL that has a canonical tag pointing to itself says to Google:<\/p>

“Howdy Google, please index me and not my stupid twin brothers.”<\/em><\/p>

Now you have to make sure that your URLs with canonical tags still know what they want after you’ve implemented hreflang on your website:<\/p>

What do URLs with hreflang want?<\/h2>

A URL with correctly implemented hreflang implementations could say to Google:<\/p>

“Bonjour Google, comment \u00e7a va? I speak French and I want to be indexed. Here are my cousins from other countries. Can you please index them too?”<\/em><\/p>

So URLs with hreflang annotations always want to be indexed and always want additional URLs (their equivalents in other language and country versions) to be indexed along with them.<\/p>

What do URLs with canonical tags and hreflang annotations want?<\/h2>

Now let’s see what a URL that has a canonical tag pointing to itself and hreflang annotations says to Google:<\/p>

“Hola Google, \u00bfqu\u00e9 tal? I am the most mature out of my twin brothers and I want to be indexed. I speak Spanish and these are my cousins from other countries. Can you please index them too?”<\/em><\/p>

This is a very clear and easy to follow instruction for Google. But what if the URL has a canonical tag pointing to another URL and hreflang annotations at the same time?<\/p>

“Guten Tag Google, wie geht’s? I don’t want to be indexed, please index my twin brother instead. I speak German, so please index me and here are my cousins from other countries. Please index them too.”<\/em><\/p>

And then Google will say:<\/p>

“What a nutcase! Let’s see what his cousins say.”<\/em><\/p>

And then Google will visit the other URLs in the hreflang annotations and hear a choir of:<\/p>

“Buon giorno,<\/em> \u4eca\u65e5\u306f, \u0434\u043e\u0431\u0440\u044b\u0439 \u0434\u0435\u043d\u044c! We don’t want to be indexed, please index our twin sisters instead of us. But we really want to be indexed, so please? And please, please index all of us because we are all cousins from different countries.”<\/em><\/p>

And then Google will say:<\/p>

“Shut up! I’m not listening to you and I will just figure out who to index myself.”<\/em><\/p>

If you send confusing signals, Google will probably just ignore your instructions. So make sure your URLs know what they want!<\/p>

\"\"<\/p>

Conclusion<\/h2>

If you are using a canonical tag solution on your website, make sure that URLs that have a canonical tag pointing to another URL do not receive hreflang annotations. hreflang annotations are okay for URLs that point to themselves via canonical tag and for URLs that do not have canonical tags.<\/p>

Possible exceptions: Mobile and AMP URLs<\/h2>

I really hope that now, in 202X, very few people are working on websites that have separate mobile URLs or still use AMP. But just in case, here are some additional non-conclusive hints for using hreflang and canonical tags on separate mobile and AMP URLs:<\/em><\/p>

After the announcement of the mobile-first index in 2016, Google changed their recommendations for hreflang on mobile URLs. In the past, it was clear that mobile URLs should have canonical tags pointing to their desktop equivalents and therefore should not receive hreflang annotations. In 2017, the new recommendation was to add hreflang to the mobile URLs and to the desktop URLs:<\/p>

Yes, mobile-to-mobile & desktop-to-desktop is our recommendation for hreflang.<\/p>

\u2014 John \u2606.o(\u2267\u25bd\u2266)o.\u2606 (@JohnMu) November 29, 2017<\/a><\/p><\/blockquote>