2011
Multilingual User Generated Content and SEO « Code as Craft
karl says: Your comment is awaiting moderation. December 2, 2011 at 2:51 pm There is a missing opportunity from both monolingual search engines and content providers. It’s kind of sad. The fact to have one unique URI that a French user can just paste to his Japanese friend is one wonderful thing of content negotiation. How do we leverage this, so search engines are able to understand it? Enter the never used 1998 RFC: “Transparent Content Negotiation in HTTP” (RFC 2295). http://tools.ietf.org/html/rfc2295 I wonder what it would take for Google to negotiate with content providers and offering this feature. The solution is super simple. We were living in a world where sites were quite monolingual but this has changed since.
virtaal:index · Translate Toolkit & Pootle
by Xavier Lacot
2010
Multilingual Drupal: Some Dos And Don'ts | Drupaler | Drupal Blog, Collaborative Drupal Resource
by claire_
Alan Dean: HTTP i18N Patterns
karlcow said...
Did you find a way for Google to index every flavors of the content. SEO people often argue that you can't do conneg, because Google will not index french, english, etc. but one of them.
January 9, 2010 3:32:00 PM PST
2009
start · Translate Toolkit
by nhoizey
