<?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>&#124; Clustr Media &#187; developer mistakes</title>
	<atom:link href="http://clustrmedia.us/blog/tag/developer-mistakes/feed/" rel="self" type="application/rss+xml" />
	<link>http://clustrmedia.us</link>
	<description>Reno/Sparks Web Design &#38; SEO</description>
	<lastBuildDate>Wed, 28 Apr 2010 20:09:50 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=9451</generator>
		<item>
		<title>Stupid Web Development Mistakes</title>
		<link>http://clustrmedia.us/blog/web-design/stupid-web-development-mistakes/</link>
		<comments>http://clustrmedia.us/blog/web-design/stupid-web-development-mistakes/#comments</comments>
		<pubDate>Sat, 06 Jun 2009 05:57:36 +0000</pubDate>
		<dc:creator>Chris Gandolfo</dc:creator>
				<category><![CDATA[web design]]></category>
		<category><![CDATA[developer mistakes]]></category>

		<guid isPermaLink="false">http://clustrmedia.us/?p=244</guid>
		<description><![CDATA[test]]></description>
			<content:encoded><![CDATA[<p>There are some things that web designers simply should not allow to happen in the course of developing  a website. These are basic, forehead-slapping, moments of shear stupidity that by today&#8217;s best practices should at the minimum land the designer or developer in hot water and at the maximum cost them the job, project or contract.</p>
<p><strong>There&#8217;s no room for mistakes.</strong> Period.</p>
<p><span id="more-244"></span></p>
<p>And yet, I see these type of mistakes almost on a daily basis. Some are due to technology while others are simply human error. My response is simple. First, technology should never stand in the way or negatively impact business operations or messaging. Second, more than one person should always review or have some insight into the project and human errors should be fixed prior to being exposed to the public.</p>
<p>In this case, the error I am referring to is allowing your test page or development site to be indexed by the search engines and made available to the public in their results. I&#8217;ve tried to illustrate this with the screen capture below from Google. Let me explain what is in it and how I found it.</p>
<p>I was trying to track down an ex-colleague that I knew ran a freelance web development business. So, I hit Google and searched for his business name. The first two results were for his home page and his bio page on his website. The third result, however, was obviously a test page he had developed for one of his clients. There it was, sitting fat and pretty in the #3 spot on the first page of results for his business name. (Click to enlarge thumbnail. All identifiable information has been blurred out.)</p>
<p style="text-align: center;"><a href="http://clustrmedia.us/wp-content/uploads/2009/06/test-page-indexed.jpg"><img class="size-medium wp-image-245 aligncenter" title="test-page-indexed" src="http://clustrmedia.us/wp-content/uploads/2009/06/test-page-indexed-300x160.jpg" alt="test-page-indexed" width="300" height="160" /></a></p>
<p>Imagine if you were given this designer&#8217;s name as a referral and you popped online to find his site. What would you think about seeing his in-development project right there, live to the world? I would wonder if he would expose my project with the same carelessness and lack of regard.</p>
<p>That led me to do a search on the client&#8217;s name and product name. Again, the first two results showed the client&#8217;s website and the #3 spot had the web designer&#8217;s test page sitting there. Now indexing and ranking can happen overnight, but it is extremely rare for a page that is online for a very short time to show up in the top ten results. This had to of been there a while. I&#8217;ve checked it 3 times since the last week of April, with the last one being on May 30th. All 3 times I have received the same results. So not only has it been allowed to be indexed, but it has stayed there.</p>
<p>There are several ways to prevent this basic mistake that with a little more quality control on the part of the designer would make sure this kind of thing would never happen. At the very least it can be blocked with a robots meta tag that includes noindex. A second way would be to lock out the search engine robots with a robots.txt file. Third, you could put it behind a secure login via htpasswd. <em>If you&#8217;re a developer reading this and you don&#8217;t know what any of those things mean, you can start by googling those terms.</em></p>
<p>Again, the bottom line is that stpuid web design mistakes like this should never, ever happen.</p>


<div class="shr-bookmarks shr-bookmarks-center shr-bookmarks-bg-enjoy">
<ul class="socials">
		<li class="shr-comfeed">
			<a href="http://clustrmedia.us/blog/web-design/stupid-web-development-mistakes/feed" rel="nofollow" class="external" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="shr-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://clustrmedia.us/blog/web-design/stupid-web-development-mistakes/&amp;t=Stupid+Web+Development+Mistakes" rel="nofollow" class="external" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="shr-twitter">
			<a href="http://twitter.com/home?status=Stupid+Web+Development+Mistakes+-+&amp;source=shareaholic" rel="nofollow" class="external" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="shr-delicious">
			<a href="http://delicious.com/post?url=http://clustrmedia.us/blog/web-design/stupid-web-development-mistakes/&amp;title=Stupid+Web+Development+Mistakes" rel="nofollow" class="external" title="Share this on del.icio.us">Share this on del.icio.us</a>
		</li>
		<li class="shr-designbump">
			<a href="http://designbump.com/submit?url=http://clustrmedia.us/blog/web-design/stupid-web-development-mistakes/&amp;title=Stupid+Web+Development+Mistakes&amp;body=test" rel="nofollow" class="external" title="Bump this on DesignBump">Bump this on DesignBump</a>
		</li>
		<li class="shr-designfloat">
			<a href="http://www.designfloat.com/submit.php?url=http://clustrmedia.us/blog/web-design/stupid-web-development-mistakes/&amp;title=Stupid+Web+Development+Mistakes" rel="nofollow" class="external" title="Submit this to DesignFloat">Submit this to DesignFloat</a>
		</li>
		<li class="shr-digg">
			<a href="http://digg.com/submit?phase=2&amp;url=http://clustrmedia.us/blog/web-design/stupid-web-development-mistakes/&amp;title=Stupid+Web+Development+Mistakes" rel="nofollow" class="external" title="Digg this!">Digg this!</a>
		</li>
		<li class="shr-diigo">
			<a href="http://www.diigo.com/post?url=http://clustrmedia.us/blog/web-design/stupid-web-development-mistakes/&amp;title=Stupid+Web+Development+Mistakes&amp;desc=test" rel="nofollow" class="external" title="Post this on Diigo">Post this on Diigo</a>
		</li>
		<li class="shr-googlebuzz">
			<a href="http://www.google.com/buzz/post?url=http://clustrmedia.us/blog/web-design/stupid-web-development-mistakes/&amp;imageurl=" rel="nofollow" class="external" title="Post on Google Buzz">Post on Google Buzz</a>
		</li>
		<li class="shr-linkedin">
			<a href="http://www.linkedin.com/shareArticle?mini=true&amp;url=http://clustrmedia.us/blog/web-design/stupid-web-development-mistakes/&amp;title=Stupid+Web+Development+Mistakes&amp;summary=test&amp;source=| Clustr Media" rel="nofollow" class="external" title="Share this on LinkedIn">Share this on LinkedIn</a>
		</li>
		<li class="shr-misterwong">
			<a href="http://www.mister-wong.com/addurl/?bm_url=http://clustrmedia.us/blog/web-design/stupid-web-development-mistakes/&amp;bm_description=Stupid+Web+Development+Mistakes&amp;plugin=sexybookmarks" rel="nofollow" class="external" title="Add this to Mister Wong">Add this to Mister Wong</a>
		</li>
		<li class="shr-mixx">
			<a href="http://www.mixx.com/submit?page_url=http://clustrmedia.us/blog/web-design/stupid-web-development-mistakes/&amp;title=Stupid+Web+Development+Mistakes" rel="nofollow" class="external" title="Share this on Mixx">Share this on Mixx</a>
		</li>
		<li class="shr-reddit">
			<a href="http://reddit.com/submit?url=http://clustrmedia.us/blog/web-design/stupid-web-development-mistakes/&amp;title=Stupid+Web+Development+Mistakes" rel="nofollow" class="external" title="Share this on Reddit">Share this on Reddit</a>
		</li>
		<li class="shr-stumbleupon">
			<a href="http://www.stumbleupon.com/submit?url=http://clustrmedia.us/blog/web-design/stupid-web-development-mistakes/&amp;title=Stupid+Web+Development+Mistakes" rel="nofollow" class="external" title="Stumble upon something good? Share it on StumbleUpon">Stumble upon something good? Share it on StumbleUpon</a>
		</li>
		<li class="shr-technorati">
			<a href="http://technorati.com/faves?add=http://clustrmedia.us/blog/web-design/stupid-web-development-mistakes/" rel="nofollow" class="external" title="Share this on Technorati">Share this on Technorati</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>

]]></content:encoded>
			<wfw:commentRss>http://clustrmedia.us/blog/web-design/stupid-web-development-mistakes/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
