Hot answers tagged

51

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. Advantages Fully supported by Google. You can add the sites to Google Webmaster Tools where ...


19

Answering a question similar to yours on his blog, Matt Cutts suggests: If you have sites with say French and German versions for a business, my preferences would be: ccTLDS such as example.fr or example.de After than, subdomains such as fr.example.com or de.example.com. If that’s not possible, I’d use subdirectories such as ...


14

In my opinion, you should use either the folder or subdomain approach, because they are more intuitive to the user. Which one is a matter of personal taste, I personally find the folder approach clearer. The filename option is far less intuitive. Parsing the Accept-Language header for directing the user to the correct content on his first visit is a good ...


11

Content-language is going away soon (note the big red "obsolete"), and I'm not sure language was ever official. The W3C recommends this instead: <html lang="en"> The lang attribute works with most tags (except <script />, <br />, <frame />, etc), so you can mix, match, and cascade: <p>This is English, since the html tag ...


11

I've been told that .htaccess should be avoided when possible, as it reduces the server performance and new servers disables it or just don't implement it anymore. The part about compatibility is absolutely not true; the part about performance is kinda true but probably irrelevant for you. What the person you quote was probably talking about is that ...


10

As a German user I hate it when a website won't let me on the English page because it's think it knows better what I want. It might be hard for Americans to understand but there are actually people who speak more than one language. Sometimes I might want to view the German websites and sometimes I might want to view the English one. Simply parsing the ...


8

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. For ...


8

Looks like it. This example comes from the HTML5 specs: For example, the following link is a French translation that uses the PDF format: <link rel=alternate type=application/pdf hreflang=fr href=manual-fr>


6

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 ...


6

...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 ...


5

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 ...


5

Use subdomain option if you use localized versions (i.e. France != French). Use subdomains, but I think it's better use directories if this country uses diferent languages. For example: us.domain.com (USA) us.domain.com/en/sample.html (USA - english) us.domain.com/es/ejemplo.html (USA - spanish) es.domain.com (Spain) es.domain.com/es/ejemplo.html (Spain - ...


5

This is the same question I asked on Stack Overflow. And I got a resource for it, which I’ll post as an answer here. I have found a nice resource from Google on the choices you can make. There is a section with pros and cons of each method you can use. I have been struggling with multi-lingual websites for a while now. There are definitely some points in ...


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

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 ...


5

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.


5

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 ...


4

If your site is handling personal data then it must (i.e. its practices for handling personal data must) comply with EU data protection laws (see the EU Data Protection Directive 95/46/EC for the definition of personal data). However, there is nowhere in the European Union a requirement for a website to have its privacy policy posted - except for "cookies". ...


4

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, ...


4

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 ...


4

I ended up emailing Google. MY LETTER 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 ...


4

Those are user agent language headers, not content language tags.


4

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 ...


4

An XML sitemap will show them where to find the alternative language pages. You can also put links in the footer of your pages linking to other languages. This is good usability as it allows people to easily find the language of their choice if they accidentally ended up on the page in a less-preferred language.


4

There isn't any cross-browser compatibility issues AFAIK. But it makes the most sense and is most commonly used by putting it in html since your document isn't just limited to body. See this page for the purpose of lang and this page for the proper use of lang versus other ways of specifying language. Since lang only specifies the language of the current ...


4

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 ...


3

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 ...


3

How should I SEO a page like that? you should firstly think about: what SEO value has the page? To be honest, the answer would be: nearly zero. then you should think about users, who maybe are looking for your page. What they are looking for? Which are keywords? How high (rather low) is the search volume of those keywords? Not every page needs to be ...


3

As this page is for people that can speak English and want to learn Italian, the URL path as well as most parts of the content (the header, the navigation, the footer, etc.) should be in English. If you care about semantic HTML, you should use lang="en" on the html element, and lang="it" on the elements that contain the Italian translation. I don’t agree ...


3

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 ...



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