Forum Moderators: open

Message Too Old, No Replies

CGI script to pull in ads?

cgi script to pull in a client side include for ads?

         

wkrammel

10:38 pm on Mar 4, 2003 (gmt 0)

10+ Year Member



I am using a client side include (perl script) that pulls in HTML code on the client side (browser), therefore the actually ad (html) content, visible to website visitors, is NOT visible to google. I was just wondering what you guys feel about this.

May I get penalized for client side includes, since I can pull in theoretically or sorts of things google can't see, or it doesn't matter?

Google has so far tons of pages in its index from my sites and everything lloks fine... Any feedback would be great!

lazerzubb

6:33 pm on Mar 5, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Welcome to Webmaster World [webmasterworld.com]

If i understand you correct you use a normal Server Side Include.

This thread will probably help you (notice GoogleGuy's response)
[webmasterworld.com...]

Also:
[webmasterworld.com...]

The page that commes out on the server is the page that Google will see.

wkrammel

6:59 pm on Mar 5, 2003 (gmt 0)

10+ Year Member



My question was about CLIENT side includes that allows me to parse in HTML code ONLY visible to a web browser BUT NOT google. Therefore I could create a webpage that looks totally different than what google "thinks" the page looks like...

Here is the code that google's "sees":

<script src="../cgi-bin/contentpush.cgi?http://www.mydomain.com/top.txt"></script>

This allows me to place ads and other text on the page ON TOP of the "important keyword heavy content". Therefore is doesn't decrease the keyword density...

Does that make sense? What are your thoughts?

aspdesigner

5:03 am on Mar 6, 2003 (gmt 0)

10+ Year Member



OK, I wondered what the heck you were talking about (client-side PERL?)

Technically, what you have described is using server-side CGI/PERL to dynamically generate client-side Javascript code. But rather than using a normal Server-Side Include, you are getting the browser to read it in as the SRC attribute of an external script tag (Similar in concept to how a "web bug" works, but dynamically generating javascript rather than an image). Interesting idea.

But why aren't you just using SSI to include this content at the server end?

Then I read...


allows me to parse in HTML code ONLY visible to a web browser BUT NOT google. Therefore I could create a webpage that looks totally different than what google "thinks" the page looks like...

Ah, OK.

There's a name for using various tricks to accomplish that....cloaking!

IMHO, I would avoid this, particularly if you are using it for the purpose you indicated!

You may fool the bot, but that won't prevent a competitor from turning you in!

gsx

10:11 am on Mar 6, 2003 (gmt 0)

10+ Year Member



Therefore any form of JavaScript with a document.write command could be cloaking and could be banned?

Actually, I do the same thing, not because I am trying to hide anything, but because I want to know if the users browser is JS enabled and also because I don't want to have to change all my filenames to .shtml, thus 404ing any current engine listings. (But I can't use htaccess - my host says I can, but it does not work and creates errors otherwise I would use SSI to accomplish the above - it would be faster, more reliable and in my case would increase the keyword density/variations)