Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Google Webmaster Help
Home
About this group
Join this group
Message from discussion Questions from "How Google defines IP delivery, geolocation, and cloaking"
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
webado  
View profile  
 More options Jun 2 2008, 9:16 pm
From: webado
Date: Mon, 2 Jun 2008 18:16:16 -0700 (PDT)
Local: Mon, Jun 2 2008 9:16 pm
Subject: Re: Questions from "How Google defines IP delivery, geolocation, and cloaking"
Print | View thread | Report this message | Find messages by this author
Well content is really just text and links. Styling doesn't count -
except in order to determine if you have text or links which are
hidden from the human visitor.

That said you can certainly engage in some serious black hat things
that way. If the css is handled server-side rather than client side
(in js) then robtos won't know. Unless of course they use tricks like
spoofing their user agent string to check up on such things.

I'd suggest you don't do this kind of thing. With a bit of effort you
can fix your css so you don't have to d this at all.
Or at worst you can keep one basic css file and supply separate style
sheet directives as needed with elements to override for  some special
browser based considerations.

There too I'm quite convinced that with a bit of effort you'd likely
eliminate this need altogether.

On Jun 2, 7:48 pm, masterleep wrote:

> On our site we serve different CSS files depending on browser
> detection, so we can work around CSS differences between different
> browsers.  We serve robots a "generic" css.  It does cause a minor
> difference in the HTML (the file name of the CSS includes "generic"
> rather than "firefox-2" or "ie-7").  The rest of the HTML is the same.

> Hopefully this is legit, but if not, how in general should browser
> specific HTML generation be handled?  Should we pretend that robots
> are IE7 or Firefox, for example?


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google