Hey Edmond,

Vic already answered with most of what I was going to say - a big thing to remember is the issue of duplicate content if you are making a direct translation. You probably want to keep all content under the same domain for potential future link-building efforts. Using the /en approach Vic suggested will help with this.

Bear in mind, however, that such an approach can result in duplicate content penalties (see: Panda) if you are not careful with the translation process. It might be better to paraphrase your content when translating it in order to avoid these penalties.

The rest depends on what aspects of the site you want to translate, where your markets are and what language your potential customers are likely to speak.

Feel free to touch base with any questions,

Rob

Hi Tamir,

Matt has already done a great job in answering this and I would add just a small side note - my guess for the new domain came from someone reading that keyword matching between domains and content was a great way to get better results in SERPs. It's antiquated thinking but that's what it looks like (adding "travel" to the domain in the hopes that potential customers would better understand what they were all about).

As Matt said, the big issue is the way the redirects were handled (should be 301'd to a similar site structure for the smallest possible rankings impact). If you were to create a site structure similar to that found on the previous site, you would probably see a return to those traffic levels (or close) fairly quickly. Another method might be to re-institute the previous site by reloading the site map on the old domain (there are tools for this). This would permit you to use the old site until you could get a proper site structure set up for the new one.

You don't have to move back to the previous website permanently, but it wouldn't be a bad idea until to have sorted out what you want to do with the new site moving forward. A properly-executed 301 redirect should cost you between 1-3% of your overall link juice.

Hope this helps a bit.

Rob

Hi Tamir,

Matt has already done a great job in answering this and I would add just a small side note - my guess for the new domain came from someone reading that keyword matching between domains and content was a great way to get better results in SERPs. It's antiquated thinking but that's what it looks like (adding "travel" to the domain in the hopes that potential customers would better understand what they were all about).

As Matt said, the big issue is the way the redirects were handled (should be 301'd to a similar site structure for the smallest possible rankings impact). If you were to create a site structure similar to that found on the previous site, you would probably see a return to those traffic levels (or close) fairly quickly. Another method might be to re-institute the previous site by reloading the site map on the old domain (there are tools for this). This would permit you to use the old site until you could get a proper site structure set up for the new one.

You don't have to move back to the previous website permanently, but it wouldn't be a bad idea until to have sorted out what you want to do with the new site moving forward. A properly-executed 301 redirect should cost you between 1-3% of your overall link juice.

Hope this helps a bit.

Rob

Hey Edmond,

Vic already answered with most of what I was going to say - a big thing to remember is the issue of duplicate content if you are making a direct translation. You probably want to keep all content under the same domain for potential future link-building efforts. Using the /en approach Vic suggested will help with this.

Bear in mind, however, that such an approach can result in duplicate content penalties (see: Panda) if you are not careful with the translation process. It might be better to paraphrase your content when translating it in order to avoid these penalties.

The rest depends on what aspects of the site you want to translate, where your markets are and what language your potential customers are likely to speak.

Feel free to touch base with any questions,

Rob