What's the Best Strategy for Multiregional Targeting for Single Language?
-
I have a service based client who is based in the US but wants to expand to audiences in Australia, Canada, and the United Kingdom. Currently, all the content is in American English with international targeting in Google Search Console set to the US. I know that is going to have to change, but I'm unsure of the best strategy. Right now there are a few basic strategies in my head.
- Remove International Targeting in GSC and let her rip
- Remove International Targeting in GSC, install copies of the site on subfolders /au/, /ca/, and /uk/, add hreflang tags, and add canonicals pointing back to original
- Remove International Targeting in GSC, install copies of the site on subfolders /au/, /ca/, and /uk/, add hreflang tags, and risk duplicate content
- Have independent writers overcharge for English translations into different dialects and add hreflang tags
It's hard to come up with a perfect solution for content differentiation by region in order to implement hreflang tags with a region (en-au, en-ca, en-gb).
Remove International Targeting in GSC and let her rip
This one is pretty simple. However, I am completely unsure of its effectiveness.
Remove International Targeting in GSC, install copies of the site on subfolders /au/, /ca/, and /uk/, add hreflang tags, and add canonicals pointing back to original
The point of adding canonicals is to avoid the duplicate content, but then my new subfolders do not get indexed. I'm unsure of what type of exposure these URLs would receive or how they would be valuable.
Remove International Targeting in GSC, install copies of the site on subfolders /au/, /ca/, and /uk/, add hreflang tags, and risk duplicate content
High risk of a penalty with duplicate content, but my targeting will be the most efficient.
Have independent writers overcharge for English translations into different dialects and add hreflang tags
This is probably the safest bet, takes the longest, and costs the most money. However, how different will the content actually be if I change truck to lorry, trunk to boot, and optimization to optimisation?
Maybe I'm missing something, but this conundrum seems extremely difficult. Weighing the cost, time, and possible result is challenging. Hit me with your best answer and thanks for taking a look at someone else's problem.
-
The correct answer is
- Quit geo-targeting in GSC
- Implement hreflang annotations. Their same implementation will avoid the risk of Google considering the "duplicate" versions as duplicate
- DON'T CANONICALIZE ALL THE VERSION TO ONE YOU CONSIDER CANONICAL. Doing that will screw all the hreflang implementation and the other countries will always see the canonical Url (for instance the US one in the UK).
- Instead, work on canonicalization but version by version as if they were (and actually they are) different websites. This means self-canonicalization and/or canonicalization toward another url in case, you know, of parameters et al
- Try the most you can to localize the different versions of English you're using. This will improve the localization signals for Google (and will be appreciated by your users). However, if you cannot afford to do that, you're still safe because of the hreflang.
- Remember that the href of the hreflang annotations must always present a canonical Url. So, if you implement the hreflang in a canonicalized Url, its href will need to present the canonical url of the canonicalized page the hreflang is being implemented. If you don't do this, you will see "no-return" error in Search Console, and Google won't consider your hreflang implementation and, yes, it will start considering your versions duplicated content.
-
Hey Charles,
We're working on the same question, though the website for us already has separate TLDs for various countries (.com for US, .ca for Canada, etc.)
Most of our work re: SEO has been focused on US - nationally, regionally and locally - so international is a bit new for us, but something that I've found a lot of consistent information on.
On to your questions (from my point of view, as you wish to take it)...
#2 and #3 options are what I would recommend doing from a technical/setup perspective, with option #4 being the recommended approach from a linguistics perspective.
There are references to use of canonicals for internationalization in GSC help docs, that would lead you to potentially want to do #2 vs #3; however, I've read a lot of input on this topic over the past few weeks, and non of the recommendations I've seen thus far say that canonicals are required.
At the end of the day, I'd lean to implementing option #3 first (remove int. targeting in GSC, do your subfolders per country, add hreflang tags and do not do canonical referencing to US version).
Depending on the outcomes from that, I'd potentially look into adding the canonicals to further over the specificity needle (I'd test this on a few pages first to see what the impact of this change would look like).
In addition to #3, I'd also go for manual translations of content by translators, allowing room for creating more "uniqueness" in terms of localization of how the content is interpreted, as well as the fact that it's native to the country for that version of the page (if I had the means and control to do so). This obviously can be a huge thing, as you mentioned re: cost, but would ultimately provide the best UX, IMO.
One possible cost-effective route for doing the translation would be to tap into local university students (junior/senior level?) via professors, and have them do for credit and/or less pay than you would a professional translator. If time isn't a huge issue for this portion, I think you could have the best of all worlds from this.
Hope this helps.
Cheers
Kyle
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
-
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 -
How to interlink 16 different language versions of site?
I remember that Matt Cutts recommended against interlinking many language versions of a site.
International SEO | | lcourse
Considering that google now also crawls javascript links, what is best way to implement interlinking? I still see otherwhise extremely well optimized large sites interlinking to more than 10 different language versions e.g. zalando.de, but also booking.com (even though here on same domain). Currently we have an expandable css dropdown in the footer interlinking 16 different language versions with different TLD. Would you be concerned? What would you suggest how to interlink domains (for user link would be useful)?0 -
Country subfolders showing as sitelinks in Google, country targeting for home page no longer working
Hi There, Just wondering if you can help. Our site has 3 region versions (General .com, /ie/ for Ireland and /gb/ for UK), each submitted to Google Webmaster Tools as seperate sites with hreflang tags in the head section of all pages. Google was showing the correct results for a few weeks, but I resubmitted the home pages with slight text changes last week and something strange happened, though it may have been coincidental timing. When we search for the brand name in google.ie or google.co.uk, the .com now shows as the main site, where the sitelinks still show the correct country versions. However, the country subdirectories are now appearing as sitelinks, which is likely causing the problem. I have demoted these on GWT, but unsure as to whether that will work and it seems to take a while for sitelink demotion to work. Has anyone had anything similar happen? I thought perhaps it was a markup issue breaking the head section so that Google can no longer see the hreflangs pointing to each other as alternates. I checked the source code in w3 validator and it doesn't show any errors. Anyway, any help would be much appreciated - and thanks to anyone who gets back, it's a tricky type of issue to troubleshoot. Thanks, Ro
International SEO | | romh0 -
What is best practice of using google translate
Hi, I'm thinking of adding google translate to our retailing site so that we could reach more international customers. what about the pros&cons? Any experience of success of utilising it and what potential issues should I be looking at? Thanks
International SEO | | LauraHT0 -
Website Domains, Geographical targeting and Duplicate Content
My colleagues in Holland have 2 websites. I've copied and pasted their question - my comments are at the bottom "www.ancoferwaldram.nl with NL, EN and FR language www.ancoferwaldram.com with only EN language The EN versions Google sees as “duplicate content” so we have to get rid of that. I think we better use 1 website: www.ancoferwaldram.com with NL, EN, FR and maybe other languages and deactivate www.ancoferwaldram.nl Or keep the www.ancoferwaldram.nl with only the NL language? Or keep the www.ancoferwaldram.nl with direct links to www.ancoferwaldram.com and no content?" The focus is to get the site to rank in Non-eu countries for export. So given the .nl has higher DA (though only about 15) would it be better to have seperate .fr, .be, .com sites for specific languages and geo targeting. Or would it be better to keep everything on the same site? If so which domain? i assume that the duplicate content can be resolved by stating which is the canonical version, once the domain strategy is resolved welcome any thoughts here. 🙂
International SEO | | Zippy-Bungle0 -
Best way to enter Canada, SEO-wise?
We are thinking of splitting our e-Commerce site into a Canadian site w/ localized content, a potential French version and for additional relevance w/ localized currency. What would be the best way to go about this if we were wanting to gain traction as soon as possible on the organic side? Split the domain into domain.com and domain.com/ca/ (subfolders) Split the domain into ca.domain.com and domain.com Or split the domain into domain.com & wirelessemporium.ca Also, what are some key best practices we need to keep in mind to avoid duplicate content issues, etc?
International SEO | | eugeneku0 -
Best Practice for International Website with Two Versions
I have a client in the medical industry, and the company's product has been approved in various countries in Europe yet is awaiting approval in the US. That means we can share certain information in some countries that we cannot share in the US. Therefore, we plan to use an initial landing page that will ask what country the user is in (using a drop-down list to choose from if not located in the US) and then push him or her to the appropriate version of the site. Here is my question: What is the best way to ensure search engines can crawl the site beyond this landing page? Thanks for your time.
International SEO | | mollykathariner_ms0 -
The best SEO practice for a .hk domain
We are currently working on a project which involves 3 separate .com domains in relation to a UK company selling/renting residential, commercial and investment properties within the UK. We are now working on producing a .hk site for the overseas customers. Can anyone advise what the best practice is for a .hk domain and where best to start? Should the domain be hosted in that geographical location for example? We are relatively new to this so any advise would be greatly appreciated.
International SEO | | SoundinTheory0