Multilingual drupal 7
-
Hello,
I'm in a trouble with a drupal 7 installation. It's multilingual.
The problem is Google indexed some pages like this:
example.com/es/node/100
example.com/fr/node/100
example.com/en/node/100all of them, shows the same content, excepts menus, whose are in the current languages (depending of url: es, en, fr.. ).
The question...:
If a submit my sitemap, which not has those urls. Will google remove old example.com/xx/node/100 pages ? Or it'll retain them indexed. Do i must remove these indexed urls via the google remove url submissions form?
Thanks.
-
Thanks Tim. I followed your method for 1 site which is only in one language to deindex bad urls:
Disallow: /es/
Disallow: /pt/
..
...following your advise and this thread http://drupal.org/node/78313 ,
and watching how works translation redirect for solve this in other sites with multiples languages.
Thanks.
-
Do those pages still exist? If they do, and there's a reason for them existing but you don't want them to appear in the index then
1. Block spider access to the pages with robots.txt
e.g.
User-agent: *
Disallow: /es/node/100
etc.
2. Use the Drupal metatag module to set up robots "noindex" meta tag on those pages if D7
Google say they'll remove pages from index which have noindex meta tag on them (http://support.google.com/webmasters/bin/answer.py?hl=en&answer=93710&from=61050&rd=1)
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
-
Multiregional / Multilingual SEO - What do you do when there is no equivalent page?
Hello, We're building out a small number of pages for the US in a sub-folder .com/us. The idea is to show US specific pages to users in that location. However, we also have a number of pages which we will not be creating for the US as they're not relevant. I am planning on geo-targeting the US folder to instruct the search engines that this subfolder should appear in the US SERPS but since it isn't an exact science, there is a chance that US visitors may land on these non-us pages which could potentially give them a bad user experience. What should we do in instances where a US user lands on a non-us page with no equivalent page? Any help would be much appreciated!
International SEO | | SEOCT1 -
Multiregional / Multilingual SEO - Subfolders Question
Hello all, I wonder if you can help me... I have a question about subfolders in multi-regional / multi-lingual SEO - more specifically in reference to targeting the UK and the US. Having looked at some global websites these are the types of implementations I've most commonly seen: UK subfolders .com/uk .com/gb .com/gb/en-gb | .com/en-GB .com/gb-en .com/en-gb .com/uk/en US subfolders .com/us .com/us/en-us | .com/en-US .com/us-en .com/en-us .com/us/en Are any of these approaches better than others or is it all a matter of personal preference? What's the reason for using .com/gb over .com/uk (or vice versa) for example? Secondly, my assumption is that the examples above which include language subfolders do so because these companies are targeting different speaking users within these countries. Would I be right to think that since the organisation I work for is only targeting the American speakers in the US, we wouldn't need to go so far as to have language subfolders in addition to location subfolders? Would be great to get some feedback / suggestions! Thanks!
International SEO | | SEOCT0 -
What strategy is better for a multilingual site for the SEO point of view?
Hi everyone, in a case for a site with two languages like spanish and english, how would do you deal with it? I can see 4 cases, which is better?? 1. With differents domains: mydomain.es (for spanish version) and mydomain.com (for english version). 2. With subfolder mydomain.com/es/ and mydomain.com/en/ 3. With Subdomain: es.mydomain.com and en.mydomain.com 4 With URL translation (any url is translated in ther languages but not use of subdomain or subfolder): mydominain.com/hola and mydomiain.com/hello Thanks very much for your answers (i love this forum). 🙂
International SEO | | webtematica0 -
Multilingual and Canonicalization
Hey there Mozzers, If I have a site that is translated in 5 languages with main language as English ( most pages are only template translated top menu and footer ) is this correct? Right now the main page which is example.com/en is mentioned 3 times in the href code 1st as a canonical later as alternate and 3rd as x default which seems a bit weird. | |
International SEO | | Angelos_Savvaidis
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |0 -
Auto-Redirecting Homepage on Multilingual Site
The website has an auto-redirecting homepage on a multilingual site. Here is some background: User visits the site for first time > sent to javascript age verification page with country of origin selector. If selects "France" then served French page (.com/fr-fr/). If selects any other country, then served English page (.com/en-int/). A cookie is set, and next time the user visits the site, they are automatically served the appropriate language URL. 1st Question: .com/ essentially does not exist. It is being redirected to .com/en-int/ as this is the default page. Should this be a 301 redirect since I want this to serve as the new homepage? 2nd Question:. In the multilingual sitemap, should I still set .com/ as the hreflang="x-default" even though the user is automatically redirected to a language directory? According to Google, as just released here: http://googlewebmastercentral.blogspot.com/2014/05/creating-right-homepage-for-your.html "automatically serve the appropriate HTML content to your users depending on their location and language settings. You will either do that by using server-side 302 redirects or by dynamically serving the right HTML content. Remember to use x-default rel-alternate-hreflang annotation on the homepage / generic page even if the latter is a redirect page that is not accessible directly for users." So, this is where I am not clear. If use a 302 redirect of .com/ to either .com/en-int/ or .com/fr-fr/, won't I then lose the inbound link value and DA/PA of .com/ if I just use a 302? Note: there is no .com/ at this moment. Any advice is appreciated. Thanks,Alex
International SEO | | Alex.Weintraub0 -
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.
International SEO | | Alex.Weintraub0 -
Multilingual site - Best choice?
Quick question for a site that has the same content but in a different language (not machine translated) on seperate pages.
International SEO | | Crunchii
Say I have:www.mydomain.com (which is in English)
www.mydomain.com/ES (which is in Spanish)
www.mydomain.com/NL (which is in Dutch) I don't want to limit the ie. Spanish to only Spain so geotargeting isn't necessary What is the best/correct setup for the pages?0 -
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