Monday, December 05, 2011 at 8:07 AM
Many websites serve users from around the world. There are different approaches to serving content appropriate to your users' language and/or region. Last year, we launched support for explicit annotations for web pages rendering the same content with different language templates.Today we're going further with our support for multilingual content with improved handling for these two scenarios:
- Multiregional websites using substantially the same content. Example: English webpages for Australia, Canada and USA, differing only in price
- Multiregional websites using fully translated content, or substantially different monolingual content targeting different regions. Example: a product webpage in German, English and French
Specifying language and location
We've expanded our support of the rel="alternate" hreflang link element to handle content that is translated or provided for multiple geographic regions. The hreflang attribute can specify the language, optionally the country, and URLs of equivalent content. By specifying these alternate URLs, our goal is to be able to consolidate signals for these pages, and to serve the appropriate URL to users in search. Alternative URLs can be on the same site or on another domain.Annotating pages as substantially similar content
Update: to simplify implementation, we no longer recommend using rel=canonical.
Example usage
To explain how it works, let’s look at some example URLs:- http://www.example.com/ - contains the general homepage of a website, in Spanish
- http://es-es.example.com/ - is the version for users in Spain, in Spanish
- http://es-mx.example.com/ - is the version for users in Mexico, in Spanish
- http://en.example.com/ - is the generic English language version
<link rel="alternate" hreflang="es" href="http://www.example.com/" />
<link rel="alternate" hreflang="es-ES" href="http://es-es.example.com/" />
<link rel="alternate" hreflang="es-MX" href="http://es-mx.example.com/" />
<link rel="alternate" hreflang="en" href="http://en.example.com/" />
If you specify a regional subtag, we’ll assume that you want to target that region.Keep in mind that all of these annotations are to be used on a per-URL basis. You should take care to use the specific URL, not the homepage, for both of these link elements.


102 comments:
Is this limited to the <link>-tag, or do you also support rel="alternate" and hreflang on <a>-tags?
This is supported for link elements only (html-header or http-header). On anchor elements it would not be immediately obvious if this links to the same content for another language/region or something completely different.
Great resource, but not that easy to implemente, the combination of rel canonical and rel alternate could be tricky.
The original version of this required rel=canonical, but it's not clear from this post whether this is still required - please can you confirm?
Christopher, the specs clearly say that the combination of rel="alternate" and hreflang on an <a>-element indicate that the hyperlink refers to the same content as the current page in a different language, exactly like the <link>-element.
I just ask because one of our websites has hyperlinks to other languages for the current page using the appropriate attributes <a href="/nl/page.html" rel="alternate" hreflang="nl-BE">Dutch</a>
I wouldn't want to have to add a bunch of <link>-elements with exactly the same information.
The sites that really need this are often large multinationals that have expensive, unwieldy CMSs that can't be modified to accommodate new header tags. I wonder how many large companies will adopt this.
What should we do for Quebec region ?
CA-FR ?
Benoit: fr-CA
Hi,
We're launching into many European countries early in 2012, having the entire website translated into the appropriate languages.
Our original intention was to use completely different domains, such as www.website.fr, www.website.de. However, will there be more benefit to target the language pages, as stated above, from our existing .com site?
With regards to these changes, what is the impact of them on getting the new language pages crawled and ranked by Google?
Thanks in advance
Do any of the other link tag relationships work?
http://www.w3.org/TR/html401/struct/links.html#h-12.3.3
Christopher, I have to agree with Tommy, wouldn't it be simpler, as most mutliligual websites use country selection menus to allow the rel tag to be used and recognised within anchors on those menus. Therefore I could deploy one set of menu code across all language variations of a site and not have to mess around with page headers?
I presume that you don't support this because as in body code it could be much more easily hackable. IE: people pasting in the tags into comment boxes etc to steal PR.
@Ian Rel-canonical is no longer required. It is suggested for highly similar content in the same language. Not recommended for different language content, or for strong content variations.
@Kangorimo annotating the .com page with all regional variations (as well as the other way round) certainly makes sense and helps on discovery.
As for ranking, it is one of many input signals.
@Christopher_Semturs Do you think annotating the pages to the .com site makes more sense that using ccTLDs? We have already purchased the new domain names, but were wondering whether today's announcement changes what the best practice would be for a site such as ours that is just about to launch in to foreign markets.
This is a good development and helps to resolve an issue I have faced with several pan-european and global clients. Maybe the next step will be to provide markup for mobile content. As with the issue of near-duplicate content for two countries using the same language, most mobile sites will under normal circumstances provide similar or identical content to the sites from which they have been adapted. What we need is a solution to avoid duplicate content issues as well as acting as a sign-post for mobile search results.
@Kangorimo
there is no contradiction. You could:
- put the regionalized content on the TLD-variations (E.g. on example.de and example.fr).
- on all pages that you have (example.com/example.de/example.fr) annotate all 3 of them with rel-alternate-hreflang
The annotation tells where the language/region-variation is to be found, not that the .com page covers that region/language as well.
The help center article can guide you through a more detailed example.
@Christopher_Semturs: You say "[Rel=canonical] is suggested for highly similar content in the same language."
Do you mean on different TLDs? If so, wouldn't that send linkjuice just to, say, the .de version of a site leaving the .at and .ch version juiceless? And wouldn't that lead to only the .de version being presented in the SERPs?
@sfi think of it in a different way.
Step 1) Google decides to show your URL for a search result (e.g. your canonical example.de)
2) The user searches on google.at in German, and you defined:
link rel="alternate" hreflang="de-at" href="http://example.at"
on the canonical. So it will show example.at as the url instead of example.de
(same is true for all subpages).
Hi,
i have a question about these link tags.
We have a multilingual site, for example:
http://www.domain.de/de/
http://www.domain.de/at/
In Germany (de) and in Austria (at) they speak German.
To avoid duplicate content, we blocked /at/ in our
robots.txt, because Germany is our main country.
Is it recommended to remove this pages from robots.txt
if we add these link-tags per page, for each country we
support?
We have more issues with "duplicate content" on other
pages. f.e. our greece homepage is currently in english,
which would give us duplicate content to /gb/ etc.
Is this problem solved with that link-tags?
@Beerweasle
This means you have content on
/de/
/at/
/gb/
/gr/
?
You should definitely let Google crawl all of them (robotting out for controlling indexing is not a good idea).
in addition, decide for each page which language/region it represents, establish your link-rel-alternate-hreflang block and put it on all pages, e.g.:
link rel=alternate hreflang=de-at href=domain.de/at/product?id=3
link rel=alternate hreflang=de-de href=domain.de/de/product?id=3
link rel=alternate hreflang=de href=domain.de/de/product?id=3
link rel=alternate hreflang=en-gb href=domain.de/gb/product?id=3
...
and put it on all pages.
In addition, to mark highly similar content, you can use rel-canonical. For instance, on the page domain.de/at/product?id=3
link rel=canonical href=domain.de/de/product?id=3
that should work just fine.
@Christopher Semturs:
Yes, we have content on /de/ /at/ etc.
We were worried about duplicate content on /de/ and /at/ .. and we don't want that german customers use the /at/ website, and reverse.
So the best solution for us was to disallow /at/ on robots.txt
So you think, with hreflang-link on every page for each language and a canonical link on the "foreign page" would be fine?
@Beerweasle
Yes, that should work fine (hreflang and - in your case - combined with rel-canonical).
Just one last question:
if i have a page /de/search.html?word=blablaba
Whats the Language equivalent - or should i set it?
/at/search.html?word=blablaba
Whats the canonical to that?
/de/search.html?word=blablaba
or
/de/search.html
( Parameter "word" changed the content of the page, of course )
@Beerweasle
it would be
/de/search.html?word=blablaba
(there should be a 1:1 mapping between /de/* and /at/* in case of identical content).
If I have same content but different country target appearing correctly in Bing, using canonical link elements will break this.
What happened to Google and Bing working together on CLE's? It seems you are now using them in completely contradictory ways.
If you are a fairly large corporation, with i.e. 50-60 (or more) different TLD's, each containing the same content, should you then make a list in your header with 50-60 extra lines of code, one for each version of the page?
I can see this make perfect sense for fixing .us, .co.uk, .ie, .au and various other instances where different locations speak the same language, but would the correct use of the tag be to list only the true duplicates, intended for other languages, or to make a comprehensive list?
A comprehensive list would still be helpful, but you might want to issue regionalized searches on Google to see where you need to take action and where you are happy with the results.
Be aware that you can send the link-tag also in the http-header instead of html-header if that helps (e.g. so that it is not sent to real web-clients so that the page renders faster).
So this is a 'new' tag? The HTML 4 specification since 1999 have listed this tag:
http://www.w3.org/TR/1999/REC-html401-19991224/struct/links.html#adef-hreflang
I'll probably do this to one of client who have a resort and wanted to have it in English and French..
Thanks for this information
@Christopher Semturs: Going back to Tommy's point from earlier, there are now two cases where you might use the rel/hreflang attributes:
1. On link elements (as described in your post)
2. On anchor elements that link to content in other languages
Are you saying that we should only use these attributes for case 1 and not case 2? Does Google even support case 2?
@PaulD please annotate hreflang on the link-tag (Either html-header or http-header).
Heelo,
I have problem with url modifications my software it is too complicated.
Now look my url like
www.examle.com/?language_id=21 for german
what I can do ?
as you can see in the help center article, that annotation does not require URL modifications, adding the annotation on all involved pages is sufficient.
This might be just what I've been looking for.
We run a travel/local search site, localized into a dozen languages, and what we've been doing so far is using robots.txt to avoid the duplicate content on, for example, .de and .at.
So, if a restaurant was located in Austria, we'd block indexing of the page on our .de site (using robots.txt) so that the same restaurant wouldn't appear twice in German.
Am I to understand that I can now stop doing that, as long as I mark the Austrian site pages as the alternate for de-AT? In our case, the two restaurant pages would often be *indentical* , i.e. http://www.example.de/some-restaurant and http://www.example.at/some-restaurant would have the same content.
Or should I still try to sculpt this with robots.txt?
Hi,
first important message: Try to never use robots.txt for controlling indexing. Use the no-index tag.
http://code.google.com/intl/de/web/controlcrawlindex/docs/robots_meta_tag.html
In your scenario using rel-alternate-hreflang, combined with rel-canonical, sounds like a perfect match. You must enable Google to fetch all variations (aka not block in robots.txt).
Thanks for your fast reply. I'll implement these changes on our sites immediately. This may solve the problem that our .ca, .co.uk, .at, .ch, etc. sites never seem to get any traffic despite the fact that they are indexed by the GoogleBot.
How will this look if you have an international website with appr. 150 subdirectories (all representing a different country)?
Of these 150 subdirectories (countries) 110 are using English (no local translation available) and are in essence duplicate from each other.
We can canonicalize all of these URLs to the UK version, but how can we best implement the rel="alternate" hreflang="x" tags?
Does this mean we will have 150 alternate tags on top of the source code (or HTTP header)?
Also; is it recommended to also add all of the subdirectories (countries) to GWC individually and set targeting there?
I have three sites with similar but not identical, content. Our biz has offices in US, UK and AU.
We use Domain Access to allow each office to update content as needed, but much of the content is identical.
Does the use of Domain Access affect how well the hreflang element works? Does it matter that one of the sites is a ccTLD and the other two are subdomains?
Also, if you specify a canonical, do you only use the hreflang tag on the canonical versions of the pages?
How to deal with images? (when duplicated image appears on different localized pages, with localized alt attributes)
@Joni 110 English-language variations sounds a little bit too much to me. Are they really all somehow different? Feel free to post the real example, either here or via a G+-message.
@JLSW
a combination of ccTLD-URLs and sub-paths or sub-domains does not matter. We advise to annotate all of them (on the page level), not only the canonical.
eradrix:
Giving a concrete example would enable me to answer this question better, but to give a general answer:
Sounds like you consider the images as part of the page. As such, annotate the pages and you are fine.
I have just implemented this across the 3M Corporation's public facing sites. Since we already did something similar to this on all of our pages it was a snap to implement. Glad to see that Google is finally allowing us to link our country sites together in a smart fashion.
Does this means the answer of this question is a YES. The same content displayed on different cross domains like ccTLds will be considered as duplicate.
http://www.youtube.com/watch?v=Ets7nHOV1Yo
Do using the hreflang along with rel=cannonical will solve the issue of Dup content and you will be able to pick the desired domain for the purpose of SERP as per the region?
Would a site like a.co.uk will rank in UK and a.com in USA for the same query using mostly the same content depending upon the visitor's location?
Regards
Alicka
@Amjad Khan
Yes, that's correct
@Christopher,
thanks for the explanations!
What I have not understood yet: if the similar content is on different TLD, should I / can I also specify the rel on cross-domain basis?
like so:
link rel="alternate" hreflang="de-DE" href="http://www.example.de/"
link rel="alternate" hreflang="de-CH" href="http://www.example.ch/"
What I am trying to achieve is that people searching with google.de find the domain.de and people using google.ch are directed to domain.ch (without risking Duplicate Content issues)
@David cross-TLD will work
Hi Christopher
Thanks for all your help on this.
Can I check the interplay between rel=canonical and rel=hreflang?
Suppose I'm on a page that needs a canonical URL, e.g. ...
domain.de/at/product?id=3&color=blue
In this example, color=blue causes a blue image to be shown by default, and the blue value to be preselected in the color choice dropdown - no significant content changes, so the canonical URL should not contain the color query parameter. Following on from your post on December 8 at 1:43AM then, the canonical URL would be
domain.de/de/product?id=3
i.e. it would be in the /de/ rather than /at/ subdirectory, and it would have the color query parameter removed.
Question: should the hreflang URLs ALSO have the color query parameter removed, e.g.
link rel=alternate hreflang=en-gb href=domain.de/gb/product?id=3
or should they keep it?
link rel=alternate hreflang=en-gb href=domain.de/gb/product?id=3&color=blue
If we keep it, we'll be in a situation where the canonical matches none of the hreflang hrefs. Also, through those hrefs, we'll be providing links to a lot of URLs that we don't really want crawled and indexed.
If we remove it, given a URL whose content contains a set of hreflang hrefs, that URL will not appear in that set. The hreflang href would be acting a little like the canonical href. Would that be OK?
Can we specify Province or State with that new mark up and target specific language ?
e.g french in Ontario, Canada ?
Thanks a lot
@Lisa no, this is on the country level
I hate to use the "B" word, but isn't it true that if you use Rel=canonical on any page, then BING and other search engines will treat this as a 301 redirect?
I have a website whose root is targeting the USA. I have a subdirectory 'UK' that is targeting the UK. Due to international shipping costs, taxes, etc I'd prefer ALL other traffic to go to the UK equivalent page.
I could take the suggestion from this post and use a rel=canonical for the 'http:/www.../uk/' page and then provide an rel=alternative hreflang=en-us for the NON 'http:/www.../uk/' page.
However, wouldn't this be committing content-suicide to my USA content in BING and other search engines?
Is it possible to refer hreflang on 301 sites ?
We have different agencies - one in germany, the other in india.
link rel="alternate" hreflang="en-IN" href="http://example-india.com/profile/1028/john-smith.html"
link rel="alternate" hreflang="de" href="http://example.de/profile/1028/john-smith.html"
but the linked "de" page will 301 redirect to:
http://example.de/profilseite/1028/john-smith.html
the second uri segment is always multilanguage and it will be very heavy to implement such a change in my codebase .. does the may crawler recognize the 301 for hreflang ? to keep the uri segments untouched and change only domain ?
@DavidK I can't talk on how other search engines are handling this, sorry.
@crosscode
that would work, yes. Will the other direction work as well for you? Remember, this annotation needs to go both directions.
I had to laugh when I read the title of the post: "New markup for multilingual content"
I use that technique since 2001, and I posted that markup bit and advice at the forums WebProWorld back in October 2006.
A member there and blogger picked up my post and wrote a blog post here in 2006: http://www.orionsweb.net/2006/10/multilingual-websites/
So is that called now "New Markup"? LOL
Hi Christofer,
We have a website with a setup like this
domain.com/en/product
domain.com/es/product
domain.com/de/product
domain.com/it/product
etc
All in its own language
now we would like to target english in UK and USA seperately.
If i follow you corretly my approach would be:
Have the following URLs:
domain.com/en/product
domain.com/en-uk/product
domain.com/en-us/product
On each page I add the following
link rel="alternate" hreflang="en" href="http://www.domain.com/en/product"
link rel="alternate" hreflang="en-UK" href="http://www.domain.com/es-uk/product"
link rel="alternate" hreflang="en-US" href="http://www.domain.com/es-us/product"
(+ all other translations)
link rel="canonical" href="http://www.domain.com/en/product.html"
(Only on these 3 pages as other languages link to other canonical versions)
With this I make sure that each visitor from a specific country gets its designated page shown and the canonical tag makes sure there is no duplicate content issue.
This ofcourse we implement for all language issues for multiple countries like german french etc.
Is this the right approach?
Really appreciate the help!
Regards
Ide
@isdke yes, that will work.
you might want a more complete setup though:
- ALL link-rel-alternate-hreflang on all pages (that includes /de, /en-uk, /en, ...)
- on the english-related pages, the rel-canonical (for /en) as well.
Hi Christopher,
Thanks for your reply.
With “(+ all other translations)” I indeed meant alternate links on al language versions on the website.
So basically this means that the canonical version of a set of pages will always rank in google serps but depending on the users local settings it would show a different snippet?
For instance a US based searcher will see
1. the title of domain.com/en/product because the snippet always shows the canonical title.
2. The meta-description of domain.com/en-us/product
3. the URL of domain.com/en-us/product
And for UK bases searchers same title but with description and URL of the domain.com/en-uk/product page
IS this right?
If so, since it is actually the canonical page that ranks, will after clicking people also land on the canonical version or will they be "redirected" to the URL version shown in the serps?
Last question: Will this actually improve/help rankings? Because we tell google which page we specifically want to target per country, or even more specific, per language setting in a country.
Thnaks!
Ide
@ldske
Please read
http://support.google.com/webmasters/bin/answer.py?hl=en&answer=189077
section at the end. In the info-box it says that the title/snippet of the canonical should be neutral (e.g. not mention US) if you want to use rel-canonical. Otherwise don't use rel-canonical. :-)
Hello,
I have a website fot people in Netherlands. Website is dutch languange and i want to publish turkish articles for people who lives in Netherlands.
What do u advice me to do? Make a new subdomain with tr-nl.domainname.com or?
Thank you for your help?
@ali
http://support.google.com/webmasters/bin/answer.py?answer=182192
should contain all the answers you need for proper URL naming.
Hi Guys,
I implemented the canonical and hreflang on our site.
we have a domain.com.au (main site)
which ranks top 10 for most of our search words.
we decided to create 2 duplicates at .co.nz and .co.uk for the New Zealand and UK markets.
The problem is that our rankings here is extremely low, around the 90 >100 mark.
I thought I could solve this by doing some link building towards those domains .co.nz and .co.uk. from websites in the UK and NZ. The problem now is that these links are showing up under the .com.au domain according to Google Webmaster tools and not under their respective country domains (0 links).
Also when I check webmaster tools for the co.uk and co.nz pages there is absolutely no search traffic even though I see from our web analytics that we are being found sometimes on those pages.
Why is this happening, and how do I fix this?
Thanks,
Erik Withoud (ClickHome)
@Erik
the webmaster tools don't reflect the localized counts if you use rel-alternate-hreflang together with rel-canonical.
Are your URLs showing up on a search on google-new-zealand? If not, it's likely that something went wrong on your annotation. Post your real URL and I could take a look.
Hi Christopher,
yes they are showing up in NZ as .co.nz
please check the website www.clickhome.com.au and www.clickhome.co.nz
Hello Cristopher,
We have a very strong domain (example.com) in Spain ranking in top 10 for most query searches.
We have other domains targeting different countries (example.cl, example.pe, example.com.ar, example.fr some of them use the same language than the original, some of them don't. Also some of them have the same identical content, and some of them have modified content, and some of them very different content.
Let's imagine the following url's:
example.com/hotels-new-york/ (100 hotels in spanish targeting Spain)
example.cl/hotels-new-york/ (same 100 hotels than .COM in spanish targeting Chile)
example.pe/hotels-new-york/ (100 DIFFERENT hotels than .COM in spanish targeting Peru )
example.com.ar/hotels-new-york/ (100 similar hotels than .COM in spanish targeting Argentina)
example.fr/hotels-new-york/ (100 hotels similar than.COM in italian)
Right now, we don't have any tag, and sometimes .COM ranks better than other domains in the domain country.
Is it correct to add the alternate url even if the content is not the same, but targets the same keywords?
link rel=alternate hreflang=es href=http://www.example.com/hotels-new-york/
link rel=alternate hreflang=es_cl href=http://www.example.cl/hotels-new-york/
link rel=alternate hreflang=es_pe href=http://www.example.pe/hotels-new-york/
link rel=alternate hreflang=es_ar href=http://www.example.com.ar/hotels-new-york/
link rel=alternate hreflang=fr_fr href=http://www.example.fr/hotels-new-york/
With this Google should know the prefered version for each country, after this, which is the advantage of adding a rel=canonical ?
@Carlos M:
yes, add the hreflang annotations. For your scenario, simply ignore the rel-canonical part (it is purely optional).
We have numerous language/domain combinations and have a question.
Will Google ignore these for the domain it is on? Like if .com is our strongest domain, and we put a "link rel=alternate" to our .de domain (and all others), what will happen if the .de link is still in the header on the .de site?
Should every domain have an alternate link for all domains other than itself? Is there any harm done in including the same code for all domains?
Hi Johann,
look at the example in
http://support.google.com/webmasters/bin/answer.py?hl=en&answer=189077
You are encouraged to add the self-link as well (means: to have the same hreflang-block on all affected pages).
I posted question in google groups, but no answer. Probably some one here could help me.
http://groups.google.com/a/googleproductforums.com/forum/#!category-topic/webmasters/crawling-indexing--ranking/CFDKQ_qfKYg
My site's URL (web address) is: www.example.com, www.example.ca
Situation:
www.example.ca - canadian IP and https://www.google.com/webmasters/tools/settings:"Your site's domain is currently associated with the target: Canada" - done long time ago.
head
link rel="canonical" href="http://www.example.ca/"
link rel="alternate" hreflang="en-us" href="http://www.example.com/"
link rel="alternate" hreflang="en-ca" href="http://www.example.ca/"
link rel="alternate" hreflang="en" href="http://www.example.com/"
www.example.com - US IP and https://www.google.com/webmasters/tools/settings:"Geographic target Target users in: United States" - done long time ago.
head
link rel="canonical" href="http://www.example.com/"
link rel="alternate" hreflang="en-us" href="http://www.example.com/"
link rel="alternate" hreflang="en-ca" href="http://www.example.ca/"
link rel="alternate" hreflang="en" href="http://www.example.com/"
Differences: Prices and some minor changes in design.
cache:www.example.com - shows .ca version, with snapshot's date after rel="alternate" had been added.
Results: In us example.com pages do not appear in search results. Some times www.example.ca pages do, but they are even close so well ranked as example.com pages before.
Question: What we are doing wrong?
@424242 Your description looks fine, so to take a deeper look at the annotations in your HTML I'd need the actual page please.
@Christopher Semturs
Is any way to share real site address with you with out posting it on public blog?
Any way we changed both canonical tag to .com site, we will see if this work.
@424242 you can always use a link-shortener, e.g. goo.gl
@Christopher Semturs
http://goo.gl/QtNg7
Thanks.
that looks fine
@Christopher Semturs
Now main page disappear from cache:
404. That’s an error.
The requested URL /search?client=ubuntu&channel=fs&q=cache%3Aoursite.com&ie=utf-8&oe=utf-8 was not found on this server. That’s all we know.
No messages in webmastertools, and Fetch as Googlebot works fine.
answer on my last question:
http://productforums.google.com/forum/#!category-topic/webmasters/crawling-indexing--ranking/mNExmXEr4a8
whats the effect on the linkpower.
if i had a .co.uk, a .com and .ca domain would they all share the same linkpower?? if it has some effect on the linkpower what if the .ca adress gets penalized for "unnatural linkbuilding" would the other two domains get penalized as well??
Please try to answer very specificaly ;-)
Would really appreciate some help. We run an international site that offers information and books on buddhism and meditation.
You can see the site here and how it's broken up to serve different countries and languages:
goo.gl/76bsx
The issue is that something may be in English but based on where people are, different regional offices will fulfill the order.
The problem we have is that each version in the same language has all of the same content. So for example, the english version targetted for UK and Australia will have the same content as the English version targetted for the USA.
We would like it so that the subfolders don't have duplicate content problems, and so that based on the country where a user is search engine, they will get that version of the site.
Would this new markup be appropriate, and how?
We are using subdirectories:
site.com/us
site.com/uk
site.com/au
Etc. Thanks so much for your help.
@PrayForNathan Your site is a perfect candidate for this annotation. Please refer to the help center article ( http://support.google.com/webmasters/bin/answer.py?hl=en&answer=189077 ) for details on how to implement it.
Hi Christopher,
Any news about using the a tag instead of link tag? Still Google doesn't take this into consideration? It would be so convenient, as we, like many site owners, have already the links to the multilingual pages in the html bodies of each page.
Thanks,
Chris
As of now there are no plans to start using the information in the a-tag as well.
Hi Christopher thank you so much for answering my question. I was wondering if you might be able/willing to give me further clarification.
The page URLs on tharpa.com are all like this:
tharpa.com/country/book
Which means that right now Tharpas UK & US need unique URLs to promote common book content.
However, we'd like one common URL for publicity and promotion purposes that would lead people to their respective country (i.e. UK or US). For example, we could have a URL such as tharpa.com/esh (for Eight Steps to Happiness) and then when people typed this in they would automatically be redirected to tharpa.com/uk/esh or tharpa.com/us/esh.
Therefore, tharpa.com/esh would have lots of content (videos, etc) and we would widely promote that URL in social media, press releases, Adwords, etc, but that page would be a redirect only.
The reason for it being a redirect and not a static page where people then add to cart based on the country is because we don't want to send people to a static stand-alone page, we want to send them to a fully functioning website. And the website only really functions if people see prices in their currency, etc. If they have to choose their country, it's not seemless or ideal.
Would this markup still work in this way? If not, what would be a viable solution for us? We really appreciate your help/guidance, thank you!
While you redirect for end-users, I guess you can simply save the redirect for users coming in via search results by using the hreflang annotations. Is this what you are looking for?
Other than that, my advice would be to bring those questions to the webmaster forum so that others can benefit from your answers as well. This blog-post is not a support forum. :-)
Hi Christopher,
Is there a problem if the < link >-tag are not set on the main page because of technical limitations?
Will we suffer if only the translated page are "linked" together but all points toward the source page?
@Romain it must be bi-directional
Since implementing alternate tags to our site, we started getting complaints from visitors that were being redirected to other versions of our sites, and often ones that weren't appropriate for them. It seems as though including these tags triggers some clients (possibly even anti-virus software) to actually download all these alternate versions, which can have unintended consequences.
@david Shearon
that is the first time we hear about this.
Can you share more details with me via Google+? I'd like to investigate.
Hi Christopher,
I've just noticed the advice has slightly changed to strike out the rel=canonical section.
The language is a little unclear, though - Does this mean that you don't RECOMMEND it, due to the difficulty of implementation, or that implementing rel=canonical will be IGNORED in conjunction with rel=alternate hreflang?
(i.e. as a similar example, the way that nofollow functionality changed to stop people pagerank sculpting back in the day.)
Thanks in advance for any insight!
we do not recommend it because it added confusion and was used in a wrong way by webmasters.
Annotating it correctly will still work as it worked originally.
Hi Christopher,
we have one home page for each language, fully translated (e.g. /home-it.3sp, /home-en.3sp). To serve the right content to the user we have domain.com/ redirected 301 to domain.com/home.3sp, where home.3sp displays the localized version of the home depending on browser or crawler locale setting.
(inside home.3sp the links to the home page are localized also, so from there the user will navigate to home-it.3sp or home-en.3sp)
Should we add
link rel=alternate href=domain.com/home.3sp
link rel=alternate href=domain.com/home-it.3sp
link rel=alternate href=domain.com/home-en.3sp
to all three home pages to be sure Google properly understands what's the localized home page and doesn't get content duplication ?
Thanks alot!
Gianluca
@gianluca (and others). Let's move the discussions to the support forum.
http://productforums.google.com/forum/#!categories/webmasters/internationalization
@Christopher Done
http://productforums.google.com/forum/#!category-topic/webmasters/internationalization/K01fPCf_Cwg
Thanks
Mixing canonical and alternate tags seems to be inconsistent. Let's take an example:
main site is www.example.com
localized homepages are:
www.example.com/uk
www.example.com/de
If we follow the Google advice of adding only the alternate tags and forget about canonical then users in Google search results will be presented with the correct localized version of our website. So far so good.
Now the big and unanswered question is:
Without a canonical defined, how will www.example.com?someirrelevantparameter=someirrelevantvalue propagate it's SEO juice to www.example.com and even more important is how we'll prevent being penalized for duplicate content?!?
As mentioned above, let's please move the discussions to the support forum.
http://productforums.google.com/forum/#!categories/webmasters/internationalization
Christopher- pls see www.goyoda.com - Are there any changes I should make to blogger robots text or header tags to enable search results in certain countries eg India is producing no local results. Goyoda has a unique blog 23 countries, yet until UGC increases the content may appear as duplicate, but it isn't and links out to around 3000 unique Twubs. If you click on France you'll get an idea of how different they'll all become
Hi Irvin.
I saw that you already posted the same question on the internationalization forum. There is no need to double-post, just wait for an expert to answer the question in the forum.
Hi,
I have many cctlds for my site, is always the same content, translated for different languages, and between same languages "duplicated". For example, exmaple.com.br and example.pt both has content in portuguese.
We decided to do this by looking better ranking in local Googles, but we are facing a problem.
Whenever we need to reference a page, in our facebook page for example, we are not sure if we place the link like example.es/hoteles or example.com.ar/hoteles since this will give a "link vote" to the .es site so always the rest of the sites will be ignored and never linked.
We are thinking of having for exmaple, example.es and try to rank with that domain on every country that speak spanish. We already added the href lang thing but we find really hard to rank well in every country with every cctld, is like effort is being multiplied.
Please, can you give me hint on this?? I will really appreciate that.
Thank you,
Alvaro
Hello Christopher,
I am the administrator for a financial site that supports more than eight languages, all of which are translations of the text from the English site. (We use subdirectories for each language: Mydomain.com/de/, Mydomain.com/fr/, Etc…)
Currently canonical are in place all over the site, each page with its own canonical.
I wanted to clarify whether you think it advisable to use 'the hreflang tag' to specify each language? If so, do I need to implant the tag only on the English page header’s pointing to every language, or in every page on the site?
Thanks
Great article and we have one question:
We are using the hreflang at our sites. We have a Dutch shop and a Belgium shop with the same content. Google indicates that this should not be a problem. We have used the hreflang for both countries. At this moment we only have a problem with the dutch shop. Belgium results are taken over our dutch results.
So instead of showing the Dutch shop he is showing in a lot of cases the Belgium shop. For our conversion this is killing. Do you know if there are more things we can do to make clear that the Dutch shop is for the Dutch market and the Belgium shop for the Belgium market
Let me know.
Thanks
Kind regards,
Coen
All questions about hreflang should be posted on http://productforums.google.com/forum/#!categories/webmasters/internationalization , including the sites being discussed and an example query.
Post a Comment