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 tags and canonical tags - might be causing indexing and duplicate content issues
Hi, Let's say I have a site located at https://www.example.com, and also have subdirectories setup for different languages. For example: https://www.example.com/es_ES/ https://www.example.com/fr_FR/ https://www.example.com/it_IT/ My Spanish version currently has the following hreflang tags and canonical tag implemented: My robots.txt file is blocking all of my language subdirectories. For example: User-agent:* Disallow: /es_ES/ Disallow: /fr_FR/ Disallow: /it_IT/ This setup doesn't seem right. I don't think I should be blocking the language-specific subdirectories via robots.txt What are your thoughts? Does my hreflang tag and canonical tag implementation look correct to you? Should I be doing this differently? I would greatly appreciate your feedback and/or suggestions.
International SEO | | Avid_Demand0 -
Redirect to 'default' or English (/en) version of site?
Hi Moz Community! I'm trying to work through a thorny internationalization issue with the 'default' and English versions of our site. We have an international set-up of: www.domain.com (in english) www.domain.com/en www.domain.com/en-gb www.domain.com/fr-fr www.domain.com/de-de and so on... All the canonicals and HREFLANGs are set up, except the English language version is giving me pause. If you visit www.domain.com, all of the internal links on that page (due to the current way our cms works) point to www.domain.com/en/ versions of the pages. Content is identical between the two versions. The canonical on, say, www.domain.com/en/products points to www.domain.com/products. Feels like we're pulling in two different directions with our internationalization signals. Links go one way, canonical goes another. Three options I can see: Remove the /en/ version of the site. 301 all the /en versions of pages to /. Update the hreflangs to point the EN language users to the / version. **Redirect the / version of the site to /en. **The reverse of the above. **Keep both the /en and the / versions, update the links on / version. **Make it so that visitors to the / version of the site follow links that don't take them to the /en site. It feels like the /en version of the site is redundant and potentially sending confusing signals to search engines (it's currently a bit of a toss-up as to which version of a page ranks). I'm leaning toward removing the /en version and redirecting to the / version. It would be a big step as currently - due to the internal linking - about 40% of our traffic goes through the /en path. Anything to be aware of? Any recommendations or advice would be much appreciated.
International SEO | | MaxSydenham0 -
Multi Regional website - Folder strategy
Hello Seomoz people ! I've been struggling for some time now with an international website project. It's gonna be an:international website with joomla. To sum up: We have an international company The company has 13 subsidiaries worldwide (same products, different names) The company doesn't have enough resources to get 13 independent websites Some subsidiaries work in one country / one language, some others on a region (several countries, several languages) Thanks to your community we decided to: Get a main website company.com Get subsidiaries folders (middle east, oceania and south america will be easier to link to their subsidiary) .com/asia .com/middle-east .com/oceania .com/south-america .com/uk .com/usa .com/fr .com/es .com/de .com/ma .com/dz .com/it We also need to: Get some websites in different languages .com/asia-cn .com/asia-en etc. Now how do we do to manage: Regional websites (the first 4th on the upper list) Google allows to affect a website to a country not region Will they compete with the .com ? How do we set up them for google ? How do we avoid duplicate content and keep local ranking .com/asia-en/services1.html will have the exact same content that_.com/services1.html_ If we use canonical from _.com/asia-en/services1.htm_l to _.com/services1.html , d_oes that mean /asia will not rank in asia ? Hope you can help us to figure us the best solution for this good project ! Thanks a lot. Florian
International SEO | | AymanH1 -
How to fix the duplicate content problem on different domains (.nl /.be) of your brand's websites in multiple countries?
Dear all, what is the best way to fix the duplicate content problem on different domains (.nl /.be) of your brand's websites in multiple countries? What must I add to my code of websites my .nl domain to avoid duplicate content and to keep the .nl website out of google.be, but still well-indexed in google.nl? What must I add to my code of websites my .be domain to avoid duplicate content and to keep the .nl website out of google.be, but still well-indexed in google.nl? Thanks in advance!
International SEO | | HMK-NL3 -
Website Target in Europe
Hi, I am planning a site to target in Europe and I expect to translate my site into ten different languages namely English, French, Spanish, Italian, German, Russian, Greek, Portuguese, Dutch and Swedish. I am doing some study of this case in targeting different countries for SEO, most of the advise are the following: a. Build 10 different websites and target different geographical location in Google Webmaster b. Get 10 different country specific domains for 10 different websites I would like to hear any suggestion if there is anything better than this ? I had all the materials and translation ready but building 10 different websites or getting 10 different domains are very time consuming and costly. I would be appreciated if any one had any advise for me to make the website more management friendly. Thank you. Tom
International SEO | | Stevejobs20110 -
French Canadian Website and French Language URLs
Hello, One of my clients has a question on a new Quebec, Canada version of their website. The website content and copy is in the French Canadian language, but the IT Director has asked if, for the purpose of SEO, should the URLs be in French as well? So, this questions has two parts... For SEO, should the URL's be in French or left in English, to avoid crawl errors? For visitor UX, is there any reason to have them in French versus English?
International SEO | | Aviatech0