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 ...
...is it considered to be duplicate content if the site is in another
language which happens to be an exact duplicate?
Google doesn't consider the same content translated into different languages as duplicate content since the same content in English that's translated into French is different, unlike the same content appearing twice in English, as ...
One thing to note is that when Google suggests, "This page is in XYZ" and offers translation, it doesn't necessarily mean it thinks the entire page is in that language. Even if it thinks that just a very small part of the page is in that language it offers the same option to translate the page.
In your example, if you click on the translate link, ...
It makes no difference, how you translate your content. Main keywords are always: proofreading and curation. If these procedures give you the go - then everything is OK.
Google translate or Bing or Promt or a million other translation services - really no difference. They all do their job - more or less good, depending on complexity of the content and ...
It is against Google's webmaster guidelines to put machine translated text where Googlebot can find it and index it. Google will penalize your site for auto-generated content for doing so.
Here is the excerpt from the guidelines:
Q: Can I use automated translations?
A: Yes, but they must be blocked from indexing with the “noindex” robots meta tag. We ...
No, Google does not view translated content as duplicate, as content in another language is different than if it is appearing in the same language twice.However, it is recommended to have a human translation as Googlebots can tell if the site has been translated using Google Translate and may view it as 'spammy'.
The URLs should be in the same language as the content. Ideally you would also translate the relevant path segments (like "product" in your example), not only the slug.
A URL that’s in a language users might not understand is useless for them. A good URL is descriptive, it gives an idea what the content is about. If it’s in a language the users don’t ...
Google determines language by running your page through a machine learning algo, they don't use tags:
Google uses the visible content of your page to determine its language. We don’t use any code-level language information such as lang attributes, or the URL. You can help Google determine the language correctly by using a single language for content and ...
The Google Translate Toolbar only appears to send analytics events for the old (non-universal) analytics. I developed the following workaround. Just:
Ensure you set gaTrack: true and gaId: 'xxx' in your translation toolbar settings
Include the below script on your page alongside the translate snippet
* Capture Analytics for Google Translate
* As of ...
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 translate....
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 ...
As noted by Waldir:
You should specify the link and the link label as system messages and create language code subpages of said messages for them to follow user interface language. See the manual for more. For instance * portal-url|portal with [[MediaWiki:Portal]] being "Portale" and [[MediaWiki:Portal/en]] "Portal" (on an Italian wiki).
You can also use ...
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 ...
The purpose of hreflang is to help Google with geotargeting your website, especially if you are having all your language versions in different subfolders on a gTLD domain (like .com, .net, .org etc.). So its main purpose is to serve the correct version of your website to the user, depending on their language and region. It can also help prevent from ...
Multi-regional and multilingual sites
A multilingual website is any website that offers content in more than
one language. Examples of multilingual websites might include a
Canadian business with an English and a French version of its site, or
a blog on Latin American soccer available in both Spanish and
A multi-regional website is one that ...
Is that possible to rename the greek files to something like the following example:
should be renamed to
eg: Remove the -gr of all the greek documents and add /gr at the end. Also only for index file, example.com/index-gr.html should be example.com/gr
Theres a couple ways you ...
Google will reward each version of the page on its own merits, in fact, it's common if not expected that some languages have fewer words or more words than one compared to another. This also means more or less headers, again, each version is treated separately.
As long as you DO NOT use auto-translate software then you will be okay.
Everything you have done so far is correct:
Created separate URLs for the content in different languages. (See How should I structure my URLs for both SEO and localization?)
Put in hreflang meta tags.
Created XML sitemaps of the language URLs. (Although XML sitemaps have little to do which which pages Google chooses to index, see The Sitemap Paradox)
Put a ...
Problem with duplicate content becomes important when most of the pages content exactly the same content on several places, but Google as a ratio of allowed duplicate content that is allowed for example for the copyright zone, the menus, etc.
The main problem with untranslated titles is that you will have a lower Click-Through-Rate on French Queries and you ...
If you already have an English version of the site you could make this the default page and use the href=lang tag on any other language versions to specify to Google that these are the language equivalents of the English page.
This lets Google determine which language the page should be set to based on the version of the website the user is visiting. For ...
Marking it up in sitemap:
The problem is with navbar and if you use some kind of automation to "related pages", social media and all the other stuff. If it is just for a few static ones the sitemap and meta tags are ...
There is a video at Google Webmasters Youtube channel that presents a slide with a closed list of what is considered by Google as a duplicate content:
What's duplicate content?
Exact same page, or same content (or piece of content)
www / non-www / http / https / index.html / ?utm=...
Separate mobile-friendly URLs, printer-friendly URLs, CDN hosts
In both cases, adding content to your site (whether original or a translation) does not per se improve SEO. What you need are inbound links. If those posts get you inbound links, then they will improve SEO. If they don't, other than possibly adding a few matches for non-competitive requests, they won't do much for you.
Why creating pages for each language is pointless?
That is the only way of doing it, you can put your keywords to same page in every language, but that looks bad and you might get penalized by Google too.
Istockphoto for an example has separate pages for different languages too. To be more precise they have them under different subdomains.
Could you code in an event listener that pings for every keypress instead of the default space / enter key press?
Google Search API and widgets usually have an auto-suggest option, which works the same as you want this to. However, I couldn't find an exact equivalent for the transliterate API, so your only option would be code this in yourself.
Back when Google still had the free Translate API there where terms which would have made this against the rules as the terms stated that it was for the purpose of translating source content to an alternate language for end users to be able to read or for translating user content from their source language to the site language. Since the depreciation of the ...
Disavowing was the first suggestion I had.
I would file a complaint with Google. Once the claim is processes they will de-index the page or hit them with a manual action that will knock them from the SERP (though neither are guaranteed).
Because this is only for search engines and communicating where to find your site - you could move all of this code over to your Sitemap and submit it in the search engine of your choice's Webmaster interface.
Make it as big as you like, without bloating your HTML. There's no limit!
No need to worry about confusing header link structures.
Use x-default for the default version of your website that you haven't targeted yet by another hreflang. For your information, Google don't mention canonical.
From your code you have added to your question i can see a misconfiguration