
July 12th, 2004, 04:55 AM
|
|
Registered User
|
|
Join Date: Jul 2004
Posts: 2
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
|
solution to 100s of duplicate pages
Hi,
We have sites where the banner tags are passed in the URLs of our pages like this: www.domain.com/index.php?&bTag=blaablaa and these banner tags persist with the user through the site if they visit other pages. This basically means from G's perspective that we have 100s of duplications of www.domain.com/index.php and other pages - a copy for each banner tag.
Now we've made adjustments to pass the btags in a different way - not in the URLs but the duplicate pages issue still exists. There will still be plenty of live links on the web pointing to www.domain.com/index.php?&bTag=blaablaa and its 100 variations and we'll continue to serve those addresses.
In addition to the btag passing problem, we also had redirects on our site to insert btags for any visitor that came without one - which resulted in us not having a static site root. We've now fixed that as well so that we have a "static" page for the root - it now has PR5 and plently on incoming links. The problem is that G appears to be refusing to cache this page. the result of a cache:www.domain.com search on google reveals that "no content exists for this page...". Also when I do site:www.domain.com the root index.php page isn't listed. I suspect that G is refusing to acknowledge this page because of the 100s of duplicates of it that still exist due to the various btag versions out there.
Questions:
1. What does it mean when G knows about a page but won't cache it?
2. Is it likely that G is refusing to acknowledge the root because it considers it just another one of the 100 duplicates that are already out there?
3. If so how can you get G to accept the root index.php (in this case) as the original and to discount all the others?
Thanks
|