Multiple language Website SEO advice
I am just copying the whole content from WMW to start the conversation about Multiple Language website SEO. This is a tricky one, we have been work on it for last one year and have faced a lot of problems ourselves. Here is a checklist to start with, I will keep adding it here:
- all page content is translated, (except for UGC sections)
- all window
- all pages are in UTF-8
- all data is stored as UTF-8
- images that have text in them are available in i18n versions
- all images have @alt text and @title attributes translated
- page delivers a “Content-Language” HTTP header
- the tag has attributes @lang and @xml:lang
- dates are presented in translated formats (eg “el 4 de agosto 2010″)
- outgoing emails are translated into the user’s preferred language
- numbers are presented with internationalized formatting (eg. $1,234.56 vs $1.234,56)
- other subtle formatting, eg. 50% vs 50 %, Name: vs Nom :
Some practical things I learned during this project:
- Pages that contain a lot of mixed UGC language can/should be blocked from indexes using a tag, because they can only do more harm than good
- alt language pages all have unique URLs, they are not dynamically rendered using a cookie or geo-targeting
- geotargeting may be useful for setting sessions but should not override URL-based navigation to another language
- ccTLDs are perceptually better than subdomains or subfolders
- massive cross-linking of pages is good
- for storing the phrase lexicon, SQLite is faster than MySQL, XML, or even a hard-coded array, on a typical LAMP server. see: [webmasterworld.com...]
- liberal use of memcache is a good thing
- offering translated file paths is good, if your architecture is flexible enough to do that without causing great suffering.
- start every project using UTF-8 for everything. It’ll save you big headaches later on.
- Translating will take longer than you expect
- Not all translators are comfortable with internet jargon like “download” and “ringtone” and “widget” etc. You may need to shop around for someone specialized… or pretty much anyone under 25. LOL
- Store verbal metadata (name, description, tags) in a separate table from non-verbal metadata (price, popularity), keyed with a language code (“en”, “es”, “fr”…), with a one-to-many relationship with the item ID. That way you can offer verbal metadata in more than one language without rewriting all your SQL queries. (I had to do that. Not fun.)
- May be worthwhile to hire folks who read/write the other languages to do some blitzkrieg link-building
- In some situations a templating language like Smarty comes in handy
Some of the debate is still on:
>Translating will take longer than you expect
Absolutely – and you should use local people if you’re really serious. Stay AWAY – far AWAY – from automated services. Google translate will NOT be good enough!
No related posts.
Related posts brought to you by Yet Another Related Posts Plugin.