{"id":1453,"date":"2012-10-26T07:21:40","date_gmt":"2012-10-25T23:21:40","guid":{"rendered":"http:\/\/blog.lolyco.com\/sean\/?p=1453"},"modified":"2012-10-26T08:06:52","modified_gmt":"2012-10-26T00:06:52","slug":"getting-a-multi-language-page-on-a-chinese-search-engine","status":"publish","type":"post","link":"https:\/\/blog.lolyco.com\/sean\/2012\/10\/26\/getting-a-multi-language-page-on-a-chinese-search-engine\/","title":{"rendered":"Getting a multi-language page on a Chinese search engine"},"content":{"rendered":"

I made a multi-language page for Lolyco.com<\/a> recently that switches between language based on the Accept-Language<\/a> header sent by the User-Agent or by setting a session variable. There’s an English version<\/a> (the default), a Malay version<\/a> and a Chinese version<\/a>. I’ve had sites online before that are aggressively crawled by (for example) the BaiDuSpider<\/a> but never seem to appear in search results, even when they contain Chinese content.<\/p>\n

\"Sogou.com<\/a>The Lolyco page not only changes its content but also sets its Content-Language<\/a> and Vary<\/a> response headers. Returning different content on the same URI is not something I’m entirely happy with, but returning content tailored to User-Agents is not uncommon.<\/p>\n

The page has so far been crawled by obviously Chinese crawlers BaiDuSpider, YodaoBot<\/a> and Sogou Spider<\/a>. In place of a logo, ‘Lolyco’ is a h1 element whose content is changed for Chinese-requesting user agents to ‘\u7edc\u7acb\u79d1’ (In pinyin “l\u00f9o l\u00ec k\u0113”: no meaning, just sounds like “lo ly co”). After a few days, I can see Sogou<\/a> is returning a result for lolyco.com<\/a> and has a cached copy of the Chinese page<\/a>. Soso<\/a> also has a result for the new Lolyco page<\/a>, though no sign of the Soso spider<\/a> in the log. Nothing yet at Baidu<\/a> nor Youdao<\/a>.<\/p>\n

\"Soso.com<\/a>A problem with doing it this way is that Google<\/a> won’t crawl the non-English pages because for one thing it does not send an Accept-Language header and for another it does not use cookies. Those are some sensible crawler design choices. The Lolyco page defaults to English in the absence of an Accept-Language header. What Google needs (and I’m not a great fan of web standards being imposed by Google’s business requirements) is one URL per indexable entity.<\/p>\n

The same issue exists with non-English search engines. A little twiddle of my Apache<\/a> (I use it as a proxy) LogFormat<\/a> to add on the Accept-Language header value to my log lines tells me that Sogou Spider requests “zh-cn<\/a>” content. Sogou has the Chinese content in its results, but will never see the English or Malay content.<\/p>\n

I reluctantly added a list of anchors to the Lolyco page that override the Accept-Language header with a “content-language” query parameter. The list is made invisible to human visitors with a CSS display:none<\/a>, but should allow crawlers to fetch the other language versions of the page.<\/p>\n

I’m not entirely confident I’ll be able to get search results from all search engines in all languages. Some of the crawlers seem to be restrictive: the zh-cn Accept-Language header on some Chinese crawlers makes me think they are only looking for Chinese content. Google doesn’t specify the header so will probably index the 3 languages indifferently. If you believe the hype then Baidu is the major Chinese search engine, which makes me wonder why its developers (if there are more than one) have chosen to send an Accept-Language header of ‘en-US’<\/strong>.\u00a0 \u4e3a\u4ec0\u4e48\u767e\u5ea6\uff1f<\/p>\n","protected":false},"excerpt":{"rendered":"

I made a multi-language page for Lolyco.com recently that switches between language based on the Accept-Language header sent by the User-Agent or by setting a session variable. There’s an English version (the default), a Malay version and a Chinese version. I’ve had sites online before that are aggressively crawled by (for example) the BaiDuSpider but […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11,36,3],"tags":[24,41,4,34,18,57],"class_list":["post-1453","post","type-post","status-publish","format-standard","hentry","category-google","category-search","category-software","tag-apache","tag-http","tag-lolycocom","tag-network","tag-server","tag-web"],"_links":{"self":[{"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/posts\/1453","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/comments?post=1453"}],"version-history":[{"count":8,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/posts\/1453\/revisions"}],"predecessor-version":[{"id":1469,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/posts\/1453\/revisions\/1469"}],"wp:attachment":[{"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/media?parent=1453"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/categories?post=1453"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.lolyco.com\/sean\/wp-json\/wp\/v2\/tags?post=1453"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}