<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Ignoring specific content on a page</title>
	<atom:link href="http://www.gsadeveloper.com/2006/07/28/ignoring-content/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gsadeveloper.com/2006/07/28/ignoring-content/</link>
	<description>Google Search Appliance and Google Mini development</description>
	<pubDate>Wed, 09 Jul 2008 01:29:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Michael</title>
		<link>http://www.gsadeveloper.com/2006/07/28/ignoring-content/#comment-2030</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Fri, 03 Aug 2007 19:04:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.gsadeveloper.com/2006/07/28/ignoring-content/#comment-2030</guid>
		<description>A great tip; thanks!</description>
		<content:encoded><![CDATA[<p>A great tip; thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny Dawson</title>
		<link>http://www.gsadeveloper.com/2006/07/28/ignoring-content/#comment-113</link>
		<dc:creator>Danny Dawson</dc:creator>
		<pubDate>Fri, 28 Jul 2006 16:48:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.gsadeveloper.com/2006/07/28/ignoring-content/#comment-113</guid>
		<description>While this technique does seem to be the official method for excluding certain page content from appearing in GSA search results, there is another method which does not affect the amount of markup you serve to your regular visitors.

As a GSA administrator, you have control over the GSA's user-agent string. Even though it's generally not a good idea to rely on user-agent sniffing for content delivery, in this case you're the one with control over how the client (your GSA) identifies itself. As such, if you assign a unique user-agent to your GSA, you can then sniff for it server-side and omit only the bits of content you don't want the GSA to see.

For example, if you assign the user-agent "businessname-searchappliance", you can use this php to omit content:
 if ( !strstr($_SERVER['HTTP_USER_AGENT'], 'businessname-searchappliance') ){
    // Content to omit goes in this block
}</description>
		<content:encoded><![CDATA[<p>While this technique does seem to be the official method for excluding certain page content from appearing in GSA search results, there is another method which does not affect the amount of markup you serve to your regular visitors.</p>
<p>As a GSA administrator, you have control over the GSA&#8217;s user-agent string. Even though it&#8217;s generally not a good idea to rely on user-agent sniffing for content delivery, in this case you&#8217;re the one with control over how the client (your GSA) identifies itself. As such, if you assign a unique user-agent to your GSA, you can then sniff for it server-side and omit only the bits of content you don&#8217;t want the GSA to see.</p>
<p>For example, if you assign the user-agent &#8220;businessname-searchappliance&#8221;, you can use this php to omit content:<br />
 if ( !strstr($_SERVER['HTTP_USER_AGENT'], &#8216;businessname-searchappliance&#8217;) ){<br />
    // Content to omit goes in this block<br />
}</p>
]]></content:encoded>
	</item>
</channel>
</rss>
