Tag Info

Hot answers tagged

25

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


14

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


11

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


8

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


5

This is the same question I asked on StackOverflow. And I got a recource for it, ill post the answer. 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 the multi-lingual websites for a while now. There are definitely some points in the article ...


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


4

Google Webmaster Central has a great blog post discussing this topic: http://googlewebmastercentral.blogspot.com/2010/03/working-with-multi-regional-websites.html


4

I would suggest utilizing a 301 redirect to a new subdomain location. Subdirectories aren't handled as well from an SEO perspective, and it also diminishes the geo-focus of a site. I say this based off of practice, lest you wonder. Another question is where the hosting is occurring for the international domains? Do you have them hosted in those countries ...


4

I can't tell you what the consequences of this will be for sure but I think you can do this and reasonably manage your rankings if you follow best practices. If possible do a 301 redirect from the old URLs to the new URLs. This means for each and every page. This will let the search engines, and users, know the page has moved and let them know the location ...


4

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


4

The canonical tag tells spiders and other automated thingies that all URLs that return pages with the same tag are all effectively returning the exact same page. I don't think you want to tell robots that your UK and US pages are identical unless they really are. Do they show different currency? Do they maybe even spell words differently? Furthermore, ...


4

Google has written a fair amount on the recommended way to present multilingual content: http://googlewebmastercentral.blogspot.com.au/2011/12/new-markup-for-multilingual-content.html They also have a fair amount of detail in terms of implementation on this subject: http://support.google.com/webmasters/bin/answer.py?hl=en&answer=182192


4

Looking at the wikipedia page on IP Addresses: The Internet Assigned Numbers Authority (IANA) manages the IP address space allocations globally and delegates five regional Internet registries (RIRs) to allocate IP address blocks to local Internet registries (Internet service providers) and other entities. I'm no expert, but what I think that ...


4

After reading Christofian's answer, I did some research and found out that the five Regional Internet Registry members (APNIC, AFRINIC, ARIN, RIPE, and LACNIC) each maintain a copy of the allocated IP address ranges and the associated countries on their public FTP servers. This information is updated daily and mirrored between the five servers. For example, ...


4

As Stephen said, it is mostly likely an attempt at defining locale. In some of the web-based software that I've worked with, I've come across form values and URLs like: <input type="hidden" name="lc" value="US"> Or page.php?id=233&lc=FRA The meta tag for "lc" is undocumented, which means that it is either a mistake or some sort of custom tag ...


3

Use numbers only. I've seen Russian, Chinese, and other non-Roman language sites take this approach. Presenting Roman captures is unwise, as it's not safe to assume that mangled alien characters will be legible to non-native speakers. (I find them hard to decipher at the best of times.) You might also consider omitting CAPTCHAs altogether by using a service ...


3

I don't think reinventing the wheel is the right path. There are a lot of standards currently on use. I think if you wanna markup your elements correctly, start from the basis: there is a global HTML attribute named lang for this purpose. <html lang='de-de'> <html lang='en-us'> ... for an element only <html lang='pt-br'> ... ...


3

What you're looking for is called Punycode. You can do pretty much any Unicode character with it, I believe. Verisign have a nifty conversion tool here. In your scenario, mjölk.com translates to xn--mjlk-6qa.com - xn--mjlk-6qa.com is the domain you'll need to register and the DNS entries you'll need to create if you want that IDN. (You can try this in ...


3

Not a complete list: USA Canada Australia China (PRC) Mexico Malaysia Italy (strictly speaking; we don't collect Italian provinces and I don't think we've ever had a problem with sending mail there) To the best of my knowledge no other European country requires states/provinces in addresses. Also see ...


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

There is a free version of a GeoIP database available from Software77. In their FAQ page they say: We cannot add or remove IPs from the database. The process we use is automated and the IPs in the database are as as we get them from the various registries around the world. If a registry does not list an IP the only way to get it in our database is for ...


3

Wherever feasible, ccTLDs should be first preference. Google recognise them and try to target a site accordingly. User preference should be considered too, as users in some countries exhibit strong preferences for sites on their own ccTLD. For example, a "survey conducted by AFNIC in June 2010 showed a marked preference among French people for .fr domain ...


3

I have localized sites in English for US/UK/AU/IN, in Spanish for ES/MX and in Portuguese for PT/BR. I would recommend splitting out the localized sites into separate top-level or sub-domains. You won't get hit with any duplicate content penalties. Google understands when content is localized like this and allows the same content on multiple sites. When ...


3

Using a combination of localised sites (de.example.com or www.example.com/de/), with a global default landing page at www.example.com in conjunction with conditional redirects based on Accept-Language value is a common and perfectly search engine friendly approach, if properly optimised. Optimise the regional variants by applying lang attribute for those ...


3

also geotarget the subfolder to the main territory he would wish to target for that langauge? You can specify the region (as well as the language) in the hreflang attribute. However, whether you should or not is really dependent on your subject matter. You say that these other languages are simply translations of the English version, so I would guess ...


3

Ok. Found the answer at: Help Google serve the correct language to your visitors We need to have a url tag for each of the url and specify the others as alternate urls.


3

It is not valid. ea.com is using HTML5, but in HTML5 it is only allowed to use name values that are defined in the specification, or registered on the WHATWG wiki page MetaExtensions. lc is not included. If they were using older HTML versions (e.g., HTML 4.01), it would be valid to use this value.


3

This happens when a page includes a hreflang link to an alternate language, but the linked page doesn't link back to it. This Official Google Webmaster Central Blog post explains that: Annotations must be confirmed from the pages they are pointing to. If page A links to page B, page B must link back to page A, otherwise the annotations may not be ...


2

Since your site appears to serve country-specific information at different URLs, you could provide a sitemap to help search engines discover them all. Just make sure you don't block access to any countries due to the assumptions you make based on IP. Always give the user (or in this case, Web crawler) the option to choose a different country.



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