<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.2.3" -->
<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/"
	>

<channel>
	<title>Metashit</title>
	<link>http://www.metashit.com</link>
	<description>situated behind or beyond shit, transcending shit</description>
	<pubDate>Sat, 31 Mar 2007 21:52:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>
	<language>en</language>
			<item>
		<title>Is Googlebot Indexing Your Site Too Rapidly?</title>
		<link>http://www.metashit.com/2007/03/31/is-googlebot-indexing-your-site-too-rapidly/</link>
		<comments>http://www.metashit.com/2007/03/31/is-googlebot-indexing-your-site-too-rapidly/#comments</comments>
		<pubDate>Sat, 31 Mar 2007 21:48:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[SEO]]></category>

		<guid isPermaLink="false">http://www.metashit.com/2007/03/31/is-googlebot-indexing-your-site-too-rapidly/</guid>
		<description><![CDATA[For most of us, search engine robots such as Googlebot indexing our site TOO quickly is not a problem.  But what if your domain has 50,000 pages and your webserver cannot handle requests as quickly as Googlebot demands?  Well, here are a few solutions:

Add the following code to your robots.txt file, which instructs [...]]]></description>
			<content:encoded><![CDATA[<p>For most of us, search engine robots such as Googlebot indexing our site TOO quickly is not a problem.  But what if your domain has 50,000 pages and your webserver cannot handle requests as quickly as Googlebot demands?  Well, here are a few solutions:</p>
<ol>
<li>Add the following code to your <a href="http://en.wikipedia.org/wiki/Robots.txt">robots.txt</a> file, which instructs robots to wait 5 seconds between each request (the default is 1 second):<br />
<blockquote><p>User-agent: *<br />
Crawl-delay: 5</p></blockquote>
</li>
<li>Sign up for <a href="http://www.google.com/webmasters">Google Webmaster Tools</a> and change the crawl rate to <em>slower</em>.<br />
<blockquote><p><a href="http://www.metashit.com/wp-content/uploads/2007/03/crawl-delay.jpg" title="crawl-delay.jpg"><img src="http://www.metashit.com/wp-content/uploads/2007/03/crawl-delay.thumbnail.jpg" alt="crawl-delay.jpg" /></a></p></blockquote>
</li>
<li>As a last resort, you can block robots altogether.  This is not recommended since you will not be indexed, but it may be necessary if your webserver cannot handle the bandwidth:<br />
<blockquote><p>User-agent: *<br />
Disallow: /</p></blockquote>
</li>
</ol>
<p>Hopefully this will not even be an issue if you are using a good webhost.  I recommend getting a dedicated server from <a href="http://www.metashit.com/dreamhost.php">Dreamhost</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.metashit.com/2007/03/31/is-googlebot-indexing-your-site-too-rapidly/feed/</wfw:commentRss>
		</item>
		<item>
		<title>5 Useful Things Myspace Glitches Have Taught Me To Do</title>
		<link>http://www.metashit.com/2007/03/08/5-useful-things-myspace-glitches-have-taught-me-to-do/</link>
		<comments>http://www.metashit.com/2007/03/08/5-useful-things-myspace-glitches-have-taught-me-to-do/#comments</comments>
		<pubDate>Thu, 08 Mar 2007 10:18:24 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[Myspace]]></category>

		<guid isPermaLink="false">http://www.metashit.com/2007/03/08/5-useful-things-myspace-glitches-have-taught-me-to-do/</guid>
		<description><![CDATA[
Always copy my blogs to the clipboard before clicking post.  I am completely OCD about this now, having lost countless postings to the infamous &#8220;SERVICE UNAVAILABLE&#8221; error.
Always check the domain in the URL address bar to make sure I&#8217;m still on the site I thought I was on.  Myspace is chock-full of Javascript [...]]]></description>
			<content:encoded><![CDATA[<ol>
<li style="padding: 3px"><em>Always</em> copy my blogs to the clipboard before clicking post.  I am completely OCD about this now, having lost countless postings to the infamous &#8220;SERVICE UNAVAILABLE&#8221; error.</li>
<li style="padding: 3px"><em>Always </em>check the domain in the URL address bar to make sure I&#8217;m still on the site I thought I was on.  Myspace is chock-full of Javascript or Flash redirects in combination with phished accounts using creative linking.  It&#8217;s one of the few sites you can <em>already </em>be at, and then somehow end up at a phishing site.</li>
<li style="padding: 3px">Stock up on Firefox plugins.  <a href="http://adblock.mozdev.org/">Adblock</a> has never had a more useful application, and <a href="http://www.greasespot.net/">Greasemonkey</a> <a href="http://userscripts.org/scripts/show/7637/">scripts</a> allow me to download Myspace songs without having to suffer through their crappy/stuttering streaming music players.</li>
<li style="padding: 3px">Ignore hot girls that I do not know.  Yes, they are all porno spambots from India.  No, blonde Leah in her underwear does not really want to be my friend.  Having accepted this fact, I am free to be productive and prosper in my entrepreneurial endeavors without distraction.</li>
<li style="padding: 3px">Build my websites on a solid foundation.  Think up the architecture, the ideas, get your flowcharts spread out on the table!  Know what you want to do before you try and do it!  Myspace tries to do <em>everything</em>, but succeeds at very little.  Get focused, try and build a site that does <em>one</em> thing very well!  Myspace&#8217;s biggest mistake was growing too fast without a solid foundation, and the site&#8217;s major security flaws lead the way for spammers, phishers and worms. Instead, Myspace is constantly tied up with fixing these security flaws instead of making the site run more efficiently.  Know where you&#8217;re going before you get there.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.metashit.com/2007/03/08/5-useful-things-myspace-glitches-have-taught-me-to-do/feed/</wfw:commentRss>
		</item>
		<item>
		<title>10 Steps To Getting Your Competitor&#8217;s Adsense Account Banned</title>
		<link>http://www.metashit.com/2007/03/03/10-steps-to-getting-your-competitors-adsense-account-banned/</link>
		<comments>http://www.metashit.com/2007/03/03/10-steps-to-getting-your-competitors-adsense-account-banned/#comments</comments>
		<pubDate>Sat, 03 Mar 2007 22:37:44 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[Adsense]]></category>

		<guid isPermaLink="false">http://www.metashit.com/2007/03/03/10-steps-to-getting-your-competitors-adsense-account-banned/</guid>
		<description><![CDATA[The point of this post is not to play dirty. The point is to expose a fatal flaw in the way Google Adsense does business in hopes that they will fix the problem.
Background
We already know there are a variety of blackhat tactics that can be used to get a competitor&#8217;s site banned or penalized in [...]]]></description>
			<content:encoded><![CDATA[<p>The point of this post is not to play dirty. The point is to expose a fatal flaw in the way Google Adsense does business in hopes that they will fix the problem.</p>
<p><strong>Background</strong></p>
<p>We already know there are a variety of blackhat tactics that can be used to get a competitor&#8217;s site banned or penalized in Google&#8217;s <em>search </em>listings (e.g. spamming backlinks in bad neighborhoods, duplicate content on multiple domains, etc.). All of these methods are off-site, meaning the webmaster has no way of stopping anyone from setting up hundreds of domains scraping his content and plummeting his SERP ranking. But what about sabotaging your competitor&#8217;s Adsense account?</p>
<p>There is always the obvious &#8220;go crazy clicking your competitor&#8217;s ads&#8221; tactic, but at least Google makes some attempt to combat this problem by tracking IP addresses and cookies. Publishers are being banned from Adsense at a steadily increasing rate, but I tend to think that usually it is the publisher&#8217;s own fault for encouraging clicks, providing adult content, or utilizing &#8220;shady&#8221; methods of driving traffic to their site.</p>
<p>When you signup for an Adsense account, you are approved based solely on the original domain you submit for review. Once you are approved, then you are allowed to instantly place your Adsense code on any number of sites that you own without having to have get them approved, or even put them on file with Adsense. As a publisher myself with hundreds of domains, I find this to be very convenient.  <em>But</em>…</p>
<p><strong>The Problem</strong></p>
<p>Since you have never submitted any of your domains to Adsense (beyond the initial domain), Google just ASSUMES that you own all of the domains that display your Adsense code. Consequently, your account will be held responsible for the traffic sources, promotional methods, spammy content, illegal ad placement, or poor click-through rate of a site that you may not even own (as long as they display your code)! And no, it&#8217;s not that easy to just signup for another account (you need a new SSN/EIN).</p>
<p><strong>The How-To List</strong></p>
<p>So with that in mind, I present to you a step-by-step guide to getting your competitor&#8217;s Adsense account banned:</p>
<p>1. Identify your competitor&#8217;s website.<br />
2. View the source code of any page that displays his Adsense javascript code, and copy it to your clipboard. It will look something like this (the section that reads <em>pub-xxxxxxxxxxxxxxxx</em> is his unique publisher ID):</p>
<blockquote><p>&lt;script type=&#8221;text/javascript&#8221;&gt;&lt;!&#8211;<br />
google_ad_client = &#8220;pub-xxxxxxxxxxxxxxxx&#8221;;<br />
google_ad_width = 728;<br />
google_ad_height = 90;<br />
google_ad_format = &#8220;728&#215;90_as&#8221;;<br />
google_ad_type = &#8220;text_image&#8221;;<br />
google_ad_channel = &#8220;&#8221;;<br />
google_color_border = &#8220;FFFFFF&#8221;;<br />
google_color_bg = &#8220;FFFFFF&#8221;;<br />
google_color_link = &#8220;0000FF&#8221;;<br />
google_color_text = &#8220;000000&#8243;;<br />
google_color_url = &#8220;000000&#8243;;<br />
//&#8211;&gt;&lt;/script&gt;<br />
&lt;script type=&#8221;text/javascript&#8221;<br />
src=&#8221;http://pagead2.googlesyndication.com/pagead/show_ads.js&#8221;&gt;<br />
&lt;/script&gt;</p></blockquote>
<p>3. Copy the javascript and paste it into any website that you own (I am assuming you know how to &#8220;replicate&#8221; your competitor&#8217;s whois info for your site, or at least make it private). It should instantly display your competitor&#8217;s ads on your site without any problem.<br />
4. Write a little note to your visitors: thank them for visiting and let them know that they should &#8220;check out our sponsored links.&#8221; Bonus points if you can rig up an animated gif arrow pointing to the ads.<br />
5. Blog about dildos or whatever sex toy you happen to fancy. Adsense loves adult content for sure!<br />
6. Spam your site to Craigslist every single day in all 400 cities (though 30 will probably do just fine), or <a href="http://www.scriptlance.com" title="Scriptlance">hire someone from India</a> to do it for you (it will only cost you about 15 cents per post).<br />
7. Buy bulk amounts of <a href="http://search.ebay.com/website-visitors_W0QQfromZR8QQssPageNameZWLRSQQsubmitsearchZSearch" title="traffic on Ebay">traffic on Ebay</a>! And I&#8217;m talking like a <em>million</em> hits to your site in a few weeks. If this shitty traffic doesn&#8217;t kill his Adsense click-through rate, nothing will. And who knows what kind of zombie computers or sneaky redirects are conjuring up your mystery traffic. (The Adsense javascript can relay to Google the <a href="http://en.wikipedia.org/wiki/HTTP_REFERER" title="HTTP_REFERER">HTTP_REFERER</a> attribute, which more or less reveals the source of your traffic.)<br />
8. Optional: Advertise your site via unsolicited email. This is illegal in many countries and people will hate you for this. The wise ones may even report you to Adsense (let&#8217;s hope!). Of course, they will probably report you to your host first, so I don&#8217;t recommend this one.<br />
9. Keep doing this for a month. Actually, you probably only have to do ONE of these methods for a month, but multiple ones won&#8217;t hurt. Every month before payment, Adsense quality control reviews accounts for… quality. You can be sure your site now has an extreme LACK of quality and is ready to get banned.<br />
10. Report your site to Google. Email adsense-abuse@google.com or click on the &#8220;Ads by Goooooogle&#8221; link to give them some helpful feedback on how their ad network is being abused.</p>
<p><strong>A Personal Experience and a Reply from Adsense</strong></p>
<p>When Google warns/bans an Adsense publisher for violating TOS, they generally provide at least a vague reason along with the violating domain. Couldn&#8217;t the publisher reply to Google and deny ownership of the domain? Well, at least according to an email I received from Adsense support, a publisher is reponsible for their Adsense code even if it is displayed against their will on a site they do not own!</p>
<p>Case in point, I sold one of my websites to a party who apparently did not know very much about web development. Instead of installing the PHP script that allows easy modification of pages and Adsense code through an admin interface, he simply ripped the static HTML of all 2000 pages! (Unbelievable, but okay whatever it&#8217;s his site now.) But even worse, he kept my Adsense code on his page. I asked him to remove it, but apparently he was trying to go through all 2000 pages and do it manually, so it was taking forever. Concerned about an incompetent webmaster displaying my Adsense code, I emailed Google asking them to keep my ads from displaying on that domain, as it was now out of my control. Their response:</p>
<p><em>Hello XXXX,</em></p>
<p><em>Thanks for writing in about your site. I understand that you&#8217;re having trouble with the person you&#8217;ve sold the site to. Unfortunately, we cannot blocks ads connected to your publisher ID from showing on this site.</em></p>
<p><em>I can only offer you two suggestions to remove your ads from this site.</em></p>
<p><em>First, you can contact the new owner of your site again and request that he remove your ads from the site.</em></p>
<p><em>Alternatively, you can permanently close your AdSense account. If you close your account, your ads will no longer appear on this site. Unfortunately, you&#8217;ll no longer have access to the Google code and you&#8217;ll receive no further emails from us. Your remaining earnings will be paid out according to the payment schedule outlined in the AdSense Terms and Conditions (https://www.google.com/adsense/terms), provided there are no holds on your account.</em></p>
<p><em>If you&#8217;d like to permanently close your AdSense account, please reply to this email and we&#8217;ll process your request. We also encourage you to let us know why you feel Google AdSense hasn&#8217;t worked well for you so far. We&#8217;re constantly working to improve our program and will carefully review all of your suggestions.</em></p>
<p><em>Thanks for your patience.</em></p>
<p><em>For additional questions, I&#8217;d encourage you to visit the AdSense Help Center (http://www.google.com/adsense_help), our complete resource center for all AdSense topics. Alternatively, feel free to post your question on the forum just for AdSense publishers: the AdSense Help Group (http://groups.google.com/group/adsense-help).</em></p>
<p><em>Sincerely,</em></p>
<p><em>XXXX<br />
The Google AdSense Team</em></p>
<p>So basically, Google told me my options were to either ask him again nicely to remove my code, or close my Adsense account altogether. Incompetent-webmaster-guy wondered why the hell I wouldn&#8217;t want to make more money while my code was still on his site. But I knew better than that. I knew he could put my ads in the wrong place, and I would get banned. I knew he could promote his new site using less than professional methods, and I would get banned. Frankly, a small site like the one I sold him was not worth jeopardizing a major source of income for my entire network of sites, and it made clear to me how easy it would be for a competitor to destroy me… or how easy it would be for me to destroy a competitor if I would so choose.</p>
<p><strong>Solution</strong></p>
<p>It&#8217;s very simple actually. Google should require every domain to be submitted to Adsense before ads are displayed, not for approval purposes, but for confirmation of ownership. Ads would display on the domain only after the publisher has claimed ownership of the domain and thus taken responsibility for the manner in which the ads are displayed.  This would prevent the sort of Adsense sabotage that I have described.</p>
<p><strong>Resources</strong></p>
<p><a href="https://www.google.com/adsense/localized-terms" title="Adsense Terms and Conditions">Google Adsense Terms and Conditions</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.metashit.com/2007/03/03/10-steps-to-getting-your-competitors-adsense-account-banned/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
