Thanks so much Gianluca, I'll take all your ideas into account.
- Home
- robertorg
Latest posts made by robertorg
-
RE: Correct site internationalization strategy
-
RE: Correct site internationalization strategy
Thanks Dmitrii.
Any other opinions will be appreciated aswell, this process is really important for this webpage.
-
Correct site internationalization strategy
Hi,
I'm working on the internationalization of a large website; the company wants to reach around 100 countries. I read this Google doc: https://support.google.com/webmasters/answer/182192?hl=en in order to design the strategy.
The strategy is the following:
For each market, I'll define a domain or subdomain with the next settings:
- Leave the mysitename.com for the biggest market in which it has been working for years, and define the geographic target in Google search console.
- Reserve the ccTLD domains for other markets
- In the markets where I'm not able to reserve the ccTLD domains, I'll use subdomains for the .com site, for example us.mysitename.com, and I'll define in Google search console the geographic target for this domain.
Each domain will only be in the preferred language of each country (but the user will be able to change the language via cookies).
The content will be similar in all markets of the same language, for example, in the .co.uk and in .us the texts will be the same, but the product selections will be specific for each market.
Each URL will link to the same link in other countries via direct link and also via hreflang. The point of this is that all the link relevance that any of them gets, will be transmitted to all other sites.
My questions are:
- Do you think that there are any possible problems with this strategy?
- Is it possible that I'll have problems with duplicate content? (like I said before, all domains will be assigned to a specific geographic target)
- Each site will have around 2.000.000 of URLs. Do you think that this could generate problems? It's possible that only primary and other important locations will have URLs with high quality external links and a decent TrustRank.
- Any other consideration or related experience with a similar process will be very appreciated as well.
Sorry for all these questions, but I want to be really sure with this plan, since the company's growth is linked to this internationalization process.
Thanks in advance!
-
RE: Internationalization and 302 redirects
Thanks to both for your responses.
I don't think that search engines shouldn't see this like a manipulative action, but maybe they do and we'll be banned.
Thomas, I couldn't use a GeoDNS because I think that GoogleBot always come from an US IP, so it will only index and rack our US domain. This is the reason for try to identify GoogleBot and don't make the redirect, I Google had a spider with an IP of each country we shouldn't have this problem, but think that this isn't suceed.
We'll use ccTLD for each one, so Webmaster Tools assign the country automatically.
Best regards,
Robert
-
Internationalization and 302 redirects
Hi,
We're thinking in an internationalization process for a travel webpage. We'd like to use one domain (.com) in TV and press marketing and have several domains with each country ccTLD domain.
We've shown that for example Tripadvisor makes a 302 redirect if you connect to tripadvisor.com and you are in another country. But we've detected aswell, that if you use the Browser Agent Google Bot, it didn't.
It appears to be a cloaking, but really they're redirecting the users to the best places for them, and detecting Googlebot for not make the redirect, they ensures that it indexes well all the place. Booking.com makes something similar but with the same domain, detecting if you're Googlebot or not.
Do you think that this is a danger thing if you're not as big as Tripadvisor? They makes this redirection by level server, could be safest to do with javascript? if we do with javascript, Google will take this path instead of read the page?
Thanks!
Looks like your connection to Moz was lost, please wait while we try to reconnect.