How to localise a content-managed site - Case Study
Monday, May 17th, 2010We’re going to take you step-by-step through a localisation project to explain how it’s done. The example we’ve chosen is the multilingual site we did for Loc8tor.
Loc8tor.com is an ecommerce site where customers can buy Loc8tor devices to help them keep track of keys, mobile phones, pets and all sorts of other belongings. This is an ideal showcase for the different elements involved in the professional localisation of a website.
With any website, the first step is to get the content into a format that translators can easily work with.
There are two main ways of translating content from a CMS - the translators can work directly into the system and input translations as they go along, or an export can be obtained from the system - usually either XML or Excel format.
Translation is not always done in a linear fashion - starting at the beginning and finishing at the end - a translator needs to be able to skip parts and come back to them later, raise queries if something is unclear etc. When it comes to proofreading the translation, a file will usually be easier to work on and edit than the content within the CMS. With this in mind, an exported file is often the best method.
So, the Project Manager will deliver the file to the translators, or give them access to the CMS as necessary. Once the translation is complete, the proofreaders do their part. Any images or other parts of the website not already part of the CMS/export file would be localised at this stage too - a professional localisation includes everything, not just the obvious text components of the website.
If an export file has been used, then this needs to be imported back into the CMS. This is usually done by the client’s web team, but sometimes we are given an access login to the system and can upload it ourselves.
The published sites we localised for Loc8tor can be found at www.loc8tor.eu, www.loc8tor.fr and www.loc8tor.es.
With some projects, this is where our involvement ends, but there are other stages that are recommended in order for the localised website to be a success:
Usability testing - this is especially important for eCommerce websites or any others where transactions take place. The localised site is tested from the user’s point of view to make sure all functions work correctly, links lead to the pages they should, etc.
Multilingual SEO & eMarketing - just because you’ve invested in localising your site doesn’t mean that customers in that particular country know it is there! Submitting your site to local search engines, building some inbound links and promoting the new website online will all help get more traffic, and these initial measures are included as standard in our Strategic Approach to Localisation packages.
Managing updates - it’s important that you consider how updates to the website will be managed. Many CMSs can be configured to send updates for translation, which minimises the delay in keeping the multilingual site current.
Keyword Research - Knowing the most popular search terms for your product or service is critical. We help to capture maximum exposure by identifying not just your keywords, but also complementary keywords and competitive keywords to help you optimise your website, and maximize the effectiveness of your multilingual Pay Per Click campaigns.
Pay-Per-Click - ideal for giving your web traffic a boost, for promotions, sales and to announce new content. In most industries it will be expensive to stay at the top of results using PPC alone, but it should form part of your overall web strategy if you have sufficient budget.
A good localisation strategy will consider these additional elements of the process as well as simply translating the main body of text on a website.
If you have any questions about website localisation, or any comments about this article, please let us know.
[/caption]
