We have a site which is hosted in a home country with a country domain extension, i.e. it is not a generic domain.

The site has another languages version and ALL content is generated dynamically from database depending on the language.

Home page is shown in home language, if the user then click on "Language1", the client sends a request to a server which includes language parameter and a different content is pulled out of database and the page in "Language1" is shown (and vice-versa, if clicking on home language whilst on Language1 version of the page).

We are finding difficult to rank the site in another language since the site is automatically geo-targeted for a home country owing to the current hosting/TLD domain combination.

I am wondering the possibility and implications of the following:

1. Buy a new domain for Language1, which is (preferably) country specific TLD of Language1, or alternatively, a generic domain (.com).

2. Upload a copy of our current web page code (aspx) to the new domain and make the home page language default to Language1.

3. On the server side of the new domain, when building a new page content for the Language1, all DB access to point to the current database which is hosted in the home country (is it possible?).

4. On the home page of the home language site (i.e. of the original site), if Language1 is clicked, do 301 to a new domain which hosts site in Language1

5. On the new Language1 site, if home language is clicked, do 301 to original site in the home language.

This (I hope!) would give us two separate sites, one for each language, but with each hosted in their appropriate countries, however, both using the same database (which has admin back end, hence it is important that the same DB is used).

Is the above possible (especially with using existing DB hosted elsewhere) and are there any negatives?

Or is there a more simple way to achieve what we want? The key requirements are: one database, two domains, one for each country.

Many thanks.