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.
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
-
International SEO - Targeting US and UK markets
Hi folks, i have a client who is based in italy and they set up a site that sells travel experiences in the sout of Italy (the site currently sit on a server in Italy). The site has been set up as gTLDs: www.example.com They only want to target the US and the UK market to promote their travel experiences and the site has only the english version (the site does not currently offer an italian version). If they decide to go for the gTLDs and not actually change to a ccTLDs (which would be ideal from my point of view) how are the steps to be taken to set this up correctly on GSC? They currently only have one property registered on GSC: www.exapmple.com therefore i guess the next steps are: Add new property - www.example.com/uk and and set up geo targeting for UK Existing property - www.example.com/ set up geo targeting for US In case the client does not have the budget to optimise the content for american and british languages, would still make sense to have 2 separate property in GSC (example.com for US market and example.com/uk for UK market)? Few considerations: Add canonical tag to avoid duplicate content across the two versions of the site (in the event there is no budget to optimise the content for US and UK market)? Thank you all in advance for looking into this David
International SEO | | Davide19840 -
Problems with the google cache version of different domains.
We have problems with the google cache version of different domains.
International SEO | | Humix
For the “.nl” domain we have an “.be” cache..
Enter “cache:www.dmlights.nl” in your browser to see this result. Following points are already adapted: Sitemap contains hreflang tag Sitemap is moved to the location www.dmlights.nl/sitemap.xml We checked the DNS configuration Changed the Content language in de response header to : Content-Language: nl-NL Removed the cache with webmastertools Resolved serverrequest errors. Can anyone provide a solution to fix this problem? Thanks, Pieter0 -
HELP: Incorrect Meta Tag description showing for the wrong search results
Hi Guys I'm stuck here! I have update the hreftags, updated the sitemaps. I have 3 top level domains and my zenory.com site is showing for the home page the wrong meta tag description, as you can see in the attachement the meta tag is showing the new zealand site meta tag description which is for zenory.co.nz Anyone know what might be going on here? I have also fetched the home page through WMT as well and its still returning the same results any advice would be much appreciated! Thanks
International SEO | | edward-may0 -
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 -
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 -
How can I see what my web site looks like from a different country?
I've tried a few proxy tools to try to see how my site looks from other global locations, but haven't found one that works very well yet -- or a list of reliable proxies around the world. I need to do this to test various geo-targetted ads and other optimizations. Can anyone make a recommendation? Thanks!
International SEO | | Dennis-529610 -
Pop-up to select country. Any negative SEO effect?
Hi there! We have similar websites in different countries (it's an ecommerce site). Some times, those websites share the same language and, for example, people from Mexico end up in a page from our website in Argentina. Therefore they see our products in their language buy in a foreign currency. We would like to show them a pop-up (like a shadowbox) depending on their IP to allow them to go to their local website. There wouldn't be any redirect. Would that affect our rankings in any way? Would Googlebots see that as well? Thanks!
International SEO | | jorgediaz0 -
Subdomain hosted in a different country - what are the implications?
Hello, We are looking at creating an eCommerce section to a website and we are just weighing up the options: Magento - host on hour own server - great but it can often be very slow when hosting a shared server. Shopify - hosted solution but hosting is in the US and we are in the UK and shop will be hosted on a subdomain as a result Build our own solution - time consuming and costly There are two issues that have arisen from this situation.... Is it worse for SEO to host your store in a different country or to host in your country but your store potentially run slower? I'm swaying to the side of the argument that says give your users a good and fast experience instead of worrying about where you host the store. Bearing in mind that the main website will be hosted in the UK anyway and it is just the subdomain that will be hosted in the US. Just wondered if anybody has had experience with this or if I'm missing something? All feedback greatly appreciated! Thanks, Elias
International SEO | | A_Q0