Proper use of HREF-LANG tag and Geotargeting.
-
I am working with a global company that has different country sites (these are distinguished via country subdomains - country.site.com). Upon looking at the Google Analytics data, I noticed that even though the different country geotargeting settings aren't set up correctly, we are reaching the right target market for each site.
My hunch is because even though there is no geotargeting, the language for each country site is making the content relavant (this in combination with the subdomain).
I have read through various resources here on MOZ, and noticed that the primary purpose of the href-lang tag is important if you have similar/identical pages that are targeted towards different countries/languages. If the pages are translations however, how important or impactful is it to set the geotargeting and href-lang tags for the other sites altogether?
-
The Matt Cutts stated that href-lang is important because it will help Google bot know that the page is intended for a different language, rather than a poorly translated page 'written' just to 'rank'. If it seems like everything is okay, then err on the side of caution and use href-lang. You may just see an improvement.
However, the critical piece is making sure the pages are well written/translated for their intended target. Perhaps search engines have gotten better at weeding out/penalizing poor translations, but I would use href-lang just so I could sleep at night. At least you'll know you did that much.
If you really want to go for the gold, get someone fluent in the target languages and see what they think. You may end up with some edits. There are a ton of Spanish dialects and what reads well in Mexico might not read so well in Spain.
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
-
Targeting/Optimising for US English in addition to British English (hreflang tags)
Hi, I wonder if anyone can help? We have an e-commerce website based in the UK. We sell to customers worldwide. After the UK, the US is our second biggest market. We are English language only (written in British English), we do not have any geo-targeted language versions of our website. However, we are successful in selling to customers around the world on a regular basis. We have developers working on a new site due to launch in Winter 2021. This will include a properly managed site migration from our .net to a .com domain and associated redirects etc. Management are keen to increase sales / conversions to the US before the new site launches. They have requested that we create a US optimised version of the site. Maintaining broadly the same content, but dynamically replacing keywords: Example (clothing is not really what we sell): Replacing references to “trainers” with “sneakers”
International SEO | | IronBeetle
Replacing references ‘jumpers with “sweaters”
Replacing UK phone number with a US phone number It seems the wrong time to implement a major overhaul of URL structure, considering the planned migration from .net to .com in the not too distant future. For example I’m not keen to move British English content on to https://www.example.com/en-gb Would this be a viable solution: 1. hreflang non-us visitors directed to the existing URL structure (including en-gb customers): https://www.example.com/
2. hreflang US Language version of the site: https://www.example.com/en-us/ As the UK is our biggest market It is really important that we don’t negatively affect sales. We have extremely good visibility in SERPS for a wide range of high value/well converting keywords. In terms of hreflang tags would something like this work? Do we need need to make reference to en-gb being on https://www.example.com/ ? This seems a bit of a ‘half-way-house’. I recognise that there are also issues around the URL structure, which is optimised for British English/international English keywords rather than US English e.g. https://www.example.com/clothing/trainers Vs. https://example.com/clothing/sneakers Any advice / insight / guidance would be welcome. Thanks.0 -
Hreflang implementation via sitemap - don’t need canonical tags?
Hi, Quick easy question here I hope! An international site has hreflang and canonical tags in page head sections and also hreflang in the sitemap so I can see one version needs removing. The head section versions are relative URLs and need updating so think we will keep the sitemap hreflangs instead. If the sitemap implementation is going to be used (sitemap auto-updates when changes are made to pages so seems easier to do this way) am I right in thinking No canonical tags are needed at all (and can safely be removed from head section too?). Pretty sure links included in sitemap are assumed to be canonicals, or any issues with this approach? Will be using x-default for the default language version of homepage too.
International SEO | | MMcCalden0 -
Empty href lang
Our site is a multilingual , and its our structure for different lang : for en :domain.com/myPost for Arabic : domain.com/ar/myPost and most of the page and post in main site , have Arabic version also. and we want to generate href lang tag for all pages and posts.(for both language) and its my problem ; if i have a post or page in main site( English ), but the Arabic version not published yet and the href lang in English site pointed to the arabic url page (the page that doesn't exist yet) {arabic version almost will publish after 4-5 days } is it harmful for our SEO ? that href lang point to the URL that doesnt exist?
International SEO | | alishb13730 -
How is Google determining location for geotargeting
Hello, I have a question related to Geotargeting.
International SEO | | Lvet
Let's suppose I have a website: mysite.co.uk
As far as I understand Google will consider this site targeted for the UK and will appear on searches preferentially from the UK. What happen now if I have a person located in Spain (with a Spanish IP) and searching in Google.co.uk. Will mysite.co.uk still appear in searches? What are the factors that Google takes into account for Geotargeting? Thank you0 -
What is the best NAP format to use?
Canadian client with a suite number in a shopping center. Does it matter if the NAP is the way it's displayed on Google Maps? Canada Post (or in the US, USPS)? Or does it only matter that all the citations are as similar as possible to one another? Canada Post says: 400-3033 IMMEL ST
International SEO | | rayvensoft
ABBOTSFORD BC V2S 6S2 But if I look that up on maps.google.com, it defaults to: 3033 Immel St Abbotsford, BC V2S 4L3, CanadaAnd the client does not appear in the list of about 20+ businesses at this address.Which should I use for Places (and I assume any other citation)?1 -
Use country-specific domains or stick to already strong .com domain?
We run an online store with the majority of our customers coming from 4 different European countries. The site is accessible through TLD's of all of these countries. However our .com domain currently has the most links pointing to it and the highest domain authority. Unfortunately, we are unable to tell through which TLD visitors reach our site. The niche is rather competetive, and therefore I am unsure whether it would be worth it to solely use our .com domain for the English language, and try to rank for each of the seperate languages with its own country-specific domain. **Question/discussion: **Will it be worth the costs and time to spent to build links for the country specific domains in these countries, or should we focus on making our .com domain stronger and use it for all countries? I'm aware of the benefits of ranking with a domain in the country the user is in. Note: We have major duplicate content issues at this moment, due the content being available in different languages, on a handful of domains. On each domain, users can view the site in different languages. In addition, the language indication in the url is not very clear (?lang=x) so I believe this should be improved to make it easier for search engines to tell which language is presented. If I choose to use a different language for each TLD, then the language flag in the navigation on the site will point to a different domain, so each language is hosted on 1 domain and there is no more duplicate content. However, I'm afraid this will lead to lower rankings, as the (strong) .com domain will no longer host the content in different languages.
International SEO | | 1200wd0 -
Does it matter whether you use /en vs /uk
I have a global site targeting many countries including the UK which is the only English language site. Does it matter whether I use /en or /uk for the UK sub-folder? If I already have /en in place, but my Google UK listings are struggling, will it benefit me to switch to /uk? I honestly don't think it matters too much, but given the choice would've gone for the /uk I'm trying to weigh up whether it is worth the effort of changing it.
International SEO | | Red_Mud_Rookie0 -
Targeting specific Geographic areas. Use 1 large.Com or several smaller country specific TLDs?
Hi, I have a small number of exact match domains, both country specific TLDs and also the Generic TLD dot com and dot net. They are: ExactMatch**.Com**
International SEO | | Hurf
ExactMatch**.Net** ExactMatch**.Co.Uk**
ExactMatch**.Ca**
ExactMatch**.Co.Nz**
ExactMatch**.Co.Za** We have already successfully launched our UK site using the exact match .co.uk and this is currently number 2 in the UK SERPS for the Google, Yahoo and Bing. They are/will be niche specific classified ad sites, which are Geographically targeted by country (to Engish speakers in the main) and each region is likely to have a minumum of 2,000 unique listings submitted over the course of a year of so. My question (FINALLY) is this: Am I better to build one large global site (will grow to approx. 12,000 listings) using EXACTMATCH.Com with .com - targeting US users and then geo-targeted sub directories (ExactMatch.Com/Nz etc) - each sub dir targeted to the matching geographic area in webmaster tools, or use the ccTLDs and host each site in the country with perhaps (each site growing to approx 2,000 listings) I could use the ccTLDs just for marketing/branding onlyand redirect these to the specific sub directory of the .com site? I am aware that there is one main ccTLD that I cannot get .Com.Au (as I am not a resident of Australia - and it is already in use.) so I was wondering if the single site with .Com/AU/ etc might help me better target that country? If I use each ccTLD as separate sites I suppose I could use the largely redundant .net to target Australia? Your thoughts and advice would be most welcome. Thanks! An additional bit of intormation (or two) the .com is circa 2004. The product advertised is a reasonably bulky (perhaps 6kgs boxed) physical product and therefore the seller is unlikely to want to ship globally - will this make them shy away from a global site - even one divided into global sub sections? FYI Seller can specify in their listing Will Ship To ....... I would be open to looking at using the front page of the .Com site as a page which visitors select the country they wish to buy/sell on. (IF it is the general consensus that it is better to create one large site.) Consider also please how the end user is likely to percieve the benefits to them of one LARGE SITE versus TARGETED SITE - I know the .Com would be divided into geographic sub directories, but I am not sure if they won't see an additinal benefit to the ccTLD - Does this add a degree of reassurance and relevance that a .com/ccTLD cannot provide? I suppose I am biased by the fact that ebay use ccTLDs? Thanks again - and please forgive my tone which may suggest I am playing devil's advocate here. I am very torn on this issue.0