﻿<?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/"
		>
<channel>
	<title>Comments on: MayDay, MayDay &#8212; Some Retailers Have a Google Problem!</title>
	<atom:link href="http://www.seotool.com/blog/mayday-mayday-some-retailers-have-a-google-problem.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.seotool.com/blog/mayday-mayday-some-retailers-have-a-google-problem.html</link>
	<description>SEO from the ground up</description>
	<lastBuildDate>Mon, 12 Jul 2010 19:27:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: paul</title>
		<link>http://www.seotool.com/blog/mayday-mayday-some-retailers-have-a-google-problem.html#comment-498</link>
		<dc:creator>paul</dc:creator>
		<pubDate>Mon, 12 Jul 2010 19:27:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.seotool.com/blog/?p=103#comment-498</guid>
		<description>Very interesting article.  My e-commerce company has been customizing our product page content for 4 years now.  The issue we are finding is that there is little one can do from having competitors pilfering that content and posting it on their e-commerce site.  It&#039;s hard to prove that information which was modified by us is copyrightable.  It is even harder to prove damages.  

Any thought or suggestions to combat this issue would be greatly appreciated and welcomed!</description>
		<content:encoded><![CDATA[<p>Very interesting article.  My e-commerce company has been customizing our product page content for 4 years now.  The issue we are finding is that there is little one can do from having competitors pilfering that content and posting it on their e-commerce site.  It&#8217;s hard to prove that information which was modified by us is copyrightable.  It is even harder to prove damages.  </p>
<p>Any thought or suggestions to combat this issue would be greatly appreciated and welcomed!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

