<?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>Global Search Engine Marketing &#38; Social Media News And Analysis &#187; International Domains</title> <atom:link href="http://www.multilingual-search.com/category/international-domains/feed/" rel="self" type="application/rss+xml" /><link>http://www.multilingual-search.com</link> <description>Global Search Engine Marketing News And Global Social Media</description> <lastBuildDate>Sun, 20 May 2012 19:30:02 +0000</lastBuildDate> <generator>http://wordpress.org/?v=2.9.2</generator> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>International Companies Should Embrace the Hreflang tag</title><link>http://www.multilingual-search.com/international-companies-should-embrace-the-hreflang-tag/11/04/2012/</link> <comments>http://www.multilingual-search.com/international-companies-should-embrace-the-hreflang-tag/11/04/2012/#comments</comments> <pubDate>Wed, 11 Apr 2012 18:06:53 +0000</pubDate> <dc:creator>Kristjan Mar Hauksson</dc:creator> <category><![CDATA[Global Processes]]></category> <category><![CDATA[Global Strategies]]></category> <category><![CDATA[International Domains]]></category> <category><![CDATA[Localisation]]></category> <category><![CDATA[global Search Engine Marketing]]></category> <category><![CDATA[Hreflang tag]]></category> <category><![CDATA[Panda]]></category><guid isPermaLink="false">http://www.multilingual-search.com/?p=3571</guid> <description><![CDATA[<b class="gold">:</b>&#160;<p>The year 2011 was a good year for search engine marketing. As content became the king, some real impressive search engine optimized websites were developed. Many small and big players around the globe also poured into the domain of search [...]]]></description> <content:encoded><![CDATA[<p>The year 2011 was a good year for search engine marketing. As content became the king, some real impressive search engine optimized websites were developed. Many small and big players around the globe also poured into the domain of search engine marketing. Then in August 2011, the search engine giant Google came up with a new algorithm update and rolled out Panda internationally. This proved to be quite a challenge for websites that had a .com extension with either a sub domain or subdirectory structure. The problem was naturally more intense for companies that had presence in more than one country.</p><p>Multilingual and multi-country websites have similar content or translated similar content with perhaps some variations in terms of currency signs and title tags. So the combination of duplicate content and a directory/sub directory structure caused websites to get stuck in the Panda filter.</p><p>Google rolled out a solution for the problem that <a href="http://support.google.com/webmasters/bin/answer.py?hl=en&amp;answer=182192">multiple language</a> sites started facing due to Panda filter. This key was in the form of ‘hreflang’ and ‘canonical’ tags. This is Google’s way of telling site owners that they should use a regional subtag in their head tag for the website URL. This will help Google search crawlers to figure out the nature of content on each page and its relevance to a search performed. With these tags on websites, Google will comprehend that content on the site is truly intended for that region.</p><p><strong><em>So how do the Hreflang and Canonical tags help? </em></strong></p><p><strong><em> </em></strong></p><p><strong>Hreflang Tag</strong></p><p>The hreflang attribute (hreflang: rel=&#8221;alternate&#8221; hreflang=&#8221;x&#8221;) is very helpful for website owners in different parts of the world who need content translated in native languages to target a particular region. It can be easily used for multilingual websites using substantially the same content on all web pages with some differences in spellings – for instance pages in English for Canada, USA and Australia.</p><p>Hreflang can also be used by multiregional websites using fully translated content or substantially monolingual content that targets different regions – pages in English, French, German, Spanish, and other languages.</p><p>To use the hreflang tag for multiple language versions of a website, each language must use rel=&#8221;alternate&#8221; hreflang=&#8221;x&#8221;. So, a page in German needs to have a rel=&#8221;alternate&#8221; hreflang=&#8221;x&#8221; link to the English and Spanish version and the English and Spanish version must include a link pointing to the German site.</p><p>Google has expanded its support of the rel=&#8221;alternate&#8221; hreflang link element to take care of content that is translated or offered for more than one geographic region. The hreflang attribute mentions the language, optionally the country, and URLs of equivalent content. By stating these alternate URLs, Google&#8217;s goal is to be able to consolidate signals for such web pages, and to serve the appropriate URL to users in search. Alternative URLs may be on the same website or on another domain.</p><p><strong>Canonical Tag</strong></p><p><strong> </strong></p><p>The multilingual canonical tag (rel=&#8221;canonical&#8221;) tells Google that a certain URL is the preferred location and the most significant translated version of the content of the primary or general URL.</p><p>So multilingual canonical tag:</p><ul><li>Is used in      tandem with hreflang</li><li>May be      used when web pages have the same content in same language but target      multiple countries</li><li>Designate      the translation of content that gets indexed and returned to users</li></ul><p>With canonical tag on web pages, when users enter content into search results, they are likely to see the URL that has relevant content in their preferred language. In other words, Google will use &#8220;canonical&#8221; signal to focus on preferred version of web pages in each search, while displaying the local URLs to users where appropriate. To quote an example, you can use the tag if you have the same product page in Spanish, but want to target it separately to users searching on the Google properties for Spain, United Kingdom, and Germany.</p><p>To explain how the tags would work, here is an illustration for a hypothetical site abc.com</p><p>http://www.abc.com/ &#8211; contains the general homepage of a website, in Spanish</p><p>http://es-es.abc.com/ &#8211; is the version for users in Spain, in Spanish</p><p>http://es-uk.abc.com/ &#8211; is the version for users in United Kingdom, in Spanish</p><p>http://en.abc.com/ -     is the generic English language version</p><p>For all of these pages, the website owner can use the following markup to specify language and optionally the region:</p><p>&lt;link rel=&#8221;alternate&#8221; hreflang=&#8221;es&#8221; href=&#8221;http://www.abc.com/&#8221; /&gt;</p><p>&lt;link rel=&#8221;alternate&#8221; hreflang=&#8221;es-ES&#8221; href=&#8221;http://es-es.abc.com/&#8221; /&gt;</p><p>&lt;link rel=&#8221;alternate&#8221; hreflang=&#8221;es-UK&#8221; href=&#8221;http://es-uk.abc.com/&#8221; /&gt;</p><p>&lt;link rel=&#8221;alternate&#8221; hreflang=&#8221;en&#8221; href=&#8221;http://en.abc.com/&#8221; /&gt;</p><p>When a regional sub tag is specified, Google assumes that the website owner wants to target that region. Website owners need to remember that all of these annotations are to be used on a per-URL basis. They need to use the specific URL, not the homepage, for both of these link elements.</p><p><strong>You can employ:</strong></p><ul><li>Hreflang      tags to segregate same language, different content or different languages      on different URLs</li><li>Canonical      tags to bring together same language and same content under one URL</li></ul><p>While canonical acknowledges that this is the same content, the Hreflang tag identifies which URL should be displayed in different sets of results.</p><p>And, Canonical + Hreflang = same content + different URL</p><p>Google understands that the content is the same, but displays the correct URL as per the Google domain search. The use of Hreflang and canonical tags applies to local domains as well as dot coms, though the examples stated by Google are based on dot coms. The canonical and Hreflang tags do not have any direct impact on ranking – canonicals do not share the link equity of the domestic market with the new markets targeted.</p><p>The obvious benefits of Hreflang –</p><ul><li>It helps      Google to comprehend your site better and know that pages are related to      each other.</li><li>It helps      Google discover new URLs that could be the ones that it missed before in      searches.</li><li>It creates      more targeted URL for searchers: Different users can see a suitable,      localized URL.</li></ul><p>So start using the Hreflang tag – there are no reasons to be scared!</p><p>No related posts.</p>]]></content:encoded> <wfw:commentRss>http://www.multilingual-search.com/international-companies-should-embrace-the-hreflang-tag/11/04/2012/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Egypt, Saudi Arabia and UAE Non-Latin Domain Names Live</title><link>http://www.multilingual-search.com/egypt-saudi-arabia-and-uae-non-latin-domain-names-live/06/05/2010/</link> <comments>http://www.multilingual-search.com/egypt-saudi-arabia-and-uae-non-latin-domain-names-live/06/05/2010/#comments</comments> <pubDate>Thu, 06 May 2010 14:11:07 +0000</pubDate> <dc:creator>Andy Atkins-Krüger</dc:creator> <category><![CDATA[International Domains]]></category> <category><![CDATA[domains]]></category><guid isPermaLink="false">http://www.multilingual-search.com/?p=1690</guid> <description><![CDATA[<b class="gold">Marina del Rey:</b>&#160;<p>Since November last year it has been possible to use characters that were not formerly part of the Latin character set used for creating web addresses and URLs.  For example, the German umlaut &#8211; a character with two dots [...]]]></description> <content:encoded><![CDATA[<p>Since November last year it has been possible to use characters that were not formerly part of the Latin character set used for creating web addresses and URLs.  For example, the German umlaut &#8211; a character with two dots above it such as the &#8220;ü&#8221; which should normally appear in my name &#8211; could not be used in the URL address until the changes in the Autumn.  Yesterday, ICANN turned on the newest three domain names and the first to use a script other than Latin &#8211; namely Arabic &#8211; to provide local script domains for Egypt, Saudi Arabia and the United Arabic Emirates.</p><p>The new domains (which you will only see if you have Arabic script enabled on your PC) are:-</p><p><strong><ul><li>Egypt  مصر</li><li>Saudi Arabia  السعودية</li><li>United Arab Emirates  امارات</li></ul><p></strong><br /> These new local domains &#8211; or ccTLDs (Country Code Top Level Domains) will prove highly useful for international SEO purposes and once these domains are fully available to buy it is highly recommended that you acquire your brand names, trademarks and country names in these domains to protect and use them in the Middle East. Of course, as these are Arabic which is a right-to-left language &#8211; they will actually appear on the left in the browser address bar before the actual site name!</p><p>Oddly missing from this launch is the рф Russian domain name for the Russian Federation which was &#8216;delegated&#8217; ie approved at the same time as the Arabic versions.  This domain will no doubt be the very next to go live.</p><p>In the first instance, ICANN is processing 21 local domains which span 11 different languages including Chinese, Arabic, Russian, Sinhalese, Tamil and Thai.  Initially, domains that are approved must match country or territory names &#8211; but ICANN has plans to go much further including launching new generic top level domains which use the new character set.  Domainers watch out, the dot com may soon be available in Russian, Chinese and Arabic in a transliterated form.</p><p>ICANN believes that these new local script variant domains and URLs will create new ways for end users to find and produce information online, provide more choices to registrants and provide new opportunities for investment and new businesses.  ICANN also says that international domain names or IDNs will reach out to wider parts of the globe and be more &#8216;inclusive&#8217;.  Some systems and applications will need to be updated in order to work with them.</p><p>The BBC also reported this <a href="http://news.bbc.co.uk/1/hi/technology/10100108.stm">story</a> &#8211; but omitted to clarifty that these scripts have been usable since November and that it is just the domain endings which have gone live today.</p><p>See also John Yunker&#8217;s piece on the first full length non-Latin URL:<br /> <a href="http://www.globalbydesign.com/blog/2010/05/06/the-dawn-of-a-new-url/">http://www.globalbydesign.com/blog/2010/05/06/the-dawn-of-a-new-url/</a></p><p>No related posts.</p>]]></content:encoded> <wfw:commentRss>http://www.multilingual-search.com/egypt-saudi-arabia-and-uae-non-latin-domain-names-live/06/05/2010/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Trademark owners must be on the ball in new international domain changes</title><link>http://www.multilingual-search.com/trademark-owners-must-be-on-the-ball-in-new-international-domain-changes/02/12/2009/</link> <comments>http://www.multilingual-search.com/trademark-owners-must-be-on-the-ball-in-new-international-domain-changes/02/12/2009/#comments</comments> <pubDate>Wed, 02 Dec 2009 16:53:46 +0000</pubDate> <dc:creator>Gemma Birch</dc:creator> <category><![CDATA[International Domains]]></category><guid isPermaLink="false">http://www.multilingual-search.com/trademark-owners-must-be-on-the-ball-in-new-international-domain-changes/02/12/2009</guid> <description><![CDATA[<b class="gold">:</b>&#160;<p>As of 16th November, it is now possible to register non-Latin domain names, using characters including Chinese, Cyrillic, Greek and Arabic. This development also affects certain languages such as Swedish, which use the Latin alphabet but have additional special characters, [...]]]></description> <content:encoded><![CDATA[<p>As of 16th November, it is now possible to register <strong>non-Latin</strong> <strong>domain names</strong>, using characters including Chinese, Cyrillic, Greek and Arabic. This development also affects certain languages such as Swedish, which use the Latin alphabet but have additional special characters, which have previously not been represented in domains. It will also be possible to mix character sets in a domain name, and for example have the domain name in non-Latin characters, with a .com extension.</p><p>This change will dramatically increase the number of available of domains containing <strong>trademark terms</strong>, and businesses will have to react quickly to ensure they protect those terms online. It is also likely that they will have to spend significantly to do, as prices for the new domains will be higher than they are at present. Trademark owners will have a sunrise period which will enable them to buy their trademarked domains before they are made available to all, however requirements such as holding the registered trademark in that specific country are likely to be applied.</p><p>This is a major step in the globalisation of the web and is expected to encourage more and more people to join the online community. However, it could cause a few headaches for marketers and trademark owners.</p><p>Read more at <a href="http://searchengineland.com/trademark-owners-get-your-new-international-domain-names-now-30695" target="_blank">Search Engine Land </a></p><p>No related posts.</p>]]></content:encoded> <wfw:commentRss>http://www.multilingual-search.com/trademark-owners-must-be-on-the-ball-in-new-international-domain-changes/02/12/2009/feed/</wfw:commentRss> <slash:comments>5</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Database Caching 29/89 queries in 0.009 seconds using disk

Served from: www.multilingual-search.com @ 2012-05-21 15:33:45 -->
