<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>StyleFeeder Tech Blog &#187; affiliates</title>
	<atom:link href="http://blog.tech.stylefeeder.com/category/affiliates/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tech.stylefeeder.com</link>
	<description>Bitheads Invade the Fashion World</description>
	<lastBuildDate>Mon, 02 Nov 2009 17:01:10 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How not to name your brand</title>
		<link>http://blog.tech.stylefeeder.com/2009/11/02/how-not-to-name-your-brand/</link>
		<comments>http://blog.tech.stylefeeder.com/2009/11/02/how-not-to-name-your-brand/#comments</comments>
		<pubDate>Mon, 02 Nov 2009 17:01:10 +0000</pubDate>
		<dc:creator>kilby</dc:creator>
				<category><![CDATA[affiliates]]></category>
		<category><![CDATA[complaints]]></category>

		<guid isPermaLink="false">http://blog.tech.stylefeeder.com/?p=245</guid>
		<description><![CDATA[In honor of 80%20 Shoes, signs you&#8217;ve chosen a bad brand name for your shoes, in the age of Google:

Your name contains a URL entity.  When you put %20 in the URL it represents a space character.  Oops.  If your name doesn&#8217;t URL encode to your name, you&#8217;re doing something wrong.
When someone enters your name [...]]]></description>
			<content:encoded><![CDATA[<p>In honor of 80%20 Shoes, signs you&#8217;ve chosen a bad brand name for your shoes, in the age of Google:</p>
<ol>
<li>Your name contains a URL entity.  When you put %20 in the URL it represents a space character.  Oops.  If your name doesn&#8217;t URL encode to your name, you&#8217;re doing something wrong.</li>
<li>When someone enters your name in Google, it thinks they&#8217;re doing math.  <a href="http://www.google.com/search?q=80%2520">Type 80%20 into Google</a>, and it thinks you&#8217;re doing 80 modulo 20.  The result is zero!</li>
<li>Nobody knows how to pronounce it so you can&#8217;t tell your friends, and when you do they can&#8217;t search for it.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://blog.tech.stylefeeder.com/2009/11/02/how-not-to-name-your-brand/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>10 Steps to a Better Data Feed</title>
		<link>http://blog.tech.stylefeeder.com/2009/06/24/10-steps-to-a-better-data-feed/</link>
		<comments>http://blog.tech.stylefeeder.com/2009/06/24/10-steps-to-a-better-data-feed/#comments</comments>
		<pubDate>Wed, 24 Jun 2009 22:18:08 +0000</pubDate>
		<dc:creator>kilby</dc:creator>
				<category><![CDATA[Misc]]></category>
		<category><![CDATA[affiliates]]></category>
		<category><![CDATA[affiliate]]></category>
		<category><![CDATA[data]]></category>
		<category><![CDATA[feed]]></category>
		<category><![CDATA[guidelines]]></category>
		<category><![CDATA[top 10]]></category>

		<guid isPermaLink="false">http://blog.tech.stylefeeder.com/?p=185</guid>
		<description><![CDATA[Here at StyleFeeder we work with a staggering number of merchant data feeds from affiliate networks and other partners.  The data quality of these feeds varies quite a bit, sometimes by sins of commission (data where it doesn&#8217;t belong), sometimes by sins of omission (leaving out important information).  In an effort to get the word [...]]]></description>
			<content:encoded><![CDATA[<p style="margin-bottom: 0in;">Here at StyleFeeder we work with a staggering number of merchant data feeds from affiliate networks and other partners.  The data quality of these feeds varies quite a bit, sometimes by sins of commission (data where it doesn&#8217;t belong), sometimes by sins of omission (leaving out important information).  In an effort to get the word out, we&#8217;ve produced a top 10 list for retail merchants creating product data feeds.  This is not a comprehensive list but a quick overview.</p>
<p>1.  <strong>STOP YELLING! </strong><br />
It&#8217;s easy for us to capitalize your product names and categories for emphasis on the page, but very hard to do the opposite and get the original data back.</p>
<p>2. <strong> Item names should say what they are</strong><br />
If they&#8217;re pants, put that in the name.  If they&#8217;re wedge sandals, put that in the name.  If it&#8217;s a notebook computer, put that in the name.  Especially if there are multiple items in the shot, like a belt displayed with the top and the pants.</p>
<p>3.  <strong>Keywords should be descriptive and product-specific</strong><br />
Not a repeat of the item name, not all the words from the long description with delimiters between, not keywords about the store that don&#8217;t apply to the product.</p>
<p>4.  <strong>The longer the description, the better</strong><br />
People browsing your affiliates&#8217; sites want information, and the more you give them the more will click through and the more will buy.</p>
<p>5.  <strong>Categories should be set, and contain the relevant information</strong><br />
If things have gender relevance, include that in the category names.  If you sell different types of items, the category should reflect what type each one is.</p>
<p>6.<strong> Brand fields should be filled, and consumer friendly</strong><br />
Customers like to search and browse by brand, and we can&#8217;t do this if the field is blank.  Also, customers don&#8217;t know your brand with corp or inc or things like that tacked on the end, so fill your feed with the name they know.</p>
<p>7.  <strong>Use pricing fields in a standard way</strong><br />
If all of your items have a sale price filled in, it&#8217;s probably not a sale and it should probably be in the regular price column.  Save the sale price column for specials.</p>
<p>8. <strong> If an item doesn&#8217;t have a working image, leave the image URL blank</strong><br />
404 errors, “image not available” images, store logo images.  If you can&#8217;t leave them blank, use the same “noimage.gif” type URL for all the broken ones so we can code around it.</p>
<p>9.  <strong>Use identifier columns</strong><br />
UPC when available, ISBN for books, Manufacturer Part Numbers that you&#8217;d use to order the item from the manufacturer.  And consistent SKUs for your own store that stay the same over time for the same item.</p>
<p>10. <strong> Talk with your affiliates! </strong></p>
<p>This goes without saying, but just like shoppers are the customers of your products, your affiliates are the customers of your feed.   We may have good ideas, we may have terrible ideas, but either way we may tell you something you haven&#8217;t thought of.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.tech.stylefeeder.com/2009/06/24/10-steps-to-a-better-data-feed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Updating Your Web Store?  Don&#8217;t Do This!</title>
		<link>http://blog.tech.stylefeeder.com/2009/05/06/updating-your-web-store-dont-do-this/</link>
		<comments>http://blog.tech.stylefeeder.com/2009/05/06/updating-your-web-store-dont-do-this/#comments</comments>
		<pubDate>Wed, 06 May 2009 17:04:23 +0000</pubDate>
		<dc:creator>kilby</dc:creator>
				<category><![CDATA[affiliates]]></category>
		<category><![CDATA[broken links]]></category>
		<category><![CDATA[ecommerce]]></category>
		<category><![CDATA[harmful]]></category>
		<category><![CDATA[shopping]]></category>

		<guid isPermaLink="false">http://blog.tech.stylefeeder.com/?p=177</guid>
		<description><![CDATA[The backstory
We work with a lot of web stores here at StyleFeeder, both in terms of user-added links and also by importing affiliate data feeds.  There are literally thousands of these, of varying quality, and we import a good number of them and load them regularly to keep the product listings up to date.
When dealing [...]]]></description>
			<content:encoded><![CDATA[<p><strong>The backstory</strong></p>
<p>We work with a lot of web stores here at StyleFeeder, both in terms of user-added links and also by importing <a href="http://en.wikipedia.org/wiki/Affiliate_marketing">affiliate </a><a href="http://en.wikipedia.org/wiki/Data_feed">data feeds</a>.  There are literally thousands of these, of varying quality, and we import a good number of them and load them regularly to keep the product listings up to date.</p>
<p>When dealing with lots of feeds, occasionally something odd happens.  A couple of months back we noticed that our conversions of clicks to sales at a certain retailer had dropped to basically zero, which naturally was a concern.  Looking further into it, all the product links that we had were going to 404 pages all of a sudden.  A quick comparison of the URLs we were using to the ones currently in use on the site revealed a change in link structure for the same items, which were still for sale on the site.   A look back through the affiliate messages from that merchant showed a notice that the ecommerce software would be changing but that the links in the affiliate interface would be updated to work.  Looking back, that probably meant the simple banner/text ads that they provide and not the data feed links.</p>
<p><strong>The point</strong></p>
<p>Changing ecommerce software to get new features or performance is a fine thing.  It&#8217;s always good to make a site run better and offer a better customer experience.  Having said this, unless you have tremendous brand recognition and customer loyalty there are few things you can do to harm your web site more than introducing an upgrade that breaks all of your inbound links.</p>
<ul>
<li>Assuming your home page is still your homepage, those are the only links that will still work in the eyes of search engines, so you&#8217;ll lose all SEO benefits to your deep-linked pages.</li>
<li>In the <a href="http://en.wikipedia.org/wiki/Web_2.0">modern web world of user generated content</a>, and URL shorteners, you&#8217;ve likely just broken the bulk of product links on your site that users have added to sites such as <a href="www.stylefeeder.com">StyleFeeder</a>, Facebook, or TinyURL</li>
<li>Probably minor compared to the other two, Affiliates who have loaded your product feed and do refreshes based on product content changes (or don&#8217;t do refreshes) will be tripped up since your changes will hide behind an affiliate URL and possibly not be noticed as changes.</li>
</ul>
<p><strong>How to Avoid This</strong></p>
<p>If this is something that absolutely has to be done, take an inventory of your inbound links and your affiliates.  Then notify them early and often that  a change is coming.  It&#8217;s likely that they&#8217;ll react as if you&#8217;re announcing a jump off the local bridge, but through the wonder of email you don&#8217;t have to watch or listen to this.</p>
<p>Preferably, something like <a href="http://httpd.apache.org/docs/2.0/mod/mod_rewrite.html">mod_rewrite</a> in <a href="http://httpd.apache.org/">Apache</a> could be used to remap the old URL structure to the new one.  Or, if the product identifiers in the URL change then some other sort of <a href="http://www.php.net/">page </a>or <a href="http://en.wikipedia.org/wiki/Common_Gateway_Interface">script</a> or <a href="http://java.sun.com/products/servlet/">program</a> could be written to map the existing IDs to the new URLs.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.tech.stylefeeder.com/2009/05/06/updating-your-web-store-dont-do-this/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
