There are many acceptable ways to structure your site for both SEO and internationalization. Each have advantages and disadvantages.
Top Level Domains
Buy the same domain name at multiple top level country domains like example.com, example.es and example.de.
Fully supported by Google. You can add the sites to Google Webmaster Tools where ...
Google Analytics Spam is linking to THIS discussion thread now. If you got to this thread because you saw a referral in your Google Analytics, YOU HAVE BEEN FOOLED. Check the Language for those referrals ("...Vote for Trump"), then read this article for the details and a filtering solution:
You can ignore this. It has no impact on your site.¹
What is happening?
When requesting resources from your site, clients (i.e., bots, humans using a browser, …) can send additional request headers (e.g., User-Agent, Referer, Accept) with values of their choice.
The Accept-Language request header tells the server which language(s) are acceptable for the ...
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 ...
Some SEOs are wary of using these non-Latin characters in URLs because
of the way it might display in certain browsers, or in certain text
cases when the link is copied and pasted somewhere online. While
having spammy-looking links is never a good thing, I personally think
the possible benefit in search results is worth the drawback.
Looks like it. This example comes from the HTML5 specs:
For example, the following link is a French translation that uses the
<link rel=alternate type=application/pdf hreflang=fr href=manual-fr>
...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 ...
The problem with your set-up (from an SEO standpoint) is that search engines don't accept cookies, so whenever a bot follows a link to your root domain, it'll be sent to your English content. Hopefully, there's an abundance of links to the other language content, too, but in my experience, this situation nevertheless seems to lie at the root of a lot of ...
The idea of the rel="alternate" hreflang="xx-XX", as I understand it, is ultimately to stop duplicate (or near duplicate) content that is intended for discrete regions from competing with itself or being actively penalised as duplicate content.
So the specification of alternates won't stop them from showing in search in regions that aren't targeted (or ...
There is no big SEO advantage using either top level domains, sub-domains, or sub-directories. This is well covered in the question: How should I structure my URLs for both SEO and localization?
The biggest differences are going to be:
Top level domains and sub-domains allow you to move the hosting near the users by getting servers that are in the correct ...
The only way to change this is by replacing the button, (e.g. with SWFUpload) but I don't see why you would want to.
You shouldn't change the user's system language. They've chosen their system language for a reason, and there's an expectation that their UI will be rendered in this language that they can read/understand.
The W3C provides this very long guide on choosing language tags/subtags.
The important bits:
Language tag syntax is defined by the IETF's BCP 47. In the past it
was necessary to consult lists of codes in various ISO standards to
find the right subtags, but now you only need to look in the IANA
Language Subtag Registry. We will describe the new ...
You should use the lang attribute (e.g., on the html element) to declare the language, not a meta tag.
This allows you to overwrite the language declaration for other parts on the page (note the lang attributes in my example markup for a language switcher).
Anyway, having a few words in a different language shouldn’t affect your SEO at all, whether you use ...
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, the only ...
Permalinks, like all other site content, should be in the native language of the website if possible.
As far as I know, there is no SEO benefit to having permalinks in a different language from the website content, and it would seem to me to be a poor choice regarding user experience.
If you think about it, your Polish-speaking customers are not going to ...
All data on a page should be in the same language to make language detection easier for search engines. On a page with <html lang="fr"> English keywords could actually be harmful because (at least) Google doesn’t use just the lang attribute to determine the real language.
In practice … I wouldn’t waste time with keywords. I don’t know any relevant ...
Well, I don't know how to merge them into Google Analytics, but I can answer the first question.
de or de_de are (obsiously) the same. They are Language tags.
de is a Language subtag
de-de is a Region subtag.
A few examples of language tags:
fr: French language,
en-AU: English language, as written and spoken in Australia,
az-Latn-IR, Azeri language, ...
I ended up emailing Google.
If my website is written in English, but I allow my visitors to
temporarily translate the page using the Google Translate tool, do I need to remove
unsupported adsense languages from the Google Translate tool? Since the
translation is a temporary one I assume that the language is primarily
in English and thus not in ...
As of Jun 10, 2014 Google recommends either ccTLDs, Subdomains with gTLDs or Sub-directories with gTLDs. URL parameters such as ?lang=en are not recommended:
(Funny that the page which says that it's not recommended to use URL parameters for this, is actually doing exactly this.)
I don't speak Albanian, but I ran a little test on google.al. When I type keng in the search box, it offered me kenge and keng popullore in the drop box.
keng popullore returns many music videos and some include the këngë spelling in their title.
This confirms what I thought. Google can deal with incorrect spellings in your language. If I were you, I would ...
You'll have better user metrics, if you create slugs in language according to the language version:
users will easier remind about page addresses to visit them twice,
users will faster understand the page's topics reading them in their mother tongue,
in general, you get all benefits of using mother tongue instead of foreign language.
such setup ...
To answer your questions:
If you do not have localized country-specific versions of your site live at the https://www.construct.net/en-us and https://www.construct.net/fr-fr URLs, then remove those lines. By just having en and fr, they will act as a catchall for all language regions.
Google shouldn't be showing the French version in normal English results, ...
As further addition, consider that the California Online Privacy Protection Act (in practice reflecting on any ...
Adding nofollow generally does not prevent Googlebot from discovering content. See: Does a "nofollow" attribute on a link prevent URL discovery by search engines?
If the nofollow link is the only link to that page, then Google won't index it. In your case, I highly doubt that your alternate language links are the only links into your other sites. Once ...
No you cannot do this using hreflang, they are primarily for language and location is optional, but you cannot just mark up the location:
Do not specify a country code by itself! Google does not automatically
derive the language from the country code.
Use hreflang for language and regional URLs
I think the other option here is to try and detect what ...
The fact that http://www.productontology.org/id/Vinothek works (it redirects to http://www.productontology.org/id/Enoteca) is not because it’s called "Vinothek" in German, but because the English Wikipedia has a redirect from Vinothek to Enoteca.
The PTO only uses the terms from the English Wikipedia:
You can use this ontology to describe any object for ...
I think it’s better to include the language code for the default language, too. Quoting the pros from my answer on Stack Overflow:
If you decide to change the default language, you don’t have to change your URLs.
It allows you to redirect from / based on the visitor’s language preference.
It’s a signal that your site is available in ...