Getting De-indexed by Google

[anniebelle82]

I am currently implementing a few websites (for different clients) that basically sell the same products. Essentially, these websites run from one central CMS. The reason for doing this was to make things efficient (i.e when I need to update products, I do not need to update the same product for each website, I can just go into the central database and update it once and it gets applied through all the websites).

On the internet marketing and business side of things, I am trying to get the websites ranked as high as possible (on search engines, especially Google).

What I fear is that this can have an adverse effect. Because these websites may come to 'dominate' the industry, Google (or any other search engine) may pick up on the fact that all these websites are coming from one central database, and as a result, may de-index all the websites because is it recognising it as a nuisance that all these websites are doing the same thing.

However, as stated before, these websites are for different clients, although they are selling the same products, they do not work together on a business level.

What can I do to work around this dilemma. I certainly want to keep the central database (because it makes things much more efficient), but at the same time, prevent (or decrease the chances of) getting de-indexed.

[sae]

Not sure if google would see the fact that it's all coming from one database as google only sees the end code.

If you are worried about this though, you could have each website with it's own dB and when you update one of the sites, just copy that dB to the other sites.

[KDLA]

Google indexes according to content, metadata, and links to/from; I doubt your database will be a factor. Our gov. network is tied into one CMS system. Everything is indexed separately based on end code (as mentioned) and by domain name.

KDLA

[Reli4nt]

I think the biggest concern should be if the clients take issue with the shared db and not whether or not the search engines will.

[KDLA]

I think the biggest concern should be if the clients take issue with the shared db and not whether or not the search engines will.

I agree. Good point, reli4nt.

[anniebelle82]

The clients are fine with this. They all understand the process and what is being done.

[stephan.gerlach]

If the clients are fine with this then thats ok.

If you are worried about becomeing de-indexed by google I would suggest the following.

Set up each site with the their own db. then have a central db seperate from their database. Create your self an admin system and implement some xml-rpc functions. In this way you can update the databases by simply updateing your database.

The only problem would be if your clients can change data in the database as well. if not then this would be a good solution. Thats what I think at least.

Any comments on this?

[anniebelle82]

what are xml-rpc functions?

[Christine8]

Set the sites up on different IPs (ideally from different C-Blocks).