International Sites - Sitemaps, Robots & Geolocating in WMT
-
Hi Guys,
I have a site that has now been launched in the US having originally just been UK. In order to accommodate this, the website has been set-up using directories for each country. Example:
As the site was originally set-up for UK, the sitemap, robots file & Webmaster Tools account were added to the main domain. Example:
The question is does this now need changing to make it specific for each country. Example:
The sitemap and robots.txt for the UK would move to:
and the US would have its own separate sitemap and robots.txt. Example :
Also in order to Geolocate this in WMT would this need to be done for each directory version instead of the main domain? Currently the WMT account for the UK site is verified at www.domain.com, would this need reverifying at domain.com/en-gb?
Any help would be appreciated! Thanks!
-
Thanks for the insights. Very helpful. What about the robots.txt, though? Should it stay under http://www.example.com, where crawlers can find the file?
-
Yes, that's how I did it.
-
Thanks for the response, much appreciated.
Would this mean that the sitemap featured at www.domain.com would need to reference each directory version (UK & US etc etc), leaving the en-gb & en-us to reference just their own?
-
Hi, here's what Google officially has to say:
Webmaster Tools data and reporting work best on a site level. For example, if your site http://www.example.com has separate sections for different countries, we recommend adding each of those subsites or subfolders as a separate site. For example, if you have a travel site with specific subfolders covering Ireland, France, and Spain, you could add the following sites to your Webmaster Tools account:
- http://www.example.com
- http://www.example.com/france
- http://www.example.com/ireland
- http://www.example.com/spain
Following this I have solved the exactly the same problem you had for a client. And it works perfectly.
- _The question is does this ["sitemap"] now need changing to make it specific for each country. _What I have done is add the sitemaps for each subdirectory as well as the main domain. It works (tracking and all that) and is easy to do.
- _Also in order to Geolocate this in WMT would this need to be done for each directory version instead of the main domain? _Yes, that is the way to go.
- _Currently the WMT account for the UK site is verified at www.domain.com, would this need reverifying at domain.com/en-gb? _Yes, it does. And so do every other subdirectory you add down the line. That allows precise international targeting per subdirectory via the hreflang and country targeting settings and setting the main GWT site for the root domain to be for global traffic.
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
-
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 -
Expanding into new country & what to do with Seach Console
Hi! We're looking at expanding into new countries, and will probably go with the subfolder route. Our main website is focused on Ireland on Search Console (and probably always will be), so will this be affected if I add subfolders onto the end? And can I shop the main site from crawling the new URL's in the subfolder. So if www.example.com is focused on Ireland, and we add www.example.com/de for Germany, can we let Google know not to index the German pages in Ireland? And will I need to do anything to the Irish version (e.g, change www.example.com to www.example.com/ie)
International SEO | | Frankie-BTDublin0 -
International SEO - Alternatives to Automatic IP re-direct
Hello, When doing international SEO I've read that it's not good practice to automatically re-direct users to the correct part of the website based on their IP address. But what alternatives are there to this? Let's say you're targeting the US and the UK through multiregional SEO. What can you do to ensure that users from the US go to the US sub-directory and that users from the UK go to the UK sub-directory? In Moz's international SEO guide it says that: "If you choose to try to guess at the user’s language preference when they enter your site, you can use the browser’s language setting or the IP address and ask the user to confirm the choice. Using JavaScript to do this will ensure that Googlebot does not get confused. Pair this with a good XML sitemap and the user can have a great interaction. Plus, the search engines will be able to crawl and index all of your translated content." Can anyone explain this further? Any help would be much appreciated! Thanks in advance
International SEO | | SEOCT0 -
International URL paths
Wanted to ask everyone a questions: So our company is going to be doing a website that is going to be full of videos. The url path will be country.domain.com/language/slug/content-id. We redirect the user when they go to the different country. So if you're in spain on a train to france your URL will change from es.domain.com/es/slug/content-id to fr.domain.com/es/slug/content-id. Each country can listen to each video in all languages. My question is with hreflang tags and canonicals. Aside from targeting users in a certain country via Google Search Console, how do I eliminate duplication and tell Google which I'd like to show up via which country. In spain I would like es.domain.com/es/slug/content-id to show in Google and would have hreflang tags on each of the es.domain pages but what about fr.domain.com/es/slug/content-id since it would show the same content? I can't canonical to one of them since I need them to show in their respective country. How do I show the difference in language and country without showing duplication?
International SEO | | mattdinbrooklyn0 -
International SEO question domain.com vs domain.com/us/ , domain.com/uk etc.
Hi Mozzers, I am expanding a website internationally. I own the .com for the domain. I need to accommodate multiple countries and I'm not sure if I should build a folder for /us/ for United States or just have the root domain .com OPTION 1:
International SEO | | jeremycabral
domain.com/page-url -- United States
domain.com/de/page-url -- Denmark
domain.com/jp/page-url -- Japan OPTION 2:
domain.com/us/page-url -- United States
domain.com/de/page-url -- Denmark
domain.com/jp/page-url -- Japan My concern with option 2 is there will be some dilution and we wouldn't get the full benefit of inbound links compared to Option 1 as we would have geo ip redirection in place to redirect users etc. to the relative sub-folder. Which option is better from an SEO perspective? Cheers, Jeremy0 -
International advice.... can anyone help and check my site?
Hi ALL, I'm running 3 sites, internationally .com, com.au and co.nz Can anyone please look at my site and give me feedback about the hreflang tags, I ran a W3C and i have errors stating https://validator.nu/?doc=http%3A%2F%2Fzenory.co.nz for www.zenory.com and its relevant domains
International SEO | | edward-may0 -
Best practice for multi-language site?
Recently our company is going to expand our site from just english to multi-language, including english, french, german, japanese, and chinese. I deeply understand a solid and feasible plan is pretty important, so I want to ask you mozzers for help before we taking action! Our site is a business site which sells eBook software, for the product pages, the ranks are taken by famous software download sites like cnet, softonic, etc. So the main source of our organic traffic is the guide post, long-tail keywords. We are going to manually translate the product pages and guide post pages which targeting on important keywords into other languages. Not the entire english site. So my primary question is: should I use the sub-domain or sub-category to build the non-english pages? "www.example.com/fr/" or "fr.example.com"? The second question: As we are going to manually translate the entire pages into other languages, should I use the "rel=alternate hreflang=x" tags? Because Google's official guideline says if we only translate the navigations or just part of the content, we should use this tag. And what's your tips for building a multi-language site? Please let me know them as much as possible Thanks!
International SEO | | JonnyGreenwood0 -
Multilingual site - separate domain or all under the same umbrella
this has been asked before with not clear winner. I am trying to sum up pros and cons of doing a multilingual site and sharing the same domain for all languages or breaking it into dedicated subdomains e.g. as an example lets assume we are talking about a french property portal with an english version as well. Assume most of the current incoming links and traffic is from France. A) www.french-name.fr/fr/pageX for the french version www.english-name.com/en/pageX for the english version B) www.french-name.fr/fr/ for the french name (as is) www.french-name.fr/en for the english version the client currently follows approach A but is thinking to move towards B we see the following pros and cons for B take advantage of the french-name.fr domain strength and incoming links scalable: can add more languages without registering and building SE position for each one individually potential issues with duplicate content as we are not able to geotarget differenly on web master tools of google potential dilution of each page's strength as we will now have much more pages under the same domain (double the pages basically) - is this a valid concern? usability/marketing concerns as the name of the site is not in english (but then people looking for a house in France would be at least not completely alien to it) what are your thoughts on this? thanks in advance
International SEO | | seo-cat0