<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Google Product Search Partner Program</title>
	<atom:link href="http://comparisonengines.com/2007/11/07/google-product-search-partner-program/feed/" rel="self" type="application/rss+xml" />
	<link>http://comparisonengines.com/2007/11/07/google-product-search-partner-program/</link>
	<description>Just another WordPress.com weblog</description>
	<lastBuildDate>Fri, 09 Dec 2011 18:27:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: psurplus</title>
		<link>http://comparisonengines.com/2007/11/07/google-product-search-partner-program/#comment-1089</link>
		<dc:creator><![CDATA[psurplus]]></dc:creator>
		<pubDate>Thu, 08 Nov 2007 16:57:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.comparisonengines.com/new/?p=780#comment-1089</guid>
		<description><![CDATA[]]></description>
		<content:encoded><![CDATA[<p>I am happy for you and your team Brian!</p>
<p>afreydin- we have similar challenges with over 45k sku’s that need attributes pulled from the description into managable fields in our database. with our wide product offering, the attributes specific to particular groups of products vary greatly and our gbase feed would have dozens of different attributes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: afreydin</title>
		<link>http://comparisonengines.com/2007/11/07/google-product-search-partner-program/#comment-1088</link>
		<dc:creator><![CDATA[afreydin]]></dc:creator>
		<pubDate>Wed, 07 Nov 2007 14:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.comparisonengines.com/new/?p=780#comment-1088</guid>
		<description><![CDATA[]]></description>
		<content:encoded><![CDATA[<p>Brian, that’s certainly good news for SingleFeed &#8211; congrats!</p>
<p>My question is this: How many retailers out there can take advantage of anything more than the standard attributes requested by Google Base?<br />
For instance, if you’re an electronics etailer, you would LOVE to be able to provide screen size, screen type, resolution, megapixel count, etc. What happens when you haven’t defined those attributes on the backend? We’re talking about an enormous undertaking in assigning all of your skus with specific attribute values.</p>
<p>I’ve been suffering in getting proper exposure on Base for a while now. I’ve submitted all the attributes I can and have reached our internal limitations. It seems like the most ridiculous merchants show up on key phrases such as “plasma tv” and “lcd tv”.</p>
<p>I would love to hear how you would tackle this differently.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

