IMO, seems to me the option 3 is only making the one site multilingual but not multi-regional. it cannot gain ranking advantages in local serps. such as to rank in google.frI suggest option 3: Make the site in one language. Then translate it using javascript to different languages. Bots will crawl the site for the main language, but the users will still be able to browse the site in different languages.
This, or plan B.
This method, in my opinion, is unsuitable since Google Translate, which uses javascript throughout the site, occasionally fails to fulfill accurate language conversion.I suggest option 3: Make the site in one language. Then translate it using javascript to different languages. Bots will crawl the site for the main language, but the users will still be able to browse the site in different languages.
It works just fine. Google translate may have problem, but I am not talking about using that. We have used a similar approach in an EU company before (we had Czech, Slovak, German and French translation using js). Never had any issues. If you guys need a snippet that can do such things, lemme know. Will find it and paste it here.This method, in my opinion, is unsuitable since Google Translate, which uses javascript throughout the site, occasionally fails to fulfill accurate language conversion.
I would also recommend moving with Plan B.
Agreed. If OP is targeting multiple geo through translations (imo, not a very good way but little do I know about seo lol), Option 2 is what I would suggest as well.IMO, seems to me the option 3 is only making the one site multilingual but not multi-regional. it cannot gain ranking advantages in local serps. such as to rank in google.fr
The OP's example is to target EU zone with sub-markets like de, fr. IMO, plan B is the way to go. with abc.com/de, abc.com/fr, targeting each market independently, with its own language.
As I previously stated, this is simply my view based on the use of javascript and a translator. Anyway, thank you for the clarification buddy.It works just fine. Google translate may have problem, but I am not talking about using that. We have used a similar approach in an EU company before (we had Czech, Slovak, German and French translation using js). Never had any issues. If you guys need a snippet that can do such things, lemme know. Will find it and paste it here.
That's what I'm concerned mate, I don't know if three-domain can do better in local SERPs than option B,IMO, seems to me the option 3 is only making the one site multilingual but not multi-regional. it cannot gain ranking advantages in local serps. such as to rank in google.fr
The OP's example is to target EU zone with sub-markets like de, fr. IMO, plan B is the way to go. with abc.com/de, abc.com/fr, targeting each market independently, with its own language.
if you take a look at those huge international corp sites, they all go with plan B now and 301 most of the local TLDs .That's what I'm concerned mate, I don't know if three-domain can do better in local SERPs than option B,
Do I need to differentiate them or can I JUST based the English(.com) and translate it to the target language by google translate, (I'm not good at German and French at all)
Does planA is better than planB at ranking local SEO?I'm sure plan B is better. All of my sites are multilingual and the language can be changed with just 2 clicks. This method is cheap and easy. It is better to concentrate on more important things.