Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Problems with the google cache version of different domains.
- 
					
					
					
					
We have problems with the google cache version of different domains.
For the “.nl” domain we have an “.be” cache..
Enter “cache:www.dmlights.nl” in your browser to see this result.Following points are already adapted:
- Sitemap contains hreflang tag
 - Sitemap is moved to the location www.dmlights.nl/sitemap.xml
 - We checked the DNS configuration
 - Changed the Content language in de response header to : Content-Language: nl-NL
 - Removed the cache with webmastertools
 - Resolved serverrequest errors.
 
Can anyone provide a solution to fix this problem?
Thanks,
Pieter
 - 
					
					
					
					
The one issue I see is that at least for the homepage, these two sites are identical. You have so many different geo-target sites, but between two sites of the same language regardless of location, does anything change? I'm seeing no differences on the homepage so I need to ask.
This might be part of why .be is cached for .nl, you're not giving them something new to index. They are hreflang'd as well, which is telling them even more that the content is the same.
I am going to assume that .be launched before .nl, or has gotten more play in the search results. Something is making it the go to for Dutch.
 - 
					
					
					
					
Using the hard coded hreflang or the sitemap option is indifferent.
Regarding why Google is caching the .be flemish version of your website, instead of the .nl one, I sincerely have no answer to give you, but - with the few information I have about it right now - what I would look is at the CMS you are using, in the case you have a centralized CMS that then distributes the content along the domains.
Your case is weird, because that something I usually experience with hacked sites.
I put this in discussion, and ask others to give their answer.
 - 
					
					
					
					
Hi Gianluca,
Thanks for your response. The HREFlang tags are a part of the sitemaps.xml. Do you think it might be a better idea to insert the HREFlangs on each page? Any idea why Google might cache another domain for this website?
Pieter
 - 
					
					
					
					
Hi Pieter,
can you answer to this question?
I checked you .nl website with flang by Dejan SEO, and it is not showing me any hreflang annotation... I check directly looked into the code and confirmed that was not a Flang mistake.
So... are you using hreflang in your sitemaps.xml file?
 - 
					
					
					
					
Hi Andy,
Thank for your response. I've checked the HREFlang tags and to me it looks like everything is inserted correctly. The problem is that google keeps on indexing the cache of the .be domain for the .nl domain. Any idea why Google might do this (indexing the .be domain as the .nl domain?)
Thanks
Pieter
 - 
					
					
					
					
The only think I can see that is missing, is a self rel=canonical to the home page. I would have this as a matter of course.
I also can't do a quick crawl on the site as I am getting a 403 Denied error.
-Andy
 
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
- 
		
		
		
		
		
		
Help! Choosing a domain for a European sub-brand when working as a partner in North America
Background: Let's say there's a European company ABC.com, they have some presence in the US already for a lot of product brands in a certain space (let's say they make widgets). ABC Co gets 1,600 searches a month and all of that volume centers around the widgets they are known for. ABC Co purchases a company that makes gears, let's call it Gears Inc (gears.com). Gears Inc. was known for making gears in Europe, but their brand is not known in the US (search volume 0). Ideally, I would keep the Gears Inc. brand and build up the presence in the US, separating it from ABC Co. ABC Co wants to maintain their brand and eliminate Gears Inc. But we've received permission to keep the Gears brand for bringing that product to the US ... we will have an uphill battle building up the brand recognition, but at least it won't get lost in what ABC Co is already known for in the US. (ie: we don't want calls for widgets). Domain Situation: ABC Co. has redirected gears.com (DA 1) to a subdomain: {gearmakers}.abcco.com (DA 66) ... they have agreed to place a landing page under that 301 that links to the regional domains (theirs in the EU and ours in the US/North America). They are unwilling to let us use or purchase gears.com OR 301 gears.com directly to our domain. What we're trying to do: build Gears Inc. as a recognizable brand when someone searches "gears inc", this domain would rank first create a simple "brand domain" that a less-tech-savvy users could easily navigate to needs to have recognition in US, Canada and Mexico
International SEO | | mkretsinger
I don't know if this helps or provides anything more? The question is what do we use as our domain name? Any feedback is appreciated!0 - 
		
		
		
		
		
		
Redirect to 'default' or English (/en) version of site?
Hi Moz Community! I'm trying to work through a thorny internationalization issue with the 'default' and English versions of our site. We have an international set-up of: www.domain.com (in english) www.domain.com/en www.domain.com/en-gb www.domain.com/fr-fr www.domain.com/de-de and so on... All the canonicals and HREFLANGs are set up, except the English language version is giving me pause. If you visit www.domain.com, all of the internal links on that page (due to the current way our cms works) point to www.domain.com/en/ versions of the pages. Content is identical between the two versions. The canonical on, say, www.domain.com/en/products points to www.domain.com/products. Feels like we're pulling in two different directions with our internationalization signals. Links go one way, canonical goes another. Three options I can see: Remove the /en/ version of the site. 301 all the /en versions of pages to /. Update the hreflangs to point the EN language users to the / version. **Redirect the / version of the site to /en. **The reverse of the above. **Keep both the /en and the / versions, update the links on / version. **Make it so that visitors to the / version of the site follow links that don't take them to the /en site. It feels like the /en version of the site is redundant and potentially sending confusing signals to search engines (it's currently a bit of a toss-up as to which version of a page ranks). I'm leaning toward removing the /en version and redirecting to the / version. It would be a big step as currently - due to the internal linking - about 40% of our traffic goes through the /en path. Anything to be aware of? Any recommendations or advice would be much appreciated.
International SEO | | MaxSydenham0 - 
		
		
		
		
		
		
International SEO Question: Using hreflang tags across two different TLDs.
Hi! My UK based company just recently made the decision to let the US market operate their ecommerce business independently. Initially, both markets were operating off the same domain using sub-directories (i.e: www.brandname.com/en-us/ , www.brandname.com/en-gb/ ) Now that the US team have broken away from the domain - they are now using www.brandnameUSA.com while the UK continues to use www.brandname.com/en-gb/. The content is similar across both domains - however, the new US website has been able to consolidate several product variations onto single product pages where the UK website is using individual product pages for each variation. We have placed a geo-filter on the main domain which is 301 redirecting North American traffic looking for www.brandname.com to www.brandnameUSA.com However, since the domain change has taken place, product pages from the original domain are now indexing alongside the new US websites product pages in US search results. The UK website wants to be the default destination for all international traffic. My question is - how do we correctly setup hrlang tags across two separate TLDs and how do we handle a situation where multiple product pages on the "default" domain have been consolidated into one product page on the new USA domain? This is how we are currently handling it: "en-us" href="https://www.BRANDNAMEUSA.com/All-Variations" /> href="https://www.BRANDNAMEUSA.com/All-Variations" />
International SEO | | alexcbrands0 - 
		
		
		
		
		
		
In the U.S., how can I stop the European version of my site from outranking the U.S. version?
I've got a site with two versions – a U.S. version and a European version. Users are directed to the appropriate version through a landing page that asks where they're located; both sites are on the same domain, except one is .com/us and the other is .com/eu. My issue is that for some keywords, the European version is outranking the U.S. version in Google's U.S. SERPs. Not only that, but when Google displays sitelinks in the U.S. SERPs, it's a combination of pages on the European site and the U.S. site. Does anyone know how I can stop the European site from outranking the U.S. site in the U.S.? Or how I can get Google to only display sitelinks for pages on the U.S. site in the U.S. SERPs? Thanks in advance for any light you can shed on this topic!
International SEO | | matt-145670 - 
		
		
		
		
		
		
If I redirect based on IP will Google still crawl my international sites if I implement Hreflang
We are setting up several international sites. Ideally, we wouldn't set up any redirects, but if we have to (for merchandising reasons etc) I'd like to assess what the next best option would be. A secondary option could be that we implement the redirects based on IP. However, Google then wouldn't be able to access the content for all the international sites (we're setting up 6 in total) and would only index the .com site. I'm wondering whether the Hreflang annotations would still allow Google to find the International sites? If not, that's a lot of content we are not fully benefiting from. Another option could be that we treat the Googlebot user agent differently, but this would probably be considered as cloaking by the G-Man. If there are any other options, please let me know.
International SEO | | Ben.JD0 - 
		
		
		
		
		
		
For a website in portuguese what would you use? pt.domain.com, br.domain.com or domain.com.br
Hello We are a company with a website in several languages, one of them is portuguese. Our market is 2 times bigger in Brazil than in Portugal, but obviously Brazil has more potential in the future. In domain.com we have our main site in English. What would you use? pt.domain.com, br.domain.com or domain.com.br? In the first case, it means just portuguese, in the second Brazil but it is not geolocalized, and in the third, you are almost ignoring Portugal users... Duplicating content, doesn't seem to make sense... The content is basically international, so it is just the language that matters. Any help will be very much appreciated.
International SEO | | forex-websites0 - 
		
		
		
		
		
		
Country name displayed after domain name in google SERP
our online shop targets clients in the US and worldwide (same URL - no subdirectories - currency changes based on IP). when searching in google.ie or google.no for our site google displays in the SERPS "US" or "United States" after the URL for our site, but for most other US competitors it does not show the country in the SERPS. I deleted our google places listing 2 weeks ago, since I suspected it may be related, but no change so far. In google webmaster tools we have targeted the shop domain to United States, which may be another factor. Unfortunately we can not undo this setting since without it our google US ranking for the most relevant competitive keyword drops from position 8 to position 100+. Server location is in Germany which despite lots of US links and US contact info and USD currency appparently makes google think that the site is not targeting the US. Does anybody know what triggers the country name in the SERPS (google places or webmaster tools or other) and can give advice if there is any way to get rid of it.
International SEO | | lcourse0 - 
		
		
		
		
		
		
Google Webmaster Tools - International SEO Geo-Targeting site with Worldwide rankings
I have a client who already has rankings in the US & internationally. The site is broken down like this: url.com (main site with USA & International Rankings) url.com/de url.com/de-english url.com/ng url.com/au url.com/ch url.com/ch-french url.com/etc Each folder has it's own sitmap & relative content for it's respective country. I am reading in google webmaster tools > site config > settings, the option under 'Learn More': "If you don't want your site associated with any location, select Unlisted." If I want to keep my client's international rankings the way it currently is on url.com, do NOT geo target to United States? So I select unlisted, right? Would I use geo targeting on the url.com/de, url.com/de-english, url.com/ng, url.com/au and so on?
International SEO | | Francisco_Meza0