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 -
How do hreflang attributes affect ranking?
We have a site in English. We are considering translating the site into Dutch. If we use a hreflang attribute does that mean we have to create a duplicate page in Dutch for each English page, or does Google auto-translate? How would duplicate pages, even if they are in a different language, affect ranking?
International SEO | | Substance-create0 -
How to Localise per Region (Europe, America, APAC, EMEI) and not per country as best SEO practise?
Hi SEO expertises! I am currently working with a client that initially have an English website targeting UK users but want to expand their market into four new regions (Europe, America, APAC and EMEI) keeping English as a main language. I would like to request your help here as I told the client ISO location and hreflang it will be just possible per language and they must need to localise each English region with local keywords, however I would like to double check if it will be any way (Sitemap, Hreflang) we can tell Google we are targeting per region and not per country? Thanks a lot!
International SEO | | Atalig20 -
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 -
International SEO Subfolders / user journey etc
Hi According to all the resources i can find on Moz and elsewhere re int seo, say in the context of having duplicate versions of US & UK site, its best to have subfolders i.e. domain.com/en-gb/ & domain.com/en-us/ however when it comes to the user journey and promoting web address seems a bit weird to say visit us at: domain.com/en-us/ !? And what happens if someone just enters in domain.com from the US or UK ? My client wants to use an IP sniffer but i've read thats bad practice and should employ above style country/language code instead, but i'm confused about both the user journey and experience in the case of multiple sub folders. Any advice much appreciated ? Cheers Dan
International SEO | | Dan-Lawrence0 -
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 -
Correct Hreflang & Canonical Implementation for Multilingual Site
OK, 2 primary questions for a multilingual site. This specific site has 2 language so I'll use that for the examples. 1 - Self-Referencing Hreflang Tag Necessary? The first is regarding the correct implementation of hreflang, and whether or not I should have a self-referencing hreflang tag. In other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), I am uncertain whether the source code should contain the second line below: Obviously the Spanish version should reference the English version, but does it need to reference itself? I have seen both versions implemented, with seemingly good results, but I want to know the best practice if it exists. 2 - Canonical of Current Language or Default Language? The second questions is regarding which canonical to use on the secondary language pages. I am aware of the update to the Google Webmaster Guidelines recently that state not to use canonical, but they say not to do it because everyone was messing it up, not because it shouldn't be done. So, in other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), which of the two following canonicals is correct? OR For this question, you can assume that (A) the English version of the site is our default and (B) the content is identical. Thanks guys, feel free to ask any qualifiers you think are relevant.
International SEO | | KaneJamison1 -
Optimizing terms with accents/tildes in Spanish
Hello all, quick question. We are optimizing for a keyword that includes an accent in Spanish. Is it better to use the accented or regular form (i.e. inglés vs. ingles)? Also, is there any distinction between accents (áéí...) and the ene (ñ) in terms of strategy/best practices? Does this accent issue have a huge impact on ranking?
International SEO | | CuriosityMedia0