Upper case or/and lower case in rel="alternate" hreflang
-
Hi Mozzers,
I have a question about the rel="alternate" hreflang tag, with an example.
When I use two subfolders for two different countries/languages, for instance www.domain.com/nl-nl/ and www.domain.com/nl-en/ (for the English version) and I want to use the rel="alternate" hreflang tag, do I need to follow the ISO standards concerning Uppercase country code and Lowercase language code (en-NL)? Or is it okay to use the Lowercase country and language code (en-nl), since we also use this in the URL of the Subfolder.
What does Google prefer?
Thanks in advance.
-
Hey there, Lowercase is fine.
Not sure why you would have /nl-nl/ and /nl-en/ though, it's either English or Dutch, right?
I've set this up many times before and it works just fine, although it's sometimes a little overkill unless you have the English version of a page ranking higher than the Dutch version in Google.nl for example.
I usually find adding these as separate websites in WMT's and setting the target country correctly for each site you shouldn't have any problems.
So add http://www.domain.com/nl/ as its own site in WMT and set target country to Netherlands, then add http://www.domain.com/en/ as another site and set its target country to UK.
Hope this helps,
Goodluck,
Woody
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Hreflang alternate as single-hop 301 - is this actually a problem?
First, this is not a question about whether 301 redirects pass page rank. My question is that if your hreflang alternative page URL is a 301 redirect*, are there any downsides. In all cases with our situation, the 301 redirect is single-hop and working. Tools, such as SEMRush seem to flag this as a non-canonical hreflang error, but I'm not able to find any cases where Google has suggested a redirecting hreflang is a problem. I'd appreciate any information on this issue before we invest extra time on a large international site. *In Drupal, there are scenarios where it's all but impossible to avoid having a 301 redirect in your hreflang alternate URL without significant custom work.
International SEO | | scottclark0 -
Should Hreflang x-default be on every page of every country for an International company?
UPDATED 4/29/2019 4:33 PM I had made to many copy and pastes. Product pages are corrected Upon researching the hreflang x-default tag, I am getting some muddy results for implementation on an international company site older results say just homepage or the country selector but…. My Question/Direction going forward for the International Site I am working on: I believe I can to put x-default all the pages of every country and point it to the default language page for areas that are not covered with our current sites. Is this correct? From my internet reading, the x-default on every page is not truly necessary for Google but it will be valid implemented. My current site setup example:
International SEO | | gravymatt-se
https://www.bluewidgets.com Redirects to https://www.bluewidgets.com/us/en (functions as US/Global) Example Countries w/ code Site:- 4 countries/directories US/Global, France, Spain Would the code sample below be correct? https://www.bluewidgets.com/us/en/ (functions as US/Global) US/Global Country Homepage - https://www.bluewidgets.com/us/en/ US/Global Country Product Page(s) This would be for all products - https://www.bluewidgets.com/us/en/whizzer-5001/ http://www.bluewidgets.com/us/en (functions for France) France Country Homepage - https://www.bluewidgets.com/fr/fr/ France Country Product Page(s) This would be for all products- https://www.bluewidgets.com/es/es/whizzer-5001 http://www.bluewidgets.com/us/en (functions as Spain) Spain Country Homepage - https://www.bluewidgets.com/es/es/ Spain Country Product Page(s) This would be for all products - https://www.bluewidgets.com/es/es/whizzer-5001 Thanks for the spot check Gravy0 -
Multiregional / Multilingual SEO - Subfolders Question
Hello all, I wonder if you can help me... I have a question about subfolders in multi-regional / multi-lingual SEO - more specifically in reference to targeting the UK and the US. Having looked at some global websites these are the types of implementations I've most commonly seen: UK subfolders .com/uk .com/gb .com/gb/en-gb | .com/en-GB .com/gb-en .com/en-gb .com/uk/en US subfolders .com/us .com/us/en-us | .com/en-US .com/us-en .com/en-us .com/us/en Are any of these approaches better than others or is it all a matter of personal preference? What's the reason for using .com/gb over .com/uk (or vice versa) for example? Secondly, my assumption is that the examples above which include language subfolders do so because these companies are targeting different speaking users within these countries. Would I be right to think that since the organisation I work for is only targeting the American speakers in the US, we wouldn't need to go so far as to have language subfolders in addition to location subfolders? Would be great to get some feedback / suggestions! Thanks!
International SEO | | SEOCT0 -
Why Google is not indexing each country/language subfolder on the ranks?
Hi folks, We use Magento 2 for the multi-country shops (its a multistore). The URL: www.avarcas.com The first days Google indexed the proper url in each country: avarcas.com/uk avarcas.com/de ... Some days later, all the countries are just indexing / (the root). I correctly set the subfolders in Webmaster tools. What's happening? Thanks
International SEO | | administratorwibee0 -
Is this setup of Hreflang xml sitemap correct?
Hi, I'm trying to setup hreflang for 2 domains. One is purely a US site and the other domain has the language-country as subdomains. For example: http://www.websiteUSA.com (Targets English - USA) https://www.websiteINT.com/en-CA (Targets English - Canada) https://www.websiteINT.com/fr-CA (Targets French - Canada) https://www.websiteINT/es (Targets Spanish) ..and so on and so forth for about 12 of these international URLs. I created an XML sitemap that looks something like this: <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml"><url><loc>http://www.websiteUSA.com</loc></url></urlset> <url><loc>https://www.websiteINT.com/en-CA</loc></url> <url><loc>https://www.websiteINT.com/fr-CA</loc></url> Question 1: Is this correct? In my actual file, I have all the countries listed and self-referencing. Question 2: I'm hosting this file at https://www.websiteINT.com/hreflang.xml AND at http://www.websiteUSA.com/hreflang.xml. Is this correct? Question 3: Will this help the SERPs direct english speakers from the US to http://www.websiteUSA.com while show SERPs for say English Speakers in Canada to https://www.websiteINT.com/en-CA? Question 4: For some reason, when I put up the xml site, it only listed each URL once instead of the full XML file. Should I have uploaded a text file instead? It doesn't seem to render correctly. Thank you!
International SEO | | SylviaH0 -
/en-us/ Outranking Root Domain and other hreflang errors
I'm working with a new site that has a few regional sites in subdirectories /en-us/, /en-au/, etc and just noticed that some of our interior pages (ourdomain.com/en-us/interior-page1/ ) are outranking the equivalent ourdomain.com/interior-page1. This only occurs in some SERPS while others correctly display the non-regional result. I was told we have hreflang tags implemented correctly in the meta information of each of our pages but have yet to research deeply. Should we even have a /en-us/ version when our root domain is the default version, in english, and targeted to US primarily? Any help would be appreciated as I am a little lost. Cheers, Andrew
International SEO | | AndyMitty0 -
Alternate Hreflang Problem
We have two travel websites.
International SEO | | Izzet
One in English language for people living in the UK.
One in Turkish language for people living in Turkey. The major difference is:
English (UK) website shows 4+ nights accomodation prices because UK travellers never come for less than 4 nights.
Turkish website shows 1-night, 2-night, 3-night prices because Turkish travellers never stay for more than 3 nights. We are using rel="alternate" hreflang="x" tags properly on our two websites. Today, I am disappointed to see Google display the wrong result. When a user in Turkey searches a Turkish keyword on Google.com.tr;
Google is showing the English language website. When I click on Search Settings > Language;
I see that English is selected under this question:
"Which language should Google products use?" This is a big problem for us.
Many rich users in Turkey, who are more willing to buy our services, speak English fluently and they may choose to use Gmail in English. But we are losing business because these Turkish customers don't convert at all on the Enlish (UK) website because of the reason I explained above. 1) What can we do?
2) If we remove the rel="alternate" hreflang="x" tags now, will it hurt any of the websites?
We have seen an increase in Google rankings for the Turkish language website after using rel="alternate" hreflang="x" tags. Izzet0 -
Is having duplicated content on different domains a problem when using alternate tag, but no canonical?
We will be launching a couple of new language versions. I understand that ccTLD is mostly considered as best option, however I thought that to start with it might be better to launch the new language version first on a subdirectory of our established domain with strong backlink profile as it may rank much better until I can attract some strong links to new ccTLD. I would wait for the pages of new language versions to be indexed on the main domain and then after a month launch the same content paralell on the ccTLD setting up an alternate tag in the main domain pointing to the ccTLD. I would not setup any canonical tag. As I understand google would rank whatever of the 2 versions ranks higher. Should not cause duplicated content issues right?
International SEO | | lcourse
Any thoughts? EDIT:
For clarification. The language we are launching are mostly spoken in several countries. E.g. for Portuguese I would add in main domain an altnernate tag for Brazilian visitors to Brazilian ccTLD, but no alternate tag for Portuguese visitors. For Corean I would add in main domain an alternate tag for visitors in south corea, but not one for visitors in north corea.0