<?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>Metal Monster Marketing &#187; Search Results</title>
	<atom:link href="http://metalmonstermarketing.com/blog/category/search-results/feed/" rel="self" type="application/rss+xml" />
	<link>http://metalmonstermarketing.com/blog</link>
	<description></description>
	<lastBuildDate>Wed, 29 Apr 2009 16:57:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Keeping Google out of the WordPress backend</title>
		<link>http://metalmonstermarketing.com/blog/wordpress/keeping-google-out-of-the-wordpress-backend/</link>
		<comments>http://metalmonstermarketing.com/blog/wordpress/keeping-google-out-of-the-wordpress-backend/#comments</comments>
		<pubDate>Wed, 29 Apr 2009 16:53:58 +0000</pubDate>
		<dc:creator>Steve Gerencser</dc:creator>
				<category><![CDATA[SEO]]></category>
		<category><![CDATA[Search Results]]></category>
		<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://metalmonstermarketing.com/blog/?p=37</guid>
		<description><![CDATA[Over the past few months we&#8217;ve noticed that more and more pages from inside the WordPress backend are finding their way in to the Google index. This has always been a problem, but as Google seems to index more useless pages, and crackers get more sophisticated at finding vulnerabilities in WordPress modules, it is important [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignright size-full wp-image-38" title="spider-bots" src="http://metalmonstermarketing.com/blog/wp-content/uploads/2009/04/spider-bots.jpg" alt="spider-bots" width="250" height="150" />Over the past few months we&#8217;ve noticed that more and more pages from inside the WordPress backend are finding their way in to the Google index. This has always been a problem, but as Google seems to index more useless pages, and crackers get more sophisticated at finding vulnerabilities in WordPress modules, it is important to protect your site from both the crackers and Google.</p>
<h2>So what is the real harm?</h2>
<p>The most obvious, and urgent harm, comes from exposing your website to potential comprimise. If a vulnerability is found in a WordPress plugin it can take just a few seconds to find a host of web sites  to attack. Using Google&#8217;s inurl command a simple search of <a href="http://www.google.com/search?hl=en&amp;rls=GGGL%2CGGGL%3A2006-34%2CGGGL%3Aen&amp;q=inurl%3Awp-content%2Fplugins&amp;btnG=Search">inurl:wp-content/plugins</a> returns more than 8 million results for a cracker to start his or her search for likely targets.</p>
<p><img class="aligncenter size-full wp-image-39" title="wp-content-inurl" src="http://metalmonstermarketing.com/blog/wp-content/uploads/2009/04/wp-content-inurl.jpg" alt="wp-content-inurl" width="473" height="46" /></p>
<p>A dedicated cracker will comprimise your site, but there is no reason to make it easy for them.</p>
<p>Another less obvious problem is created by Google itself. In just this one simple search we&#8217;ve seen more than 8 million web pages that have no reason to be in the index. They serve no useful purpose other than to show how invasive Google can be with it&#8217;s crawler. It also demonstrates a duplicate content issue that needs to be addressed.</p>
<p>The real problem, however, is the harm this can cause each website this happens to.</p>
<p>It is known that Google may not index all of the pages in a website for various reasons. Assume you have a website with 100 pages. Yet Google decided to index 30 pages of your /wp-content or wp-admin/ folders. You have lost the postential for 30% of your pages to be indexed in favor of pages that should never have been in the index at all. I have seen sites with more than 50% of their indexed pages coming from the back end of WordPress.</p>
<h2>What can you do about it?</h2>
<p>There are two things that you should do to help secure your site from search engines exploring where they don&#8217;t belong.<strong></strong></p>
<p>1. Robots.txt: With every WordPress install I do these days I add this to my robots.txt file.</p>
<blockquote><p>User-agent: *<br />
Disallow: /blog/wp-admin/<br />
Disallow: /blog/wp-content/<br />
Disallow: /blog/wp-includes/</p></blockquote>
<p>Be sure to adjust the URL for your site&#8217;s install folders.</p>
<p>2. Google&#8217;s Webmaster Tools: If you find these pages indexed for your site first install the robots.txt file. Once that is done you should enter your GWT account and remove those pages from the index. Once removed the robots.txt should keep them from being re-indexed.</p>
<p>Unfortunately, from then on you will see and error message in your GWT account. You can ignore this error.</p>
<p>What does all of this tell us? The biggest thing it tells us is that the Google spiders are not as smart as everyone, including Google, would like us to believe. Indexing these pages serves no purpose, and it shows that the bots can and will go to places that they really should not be in and you must be proactive in protecting your website from them. A person would know that there is no reason to index more than 8 million of the exact same pages. An algorithm cannot make that decision.</p>
]]></content:encoded>
			<wfw:commentRss>http://metalmonstermarketing.com/blog/wordpress/keeping-google-out-of-the-wordpress-backend/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Do I really need a sitemap?</title>
		<link>http://metalmonstermarketing.com/blog/seo/do-i-really-need-a-sitemap/</link>
		<comments>http://metalmonstermarketing.com/blog/seo/do-i-really-need-a-sitemap/#comments</comments>
		<pubDate>Mon, 26 Jan 2009 13:38:47 +0000</pubDate>
		<dc:creator>Steve Gerencser</dc:creator>
				<category><![CDATA[SEO]]></category>
		<category><![CDATA[Search Results]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[sitemaps]]></category>

		<guid isPermaLink="false">http://metalmonstermarketing.com/blog/?p=34</guid>
		<description><![CDATA[Do I really need a sitemap? This question has been asked for a long time, and in mid 2005 Google made it even more complicated by introducing a sitemap format just for their spiders. First of all there are two types of sitemaps. One sitemap for users and one for Search engines. A sitemap for [...]]]></description>
			<content:encoded><![CDATA[<p>Do I really need a sitemap? This question has been asked for a long time, and in mid 2005 Google made it even more complicated by introducing a sitemap format just for their spiders.</p>
<p>First of all there are two types of sitemaps. One sitemap for users and one for Search engines. A sitemap for users may be beneficial in that it allows you to put every page on your web site just one click away for end users. Fewer clicks tend to help conversions, and on large web sites they may provide for an easy way for users to find exactly what they are looking for with the fewest clicks.</p>
<p><img class="size-medium wp-image-35 alignright" title="Sitemap confusion" src="http://metalmonstermarketing.com/blog/wp-content/uploads/2009/01/istock_000005483484xsmall-300x225.jpg" alt="Sitemap confusion" width="300" height="225" /></p>
<p>Sitemaps for search engines are another matter entirely. Originally the xml sitemap, as proposed by Google, was designed to help their spider crawl complex URLs that might have been missed by their spiders. These URLs tended to be in shopping cart systems and database driven sites developed by programmers that had little regard for the real world needs of a modern web site. Urls like domain.com/id7734&amp;ask?whyam-i:like&amp;this made deep crawls by spiders nearly impossible.</p>
<p>Since then having an xml sitemap has been trotted out as the solution to a long list of problems with websites when it comes to them not ranking well, or not having as many pages in the Google index . And for the vast majority of sites this isn&#8217;t true.</p>
<p>One of the deep indexing factors that Google does rely on is linking. On Matt Cutt&#8217;s blog in 2006 a discussion was raging about the <a href="http://www.mattcutts.com/blog/indexing-timeline/">supplemental index</a> and Matt mentioned that the number of links pointing toward a site was a factor in how often it was crawled and how deeply the site was indexed. No mention of the, by then, 1 year old sitemap.xml.</p>
<p class="answer_title">Google itself even says &#8220;<em>We don&#8217;t guarantee that we&#8217;ll crawl or index all of your URLs</em><sup>1</sup>&#8221; and that the sitemap is just used to <em>learn about your site&#8217;s structure</em><sup>1</sup>.</p>
<p>One of the major reasons that I recommend against xml sitemaps is that they require constant updating every time you update your website. And while there are tools available to help automate the process<sup>2</sup>, that in itself is reason enough not to do it, more work for questionable benefits. The only time an xml sitemap might be justified is when your site navigation is less than useful and is a challenge for search engine spiders to crawl. Unfortunately this may mean that your site navigation is a challenge to follow for end users as well, so it should be dealt with by fixing the navigation, not slapping a sitemap on it and calling it &#8220;fixed&#8221;.</p>
<p>Another reason that I don&#8217;t recommend xml sitemaps, in most cases, is that Google has had a long standing policy that we should build web sites for our users and not for the search engines. Unless their spider isn&#8217;t advanced enough to do the job, then webmasters are expected to step up and make things easier for them. Xml sitemaps and nofollow are just a couple of examples of building something for search engines only that has no benefit as all for the user viewing your website.</p>
<p>So to answer the question, Do I really need a sitemap?, no, you don&#8217;t. You need clean navigation on a well structured web site. However, if you have complex URLs on an incredibly large web site with lousy navigation, it can&#8217;t hurt, but it also probably won&#8217;t help much either.</p>
<ol>
<li>From <a href="http://www.google.com/support/webmasters/bin/answer.py?answer=35184&amp;topic=13450">Will Google crawl and index all of the URLs in my Sitemap?</a></li>
<li><a href="http://www.google.com/search?hl=en&amp;safe=off&amp;rls=GGGL%2CGGGL%3A2006-34%2CGGGL%3Aen&amp;q=free+sitemap+generator&amp;btnG=Search">Free Sitemap Generators</a></li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://metalmonstermarketing.com/blog/seo/do-i-really-need-a-sitemap/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Where does your name go?</title>
		<link>http://metalmonstermarketing.com/blog/firefox/where-does-your-name-go/</link>
		<comments>http://metalmonstermarketing.com/blog/firefox/where-does-your-name-go/#comments</comments>
		<pubDate>Wed, 13 Feb 2008 21:11:20 +0000</pubDate>
		<dc:creator>Steve Gerencser</dc:creator>
				<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Keywords]]></category>
		<category><![CDATA[Search Results]]></category>
		<category><![CDATA[Matt Cutts]]></category>
		<category><![CDATA[Vanity]]></category>

		<guid isPermaLink="false">http://metalmonstermarketing.com/blog/?p=9</guid>
		<description><![CDATA[I was taking a short cut the other day to get to Matt Cutts&#8217; blog and just typed his name in to the address bar of Firefox expecting it to hit the Google search results and give me a link to click. Imagine my surprise when it took me straight to his website. I do [...]]]></description>
			<content:encoded><![CDATA[<p>I was taking a short cut the other day to get to <a href="http://www.mattcutts.com/blog/">Matt Cutts&#8217; blog</a> and just typed his name in to the address bar of Firefox expecting it to hit the Google search results and give me a link to click. Imagine my surprise when it took me straight to his website. I do have the Google Toolbar installed on Firefox, so I thought I&#8217;d give IE a shot. <em>Matt Cutts </em>turned up wiki as the #1 result in Live Search and his blog as #2. Hmm, maybe this is an indication of FireFox (or Toolbar) fandom.</p>
<p><em>Danny Sullivan</em> in the address bar hits Google search results and has <a href="http://searchengineland.com/">Search  Engine Land</a> as #1. Fair Enough. My name brings up my LinkedIn profile in the search results, still no direct push to my website. Maybe someone more famous than me or Danny will help. <em>George Bush</em>? Nope. <em>Hillary Clinton</em>? Nope. At least there is no political favoritism going on. Maybe another Googler? <em>Sergy Brin</em> pops me over to the <a href="http://www.thebiographychannel.co.uk/biography_home/1352:0/Google_Boys_-_Sergy_Brin_Larry_Page.htm">Biography Channel &#8211; UK</a> and <em>Larry Page</em> lands us over at <a href="http://en.wikipedia.org/wiki/Larry_Page">wikipedia</a>. Hmm, beginning to see a trend here.</p>
<p>Time to uninstall the toolbar. . . . . . .</p>
<p>Hmm, no toolbar and Yahoo! set as the default search and still redirected to Matt&#8217;s blog. It&#8217;s beginning to look like a Firefox admiration (funding?) issue. Damn, not even <em>Marc Andreessen</em> gets this level of respect.</p>
<p>What does Firefox think of your name?</p>
]]></content:encoded>
			<wfw:commentRss>http://metalmonstermarketing.com/blog/firefox/where-does-your-name-go/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
