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
-
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 -
Worldwide and Europe hreflang implementation.
Hi Moz ! We're having quite a discussion here and I'd like to have some inputs. Let me explain the situation and what we plan to do so far. One of our client has two separate markets : World and Europe. Both pages versions will be mostly the same, except for the fact that they will have their own products. So basically, we'd want to show only the European EN version to Europe and the standard EN version to the rest of the world, same goes for FR and ES. As far as IT, DE, CS and SK, they will only be present within the european version. Since we cannot target all Europe with a single hreflang tag, we might have to do it for every single european countries. Regarding this subject, SMX Munich recently had quite an interesting session about this topic with a confirmation coming from John Mueller saying that we can target a single URL more than once with different hreflang tags. You can read more here : http://www.rebelytics.com/multiple-hreflang-tags-one-url/ So having all this in mind, here's the implementation we plan to do : www.example.com/en/ Self canonical www.example.com/fr/ - hreflang = fr www.example.com/es/ - hreflang = es www.example.eu/it/ - hreflang = it www.example.eu/de/ - hreflang = de www.example.eu/cs/ - hreflang = cs www.example.eu/sk/ - hreflang = sk www.example.eu/fr/ - hreflang = be-fr www.example.eu/fr/ - hreflang = ch-fr www.example.eu/fr/ - hreflang = cz-fr www.example.eu/fr/ - hreflang = de-fr www.example.eu/fr/ - hreflang = es-fr www.example.eu/fr/ - hreflang = fr-fr www.example.eu/fr/ - hreflang = uk-fr www.example.eu/fr/ - hreflang = gr-fr www.example.eu/fr/ - hreflang = hr-fr etc… . This will be done for all european countries (FR, EN and ES). www.example.com/en/ - x-default Let me know what you guys think. Thanks!
International SEO | | Netleaf.ca0 -
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://a-moz.groupbuyseo.org/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 -
If I redirect based on IP will Google still crawl my international sites if I implement Hreflang
We are setting up several international sites. Ideally, we wouldn't set up any redirects, but if we have to (for merchandising reasons etc) I'd like to assess what the next best option would be. A secondary option could be that we implement the redirects based on IP. However, Google then wouldn't be able to access the content for all the international sites (we're setting up 6 in total) and would only index the .com site. I'm wondering whether the Hreflang annotations would still allow Google to find the International sites? If not, that's a lot of content we are not fully benefiting from. Another option could be that we treat the Googlebot user agent differently, but this would probably be considered as cloaking by the G-Man. If there are any other options, please let me know.
International SEO | | Ben.JD0 -
What are the best practices for translation of city/state names for international SEO? (ie. New York in English vs. Nueva York in Spanish)
I'm working on international SEO / translation of a global travel site. While we have a global keyword research and translation strategy in process for each market they serve, I've run into a unique question. Overall, we are translating (and localizing) content for each market but aren't sure what to do with location names. Each country/state has cities and locations that have their own dedicated pages. I see three options for these location names (when titling a page and writing content): keep them in English, translate the names in the market languages, or use a combination of the two. The challenge with altering the location names to the market languages is that they are truly not known by those names. Though there are some instances where it may make sense…for instance **New York **in Spanish would be "Nueva York" with **‘**Nueva' being the Spanish translation of ‘new’. There are other instances, where no translation exists. If you’ve had a similar experience I'd love to hear your approach/recommendation.
International SEO | | JonClark150 -
Spanglish? Picking keywords for an English website with a Spanish speaking search demographic
I'm putting together meta data for an English website whose target search demographic is the Hispanic market. The website has a Spanish translation as well. When I entered the website into the Google Adwords keyword tool to begin doing keyword research, all keywords returned to me were in Spanish. I am unsure if the meta data keywords I'm preparing for the page should be in Spanish despite the fact that I am preparing the meta data for the English version. Moreover, should there be any mixed Spanish English (Spanglish?) keywords as users might be searching under the English search but in Spanish or with queries that are partially in Spanish?
International SEO | | IMM0 -
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