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" />
-
You are using bad the x-default annotation (I must admit, though, that I did not completely understood the code you copy/pasted in your question).
The x-default is meant for showing to Google what URL to show to those users, who are not explicitly targeted by a dedicated version of the website.
For instance, if we are targeting both USA and UK, but we know that the USA version has traction also in other countries like AU, NZ, South Africa and Spain, then we could use the x-default so to suggest Google that the USA URLs should be shown to all people independently of the language (in my example, not only English speaking users, but also Spanish speaking ones) and geography (not only the USA, but also all the others countries). The only exception will be the UK, because with the hreflang="en-GB" we are telling Google to shown the UK version of the site to English speaking users in Great Britain.
The only solution I see in your case is consistency between the two versions. You must choose with which architecture option to go and use just that. Only after you should think in the hreflang implementation.
-
Hi Dirk,
Thank you for your response. The US team has implemented the hreflang tags at the homepage level but not at the product and internal page level for the reasons you mention. The UK team however HAS implemented hreflang tags across all their pages and is designating the "brandname.com/en-gb/" site as the x-default AND the alternate for general EN language.
Curious to know your thoughts on this approach and how you would implement.
Thanks,
Alex
-
The solution you propose is not going to work. Hreflang is used to identify different language versions of the same page (with minor variations). This implies that each page has a one to one relation with it's equivalent in the other languages.
This isn't the case on your site - the category pages on your US site do not correspond with the category pages on the en-gb site - you can't use the hreflang here (1 page US = 3 pages in en-gb).
You could do this on homepage, product pages and all pages that are more or less equivalent in all languages.
Please also note that hreflang is reciprocal - if you have following hreflang's
you have to put this code on both pages - on http://www.brandname.com/en-gb/product-a & https://www.BRANDNAMEUSA.com/product-a - it's no use to only put it on the en-gb version as you currently do.
I also have doubts about "es-mx" for a site which is in entirely in English.
Dirk
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
-
Help with international targeting
Hi all! Okay, so we've got a site, let's say example.com - we sell training courses worldwide with a particular focus in just 8 countries.
International SEO | | JamieM1611
Historically, we've never targeted users in different countries effectively, we've just got the example.com that floats about ranking in different countries, but our content is dynamic (obviously a big SEO no-no - we pick up the IP of the user and show the content relevant for that country without the URL's changing)
This obviously presents an SEO flaw in that we can effectively target people in our key countries effectively. So, we're introducing the targeting as subfolders (/uk/, /ie/ etc) my questions are: 1. Would this be the correct implementation of hreflang AND canonical tags for the URL: https://www.example.com/es/ 2. The second thing I was wondering is the 'international targeting' in search console. We haven't (because of our current set up) set a target country for www.example.com (because of the lack of regional targeting and dynamic catch all) - would we be better leaving that untargeted and only specifying the regional targets for the new subfolder URLs (www.example.com/us/ /uk/ etc) or should we set the .com as the USA as default? We'd be a bit weary of doing this because most of our traffic comes from the UK and South Africa, so I'm assuming it would be best to leave this alone unless someone else has a different opinion? I know Googlebot almost always crawls .coms from US, which is why we were thinking of leaving the .com as the 'catch all' and specifying the US version. 3. Finally, we do have a lot pages which don't really change at all (like the about us page) would we give these any special directives to avoid duplicate content (as the content on these won't be changing at all?) or do we just keep the structure as shown above? I.E would the about us page (even though not changing) still be (with the canonical): URL: https://www.example.com/about-us/ (x-default) ? Thanks in advance!0 -
Hreflang for selected pages?
My English site example.com has 1300 Pages I have launched a Russian transasation of the site example.ru This site has only 20 pages so far. Doubt: I need to set hreflang for all 1300 pages or only for 20 Pages of example.com that are converted to russian? Due to the limitations of the plugins avaialable I need to MANUALLY set hreflang for all 1300 pages of example.com Please guide
International SEO | | Janki990 -
Is this setup of Hreflang xml sitemap correct?
Hi, I'm trying to setup hreflang for 2 domains. One is purely a US site and the other domain has the language-country as subdomains. For example: http://www.websiteUSA.com (Targets English - USA) https://www.websiteINT.com/en-CA (Targets English - Canada) https://www.websiteINT.com/fr-CA (Targets French - Canada) https://www.websiteINT/es (Targets Spanish) ..and so on and so forth for about 12 of these international URLs. I created an XML sitemap that looks something like this: <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml"><url><loc>http://www.websiteUSA.com</loc></url></urlset> <url><loc>https://www.websiteINT.com/en-CA</loc></url> <url><loc>https://www.websiteINT.com/fr-CA</loc></url> Question 1: Is this correct? In my actual file, I have all the countries listed and self-referencing. Question 2: I'm hosting this file at https://www.websiteINT.com/hreflang.xml AND at http://www.websiteUSA.com/hreflang.xml. Is this correct? Question 3: Will this help the SERPs direct english speakers from the US to http://www.websiteUSA.com while show SERPs for say English Speakers in Canada to https://www.websiteINT.com/en-CA? Question 4: For some reason, when I put up the xml site, it only listed each URL once instead of the full XML file. Should I have uploaded a text file instead? It doesn't seem to render correctly. Thank you!
International SEO | | SylviaH0 -
International Link Building Vendors
I'm working with a large enterprise site with many international domains. I have most of the markets covered but am having trouble identifying link building specialists/vendors in APAC - specifically Japan and Korea. Any recommendations from the community? Many thanks in advance!
International SEO | | JonClark150 -
International SEO
Hi If you were developing a US version of an existing UK site then is this the correct format/instructions for on-page SEO. Ive taken quite a lot from Aleydas great post: http://moz.com/blog/the-international-seo-checklist but just want to confirm below is a good overall checklist to provide to clients developers ? Create US & UK country & language subfolders such as: domain.com/en-us/ and domain.com/en-gb/ Add 'rel=alternatehreflang' attribute according to google guidelines Add individual site map to each subfolder or will the hreflang attribute do or vice versa or both best? Don't redirect users via IP sniffing their location and serving up country/language version. Instead obviously link between language/country versions with a crawlable and very visible menu. Use the meta content language/country by adding the 'country-language' meta-tag in your html head Create individual profiles in GWT & GA for each country/language version and geotarget accordingly Localise content: spelling, currency, contacts etc Anything else re on-page/technical im missing ? Many Thanks
International SEO | | Dan-Lawrence
Dan [edited to fix formatting]0 -
SEO in the UK
Will soon be starting to do SEO for a client in the UK and wondered if there was anything I should do differently for what I do in the United States?
International SEO | | hwade0 -
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 -
Google Webmaster Tools - International SEO Geo-Targeting site with Worldwide rankings
I have a client who already has rankings in the US & internationally. The site is broken down like this: url.com (main site with USA & International Rankings) url.com/de url.com/de-english url.com/ng url.com/au url.com/ch url.com/ch-french url.com/etc Each folder has it's own sitmap & relative content for it's respective country. I am reading in google webmaster tools > site config > settings, the option under 'Learn More': "If you don't want your site associated with any location, select Unlisted." If I want to keep my client's international rankings the way it currently is on url.com, do NOT geo target to United States? So I select unlisted, right? Would I use geo targeting on the url.com/de, url.com/de-english, url.com/ng, url.com/au and so on?
International SEO | | Francisco_Meza0