Tag Info

Hot answers tagged

6

Is it legal to use translated comments from other sites? Depends upon the terms and conditions set forth by the website whose content you are using. Most sites, by default, don't allow others to use their content without their permission. Other sites, like the Stack Exchange sites, are released under a creative commons license. If the content you want ...


5

rel=translation has been proposed but not adopted by the W3C (it's not in the HTML5 working document). If the words on the pages are different then Google won't penalize you for duplicate content (several people say this in the Webmaster forums). There's lots of advice on multi-language sites in this blog post.


5

Duplicate content penalties are enforced to reduce the amount of useless content on the web and having redundant results in SERPs. Translating content into a different language is neither useless nor redundant. Someone who can't read English but reads Turkish won't be able to consume an English article. So it makes no sense for Google to discourage the ...


3

I solved the problem in the end by adding following code into my default.master.php file ; <META http-equiv=content-type content=text/html;charset=iso-8859-9> <META http-equiv=content-type content=text/html;charset=windows-1254> <META http-equiv=content-type content=text/html;charset=x-mac-turkish>


3

It's very unlikely it would be duplicate content, because it's not really possible to reliably determine that one passage of text is a translation of another. You could take two similar English passages, translate them independently, and end up with the same content in the second language.


3

The short answer is "it depends", mostly on what you're going to do with it. Looking at the spec for RFC3987 Internationalized Resource Identifiers, IE is well within it's rights to encode your URLs, especially if you've got a US/UK keyboard assigned where entering an é might not be the simplest of actions for the user... On top of that, I've seen servers ...


3

To inform search engines of alternate language versions of a page, you should use the <link> element with the hreflang attribute, as described in the HTML spec. <LINK title="The manual in Dutch" rel="alternate" hreflang="nl" href="http://someplace.com/manual/dutch.html"> These links go in the head so are not visible to normal users. For users ...


3

I'm not aware of anything explicit from Google that specifically advises translating URLs to local language, however they have acknowledged that keywords in URLs do help. You can see that Google (and Bing) is doing something with URL keywords by the way they're bolded in search results. That being established, it's a reasonable extension to say that ...


2

No, you should leave the original site untouched, as by this time the Search Engines already have it well indexed and you don't want to confuse them with another site with the same content, just different url. Besides, the Search Engines already know your site is French, even if you don't have a .fr domain. Inside Webmaster Tools, for example you can select ...


2

You say you have checked Google's multilingual guidelines pages, but have you implemented the rel="alternate" hreflang= mark up, either on the pages source code or in sitemaps? If not you should do that, as it can help Google discover and understand the connection between your translated pages. If you haven't already, make sure all your URLs are in a ...


1

Are your relevant search terms are generic and popular, that are searched by users in each country in their own language? (such as, "learning French"?) Then translating it and doing some SEO work should definitely help with Baidu, which for these kind of terms shows results in Chinese.


1

On one hand this seems unnecessary because links and search takes care of all of this, but at the same time using terms in the URL more natural to a particular language would be more memorable and may help with search. I think it is a matter of what you want to do. I am a tech guy that studies and uses automation and this seems right up my ally, but if you ...


1

I'm not finished with this yet as I'm sure we'll be able to get this set up as event tracking eventually but here is one way that may help/give you what you want for now... In Google Analytics:- Audience > Geo > Language Primary Dimension: Language Secondary Dimension: Hostname Select advanced filter and set this to include hostname ...


1

How about making templates like Template:English word with its contents looking like this? 中文<noinclude>[[Category:Glossary]]</noinclude> In your wiki pages, write, for example, 当前的{{English word}}维基 which should result in 当前的中文维基 The noinclude portion in the template code is optional, but would allow you to maintain a glossary page ...


1

You should definitely have a different URL for each language for SEO. In your pages you can use Links in the header to inform the bot or useragent of the other languages: <link rel="Alternate" hreflang="en-US" title="English content" href="/english/page.htm" /> <link rel="Alternate" hreflang="nl-NL" title="Dutch translation" href="/dutch/page.htm" ...


1

There is the "lang" attribute in HTML, which you can add to the parent element: <html lang="en"> - however Google basically ignores it. Even if that wasn't the case I don't think your system would ever work, as the same URL would be returning different content. You should have different URLs for different languages - either subdomains or separate ...


1

I'm pretty sure Google will not like it. It's bots come from the US and will only see your US content which means that's likely the only content it will see and add to its index. It could also be seen as a potential violation of webmaster guidelines. Serving up different results based on user agent may cause your site to be perceived as deceptive and ...


1

You can use World Lingo to translate the site and then save the source. I just tried this on my homepage and it worked fine. http://www.worldlingo.com/en/websites/url_translator.html Or you can install a dynamic translator on the page. I found this blog entry that explains how to do that: ...



Only top voted, non community-wiki answers of a minimum length are eligible