<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0" 
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/">

  <channel>
    <title>mezzoblue: Image Replacement + Google</title>
    <link>http://mezzoblue.com/archives/2008/05/05/image_replac/</link>
    <description>Comments on the mezzoblue entry &#8220;Image Replacement + Google&#8221;</description>
    <dc:language>en-us</dc:language>
    <dc:date>2008-07-16T11:42:53-08:00</dc:date>
    <admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=3.35" />
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>


    <item>
      <title>By Anson, at 20:42:11 on 2008-05-14.</title>
      <link>http://www.mezzoblue.com/archives/2008/05/05/image_replac/comments/index.php#c038390</link>
      <content:encoded><![CDATA[<p>Abu, Google already does a lot of work parsing massive amounts of HTML, not to mention the work done with that parsed HTML to rank pages effectively according to relevancy. Checking the CSS for common methods that hide content is really not that difficult in comparison to what they're already doing with the content they're indexing.</p>]]></content:encoded>
      <dc:date>2008-05-14T20:42:11-08:00</dc:date>
    </item>
    <item>
      <title>By Web Design Glasgow, at 07:48:38 on 2008-05-16.</title>
      <link>http://www.mezzoblue.com/archives/2008/05/05/image_replac/comments/index.php#c038398</link>
      <content:encoded><![CDATA[<p>Google can't really penalise anything based on its analysis of your CSS because it can change after the page loads.  For example, you might hide a div with display:none until the user mouses over a particular area of the page.</p>

<p>Thus, Google has to resort to language analysis to detect keyword stuffing, and links to determine a level of trust in the page.</p>]]></content:encoded>
      <dc:date>2008-05-16T07:48:38-08:00</dc:date>
    </item>
    <item>
      <title>By Jordan Clark, at 18:43:39 on 2008-05-19.</title>
      <link>http://www.mezzoblue.com/archives/2008/05/05/image_replac/comments/index.php#c038421</link>
      <content:encoded><![CDATA[<p>@ Dave:<br />
"One assumes Google is smart, and their algorithms ought to know the difference between keyword-stuffed text and plain English content written for real people."</p>

<p>You're right there. For anyone who needs convincing on Google's intelligence, take a look at the two articles written by Sergey Brin that I've linked to below – they provide an insight into the sheer thought that has gone into Google, as well as how it works "under the hood".</p>

<p>A quick glimpse at these should convince you not to worry about things like image replacement, the 'off-left' technique, or using the odd 'display: none' rule to hide a skip link etc.</p>

<p>The Anatomy of a Search Engine<br />
<a href="http://tinyurl.com/6zxo7h" rel="nofollow">http://tinyurl.com/6zxo7h</a></p>

<p>What can you do with a Web in your Pocket?<br />
<a href="http://tinyurl.com/6dblxl" rel="nofollow">http://tinyurl.com/6dblxl</a></p>

<p>PS: I've converted these rather ugly, long-winded links into "tiny URLs" because I don't want to be responsible for breaking your layout (I'm good like that!). Also, the documents are only available in Postscript and PDF respectively, so I've linked to the HTML versions generated by Google.</p>]]></content:encoded>
      <dc:date>2008-05-19T18:43:39-08:00</dc:date>
    </item>
    <item>
      <title>By Mike Cherim, at 13:58:35 on 2008-05-21.</title>
      <link>http://www.mezzoblue.com/archives/2008/05/05/image_replac/comments/index.php#c038443</link>
      <content:encoded><![CDATA[<p>I spoke with Google about this about a year ago and it was put to me quite matter-of-factly: They don't care about legitimate uses of hiding text for design and accessibility, that they check before pulling the plug, and that logic and common-sense is applied. </p>

<p>I was relieved to hear it.</p>]]></content:encoded>
      <dc:date>2008-05-21T13:58:35-08:00</dc:date>
    </item>
    <item>
      <title>By David, at 18:04:02 on 2008-06-01.</title>
      <link>http://www.mezzoblue.com/archives/2008/05/05/image_replac/comments/index.php#c038548</link>
      <content:encoded><![CDATA[<p>Hey,</p>

<p>google uses image replacement techniques like Ole mentioned above: Have a closer look at Google Reader - the logo is replaced via css. Actually, it's a h1 which inner text is hidden and replaced by an image.</p>

<p>I think Google does not flag a site for using these techniques without manual review. I use as much text replacement images as it makes sense...</p>]]></content:encoded>
      <dc:date>2008-06-01T18:04:02-08:00</dc:date>
    </item>
    <item>
      <title>By Ricardo Zea, at 11:24:06 on 2008-06-04.</title>
      <link>http://www.mezzoblue.com/archives/2008/05/05/image_replac/comments/index.php#c038590</link>
      <content:encoded><![CDATA[<p>That's why I hate that 'innocent' attitude from Google.</p>

<p>What if then Google comes and says: "Using images to replace text is not a proper technique, is not search engine/bot friendly."</p>

<p>Then we all have to bow down and obey. BS.</p>

<p>It's like if Google 'owns' the truth now, a truth that we all already know exists WAY before Google existed.</p>

<p>It's OBVIOUS this technique es proper, it respects human users and search bots/spiders in every sense, and this happens even without Google having to state it in their Webmaster Help Center.</p>

<p>We were lucky, VERY lucky, that Google considered that rule as 'valid', otherwise, web designers/SEO consultants would've had to kneel and bow.</p>

<p>Google sucks big time, it's either what they WANT or what they WANT.</p>

<p>Sad reality mates.</p>]]></content:encoded>
      <dc:date>2008-06-04T11:24:06-08:00</dc:date>
    </item>
    <item>
      <title>By Rick Lecoat, at 05:03:10 on 2008-06-26.</title>
      <link>http://www.mezzoblue.com/archives/2008/05/05/image_replac/comments/index.php#c038688</link>
      <content:encoded><![CDATA[<p>@Anson:<br />
"Checking the CSS for common methods that hide content is really not that difficult in comparison to what they’re already doing with the content they’re indexing."</p>

<p>I'm sure your analysis of the relative complexities is correct. But I routinely list my external CSS files as off-limits to robots via my robots.txt file. (After all, I do want the content of my pages indexed, but why would I want my styling code indexed?)</p>

<p>Which raises the questions that I've asked in several SEO forums over time (but never got a conclusive response to): if Google has been told to ignore your CSS files, and assuming that it honours that instruction, how then can it determine when CSS has been used to hide text in the markup? External CSS must, by now, be more prevalent than styles placed in the head of the page after all. Does it simply look for markup that has been known to be used for image replacement? That would be quite a big assumption to make -- I'm sure that image replacement is not the only use for an empty span.</p>

<p>Can Google really get past a disallowed external CSS file?</p>]]></content:encoded>
      <dc:date>2008-06-26T05:03:10-08:00</dc:date>
    </item>
    <item>
      <title>By Tilaka, at 12:21:20 on 2008-07-11.</title>
      <link>http://www.mezzoblue.com/archives/2008/05/05/image_replac/comments/index.php#c038751</link>
      <content:encoded><![CDATA[<p>We've just begun to use CSS sprites with one client - and I never thought about this particular approach to introducing descriptive text.</p>

<p>Sprites are not very mainstream yet, but they certainly can help download speed by reducing the number of http connections. With google putting more and more emphasis on the end user experience when they click on google search results, all those factors that improve page speed seem to be potentially helpful in ranking. </p>]]></content:encoded>
      <dc:date>2008-07-11T12:21:20-08:00</dc:date>
    </item>
    <item>
      <title>By Reynder (findability), at 01:08:26 on 2008-07-15.</title>
      <link>http://www.mezzoblue.com/archives/2008/05/05/image_replac/comments/index.php#c038761</link>
      <content:encoded><![CDATA[<p>I use already some image replacement technics and is nice to see that is still evolving. Thanks for the usefull info and the tips.</p>]]></content:encoded>
      <dc:date>2008-07-15T01:08:26-08:00</dc:date>
    </item>
    <item>
      <title>By Troy Dalmasso, at 21:07:46 on 2008-07-16.</title>
      <link>http://www.mezzoblue.com/archives/2008/05/05/image_replac/comments/index.php#c038782</link>
      <content:encoded><![CDATA[<p>@Rick</p>

<p>"Can Google really get past a disallowed external CSS file?"</p>

<p>I'm I'm correct, a "no follow" will prevent an engine from indexing a page but they will still read it, nonetheless. They will still see your styles which is how they know if you are using black hat techniques.</p>

<p>An engine will read all code that a browser would load.</p>]]></content:encoded>
      <dc:date>2008-07-16T21:07:46-08:00</dc:date>
    </item>




  </channel>
</rss>