<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Sandy Allain &#187; Multilingual</title>
	<atom:link href="http://www.sandyallain.com/blog/category/multilingual/feed" rel="self" type="application/rss+xml" />
	<link>http://www.sandyallain.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Sun, 29 Jan 2012 16:48:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
		<item>
		<title>How to develop Multilingual Websites ?</title>
		<link>http://www.sandyallain.com/blog/multilingual-websites</link>
		<comments>http://www.sandyallain.com/blog/multilingual-websites#comments</comments>
		<pubDate>Mon, 27 Jun 2011 17:28:33 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Multilingual]]></category>

		<guid isPermaLink="false">http://www.seopolyglot.com/?p=29</guid>
		<description><![CDATA[I have developed many multilingual websites. When developing a new website in several languages or adding a new version on your current site, it is very important to have your website 100% translated in the target language. Below are some best practices: Conduct user research for you to have a better understanding of cultural factors [...]]]></description>
			<content:encoded><![CDATA[<p>I have developed many multilingual websites. When developing a new website in several languages or adding a new version on your current site, it is very important to have your website 100% translated in the target language. Below are some best practices:<br />
<img class="alignleft" src="http://www.sandyallain.com/img/multilingual-websites.jpg" alt="" width="202" height="200" /></p>
<p>Conduct user research for you to have a better understanding of cultural factors for your intended audience. The online experience should be culturally relevant to establish an emotional connection with your audience. You must also enable online users to find your multilingual site through prominent access on the English website. You should make access to your multilingual website available on the global navigation on the top right hand corner of the English page.</p>
<p>I have noticed that many sites do not translate some elements of their site (menu, banners, etc.) It is very important that you have it translated not only for your site users, but also for search engines. If your site is in English and French, for example, you could have the french version in the “/fr/” folder and English in the root:</p>
<p>http://www.yourcompany.com</p>
<p>http://www.yourcompany.com/fr</p>
<p>Make sure that your multilingual site offers the same user experience to your English website. Update and maintain your site regularly to ensure that it remains comparable to the English website. You can manage user expectations by giving notice when users navigate to an English-only area or external website.</p>
<p>Allow users to toggle between comparable features content on the multilingual and English websites if available. Also provide functionality and interactive features on your multilingual website and integrate its initiatives with external consumer touch points and internal infrastructure, as well as into your general online-offline strategy.</p>
<p>I found it very useful to have the pages open in a new window. This is to avoid the users getting lost – users will still have the site in his/her language open and won’t have a problem to get back. Put yourself in users’ shoes when entering your site.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sandyallain.com/blog/multilingual-websites/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

