| 4:06 pm on Jun 28, 2010 (gmt 0)|
1) I would use the same directory structure under a /Spanish or /es folder. In other words, the Spanish version of example.com/whatever.txt would be located at example.com/Spanish/whatever.txt
2) If I was going to get another domain, I would probably get a .us one. But since the main site already has a 15-year history, I think it might be better to just keep things on the existing site.
3) A- Are the translators in Spain or the U.S.?
B- Make sure each page has links back and forth between English/Spanish versions for that page.
| 4:18 pm on Jun 28, 2010 (gmt 0)|
If you are developing this language for a specific country, I would advise getting and using the country specific domain name.
If this project is for all spanish speaking visitors from all countries, I would use a sub-folder or sub-domain off your main domain.
Agree with having a link up top to jump from either english or spanish at any time. That is useful if someone ends up on the wrong one from serps.
This thread has a great tip from user "pageoneresults" about how to specify the language in the meta tags:
| 4:20 pm on Jun 28, 2010 (gmt 0)|
Thanks for the tips
The translators are all based in the US, though they worked with translators in Argentina/Chile for one of their major books. They've been publishing the Spanish version of the book for the last 4 years, so the translation is heavily reviewed and vetted - and that content will be part of the Spanish version
The main site is a .org, and yes, the Spanish content will be put in that main site.
| 4:28 pm on Jun 28, 2010 (gmt 0)|
Which is the better way to go -- directory or subdomain?
| 5:20 am on Jun 29, 2010 (gmt 0)|
A separate domain would be my preference, but you could also consider a subdomain. I'd stay away from the folder idea.
Don't just get the material translated. Sometimes that isn't enough. You might also like to get the content rewritten by a professional native speaking copywriter. In a different language sometimes there are completely different ways to phrase things that a straight translation may not achieve.
| 3:54 am on Jul 4, 2010 (gmt 0)|
What's wrong with putting the Spanish content in a directory?
I have a site that's about 13 years old. Several years ago, I went bilingual on it. The main site was already English, so I left that alone. All the Spanish content (target audience was Spanish-speaking people in the U.S.) was put in an /es directory.
I never experienced any problems getting content indexed, nor any problems getting good rankings.
| 2:23 am on Jul 8, 2010 (gmt 0)|
I'm actually working on a site right now for a bilingual English/Spanish client catering to a Spanish speaking audience in the Greater Toronto Area. It is going to be established as 2 separate domains to take full advantage of the keyword use at the top level of the name. They will cross link to each other on each page.