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
-
Multilingual webshop SEO
Hi, I have a question concerning multilingual SEO for webshops. This is the case: the root domain is example.be, which has several subdomains. One of these subdomains is shop.example.be which is used for two webshops (Dutch and French), being shop.example.be/nl and shop.example.be/fr .
International SEO | | Mat_C
The other root domain is example.lu (for Luxemburg) which is only used for the subdomain for the Luxemburg webshop in French, being shop.example.lu/fr.
The content on the .lu/fr webshop is a small part of the content on the .be/fr webshop, and the product descriptions are the same and are both of course in French. The webshops will be redesigned and restructured, and the question is what to do with the .lu/fr webshop. There are two possibilities: Integrate this webshop for Luxemburg in the existing .be webshop, since most of the products are the same and the .lu webshop doesn't get a lot of visitors because of Luxemburg being a small country. The only thing to do then would be setting up a 301 from the .lu webshop to the .be/fr version to transfer link value.
People in Luxemburg already sometimes get pages from the .be/fr webshop in the SERP anyway because these already have a bigger authority than the .lu/fr pages. Keep the .lu/fr webshop and use hreflang tags so the correct pages with similar content are shown in the correct country. I know that when using different TLD's this normally isn't an issue anyway, so implementing hreflang tags even isn't really necessary. Please feel free to share your thoughts about what would be the best approach. Thanks!1 -
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 -
Showing different content according to different geo-locations on same URL
We would like our website to show different content according to different Geo-locations (but in the same language). For example, if www.mywebsite.com is accessed from the US, it would show text (in English) appealing to North Americans, but, if accessed from Japan, it would show text (also in English) that appeals more to Japanese people. In the Middle East, we would like the website to show different images than those shown in the US and Asia. Our main concern is that we would like to keep the same URL. How will Google index these pages? Will it index the www.mywebsite.com (Japan version) in its Asia archives and the www.mywebsite.com (US version) in its North American archives? Will Google penalise us for showing different content across Geo-locations on the same URL? What if a URL is meant to show content only in Japan? Are there any other issues that we should be looking out for? Kindest Regards L.B.
International SEO | | seoec0 -
Multinational URLs
Hi I'm wondering if the following URL structure using subdirectories would be alright to use on a multinational site. I have local products only in the local language and english. I plan to use: /uk/ - UK product in English (geo target in GWT to UK, href lang="en") /fr/ - French product in French (would geo target this in GWT to France, and hreflang="fr-FR") /fr-en/ - French product in English (no geo-targeting, hreflang ="en") /de/ - German product in German (would geo target this in GWT to Germany, and hreflang="de-DE") /de-en/ - German product in English (no geo-targeting, hreflang ="en") /at-de/ - Austrian product in German (would geo target this in GWT to Austria, and hreflang="at-DE") /at-en/ - Austrian product in English (no geo-targeting, hreflang ="en") Does the name of the subfolder matter? I've tried to keep the URL's shorter, so german users in Germany would get just /de/ rather than /de-de/, and have made the english version of the content the more ugly URL as it's used much, much less. The URL structures aren't really consistent here (ie. uk and fr-en are for english content, but are different in URL format) but I'm wondering if this is an issue, or if the above would be fine. Thanks!
International SEO | | pikka0 -
Best URL structure for Multinational/Multilingual websites
Hi I am wondering what the best URL format to use is when a website targets several countries, in several languages. (without owning the local domains, only a .com, and ideally to use sub-folders rather than sub-domains.) As an example, to target a hotel in Sweden (Google.se) are there any MUST-HAVE indicators in the URL to target the relevant countries? Such as hotelsite.com**/se/**hotel-name. Would this represent the language? Or is it the location of the product? To clarify a bit, I would like to target around 10 countries, with the product pages each having 2 languages (the local language + english). I'm considering using the following format: hotelsite.com/en/hotel-name (for english) and hotelsite.com/se/hotel-name (for swedish content of that same product) and then using rel=”alternate” hreflang=”se-SV” markup to target the /se/ page for Sweden (Google.se) and rel=”alternate” hreflang=”en” for UK? And to also geotarget those in Webmaster tools using those /se/ folders etc. Would this be sufficient? Or does there need to be an indicator of both the location, AND the language in the URLs? I mean would the URL's need to be hotelsite.com/se/hotel-name/se-SV (for swedish) or can it just be hotelsite.com/se/hotel-name? Any thoughts on best practice would be greatly appreciated.
International SEO | | pikka0 -
French Canadian Website and French Language URLs
Hello, One of my clients has a question on a new Quebec, Canada version of their website. The website content and copy is in the French Canadian language, but the IT Director has asked if, for the purpose of SEO, should the URLs be in French as well? So, this questions has two parts... For SEO, should the URL's be in French or left in English, to avoid crawl errors? For visitor UX, is there any reason to have them in French versus English?
International SEO | | Aviatech0 -
Geo-targeting a sub-folder that's had url's rewritten from a sub-domain
I have a client that's setting up a section of his site in a different language, and we're planning to geo-target those pages to that country. I have suggested a sub-folder solution as it's the most cost effective solution, and it will allow domain authority to flow into those pages. His developer is indicating that they can only set this up as a sub-domain, for technical reasons, but they're suggesting they can rewrite the url's to appear as sub folder pages. I'm wondering how this will work in terms of geo-targeting in Google Webmaster Tools. Do I geo-target the sub domain or the sub folder i.e. does Google only see urls or does it physically see those pages on the sub-domain? It seems like it might be a messy solution. Would it be a better idea just to forget about the rewrites and live with the site being a sub domain? Thanks,
International SEO | | Leighm0 -
International (greek) characters in the URL
For one of our sites we are considering restructuring the urls. This is about a Greek site and we are toying between the following options: a) English URLS e.g. www.domain.com/cars b) Greek URLs e.g. www.domain.com/αυτοκίνητα c) "Greeklish" URLs (Greek words spelled with latin characters) www.domain.com/aftokinita Normally we would imagine option b is the best since it would reinforce the main and most relevant keyword that is already present within the page content. We see many people search in google using greeklish (e.g. they are lazy to switch the keyboard locale all the time). Since we would also like to capture this part of the SE traffic but cannot obviously write in "greeklish" within our main page content maybe option c is a good compromise?
International SEO | | achatzakis0
