How to rank my website in different countries?

[Saimon86]

Good mornign all,

i've a website <snip> in italian. Visits are coming mostly from Italy.
I would like to translate all the contents in another two lengueges, Spanish and English because i'm now in the process of a "refurbishment" of the blog. At the end of this I would like that the people who are searching on google for something related to my contets in theyr languege could find my pages in their lenguage.

The fact of translation doesn't give me any SEO advantage to ranks my pages in England and Spain, (countries where i would like that google could rank my website), i'm absolutley sure.

Do you have any instructions to give me to do this...if it possible?
Having same contenten in three langueges do you think google will take this as a duplicated content?

Many thanks

S

[edited by: engine at 5:13 pm (utc) on Nov 3, 2020]

[rainborick]

Go see Google's Guide to Multi-Regional Sites [webmasters.googleblog.com]. It will tell you how to work with geo-targeting and languages.

[Mark_A]

I have tried to market a website in different languages with less than stellar success. My feeling is that you need an editor with that mother tongue for each language version. And translations should only be done into the mother tongue of the translator imo.

[tangor]

Might just start simple. ADD the new language stuff in real time. Do NOT translate the existing material, but do require that the new content is written by native "target" language authors for the best result.

Or more precisely stated: your "translated pages" are done from scratch, one at a time, and build from there.

Later, after you have some data regarding success (or not0 you can then consider reworking the older material.

[Saimon86]

I have tried to market a website in different languages

Does the material had been automatically translated? If so do you think that the problem was that google have been considering your contents as a duplicated material?

What i have in my mind is to translate one by one all the existing posts supported by a bilingual editor. This means that we will restart to rewrite and publish all the contents from the first post like it was a new one. So the material will not published in one shot automatically but i will build, post by post, the translated blogs beside the Italian one (sure, one language at time)

Do NOT translate the existing material

Sure, new content will be written by a mother tongue editor, but I honestly don't see why I shouldn't translate the existing material. Is there any negative side effect for which I might be penalized in terms of ranking? Sure i'll invest some money and time on this (long) process but at the moment i can see only benefits on this for my blog. Better sayd i don't see any penalization. Am' I see this in s wrong way?

[not2easy]

From the Google information (linked above)

Websites that provide content for different regions and in different languages sometimes create content that is the same or similar but available on different URLs. This is generally not a problem as long as the content is for different users in different countries. While we strongly recommend that you provide unique content for each different group of users, we understand that this may not always be possible for all pages and variations from the start. There is generally no need to "hide" the duplicates by disallowing crawling in a robots.txt file or by using a "noindex" robots meta tag. However, if you're providing the same content to the same users on different URLs (for instance, if both "example.de/" and "example.com/de/" show German language content for users in Germany), it would make sense to choose a preferred version and to redirect (or use the "rel=canonical" link element) appropriately.

so they make it clear that it is not considered duplicate content.

The relevant details about translating involve correct usage of canonical and hreflang meta tags to serve the correct language or URL in Search results. The correct usage and methods of implementation are explained by Google: [support.google.com...]

A good visual explanation is shown at [moz.com...]