Ok I remember why I had the session ID. The SID was added so that there would be no issues with cookies or AOL IP's.

When a person hits the site and does some shopping, adds to cart, goes off somewhere else on the site, adds something else, etc, we had to have a way
to remember which cart items belong to them. This is typically done with either cookies (or remembering a session id but session id's in memory do not work if cookies are disabled) or the users IP address changes.

We decided to pass the codes along with each link to avoid 2 problems with shopping.
Problem 1 that was resolved by this: AOL has some major problems when tracking shopping activity by IP address as AOL can and does just all the sudden change the IP address within browsing sessions when using AOL's internal browsers... therefore, a users shopping cart contents will just disappear because the number we were remembering in order to track what
items in the database belonged to them all of the sudden changed because AOL had "none standard" stuff.

Problem 2 was that many users disable cookies and when they do that, the system can not remember behind the scenes any memory variables such as what
the persons IP Address originally was and their session id automatically changes during each new page load. We wanted them to just be able to go
there and buy with no extra effort on their part regardless of what kinda of challenge we were presented by AOL or user cookies or whatever.

Therefore, we have to grab the users info (IP Address and Session ID) upon their 1st page view and always use that, regardless of whether something on
their system decides to up and change it on us in mid-stream... therefore, we pass it along the command line as a parameter and therefore avoid all
problems.

I had heard that Google didn't like to index pages with an ID= and yet we wanted to have it index the photo profile pages so we changed that parameter to RID=
We set up a html page that is automatically
generated that Google gets a hold of

http://www.latin-wife.com/ndx/profile_links.htm

Google is indexing the photo profile pages that I assume as all it has is a ?rid=GIRLSRECORDNUMBER...

So it appears maybe that the primary (main site pages) are not being indexed now due to the SID= and yet the photo profiles are being indexed because the
the before mentioned link.

So is the answer to add another html page that just points to each of my site pages without the SID='s... much like what we did for the photo profile records? I.E.
Main Home Page Title (which is a link to
http://www.latin-wife.com/Default.asp as opposed to the Default.asp?SID=1234555-2324443 or whatever) and do a page of links for each of the primary site pages?
Please let me know if this the best way to go about this?
As for the duplicate website. I do have 2 domains pointing to one website. I understood that it was ok to do this. Please tell me if this is not the case?

I will say that my ranking on MSN are pretty good. It was only recently that I had all these problems with Google.
Thanks Jamie