Multilingual Sitemap with some non-matching URLs
-
The website has two languages, English (.com/en-int/) and French (.com/fr-fr/).
Some pages only exist in French, and some only in English, but there are many that are a 1-to-1 match. So, my questions is, in the multilingual sitemap, should I only include the URLs that are alternates, and then create a 2nd sitemap for all non-matching URLs?
Or should I have 3 sitemaps: 1) Multilingual sitemap for all matching URLs (https://support.google.com/webmasters/answer/26208650 , 2) English sitemap for only URLs not included in multilingual sitemap, 3) French sitemap for only URLs not included in multilingual sitemap. And then create a sitemap index file to link to all 3 sitemaps.
-
Thanks for your response Oleg. But if I separate matching URLs into different sitemaps, then doesn't that go against what Google recommends by including them in 1 multilingual sitemap?
-
you should have 1 sitemap index and 2 sitemaps.. 1 for English and 1 for French, and the index that links to them both.
If a page has an equivalent, include the rel="alternate" meta data. If not, don't include any meta data (just do the generic ones = loc, freq, priority)
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 on non 1:1 websites
Hi. I have a client with international websites targeting several different countries. Currently, the US (.com) website outranks the country-specific domain when conducting a search within that country (i.e. US outranks the UK website in the UK). This sounds like a classic case for hrelang. However, the websites are largely not 1:1. They offer different content with a different design and a different URL structure. Each country is on a country-specific domain (.com, .co.uk, .com.au, etc.). As well, the country-specific domains have lower domain authority than the US/.com website - fewer links, lower quality content, poorer UX, etc. Would hreflang still help in this scenario if we were to map it the closest possible matching page? Do the websites not sharing content 1:1 add any risks? The client is worried the US/.com website will lose ranking in the country but the country-specific domain won't gain that ranking. Thanks for any help or examples you can offer!
International SEO | | Matthew_Edgar0 -
Is it advisable to show additionally also English ciity names of American cities in website versions of non-western languages such as Chinese, Japanese etc?
To my understanding in many Asian languages city names are transcribed as they sound and this can cause confusion especially in the case of lesser known American city names. So I was planning to put in our international website versions (Chinese, Japanese, Korean etc. ) the English name in brackets after the translated city name in meta title and H1.
International SEO | | lcourse
However when I checked Tripadvisor and Booking.com I noticed that they do not show the English city name anywhere on their Asian language versions. Any thoughts?
Would you recommend to put the English city name in brackets after the translated city name or may it rather hurt our ranking and traffic?0 -
URL structure of international hotel website
Hai all, Question about URL structure of international hotel website in Amsterdam: hotelcitadel.nl. Some information: - Target group are mainly english speaking guests from UK and US. Besides that guests from the Netherlands and some other countries. - Website in 6 languages. - No geo-targetting; just language targetting with hreflang annotations. Current situation: hotelcitadel.nl = dutch language version and hotelcitadel.nl/en = english language version We are thinking about changing this to: hotelcitadel.nl would become english version and hotelcitadel.nl/nl would become the dutch version. Reason: root domain hotelcitadel.nl has by far the most links,and making the root domain the english version could help the rankings in english speaking countries like UK and US. What do you think, would this be a wise idea? Regards, Maurice
International SEO | | mlehr0 -
Soft Launch App with Country Targeting To Match?
Hi,
International SEO | | eTinaRose
We're gearing up to do a soft launch of our app in a few countries, such as Australia. Our website says to request early access since the app is not yet publicly available in the apple store. However, it will be in those soft launch countries. This is what I'm considering... Creating a subdomain site such as au.liquidtext.net (liquidtext.au is not available). And setting that site, au.liquidtext.net, to be country targeted to Australia via webmaster tools. Once the app is available internationally, and the main site has been updated to show this, I would then redirect any subdomains to the main site. Thoughts? Are there any negative repercussions to this this approach that I am not considering? Thank you for your help Moz community!! Tina0 -
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: domain.com/en-gb domain.com/en-us As the site was originally set-up for UK, the sitemap, robots file & Webmaster Tools account were added to the main domain. Example: domain.com/sitemap.xml domain.com/robots.txt 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: domain.com/en-gb/sitemap.xml domain.com/en-gb/robots.txt and the US would have its own separate sitemap and robots.txt. Example : domain.com/en-us/sitemap.xml domain.com/en-us/robots.txt 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!
International SEO | | CarlWint0 -
Wordpress SEO/ Ecommerce , Site with Multiple Domains ( International ) & Canonical URLs
Hi I have an ecommerce site with an integrated wordpress instance. I want to have one wordpress site that outputs to 2 domains exactly the same content , but one will have canonical URL . NZ & Australia Sites. So: Would I use the rel="Alternate" hreflang="en-nz" . I want the same content to rank well for each country and not be penalised for duplicate content. Ideas?
International SEO | | s_EOgi_Bear0 -
External URLs in hreflang sitemap questions
I'm currently putting together an international sitemap for a website that has an set up like the following: example.com/us
International SEO | | Guyboz
example.com/au
example.com/ca
example.co.uk
example.se I'm planning on including the hreflang tags within sitemaps for each domain, to make sure google serves up the right version. However, I'm a bit sceptical about including the non .com domains within the .com sitemap - and the other way round for .co.uk and .se sitemaps. The way I've been doing it follows the following example: <url><loc>http://www.example.com/us/</loc></url> Putting in the .co.uk and .se domains within the .com sitemap just doesn't feel right - is this actually the right way to do it? Thanks in advance 🙂0 -
70 characters roughly where Google cuts off the title how many bytes for non-latin characters?
Hi So I was asked a good question by our localisation team regarding titles/descriptions and their cut off points on the google listing. I am unable to find any reference anywhere in terms of non-latin characters and the number of characters/bytes they would be before they are cut off in Google's Listing. So for latin characters it is generally around 70 for the title and 170 for the description. Now the same does not apply for Japanese, Chinese and other non-latin character languages. These generally work in the number of bytes. Does anyone have a standard rule for ensuring the title/description are not too long/short when the listing displays in the search results? Thanks
International SEO | | ColumK0
