| 1:34 pm on Sep 19, 2012 (gmt 0)|
They will only see the English content.
You'll need a different URL to serve the other languages. Could be as simple as ?lang=xx on the end.
| 2:23 pm on Sep 19, 2012 (gmt 0)|
Here Google recommends not to use parameters for different languages [googlewebmastercentral.blogspot.de...]
And jet they use them all over the place [support.google.com...]
Here they say: "Keep in mind that Google ignores all code-level language information, from “lang” attributes..." [googlewebmastercentral.blogspot.de...]
And here they recommend lang attributes: [support.google.com...]
Can someone bring light in the darkness?
| 8:17 pm on Sep 19, 2012 (gmt 0)|
Apples and oranges. One thing is "lang" in the query string. The other is about "hreflang" in links, leading to language-specific subdomains or to different forms of the URL itself.
I particularly like
Link: <http://es.example.com/>; rel="alternate"; hreflang="es"
| 10:45 pm on Sep 19, 2012 (gmt 0)|
google recommends against specifying a language in the url with parameters for geotargeting reasons:
|Google generally uses the following elements to determine the geotargeting of a website (or a part of a website): |
Webmaster Tools' manual geotargeting for gTLDs (this can be on a domain, subdomain or subdirectory level) ...
aside from GWT manual geotargeting, a (sub)domain can be locally hosted if necessary:
|2. Server location (through the IP address of the server) is frequently near your users. |
| 8:25 am on Sep 20, 2012 (gmt 0)|
Thanks for the info!
Geotargeting in GWT is not an option, since 20+ different countries are targeted with 2 different languages and in GWT you can only use one country not language.
| 11:27 am on Sep 20, 2012 (gmt 0)|
|If you want to reach all speakers of a particular language around the world, you probably don't want to limit yourself to a specific geographic location. This is known as language targeting, and in this case, you don't want to use the geographic target tool. |
| 4:16 pm on Sep 25, 2012 (gmt 0)|
What if I dynamically change hreflang=x and point to the page itself in the header depending on the users location?
English version: example.com
<link rel="alternate" hreflang="en" href="example.com" />
German version: example.com (same URL)
<link rel="alternate" hreflang="de" href="example.com" />
Can this work?
| 7:36 pm on Sep 25, 2012 (gmt 0)|
|The user will get the language (+cookie) based on his IP location. |
This is bad from the usability point of view. If I surf from a different country, the website will offer me a wrong language, and in fact I am wondering if I will be able to change it at all (depending whether the overriding preference is set by cookie or by IP).
With regards to which language will Google detect, if you have language only recorded in cookie and not as a part of URL, Google will only see English. So the website will miss on potential rankings on other languages.
|What if I dynamically change hreflang=x and point to the page itself in the header depending on the users location? |
If you want to do this because of Google, this will not work - Google will still only see English. The only way for Google to see other languages is to have language parameter in URL (either for all languages or only for non-default language).
| 5:30 pm on Sep 26, 2012 (gmt 0)|
Ok thanks. Will push this in the IT department.