![]() ![]() |
Star Member![]() ![]() Group: 1000 Post Club
Joined: 10-March 05
Posts: 1,065
From: Montreal Canada
|
Jul 23 2007, 10:47 AM |
|
|
I' m quite certain I saw something about giving Google a password when you are using their sitemap stuff.
http://www.google.com/webmasters/ |
||
| Offline | ![]() |
MemberGroup: Members
Joined: 23-July 07
Posts: 11
|
Jul 23 2007, 12:34 PM |
|
|
I believe that snippets and cached can be controlled. Plan would be to use the no-cache meta tag and <META NAME="GOOGLEBOT" CONTENT="NOSNIPPET"> for Google.
(http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=35304) The point would be to describe what the page is about ... not provide the content in the SERPs. Any user clicking the listing in the SERPs would see the age verification window before any content. Last week 11 major brands announced policies to curtail marketing of things like happy meals and cereal with more than 12 gm of sugar to kids under 12. http://www.cnn.com/2007/HEALTH/07/18/kids.food.ap/index.html My 10-year old daughter was actually deterred from signing up for cyworld by their age verification page and I actually know parents who restrict their kids tv watching and do not take kids under 13 to PG-13 movies. Maybe that's just because I live in the midwest My point is that this indexing issue isn't just a problem for sites marketing to people over 21. |
||
| Offline | ![]() |
Hall of Famer![]() ![]() Group: Hall Of Fame
Joined: 3-November 05
Posts: 3,461
From: CHeeseland
|
Jul 24 2007, 11:31 AM |
|
|
The IP delivery for Google's crawlers is only for news sites. The password/authentication which Bobbb mentioned is for the Adsense bot, not for the web crawler.
As I understand it, the problem is that the user should always see an age verification page before being able to view the content while a search engine should be able to crawl the site naturally. That idea alone goes against the Google Webmaster Guidelines, "Don't deceive your users or present different content to search engines than you display to users (...)" -- no matter how you solve the issue technically. Personally, I do not think that there is a way to handle it without breaking that guideline. There are a few ways it could be done, if you are willing to ignore that guideline, eg: - IP+user-agent delivery - client side coding (javascript) + cookies - server side coding + cookies Are you willing to take that risk? Would your client be willing? John |
||
| Offline | ![]() |
Star Member![]() Group: Members
Joined: 19-August 06
Posts: 583
From: Carmel, Indiana
|
Jul 24 2007, 01:53 PM |
|
|
QUOTE Google Guidelines: Don't deceive your users or present different content to search engines than you display to users This guideline certainly seems necessary in order for Google to be able to mechanically index information effectively, but it has a major flaw that naturalwoman has stumbled across: How can content owners and Search Engines provide access to information that is not completely free? (subscription, registration, verification, advice). I think that this limitation is the primary contributor to search engine dissatisfaction. Often seekers cant find an answer because not everything is indexed/displayed: books, periodicals, subscription data, subject matter expertise... And of course PPC and Organic rank are both based upon a commercialized ideal of value. Search engines work, most of the time, for most of the people, with most of the information needed. No doubt about that. Google's valuation and omnipresence makes that clear. But I think naturalwoman has found a big hole where that value equation breaks down. Sidebar: Is not Google already in a sense violating their own policy with services like the full-text search services like Google Scholar? I could be wrong, but it's my understanding that Google Scholar provides a full text search of articles, but that the full articles are not always displayed - you might have to subscribe or register to see the whole document. Even if Scholar isn't doing full-text search (maybe they only do abstract search), certainly that will change a some point if they want the value proposition to mature. And the Google Library Digitization projects. What about marketing research for example? Why do I have to search Google, then Google Scholar, then my library OPAC, then a federated search of subscription data, then site/service-specific searches of Forester, Nielson, eMarketer.... Sorry I'm ranting more than providing you a solution -Jeff |
||
| Offline | ![]() |
![]()
|
|
| Lo-Fi Version | Time is now: 9th February 2010 - 02:14 PM |
| Meet our Moderators: | cre8pc : projectphp : sanity : Black Phoenix : bwelford : EGOL : Ruud : rustybrick : AbleReach : swainzy : joedolson: eKstreme: dazzlindonna : SEOigloo: iamlost : RisaBB |