according to the docs, one can create a multi-lingual website.
however, the current implementation of multi-lingual sites will create all kinds of SEO problems, as the implementation of the hreflang looks to be wrong.
right now, if one has a multi-lingual site, one can set the language by using a $_GET var which in turn sets a SESSION var so that from that point on, all pages are now in the chosen language. for google, that is a problem. depending on the SESSION var, ZC will display the chosen language. which means the same URL could have different languages, ie mysite.com may be in english, french, italian, etc. depending on the SESSION.
in order to properly implement the hreflang tag; the tags must be bi-directional, and right now that is not the case.
for example, assuming a default language of en; one is at mysite.com; in the header there is an alternate tag for french which is mysite.com/?language=fr. when one goes to that link, because tags need to be bi-directional, there should be a link back to mysite.com for english. but of course there is not (there could be mysite.com/?language=en for english; but that does NOT satisfy the bi-directional requirement); when one does go back to mysite.com, it will now be in french, as ZC implements languages based on SESSION vars and not GET vars.
i believe that unless each language has its own unique url, zc will not be able to conform to successfully implementing the hreflang tag.
according to the docs, one can create a multi-lingual website.
however, the current implementation of multi-lingual sites will create all kinds of SEO problems, as the implementation of the
hreflanglooks to be wrong.right now, if one has a multi-lingual site, one can set the language by using a
$_GETvar which in turn sets aSESSIONvar so that from that point on, all pages are now in the chosen language. for google, that is a problem. depending on theSESSIONvar, ZC will display the chosen language. which means the same URL could have different languages, ie mysite.com may be in english, french, italian, etc. depending on theSESSION.in order to properly implement the
hreflangtag; the tags must be bi-directional, and right now that is not the case.for example, assuming a default language of
en; one is at mysite.com; in the header there is an alternate tag for french which is mysite.com/?language=fr. when one goes to that link, because tags need to be bi-directional, there should be a link back to mysite.com for english. but of course there is not (there could be mysite.com/?language=en for english; but that does NOT satisfy the bi-directional requirement); when one does go back to mysite.com, it will now be in french, as ZC implements languages based onSESSIONvars and notGETvars.i believe that unless each language has its own unique url, zc will not be able to conform to successfully implementing the
hreflangtag.