Forum Moderators: open

Message Too Old, No Replies

Google Interview

No Sir, they don't like it one bit

         

Hasenfefer

2:18 pm on May 17, 2001 (gmt 0)



[ibizinterviews.com...]

With Google having IMO probably the most clever technical staff going, their obvious distain for cloaking will soon translate into some very unhappy and unlisted cloaking fans, opinions?

skibum

9:44 pm on Jun 8, 2001 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



If I remember right, in the MarketPosition interview Silverstein denounced cloaking even if it takes the exact same content that is on the page, and strips away extra code. Google want to not only see what is on the page, but see it the way it is actually expressed on the page, headers, bold, etc..

Brett_Tabke

10:03 pm on Jun 8, 2001 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



He doesn't address the issue. It was a fud interview designed to scare.

I am on the verge of custom delivering the entire site based on user agent and possibly country of origin. So far, 3 browsers are supported and planning on two more. I also have a test copy of a on-the-fly language translator module I may or may not install. It can generate 4 languages from english.

Which version of those potential 20 pages, should I give Google? Instead of deciding, I think I just create another version and call it Google's.

budterm

12:04 am on Jun 9, 2001 (gmt 0)

10+ Year Member



Brett's right. Mr. Marckini really pushed hard to get a definitive answer. Although the editorial comments about the interview stated that Google will outright ban for cloaking, no exceptions, the actual quote stated that it was a gray area. (I would provide the actual quote, but I dont know how to without violating anyone's copyrights.)

startup

8:46 pm on Jun 9, 2001 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Let's remember that WP has a vested interest in beating the anti-cloaking drum. Cloaking skews the results of their software. I also find no mention of sites being banned for using the WP position checker.

Google cannot define cloaking or can any other SE.
index.cgi
index.asp
index.cfm
index.shtml
index.php

All the above are examples of pages delievered using a given set of parameters. These parameters can include:
Browser,
IP,
Language,
User Agent,
Time,
Date,
Screen resolution.

Google doesn't have the ability or resources to eliminate all the form of cloaking and any attempt to do so would be a waste of time for them.

This 34 message thread spans 2 pages: 34