Multi-National Website Demarcation in Organic Search
-
We launched our business in the UK many years ago using a .com domain and have built up good link equity back to our www site. Last year, we launched the same business in the US and host the US site on a "us." sub domain. We have used Google Webmaster Tools to demarcate the two websites so that the www site is set to target the UK and the "us." sub domain is set to target the US.
Our organic search results from Google UK for the UK business are fine but when our US customers Google brand terms the www UK site takes precedence in organic search. To complicate this further, the sitelinks within the search results include a mixture of pages from the www UK site and the "us." US site. Google clearly has some difficulty understanding that the two sites are for two different geographic audiences.
We have a good relationship with Google and they have indicated (with appropriate disclaimers) that we might consider aligning the URL structures for both sites to reduce the precedence that the www site currently receives. The www home page will become an International portal and the UK and US URL structures will be aligned. We have two options:
- Change both sites to subdomains so that we have "uk.xxxxx.com" and "us.xxxxx.com" linked to an International portal at the www subdomain
- Use sub folders so that we have "www.xxxxx.com/uk/" and "www.xxxxx.com/us/" again linked from the www subdomain
We're comfortable with use of 301 redirects and canonicals to change the structure in a search engine friendly way but cannot agree internally whether sub domains or sub folders is the way to go. Unfortunately we're to far down the line to seperate by tld.
Anyone have a strong opinion on the best approach?
Thanks,
Jeremy
-
Hi Jeremy...
Have you implemented hreflang tag on your website ? This tag helps Google in showing appropriate page in targeted country.
If you want know more about this issue please go through below link:
_http://www.seomoz.org/blog/international-seo-dropping-the-information-dust _
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
-
Google Search Console International Targeting - Works for Hungary, but not Ireland - Why?
company.com (root)
International SEO | | scottclark
USA - lang="en" | GSC target: USA (shows US site in SERPs for "companyname" search)
company.com/hungary
Hungary - lang="hu" | GSC target: Hungary (shows Hungarian site in SERPs for "companyname" search)
AWESOMENESS company.com/ireland
Ireland - lang="en" | GSC target: Ireland (shows US site (doh!) in SERPs "companyname" search)
NOT RIGHT! It is our theory [please weigh in!] that because we don't have a company.com/usa folder, the TLD targeting (EN) is overriding other English language sites in some manner. In other words, the reason it's not overriding Hungary is because it's a different language. What must we do to get the Irish site ranked for "companyname" searches and to show by default in Ireland?0 -
Best way to interlink 25 different language versions of a website?
I have a website which has 25 different language versions on 16 different domains. Hreflan are setup to point to different language versions. In the footer we have deeplinks to the 25 language versions. Site is not spammy but in small niche and many language versions have very few other external links. For some time this site had lost rankings for reasons that are unclear till now. I see that large international sites such as booking.com, tripadvisor, apple all use different approaches to interlink their language versions. Interestingly Tripadvisor is nowadays loading the links to their other language versions dynamically only upon click so that these links do not show up in source code, deviating from their former implementation of static deeplinks to all language versions. Matt Cutts mentioned back in 2013 “If you have 50 different sites, I wouldn’t link to all 50 sites down in the footer of your website, because that can start to look pretty spammy to users. Instead you might just link to no more than three or four or five down in the footer, that sort of thing, or have a link to a global page, and the global page can talk about all the different verions and country versions of your website.” But in their webmaster guidelines google recommends: "Consider cross-linking each language version of a page. That way, a French user who lands on the German version of your page can get to the right language version with a single click." I assume for SEO anyway these links have no value, but for user experience it would certainly be better to provide somewhere deeplinks to other language versions. Also the fact that language versions are on different domains and have few external backlinks may increase a bit the risk in our case. I guess in doubt I would prefer to be safe and load deeplinks only upon click same as tripadvisor. Any thoughts/suggestions on best interlinking in our specific case?
International SEO | | lcourse0 -
How to deal with disproportional content investment for a ccTLD for a multi-language country,
We have a website for the Belgium market, serving content and products on be/nl (Dutch/Flemmish Belgium) and .be/fr (French Belgium). However, as a Dutch-based company you can see our primary focus and objective is to serve content to Dutch Belgium rather than French Belgium. I wonder if, and so, what are the downsides are of only investing in half of the site?
International SEO | | Marketing-Omoda
Does it hurt my general .be Google rankings if we put a lot of effort in .be/nl but far less in .be/fr ? (we used to have a ccTLD .fr as well, but pulled the plug because it wasn't profitable.
our belgium website is profitable for Dutch speaking part of Belgium but now we would like to expand, and enhance rankings. We're investing heavily in (local) brand awareness and partnerships, and content marketing for the Dutch part.0 -
Search Console Hreflang-Tag Error "missing return tag": No explanation
Hey there, we have recently implemented hreflang on the sitemap level for our global website. The website has 57 sitemaps that are all referenced in a sitemap index file (www.buschvacuum.com/sitemap.xml). Google is showing several errors in search console ("Sitemap provided URLs and alternate URLs in 'en-AU' that do not have return tags."). However when I try to verify this I do find the return tags. Can this be caused by the fact that my hreflang tags span several sitemap files? To pick one random example (see screenshot for search console error message):
International SEO | | Online-Marketing-Guy
The Originating URL-hreflang-Tag is in www.buschvacuum.com/sitemap_3.xml, the return tag is in www.buschvacuum.com/sitemap_4.xml. It would be great if someone with experience regarding those errors could help me explaining that behavior. Thanks a lot. Jochen WXYQoUH.png0 -
Are Subdomains better or SubDirectories better for an international website ?
Can anyone explain why the structure of your website: yourbrand.com/es/category is better than es.yourbrand.com for multi language and multi country website.
International SEO | | Tushar_P0 -
Specific page URL in a multi-language environment
I've read a lot of great posts on this forum about how to go about deciding the best URL structure for each language that your site will support, so thank you to everyone that has provided input on that. I now have a question that I haven't really found answers/opinions on. When providing a page translation, should my content URL reflect that of the country I'm targeting or always remain the same across all sites? Below is an example using the "About Us" page. www.example.com/about-us/
International SEO | | Matchbox
www.example.com/es-mx/about-us/ -- OR -- www.example.com/about-us
www.example.com/es-mx/sobre-nosotros Thank you in advance for your help. Cheers!0 -
Homepage URL for multi-language site
Hi, We are setting up a new site, and currently considering the URL and folder structure of the site. We will have 2-3 different language versions, and we have decided to use sub folders for this. My question is regarding the homepage URL. We want the English language site (en) to be the default one, from where you can then change the language. Should I have a folder for each of the language versions (as described below)? www.mydomain.com/en
International SEO | | Awaraman
(this would be the default page where everyone would always come if they type www.mydomain.com to webrowser) www,mydomain.com/ru www.mydomain.com/es Or, would it be better for SEO to have www.mydomain.com as the default URL where we would have the English version of the site, and then have two other folders (as below) where we would have the 2 other language versions: www,mydomain.com/ru www.mydomain.com/es Thank you in advance, BR Sam0 -
Interlinking 60 ccTLD country versions of website
We will be launching 60 new ccTLD country versions of an established core website.
International SEO | | lcourse
Quality, human translated content in 35 languages.
We have a CSS dropdown menu with the 60 country flags and country/language name as anchor text. Formatted as deeplinks to the corresponding pages in the 60 country versions, that we planned to add on each page. How would you recommend to implement the interlinking between these 60 ccTLD? My concerns are: won't we dillute the link value of our links in the main page content too much with links to 60ccTLD on each page? may we trigger a google penalty as the new ccTLD have no other links yet and each page will have the same anchor text and links from exactly the same 60 domains. would you place the country dropdown rather at the bottom of the page (e.g. footer) to avoid that google will not crawl all links in main content page. Any thoughts or suggestions are appreciated1