Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Hreflang for bilingual website in the same region/location
-
Hi everyone,
got a quick question concerning the hreflang tag.
I have a website with 2 different language versions targeting to the same region(Reason: The area is bilingual however not everyone speaks the other language fluently)
Question:
Can I use hreflang in that case like:Many thanks in advance
-
Sure, I did this: http://bfy.tw/2hTu
-
Hi Dmitrii,
can you perhaps tell me the source, where you found the supported annotations above. Many Thanks
-
My answer is the correct. See what I replied above to Dmitrii
-
Lol! You're right. I was indeed thinking about Belgium and not Netherlands

-
It's a cultural thing. I'm that province of Italy people talk or Italian or German, so if you want to target both with your multilingual site you must tell it to Google with hreflang, even if it is not listed in the ISO chart.
you do the same for targeting Spanish speaking people in the usa, for instance.
-
Gianluca - I guess this time it's my turn: As far as I know they only have one official language in the Netherlands (Dutch) - I guess you refer to Belgium (3 official languages Dutch/French/German).
It's a common error to make this mistake - but the difference is easy to spot: Belgium is qualified for Euro '16 - unlike the Netherlands

-
Hi Gianluca,
Thank you for your reply. In fact I'm refering to that exact region. The difference to your CH examples are though, that in Switzerland, the 3 language regions are not the exact same "location".
In my case they are though so I got a bit confused.
So basically Im not saying, a specific region in Switzerland speaks French, another German and another Italian, but I say the exact same location/region speaks German and Italian.
-
Well, I do see the ones you mentioned on that list, but not it-it or de-it.
-
Yes, it exists (it is Alto Agide/South Tirol), and it's the same case of Netherlands (fr-NL and de-NL) or Switzerland (it-CH, fr-CH and de-CH)
-
Yes, you can.
-
Interesting. Google search doesn't return anything on this locale.
-
yes, sure about that
-
Are you sure that locale exists?
-
Hi Dmitrii,
many thanks for your reply. Great list, unfortunately I can't find my case. Though I think this list is not complete. E.x. I miss the the french speaking part in Italy for example,...
Helpful anyway though.
-
Hi there.
I found this list of all available locales, if locales you're trying to do are in this list, then go ahead, otherwise it won't work.
P.S. List might be old and updated by now, but i don't think so.
- af-ZA
- am-ET
- ar-AE
- ar-BH
- ar-DZ
- ar-EG
- ar-IQ
- ar-JO
- ar-KW
- ar-LB
- ar-LY
- ar-MA
- arn-CL
- ar-OM
- ar-QA
- ar-SA
- ar-SY
- ar-TN
- ar-YE
- as-IN
- az-Cyrl-AZ
- az-Latn-AZ
- ba-RU
- be-BY
- bg-BG
- bn-BD
- bn-IN
- bo-CN
- br-FR
- bs-Cyrl-BA
- bs-Latn-BA
- ca-ES
- co-FR
- cs-CZ
- cy-GB
- da-DK
- de-AT
- de-CH
- de-DE
- de-LI
- de-LU
- dsb-DE
- dv-MV
- el-GR
- en-029
- en-AU
- en-BZ
- en-CA
- en-GB
- en-IE
- en-IN
- en-JM
- en-MY
- en-NZ
- en-PH
- en-SG
- en-TT
- en-US
- en-ZA
- en-ZW
- es-AR
- es-BO
- es-CL
- es-CO
- es-CR
- es-DO
- es-EC
- es-ES
- es-GT
- es-HN
- es-MX
- es-NI
- es-PA
- es-PE
- es-PR
- es-PY
- es-SV
- es-US
- es-UY
- es-VE
- et-EE
- eu-ES
- fa-IR
- fi-FI
- fil-PH
- fo-FO
- fr-BE
- fr-CA
- fr-CH
- fr-FR
- fr-LU
- fr-MC
- fy-NL
- ga-IE
- gd-GB
- gl-ES
- gsw-FR
- gu-IN
- ha-Latn-NG
- he-IL
- hi-IN
- hr-BA
- hr-HR
- hsb-DE
- hu-HU
- hy-AM
- id-ID
- ig-NG
- ii-CN
- is-IS
- it-CH
- it-IT
- iu-Cans-CA
- iu-Latn-CA
- ja-JP
- ka-GE
- kk-KZ
- kl-GL
- km-KH
- kn-IN
- kok-IN
- ko-KR
- ky-KG
- lb-LU
- lo-LA
- lt-LT
- lv-LV
- mi-NZ
- mk-MK
- ml-IN
- mn-MN
- mn-Mong-CN
- moh-CA
- mr-IN
- ms-BN
- ms-MY
- mt-MT
- nb-NO
- ne-NP
- nl-BE
- nl-NL
- nn-NO
- nso-ZA
- oc-FR
- or-IN
- pa-IN
- pl-PL
- prs-AF
- ps-AF
- pt-BR
- pt-PT
- qut-GT
- quz-BO
- quz-EC
- quz-PE
- rm-CH
- ro-RO
- ru-RU
- rw-RW
- sah-RU
- sa-IN
- se-FI
- se-NO
- se-SE
- si-LK
- sk-SK
- sl-SI
- sma-NO
- sma-SE
- smj-NO
- smj-SE
- smn-FI
- sms-FI
- sq-AL
- sr-Cyrl-BA
- sr-Cyrl-CS
- sr-Cyrl-ME
- sr-Cyrl-RS
- sr-Latn-BA
- sr-Latn-CS
- sr-Latn-ME
- sr-Latn-RS
- sv-FI
- sv-SE
- sw-KE
- syr-SY
- ta-IN
- te-IN
- tg-Cyrl-TJ
- th-TH
- tk-TM
- tn-ZA
- tr-TR
- tt-RU
- tzm-Latn-DZ
- ug-CN
- uk-UA
- ur-PK
- uz-Cyrl-UZ
- uz-Latn-UZ
- vi-VN
- wo-SN
- xh-ZA
- yo-NG
- zh-CN
- zh-HK
- zh-MO
- zh-SG
- zh-TW
- zu-ZA
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
-
Traffic drop after hreflang tags added
We operate one company with two websites each serving a different location, one targeting EU customers and the other targeting US customers. thespacecollective.com (EU customers) thespacecollective.com/us/ (US customers) We have always had canonical tags in place, but we added the following hreflang tags two weeks ago (apparently this is best practice); EU site (thespacecollective.com) US site (thespacecollective.com/us/) Literally the same day we added the above hreflang tags our traffic dropped off a cliff (we have lost around 70-80% on the EU site, and after a minor recovery, 50% on the US site). Now, my first instinct is to remove the tags entirely and go back to just using canonical, but if this is truly best practice, that could do more damage than good. This is the only change that has been made in recent weeks regarding SEO. Is there something obvious that I am missing because it looks correct to me?
International SEO | | moon-boots0 -
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 -
Hreflang Alternate & Pagination
Hi everybody, So I'm setting up hreflang tags on an ecommerce site. The sites are in the USA and Canada. The Canadian site will have fewer products than the American site, meaning that there won't be as many pages in each category as there are on the American site. What is the correct way to handle hreflang tags on these extra category pages? To put this another way, the American site may have a category with 3 pages of products, while the Canadian equivalent only has 2 pages of products. What happens to this extra American category page (example.com/widget-category/page-3) ? Does it get an hreflang tag linking to the first page of the equivalent Canadian category (example.ca/widget-category/)? Does it not get any hreflang tags because it has no true Canadian counterpart? Does it matter at all if it has a canonical tag pointing to the first page in the series anyway (example**.com**/widget-category/)? Thanks, Andrew B.
International SEO | | ABullis0 -
International SEO Question: Using hreflang tags across two different TLDs.
Hi! My UK based company just recently made the decision to let the US market operate their ecommerce business independently. Initially, both markets were operating off the same domain using sub-directories (i.e: www.brandname.com/en-us/ , www.brandname.com/en-gb/ ) Now that the US team have broken away from the domain - they are now using www.brandnameUSA.com while the UK continues to use www.brandname.com/en-gb/. The content is similar across both domains - however, the new US website has been able to consolidate several product variations onto single product pages where the UK website is using individual product pages for each variation. We have placed a geo-filter on the main domain which is 301 redirecting North American traffic looking for www.brandname.com to www.brandnameUSA.com However, since the domain change has taken place, product pages from the original domain are now indexing alongside the new US websites product pages in US search results. The UK website wants to be the default destination for all international traffic. My question is - how do we correctly setup hrlang tags across two separate TLDs and how do we handle a situation where multiple product pages on the "default" domain have been consolidated into one product page on the new USA domain? This is how we are currently handling it: "en-us" href="https://www.BRANDNAMEUSA.com/All-Variations" /> href="https://www.BRANDNAMEUSA.com/All-Variations" />
International SEO | | alexcbrands0 -
Multi Regional Website Best Practices
Hi there, I have a website that is targeting 3 countries AU/US & NZ. I have set up hreflang tags for each page on each of the site however I am having difficulties getting it work right. I read this article which was a great insight into the hreflang tags. https://moz.com/blog/hreflang-behaviour-insights and as a result I have implemented hreflang tags in the following manner: When users access the root domain http://[website] it will redirect the user to their locale with a 302 redirect. I have a few questions:
International SEO | | nathanfranklin
1. When building my external link profiles, I'm not sure if I should be building link profiles for http://[website]/ or for the geo graphical pages (http://[website]/aus/ etc..). Note that the http://[website]/ is never used, it just issues a 302 to the actual geographical location. 2. It seems that the hreflang tags are not working correctly. Perhaps its the result of the 302 on the root page, but in google.com.au (using the link http://www.google.com.au/search?hl=en&gl=au&pws=0&q=[branded search]) I would expect that I should see the search results for /aus/ given the fact that the hreflang tags are setup as en-au. Instead I am seeing the root domain page. Is that correct or should it be showing all the pages with /aus/. ALSO If I do a search in google thailand (http://www.google.com.au/search?hl=en&gl=th&pws=0&q=[branded search]) it returns the /aus/ version where it should be showing the /us/ using the x-default hreflang tag. In google webmaster tools I have setup 4 site profiles:
http://[website]/
http://[website]/us/
http://[website]/aus/ (Targeted to Australia)
http://[website]/nz/ (Targeted to New Zealand) Any help would be appreciated. Thanks Nathan1 -
Best URL structure for Multinational/Multilingual websites
Hi I am wondering what the best URL format to use is when a website targets several countries, in several languages. (without owning the local domains, only a .com, and ideally to use sub-folders rather than sub-domains.) As an example, to target a hotel in Sweden (Google.se) are there any MUST-HAVE indicators in the URL to target the relevant countries? Such as hotelsite.com**/se/**hotel-name. Would this represent the language? Or is it the location of the product? To clarify a bit, I would like to target around 10 countries, with the product pages each having 2 languages (the local language + english). I'm considering using the following format: hotelsite.com/en/hotel-name (for english) and hotelsite.com/se/hotel-name (for swedish content of that same product) and then using rel=”alternate” hreflang=”se-SV” markup to target the /se/ page for Sweden (Google.se) and rel=”alternate” hreflang=”en” for UK? And to also geotarget those in Webmaster tools using those /se/ folders etc. Would this be sufficient? Or does there need to be an indicator of both the location, AND the language in the URLs? I mean would the URL's need to be hotelsite.com/se/hotel-name/se-SV (for swedish) or can it just be hotelsite.com/se/hotel-name? Any thoughts on best practice would be greatly appreciated.
International SEO | | pikka0 -
Redirecting users based on location
My site is available in EN, DE, SW, SP, FR, IT, CH and JP. However, the EN sites ranks much better than the other languages, and even when searching in another language the EN homepage is normally the result that appears. Would it be worthwhile to automatically redirect users to the site in the same language they are searching in or country they are searching from? If so, how do I go about this? Thanks!
International SEO | | theLotter0 -
Website Translation
Hi All, I know its not an SEO question, but....................... Can anyone suggest a few good website translation "widgets" I would like to give those who are not fluent in English and option to choose another language in which to view the page text. Thank You!!!
International SEO | | APICDA0