<?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>Search Engine Optimization Blog &#187; SEOTech Talk</title>
	<atom:link href="http://www.metamend.com/blog/category/seotech-talk/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.metamend.com/blog</link>
	<description>Search engine and Website Marketing tips, information, news and opinion from Metamend's team of SEM and SEO experts. The Metamend Blog covers SEO, search engines, search trends, search engine optimization and marketing.</description>
	<lastBuildDate>Fri, 12 Mar 2010 00:42:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Choose Relevant Keyword Targets</title>
		<link>http://www.metamend.com/blog/2010/01/14/choose-relevant-keyword-targets/</link>
		<comments>http://www.metamend.com/blog/2010/01/14/choose-relevant-keyword-targets/#comments</comments>
		<pubDate>Thu, 14 Jan 2010 23:44:58 +0000</pubDate>
		<dc:creator>Mark Johnstone</dc:creator>
				<category><![CDATA[SEOTech Talk]]></category>
		<category><![CDATA[Search Engines, SEO]]></category>
		<category><![CDATA[keywords]]></category>
		<category><![CDATA[long-tail]]></category>

		<guid isPermaLink="false">http://www.metamend.com/blog/?p=1214</guid>
		<description><![CDATA[Ad Hoc Keyword Research is Dead - Determining an optimal keyword list can be a very involved process and is always considered the lynchpin of any successful search marketing campaign.]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.metamend.com/blog/wp-content/uploads/2010/01/adhoc-kwblog1.gif"><img class="alignright size-full wp-image-1228" title="adhoc-kwblog1" src="http://www.metamend.com/blog/wp-content/uploads/2010/01/adhoc-kwblog1.gif" alt="" width="400" height="100" /></a></p>
<p><strong>Ad Hoc Keyword Research is Dead</strong></p>
<p>Determining an optimal keyword list can be a very involved process and is always considered the lynchpin of any successful search marketing campaign. Gone are the days of focusing your search marketing efforts on a phrase list consisting of one or two keyword terms. These “short-tail” phrases might prove to be over saturated in the search engines results or are lacking in specific relevancy to your message thus leading to a poor conversion potential. Finding those “long-tail” terms will always lead to a great ROI potential, and greater user retention.</p>
<p><strong>The Process –In a Nutshell</strong></p>
<p>The phraseology process has in recent years has truly become an art form and each analyst will have a core set of tools and different methods of data collection when crafting their final targeted terms.</p>
<p>The first step of this process typically includes the collecting of related search terms en masse. Generating large groups of search terms varying in length are gathered using keyword search tools and one should utilize more than one set of tools. Relying on one keyword tool can be detrimental to the end result when assessing your keyword targets. It is always a safe bet to back up your search data comparing the results between multiple sources. As one can imagine different search data sources can lead to very different results.</p>
<p>Most reputable search marketing firms will have a gambit of in-house developed tools at their disposal however here is a sample of commonly used search / keyword tools:</p>
<ul>
<li>Google’s Keyword Tool and Insights to Search</li>
<li>Keyword Discovery</li>
<li>Word Tracker</li>
<li>Wordstream</li>
<li>Keyword Spy</li>
<li>SEOmoz – Keyword Difficulty Tool</li>
</ul>
<p>At the end of this phase you should take a close look at historical analytics to see what terms have delivered the most relevant targets in the past. It is imperative not to destroy the great traffic you have enjoyed in the past by diluting it with new terms. Build on past successes instead of just replacing it with another term.<br />
Once your core phrase targets have been collected and loosely organized the paring down phase of the process kicks in. The removal of unachievable terms (due competition) and others that have a lower relevancy or traffic potential should be performed. The results should deliver you with somewhat of a refined core list to work from.</p>
<p>The final goal of course is to have a tightly refined targeted list to apply to your <a href="http://www.metamend.com/seo-services/" title="search engine optimization">search engine optimization</a> strategies and this is where the historical knowledge of the types of keywords that convert comes in to play.<br />
Assessing the realistic expectations of the phrases you wish to employ is prudent. Can your site compete with the others targeting that term? Are you able to do what it takes to add value to your site in order to target that particular term? These are the questions that need to be addresses before committing to the final targets.</p>
<p>These tips are truly a very broad look at what is needed to come up with solid targets that will over time deliver you with all that huge traffic increases you are looking for. An experienced keyword analyst will have the insight to provide a solid targeted list and the search / historical data to back up the choices.</p>
<p><strong>The Company Branding and Messaging Misconception</strong></p>
<p>The right mindset is essential to come up with the final keyword selection that is going to deliver you with those “money” terms.  All too often traditional marketing individuals have a difficult time understanding that what has works for years on a billboard does not necessary translate into a winning term via search. This is not to say that one should not pay close attention to fully understanding a company’s brick and mortar business and the existing marketing initiatives. The more intimate you are with the business messaging, product or service will obviously have a large impact on the phraseology process.</p>
<p>Marketing managers and business owners will also sometimes have strong views on what terms they wish to be found under. All too often these terms are not searched by web searchers in great numbers and in some cases can deliver irrelevant results.</p>
<p>For example, an auto insurance company might be apprehensive with the keyword suggestion “cheap auto insurance quotes” with the thinking that the word “cheap” degrades the quality of their business and perhaps places a misconception on the quality of their service. They may push you on this and suggest that “inexpensive automobile insurance quotes” is what they want you to utilize in your strategies. Nine times out of ten once they realize that people just don’t search that way and your suggestions will come to fruition.</p>
<p>Mark Johnstone</p>
<p><a href="http://www.metamend.com/services/" title="search engine marketing">Search Engine Marketing</a> Analyst and Project Manager<br />
Google AdWords Qualified Individual<br />
Metamend &#8211; Search Engine Marketing Experts</p>


<!-- Begin SexyBookmarks Menu Code -->
<div class="sexy-bookmarks sexy-bookmarks-expand">
<ul class="socials">
		<li class="sexy-delicious">
			<a href="http://del.icio.us/post?url=http://www.metamend.com/blog/2010/01/14/choose-relevant-keyword-targets/&amp;title=Choose+Relevant+Keyword+Targets" rel="nofollow" title="Share this on del.icio.us">Share this on del.icio.us</a>
		</li>
		<li class="sexy-digg">
			<a href="http://digg.com/submit?phase=2&amp;url=http://www.metamend.com/blog/2010/01/14/choose-relevant-keyword-targets/&amp;title=Choose+Relevant+Keyword+Targets" rel="nofollow" title="Digg this!">Digg this!</a>
		</li>
		<li class="sexy-reddit">
			<a href="http://reddit.com/submit?url=http://www.metamend.com/blog/2010/01/14/choose-relevant-keyword-targets/&amp;title=Choose+Relevant+Keyword+Targets" rel="nofollow" title="Share this on Reddit">Share this on Reddit</a>
		</li>
		<li class="sexy-stumbleupon">
			<a href="http://www.stumbleupon.com/submit?url=http://www.metamend.com/blog/2010/01/14/choose-relevant-keyword-targets/&amp;title=Choose+Relevant+Keyword+Targets" rel="nofollow" title="Stumble upon something good? Share it on StumbleUpon">Stumble upon something good? Share it on StumbleUpon</a>
		</li>
		<li class="sexy-technorati">
			<a href="http://technorati.com/faves?add=http://www.metamend.com/blog/2010/01/14/choose-relevant-keyword-targets/" rel="nofollow" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="sexy-twitter">
			<a href="http://twitter.com/home?status=Choose+Relevant+Keyword+Targets+-+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="http://www.shareaholic.com/pages/maintenanceapi.php?alias=&amp;url=http://www.metamend.com/blog/2010/01/14/choose-relevant-keyword-targets/">here</a>.</p>
</body></html>+" rel="nofollow" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="sexy-comfeed">
			<a href="http://www.metamend.com/blog/2010/01/14/choose-relevant-keyword-targets/feed" rel="nofollow" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="sexy-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.metamend.com/blog/2010/01/14/choose-relevant-keyword-targets/&amp;t=Choose+Relevant+Keyword+Targets" rel="nofollow" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="sexy-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.metamend.com/blog/2010/01/14/choose-relevant-keyword-targets/&amp;t=Choose+Relevant+Keyword+Targets" rel="nofollow" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="sexy-sphinn">
			<a href="http://sphinn.com/index.php?c=post&amp;m=submit&amp;link=http://www.metamend.com/blog/2010/01/14/choose-relevant-keyword-targets/" rel="nofollow" title="Sphinn this on Sphinn">Sphinn this on Sphinn</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>
<!-- End SexyBookmarks Menu Code -->

]]></content:encoded>
			<wfw:commentRss>http://www.metamend.com/blog/2010/01/14/choose-relevant-keyword-targets/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Its Only a C and D &#8211; Don&#8217;t Panic!</title>
		<link>http://www.metamend.com/blog/2009/06/22/its-only-a-c-and-d-dont-panic/</link>
		<comments>http://www.metamend.com/blog/2009/06/22/its-only-a-c-and-d-dont-panic/#comments</comments>
		<pubDate>Mon, 22 Jun 2009 16:06:56 +0000</pubDate>
		<dc:creator>Dustin Busmann</dc:creator>
				<category><![CDATA[SEOTech Talk]]></category>
		<category><![CDATA[Search Engine Industry News]]></category>
		<category><![CDATA[Search Engines, SEO]]></category>
		<category><![CDATA[Cease and Desist]]></category>
		<category><![CDATA[Intellectual property enforcement]]></category>
		<category><![CDATA[Trademark]]></category>

		<guid isPermaLink="false">http://www.metamend.com/blog/?p=1043</guid>
		<description><![CDATA[I have been sending and enforcing Cease and Desist letters for a while now and I have observed that people can be really emotional when you let them know they may be doing something wrong. I will share a unique instance and I will provide some helpful tips to survive your own C and D experience.]]></description>
			<content:encoded><![CDATA[<p>I have been sending and enforcing Cease and Desist letters for a while now and I have observed that people can be really emotional when you let them know they may be doing something wrong. I will share a unique instance and I will provide some helpful tips to survive your own C and D experience.</p>
<p>Once during a rather large <a href="http://www.metamend.com/reputation-management-protection/" target="_blank">Intellectual property enforcement</a>, one respondent replied with a firey e-mail stating we were persecuting him, and he was just an honest businessman who wasn&#8217;t doing anything wrong. I began to compose a reply immediately, calmly and logically presenting supporting data for our claim, and before I could finish my response and hit send, I was greeted with another e-mail from the same person. This time the man was borderline depressed and apologetic, and remarkably, only a few minutes had elapsed. I deleted my first e-mail response that I was composing, since the whole tone had changed, and before I could re-write another e-mail I was greeted with yet a third response. This was puzzling since I had yet to respond at all? The tone of this e-mail was a willingness to work with us if we could provide sufficient proof of Trademark, good faith usage, etc. I decided this time my response was getting written, hell or high water. I sent out the response with all necessary proof, and I heard nothing back for the rest of the day.<br />
The next morning the man was back with a vengeance. He was going to figure out how to destroy the company, ruin my life and make us pay for having the audacity to call him on his actions, according to the e-mail. I replied calmly and logically, staying on the issue at hand and ignoring his fantastical word imagery and terroristic threats. I reminded him of the law that he was actually breaking, only from the intellectual property standpoint, and I attached supporting evidence that we would use to defend our claim and rights. I sent the e-mail. He replied with a statement along the lines of : &#8220;you&#8217;ll be hearing from my attorney.&#8221; and it ended.<br />
Later that day we received an e-mail containing an authcode for domain transfer and an apologetic e-mail for causing so much difficulty.  To this day, I am unsure if that issue honestly ever resolved in that man&#8217;s mind or if he is still plotting my demise?<br />
Contrary to the last respondent, there is no need to get overly excited if you receive a cease and desist letter. It is honestly a courtesy extended to you in the hopes of preventing expensive legal action, no matter how it may feel. Here are some tips if you are a lucky recipient of a Cease and Desist:</p>
<p>Tips</p>
<p>1. Really read the letter. Many times people in their haste either throw the letter away or pick out one element and get hung up on it. Getting hung up on one point also may lead to you to inadvertently escalating due your frustration over simply being in this situation. Without reading the letter fully, you have no idea what you have done, to whom, or how long you have to respond to these claims.</p>
<p>2. Respond! If you Choose to ignore the issue, that is usually taken as an admission of guilt by the offended party! In fact, what you are doing is &#8220;escalating&#8221;, whether by accident or design. Throwing the letter away can lead to you getting sued, and doesn&#8217;t rectify the situation at all. This is akin to an Ostrich putting its head in the sand.  Having said that, I recommend composing a response after seeking advice as needed, and then walking away for 30 minutes to an hour before sending. Perhaps even wait until the next day or obviously let your legal counsel respond. In most cases, emotions will hang you, not the plaintiff, so re-read and remove the emotion from your response before sending.</p>
<p>3. Remain open. Take a look at what they are saying, and get comfortable with the idea that you may be in the wrong, even by accident. Most Cease and Desist letters simply want you to do just that; stop the behavior they have a problem with.</p>
<p>4. Remedy the situation. If they have a point, and you can fix this situation, you probably should. If they are wrong, then get professional counsel ASAP and counter the accusation by using a professional with evidence of your own.</p>
<p>Remember, do not let your emotions get the best of you.</p>


<!-- Begin SexyBookmarks Menu Code -->
<div class="sexy-bookmarks sexy-bookmarks-expand">
<ul class="socials">
		<li class="sexy-delicious">
			<a href="http://del.icio.us/post?url=http://www.metamend.com/blog/2009/06/22/its-only-a-c-and-d-dont-panic/&amp;title=Its+Only+a+C+and+D+-+Don%27t+Panic%21" rel="nofollow" title="Share this on del.icio.us">Share this on del.icio.us</a>
		</li>
		<li class="sexy-digg">
			<a href="http://digg.com/submit?phase=2&amp;url=http://www.metamend.com/blog/2009/06/22/its-only-a-c-and-d-dont-panic/&amp;title=Its+Only+a+C+and+D+-+Don%27t+Panic%21" rel="nofollow" title="Digg this!">Digg this!</a>
		</li>
		<li class="sexy-reddit">
			<a href="http://reddit.com/submit?url=http://www.metamend.com/blog/2009/06/22/its-only-a-c-and-d-dont-panic/&amp;title=Its+Only+a+C+and+D+-+Don%27t+Panic%21" rel="nofollow" title="Share this on Reddit">Share this on Reddit</a>
		</li>
		<li class="sexy-stumbleupon">
			<a href="http://www.stumbleupon.com/submit?url=http://www.metamend.com/blog/2009/06/22/its-only-a-c-and-d-dont-panic/&amp;title=Its+Only+a+C+and+D+-+Don%27t+Panic%21" rel="nofollow" title="Stumble upon something good? Share it on StumbleUpon">Stumble upon something good? Share it on StumbleUpon</a>
		</li>
		<li class="sexy-technorati">
			<a href="http://technorati.com/faves?add=http://www.metamend.com/blog/2009/06/22/its-only-a-c-and-d-dont-panic/" rel="nofollow" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="sexy-twitter">
			<a href="http://twitter.com/home?status=Its+Only+a+C+and+D+-+Don%27t+Panic%21+-+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="http://www.shareaholic.com/pages/maintenanceapi.php?alias=&amp;url=http://www.metamend.com/blog/2009/06/22/its-only-a-c-and-d-dont-panic/">here</a>.</p>
</body></html>+" rel="nofollow" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="sexy-comfeed">
			<a href="http://www.metamend.com/blog/2009/06/22/its-only-a-c-and-d-dont-panic/feed" rel="nofollow" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="sexy-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.metamend.com/blog/2009/06/22/its-only-a-c-and-d-dont-panic/&amp;t=Its+Only+a+C+and+D+-+Don%27t+Panic%21" rel="nofollow" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="sexy-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.metamend.com/blog/2009/06/22/its-only-a-c-and-d-dont-panic/&amp;t=Its+Only+a+C+and+D+-+Don%27t+Panic%21" rel="nofollow" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="sexy-sphinn">
			<a href="http://sphinn.com/index.php?c=post&amp;m=submit&amp;link=http://www.metamend.com/blog/2009/06/22/its-only-a-c-and-d-dont-panic/" rel="nofollow" title="Sphinn this on Sphinn">Sphinn this on Sphinn</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>
<!-- End SexyBookmarks Menu Code -->

]]></content:encoded>
			<wfw:commentRss>http://www.metamend.com/blog/2009/06/22/its-only-a-c-and-d-dont-panic/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Updates Webmaster Tools with Sources for Crawl Errors</title>
		<link>http://www.metamend.com/blog/2008/10/13/google-updates-webmaster-tools-with-sources-for-crawl-errors/</link>
		<comments>http://www.metamend.com/blog/2008/10/13/google-updates-webmaster-tools-with-sources-for-crawl-errors/#comments</comments>
		<pubDate>Tue, 14 Oct 2008 04:19:41 +0000</pubDate>
		<dc:creator>Jade Carter</dc:creator>
				<category><![CDATA[SEOTech Talk]]></category>
		<category><![CDATA[back links]]></category>
		<category><![CDATA[crawl errors]]></category>
		<category><![CDATA[google webmaster tools]]></category>
		<category><![CDATA[page rank]]></category>

		<guid isPermaLink="false">http://www.metamend.com/blog/?p=747</guid>
		<description><![CDATA[Google Webmaster Tools (GWT)  has updated their ‘Crawl Errors’ section by adding the ‘Source URL’ to the Errors for URLs in Sitemaps and Not Found (404) reports.]]></description>
			<content:encoded><![CDATA[<p>In a brilliant move yesterday, Google Webmaster Tools (<a href="https://www.google.com/webmasters/tools/docs/en/about.html" target="_blank">GWT</a>)  has updated their &#8216;Crawl Errors&#8217; section by adding the &#8216;Source URL&#8217; to the Errors for URLs in Sitemaps and Not Found (404) reports. Why is this brilliant? Well previously, for those users with challenges acquiring server log files in order to determined the source of the link for those errors which originated from external URLs, a band-aid redirect was the only option (not very many low level programs would declare the referring page so this was quite a challenge for most). While that corrects the HTTP error it doesn&#8217;t address the root cause which was a website owner posting a malformed or outdated link to your website. If this link arrives from a highly reputable source, you&#8217;ll be doing them a favour by informing them of the error which will also help with their own site&#8217;s user experience and will get you some well earned brownie points. As well, correcting the link would swing any Page Rank (<a href="http://www.google.com/technology/pigeonrank.html" target="_blank">PR</a>) your way and you&#8217;d also have a great excuse here to solidify a healthy link relationship.</p>
<h3>Show me Where these Dead Links are Coming From</h3>
<p>Okay, here&#8217;s a snip of the new feature;</p>
<div class="mceTemp mceIEcenter">
<dl id="attachment_748" class="wp-caption aligncenter" style="width: 310px;">
<dt class="wp-caption-dt"><a href="http://www.metamend.com/blog/wp-content/uploads/2008/10/gwtsourcelinks.jpg"><img class="size-medium wp-image-748" title="gwtsourcelinks" src="http://www.metamend.com/blog/wp-content/uploads/2008/10/gwtsourcelinks-300x115.jpg" alt="Google Webmaster Tools Update Broken Link Source" width="300" height="115" /></a></dt>
</dl>
</div>
<p style="text-align: left;">The &#8216;Linked From&#8217; link triggers a nifty little lightbox type window with the sources of the faulty links. Each page listed represents each page where the invalid link was detected. They may be internal links which you&#8217;ll need to correct, or they may be links from external sources which you&#8217;ll now know exactly where they are originating from. The link source report is found under the URLs in Sitemaps errors and Not Found errors.</p>
<h3>Don&#8217;t Ignore Your Crawl Errors</h3>
<p style="text-align: left;">Once again, the moral here is that in this cut throat SEO game every little bit counts and if the Search Engines, in their infinite wisdom ( except &#8216;Live&#8217; and it&#8217;s Anti Cloaking Bot :) ) are going to be kind enough to offer up some helpful advice, you&#8217;d be silly not to take notice. With this new feature be sure to completely audit each and every item detailed here as they all have the potential to represent a new lead, prospective client, referral or that last back link which bumps you into the next major PR increment. Keep your stick on the ice and don&#8217;t ignore your broken links!</p>


<!-- Begin SexyBookmarks Menu Code -->
<div class="sexy-bookmarks sexy-bookmarks-expand">
<ul class="socials">
		<li class="sexy-delicious">
			<a href="http://del.icio.us/post?url=http://www.metamend.com/blog/2008/10/13/google-updates-webmaster-tools-with-sources-for-crawl-errors/&amp;title=Google+Updates+Webmaster+Tools+with+Sources+for+Crawl+Errors" rel="nofollow" title="Share this on del.icio.us">Share this on del.icio.us</a>
		</li>
		<li class="sexy-digg">
			<a href="http://digg.com/submit?phase=2&amp;url=http://www.metamend.com/blog/2008/10/13/google-updates-webmaster-tools-with-sources-for-crawl-errors/&amp;title=Google+Updates+Webmaster+Tools+with+Sources+for+Crawl+Errors" rel="nofollow" title="Digg this!">Digg this!</a>
		</li>
		<li class="sexy-reddit">
			<a href="http://reddit.com/submit?url=http://www.metamend.com/blog/2008/10/13/google-updates-webmaster-tools-with-sources-for-crawl-errors/&amp;title=Google+Updates+Webmaster+Tools+with+Sources+for+Crawl+Errors" rel="nofollow" title="Share this on Reddit">Share this on Reddit</a>
		</li>
		<li class="sexy-stumbleupon">
			<a href="http://www.stumbleupon.com/submit?url=http://www.metamend.com/blog/2008/10/13/google-updates-webmaster-tools-with-sources-for-crawl-errors/&amp;title=Google+Updates+Webmaster+Tools+with+Sources+for+Crawl+Errors" rel="nofollow" title="Stumble upon something good? Share it on StumbleUpon">Stumble upon something good? Share it on StumbleUpon</a>
		</li>
		<li class="sexy-technorati">
			<a href="http://technorati.com/faves?add=http://www.metamend.com/blog/2008/10/13/google-updates-webmaster-tools-with-sources-for-crawl-errors/" rel="nofollow" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="sexy-twitter">
			<a href="http://twitter.com/home?status=Google+Updates+Webmaster+Tools+with+Sources+for+Crawl+Errors+-+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="http://www.shareaholic.com/pages/maintenanceapi.php?alias=&amp;url=http://www.metamend.com/blog/2008/10/13/google-updates-webmaster-tools-with-sources-for-crawl-errors/">here</a>.</p>
</body></html>+" rel="nofollow" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="sexy-comfeed">
			<a href="http://www.metamend.com/blog/2008/10/13/google-updates-webmaster-tools-with-sources-for-crawl-errors/feed" rel="nofollow" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="sexy-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.metamend.com/blog/2008/10/13/google-updates-webmaster-tools-with-sources-for-crawl-errors/&amp;t=Google+Updates+Webmaster+Tools+with+Sources+for+Crawl+Errors" rel="nofollow" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="sexy-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.metamend.com/blog/2008/10/13/google-updates-webmaster-tools-with-sources-for-crawl-errors/&amp;t=Google+Updates+Webmaster+Tools+with+Sources+for+Crawl+Errors" rel="nofollow" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="sexy-sphinn">
			<a href="http://sphinn.com/index.php?c=post&amp;m=submit&amp;link=http://www.metamend.com/blog/2008/10/13/google-updates-webmaster-tools-with-sources-for-crawl-errors/" rel="nofollow" title="Sphinn this on Sphinn">Sphinn this on Sphinn</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>
<!-- End SexyBookmarks Menu Code -->

]]></content:encoded>
			<wfw:commentRss>http://www.metamend.com/blog/2008/10/13/google-updates-webmaster-tools-with-sources-for-crawl-errors/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>IE8 And Web Standards: New Meta Tag To Target Browser Versions</title>
		<link>http://www.metamend.com/blog/2008/01/22/ie8-and-web-standards-new-meta-tag-to-target-browser-versions/</link>
		<comments>http://www.metamend.com/blog/2008/01/22/ie8-and-web-standards-new-meta-tag-to-target-browser-versions/#comments</comments>
		<pubDate>Tue, 22 Jan 2008 22:24:48 +0000</pubDate>
		<dc:creator>Colin Cochrane</dc:creator>
				<category><![CDATA[SEOTech Talk]]></category>
		<category><![CDATA[css2 specification]]></category>
		<category><![CDATA[ie7]]></category>
		<category><![CDATA[IE8]]></category>
		<category><![CDATA[internet explorer]]></category>
		<category><![CDATA[interoperability]]></category>
		<category><![CDATA[w3c specification]]></category>
		<category><![CDATA[web standards]]></category>

		<guid isPermaLink="false">http://www.metamend.com/blog/2008/01/22/ie8-and-web-standards-new-meta-tag-to-target-browser-versions/</guid>
		<description><![CDATA[The IE8 team learned from the problems that arose from the last two releases of Internet Explorer, and working together with The Web Standards Project,  have come up with as solution that could provide that perfect  balance between backwards-compatibility and modern web standards.]]></description>
			<content:encoded><![CDATA[<p>&#8220;Don&#8217;t Break the Web&#8221; is a rule that the Internet Explorer development team has been applied to six major versions of IE over the past decade, with each of these versions seeing the application of this rule in a different way. It is a rule may appear ironic for some, given that IE has been the source of many problems for web developers since the wide-spread adoption of CSS, and with the more recent popularization of standards compliant web pages.  It is also a rule that represents the balance that the IE development team attempts to find between backwards-compatibility and interoperability (web standards), and a <a href="http://blogs.msdn.com/ie/archive/2008/01/21/compatibility-and-ie8.aspx">new post on the IE Blog</a> this morning shows that the IE8 development team may have found the way to achieve this balance.</p>
<h2>The Root Cause</h2>
<p>Well aware of the problems that IE6 and IE7 created for web developers, the IE8 development team took a hard look at the root causes of these problems.  Unsurprisingly the core group of issues began with IE6; more specifically with the introduction of the <a href="http://en.wikipedia.org/wiki/Quirks_mode">DOCTYPE switch</a>.  The DOCTYPE switch was a method used by IE to alter the box model that is used in calculating the dimension and relative position of elements in a web document, depending on whether the page declared a DOCTYPE.  If a web page declared a valid DOCTYPE it would be rendered in &#8220;standards mode&#8221; using the box model outlined in the <a href="http://www.w3.org/TR/CSS21/">CSS2 specification</a>, otherwise the page would use the rather creative interpretation of the CSS2 specification employed by IE5.5.  The intention of this behaviour was to avoid breaking the countless sites that were designed for IE5.5 (yes, it&#8217;s interpretation of CSS2 was <em>that</em> creative), while allowing developers to &#8220;opt-in&#8221; to the new standards mode.</p>
<h2>Non-Standard Standards</h2>
<p>The standards mode introduced in IE6 brought Internet Explorer&#8217;s implementation of  CSS2  closer to the actual W3C specification, but introduced a new class of CSS peculiarities, many of which were hard to identify and would often result in drastic inconsistencies in web pages when compared to other browsers such as Firefox, Opera and Safari.  This rose to a multitude of well-documented IE6 &#8220;CSS hacks&#8221; and the trend of creating a distinct IE6-only style-sheet which led to popular, somewhat tongue-in-cheek, belief that one had to design a web page twice: once for IE6 and once for everything else.  IE6 had tipped the balance in favour of backwards compatibility.</p>
<h2>Breaking Changes</h2>
<p>When IE7 came along the use of CSS had become the norm and the adoption of web standards was continuing to spread, so IE7 was developed with more standards-centric approach, resulting in the first version of Internet Explorer that was in reaching distance of true standards compliance.  However, this improved support came with a price, as many of the web pages that utilized the IE6-specific CSS workarounds were suddenly broken in this latest version of IE.  Now the balance was tipped towards interoperability, at the expense of backwards-compatibility.</p>
<h2>The Perfect Balance?</h2>
<p>With IE8 well into development, things are looking good for this next major version of Microsoft&#8217;s flagship browser.  With Internet Explorer 8 recently <a href="http://blogs.msdn.com/ie/archive/2007/12/19/internet-explorer-8-and-acid2-a-milestone.aspx">passing the Acid2 test</a>, the IE8 development team proved that they mean business when it comes to improving IE&#8217;s standard&#8217;s compliance.  They also learned from the problems that arose from the last two releases of Internet Explorer, and working together with <a href="http://webstandards.org/">The Web Standards Project</a>,  have come up with as solution that could provide that perfect  balance between backwards-compatibility and interoperability with web standards.</p>
<p>The solution comes in the form of an IE8 specific meta declaration that allows a web developer to specify what rendering engine IE8 should use for a given page.  This declaration will specify the exact version of Internet Explorer that the page is targeting, and IE8 will display the page using the rendering engine from that version.</p>
<div>
<div>
<pre>meta http-equiv="X-UA-Compatible" content="IE=8" /&gt;</pre>
</div>
<div>The immediate benefit of this to the average web developer, is that they don&#8217;t have to rework their site to be compatible with IE8&#8217;s new rendering engine.  If their page works perfectly in IE7, then they can simply declare:</div>
<pre>meta http-equiv="X-UA-Compatible" content="IE=7" /&gt;</pre>
<div>And their page will play nice with IE8, giving them the freedom to update it to standards compliance at their convenience (if they so desire).</div>
<p>If this meta declaration does end up working as alleged, then IE8 could be an important step to Internet Explorer getting back in the good graces of web developers and proponents of web standards.</p></div>


<!-- Begin SexyBookmarks Menu Code -->
<div class="sexy-bookmarks sexy-bookmarks-expand">
<ul class="socials">
		<li class="sexy-delicious">
			<a href="http://del.icio.us/post?url=http://www.metamend.com/blog/2008/01/22/ie8-and-web-standards-new-meta-tag-to-target-browser-versions/&amp;title=IE8+And+Web+Standards%3A+New+Meta+Tag+To+Target+Browser+Versions" rel="nofollow" title="Share this on del.icio.us">Share this on del.icio.us</a>
		</li>
		<li class="sexy-digg">
			<a href="http://digg.com/submit?phase=2&amp;url=http://www.metamend.com/blog/2008/01/22/ie8-and-web-standards-new-meta-tag-to-target-browser-versions/&amp;title=IE8+And+Web+Standards%3A+New+Meta+Tag+To+Target+Browser+Versions" rel="nofollow" title="Digg this!">Digg this!</a>
		</li>
		<li class="sexy-reddit">
			<a href="http://reddit.com/submit?url=http://www.metamend.com/blog/2008/01/22/ie8-and-web-standards-new-meta-tag-to-target-browser-versions/&amp;title=IE8+And+Web+Standards%3A+New+Meta+Tag+To+Target+Browser+Versions" rel="nofollow" title="Share this on Reddit">Share this on Reddit</a>
		</li>
		<li class="sexy-stumbleupon">
			<a href="http://www.stumbleupon.com/submit?url=http://www.metamend.com/blog/2008/01/22/ie8-and-web-standards-new-meta-tag-to-target-browser-versions/&amp;title=IE8+And+Web+Standards%3A+New+Meta+Tag+To+Target+Browser+Versions" rel="nofollow" title="Stumble upon something good? Share it on StumbleUpon">Stumble upon something good? Share it on StumbleUpon</a>
		</li>
		<li class="sexy-technorati">
			<a href="http://technorati.com/faves?add=http://www.metamend.com/blog/2008/01/22/ie8-and-web-standards-new-meta-tag-to-target-browser-versions/" rel="nofollow" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="sexy-twitter">
			<a href="http://twitter.com/home?status=IE8+And+Web+Standards%3A+New+Meta+Tag+To+Target+Browser+Versions+-+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="http://www.shareaholic.com/pages/maintenanceapi.php?alias=&amp;url=http://www.metamend.com/blog/2008/01/22/ie8-and-web-standards-new-meta-tag-to-target-browser-versions/">here</a>.</p>
</body></html>+" rel="nofollow" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="sexy-comfeed">
			<a href="http://www.metamend.com/blog/2008/01/22/ie8-and-web-standards-new-meta-tag-to-target-browser-versions/feed" rel="nofollow" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="sexy-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.metamend.com/blog/2008/01/22/ie8-and-web-standards-new-meta-tag-to-target-browser-versions/&amp;t=IE8+And+Web+Standards%3A+New+Meta+Tag+To+Target+Browser+Versions" rel="nofollow" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="sexy-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.metamend.com/blog/2008/01/22/ie8-and-web-standards-new-meta-tag-to-target-browser-versions/&amp;t=IE8+And+Web+Standards%3A+New+Meta+Tag+To+Target+Browser+Versions" rel="nofollow" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="sexy-sphinn">
			<a href="http://sphinn.com/index.php?c=post&amp;m=submit&amp;link=http://www.metamend.com/blog/2008/01/22/ie8-and-web-standards-new-meta-tag-to-target-browser-versions/" rel="nofollow" title="Sphinn this on Sphinn">Sphinn this on Sphinn</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>
<!-- End SexyBookmarks Menu Code -->

]]></content:encoded>
			<wfw:commentRss>http://www.metamend.com/blog/2008/01/22/ie8-and-web-standards-new-meta-tag-to-target-browser-versions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Live Search Webmaster Center, A Question Answered&#8230;</title>
		<link>http://www.metamend.com/blog/2007/12/18/live-search-webmaster-center-a-question-answered/</link>
		<comments>http://www.metamend.com/blog/2007/12/18/live-search-webmaster-center-a-question-answered/#comments</comments>
		<pubDate>Wed, 19 Dec 2007 01:08:05 +0000</pubDate>
		<dc:creator>Jade Carter</dc:creator>
				<category><![CDATA[SEOTech Talk]]></category>
		<category><![CDATA[keyword_search]]></category>
		<category><![CDATA[msn]]></category>
		<category><![CDATA[search referrals]]></category>
		<category><![CDATA[search traffic]]></category>
		<category><![CDATA[seo firm]]></category>
		<category><![CDATA[webmaster center]]></category>

		<guid isPermaLink="false">http://www.metamend.com/blog/2007/12/18/live-search-webmaster-center-a-question-answered/</guid>
		<description><![CDATA[Why is MSN hammering my site with bogus search referrals which are completely skewing my metrics tools and tracking systems?]]></description>
			<content:encoded><![CDATA[<p>So back in mid-November MSN launched their own Webmaster Center Blog. As with the Google Blog this should provide a peek into some of the inner workings of the their own team of Engineer/PR/Evangelicals as they parade new MSNbot nuances to the throngs of awaiting enthusiasts. After sniffing around the blogroll today I noticed that one particular items was just put to bed. Having threatened to post about this ages ago, my procrastinating ways have lead me to the end of the saga without having weighed in until now.</p>
<p>The &#8216;Question&#8217; related to the rash of bizarre search referrals that MSN was spreading around earlier this year.</p>
<p>The question was pretty much &#8216;where the heck is all of this search traffic coming from suddenly?&#8217;. Okay, suddenly meaning towards the end of August of this year, just like everyone else. So for an SEO Firm getting hits for the keyword &#8217;search&#8217;, this could appear pretty flattering. Did I do something magical to suddenly send the MSNLive Bot into heat? Did someone hijack a PPC campain and we&#8217;re going to get a nasty bill from the folks at MSN Adcenter? After playing with those ideas for three to four seconds, it became brutally obvious that this was just bogus bot traffic masking itself with a search referral, thus triggering an entry into our Search Metrics. If I didn&#8217;t know any better I could possibly call that cloaking&#8230; The plot thickens. After spending some time reflecting on our <a href="http://www.metamend.com/seo-tools/search-ranking-reports.html">Enquisite data</a> a few items still didn&#8217;t ad up.</p>
<ol>
<li>Enquisite was tagging this traffic as arriving from MSN Live. No one could recreate a human click from this engine using &#8217;search&#8217;.</li>
<li>It was always the same keyword.</li>
<li>The same keyword hit dozens of alternate URL&#8217;s. One would think that specific traffic, though not very focused, would generally arrive at a single related page. (same phrase, same search engine)</li>
</ol>
<p align="left">
<p align="left">
<p align="left">
<p align="left">
<p align="left">
<p align="left">
<p align="left">
<p align="left">
<p align="center">
<div style="text-align: center"><img width="349" height="209" alt="Term Search from MSN Live" title="Term Search from MSN Live" src="http://www.metamend.com/blog/images/msn-live-bogus-search.JPG" /></div>
<p align="left">
<p align="left">The geo tagging was returning an &#8216;unresolved&#8217; so I grabbed the raw logs and compared the referring strings. Here are the bits that matter.</p>
<ul>
<li>65.55.165.51 (Ip of the &#8217;searcher&#8217;)</li>
<li>http://search.live.com/results.aspx?q=search&#038;mrt=en-us&#038;FORM=LIVSOP (Appears to be the referring SERP)</li>
<li>http://www.metamend.com/what-is-cloaking.html  (Target of &#8217;search result&#8217; &#8211; Irony?)</li>
</ul>
<p>This is one of many examples. All were from the same Class A IP block. Have a look for yourself <a title="Check out who owns these IP's" href="http://ws.arin.net/whois/?queryinput=65.55.165.13">ARIN &#8211; 65.55.165.13</a>. So if you caught the Owner there everything would quickly ad up. So then the question becomes &#8220;Why is MSN hammering my site with bogus search referrals which are completely skewing my metrics tools and tracking systems. As you can see from the screen above, we are still receiving traffic at time of writing.</p>
<p>Once I found the SERP string I started searching for other victims online and came across several informative posts including this rather enjoyable Post with an <a title="Thoughtful Topic Title" href="http://www.exposureonline.com/2007/09/Microsoft-is-lying-and-screwing-up-your-log-files.cfm">equally thoughtful title</a>.</p>
<p>Early this month (I did mention how late I am getting to this right?) MSN posted on it&#8217;s brand new <a title="Msn Live Webmaster Center" href="http://blogs.msdn.com/webmaster/archive/2007/12/04/live-search-and-cloaking-detection.aspx">Live Search Webmaster Center Blog</a> about this whole topic. They&#8217;ve done a pretty lousy job of responding to this epidemic of bad traffic, but hopefully it will result in some warfare in the SE marketshare. Anyhow all paths on this topic, up until the MSN post, ended at <a title="care to read this again" href="http://www.webmasterworld.com/msn_microsoft_search/3424476.htm">this discussion</a> at Webmaster World. They&#8217;ve stated that these issues should be disappearing however we&#8217;re still seeing the traffic 2 weeks after their announcement so we&#8217;ll see how that goes.</p>
<p>Later.</p>
<p align="center">


<!-- Begin SexyBookmarks Menu Code -->
<div class="sexy-bookmarks sexy-bookmarks-expand">
<ul class="socials">
		<li class="sexy-delicious">
			<a href="http://del.icio.us/post?url=http://www.metamend.com/blog/2007/12/18/live-search-webmaster-center-a-question-answered/&amp;title=Live+Search+Webmaster+Center%2C+A+Question+Answered..." rel="nofollow" title="Share this on del.icio.us">Share this on del.icio.us</a>
		</li>
		<li class="sexy-digg">
			<a href="http://digg.com/submit?phase=2&amp;url=http://www.metamend.com/blog/2007/12/18/live-search-webmaster-center-a-question-answered/&amp;title=Live+Search+Webmaster+Center%2C+A+Question+Answered..." rel="nofollow" title="Digg this!">Digg this!</a>
		</li>
		<li class="sexy-reddit">
			<a href="http://reddit.com/submit?url=http://www.metamend.com/blog/2007/12/18/live-search-webmaster-center-a-question-answered/&amp;title=Live+Search+Webmaster+Center%2C+A+Question+Answered..." rel="nofollow" title="Share this on Reddit">Share this on Reddit</a>
		</li>
		<li class="sexy-stumbleupon">
			<a href="http://www.stumbleupon.com/submit?url=http://www.metamend.com/blog/2007/12/18/live-search-webmaster-center-a-question-answered/&amp;title=Live+Search+Webmaster+Center%2C+A+Question+Answered..." rel="nofollow" title="Stumble upon something good? Share it on StumbleUpon">Stumble upon something good? Share it on StumbleUpon</a>
		</li>
		<li class="sexy-technorati">
			<a href="http://technorati.com/faves?add=http://www.metamend.com/blog/2007/12/18/live-search-webmaster-center-a-question-answered/" rel="nofollow" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="sexy-twitter">
			<a href="http://twitter.com/home?status=Live+Search+Webmaster+Center%2C+A+Question+Answered...+-+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="http://www.shareaholic.com/pages/maintenanceapi.php?alias=&amp;url=http://www.metamend.com/blog/2007/12/18/live-search-webmaster-center-a-question-answered/">here</a>.</p>
</body></html>+" rel="nofollow" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="sexy-comfeed">
			<a href="http://www.metamend.com/blog/2007/12/18/live-search-webmaster-center-a-question-answered/feed" rel="nofollow" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="sexy-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.metamend.com/blog/2007/12/18/live-search-webmaster-center-a-question-answered/&amp;t=Live+Search+Webmaster+Center%2C+A+Question+Answered..." rel="nofollow" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="sexy-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.metamend.com/blog/2007/12/18/live-search-webmaster-center-a-question-answered/&amp;t=Live+Search+Webmaster+Center%2C+A+Question+Answered..." rel="nofollow" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="sexy-sphinn">
			<a href="http://sphinn.com/index.php?c=post&amp;m=submit&amp;link=http://www.metamend.com/blog/2007/12/18/live-search-webmaster-center-a-question-answered/" rel="nofollow" title="Sphinn this on Sphinn">Sphinn this on Sphinn</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>
<!-- End SexyBookmarks Menu Code -->

]]></content:encoded>
			<wfw:commentRss>http://www.metamend.com/blog/2007/12/18/live-search-webmaster-center-a-question-answered/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Google Webmaster Tools Verification Errors</title>
		<link>http://www.metamend.com/blog/2007/11/22/google-webmaster-tools-verification-errors/</link>
		<comments>http://www.metamend.com/blog/2007/11/22/google-webmaster-tools-verification-errors/#comments</comments>
		<pubDate>Thu, 22 Nov 2007 22:52:31 +0000</pubDate>
		<dc:creator>Alex Hlinski</dc:creator>
				<category><![CDATA[SEOTech Talk]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[webmaster tools]]></category>

		<guid isPermaLink="false">http://www.metamend.com/blog/2007/11/22/google-webmaster-tools-verification-errors/</guid>
		<description><![CDATA[Google Webmaster Tools is having some "verification" issues recently. Frequently visiting Webby Tools to check on your sites' search health also allows you to catch any problems of this nature.]]></description>
			<content:encoded><![CDATA[<p>Google Webmaster Tools seems to be having some problems today with its web site verification process. Many of the sites we have listed in Webmaster Tools are no longer &#8220;verified&#8221; and the problem is reported as being due to &#8220;server timeout&#8221; and &#8220;domain name&#8221; errors. This is in spite of being able to navigate to the verification file using the link provided in the &#8220;Verify a Site&#8221; section.</p>
<p><img title="Webmaster Tools Verify Errors" id="image490" alt="Webmaster Tools Verify Errors" src="http://www.metamend.com/blog/wp-content/uploads/2007/11/google-webtools-verify-errors.jpg" /></p>
<p>This outlines the importance of frequently logging into Webmaster Tools to keep up to date on your sites search health and not assuming that this useful tool is &#8220;set and forget&#8221;. Google seems to be having periodic website verification and Sitemaps errors of late, has anyone else has noticed this?</p>


<!-- Begin SexyBookmarks Menu Code -->
<div class="sexy-bookmarks sexy-bookmarks-expand">
<ul class="socials">
		<li class="sexy-delicious">
			<a href="http://del.icio.us/post?url=http://www.metamend.com/blog/2007/11/22/google-webmaster-tools-verification-errors/&amp;title=Google+Webmaster+Tools+Verification+Errors" rel="nofollow" title="Share this on del.icio.us">Share this on del.icio.us</a>
		</li>
		<li class="sexy-digg">
			<a href="http://digg.com/submit?phase=2&amp;url=http://www.metamend.com/blog/2007/11/22/google-webmaster-tools-verification-errors/&amp;title=Google+Webmaster+Tools+Verification+Errors" rel="nofollow" title="Digg this!">Digg this!</a>
		</li>
		<li class="sexy-reddit">
			<a href="http://reddit.com/submit?url=http://www.metamend.com/blog/2007/11/22/google-webmaster-tools-verification-errors/&amp;title=Google+Webmaster+Tools+Verification+Errors" rel="nofollow" title="Share this on Reddit">Share this on Reddit</a>
		</li>
		<li class="sexy-stumbleupon">
			<a href="http://www.stumbleupon.com/submit?url=http://www.metamend.com/blog/2007/11/22/google-webmaster-tools-verification-errors/&amp;title=Google+Webmaster+Tools+Verification+Errors" rel="nofollow" title="Stumble upon something good? Share it on StumbleUpon">Stumble upon something good? Share it on StumbleUpon</a>
		</li>
		<li class="sexy-technorati">
			<a href="http://technorati.com/faves?add=http://www.metamend.com/blog/2007/11/22/google-webmaster-tools-verification-errors/" rel="nofollow" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="sexy-twitter">
			<a href="http://twitter.com/home?status=Google+Webmaster+Tools+Verification+Errors+-+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="http://www.shareaholic.com/pages/maintenanceapi.php?alias=&amp;url=http://www.metamend.com/blog/2007/11/22/google-webmaster-tools-verification-errors/">here</a>.</p>
</body></html>+" rel="nofollow" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="sexy-comfeed">
			<a href="http://www.metamend.com/blog/2007/11/22/google-webmaster-tools-verification-errors/feed" rel="nofollow" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="sexy-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.metamend.com/blog/2007/11/22/google-webmaster-tools-verification-errors/&amp;t=Google+Webmaster+Tools+Verification+Errors" rel="nofollow" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="sexy-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.metamend.com/blog/2007/11/22/google-webmaster-tools-verification-errors/&amp;t=Google+Webmaster+Tools+Verification+Errors" rel="nofollow" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="sexy-sphinn">
			<a href="http://sphinn.com/index.php?c=post&amp;m=submit&amp;link=http://www.metamend.com/blog/2007/11/22/google-webmaster-tools-verification-errors/" rel="nofollow" title="Sphinn this on Sphinn">Sphinn this on Sphinn</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>
<!-- End SexyBookmarks Menu Code -->

]]></content:encoded>
			<wfw:commentRss>http://www.metamend.com/blog/2007/11/22/google-webmaster-tools-verification-errors/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Search Engine Traffic and Website Problems</title>
		<link>http://www.metamend.com/blog/2007/11/21/search-engine-traffic-and-website-problems/</link>
		<comments>http://www.metamend.com/blog/2007/11/21/search-engine-traffic-and-website-problems/#comments</comments>
		<pubDate>Wed, 21 Nov 2007 21:34:06 +0000</pubDate>
		<dc:creator>Alex Hlinski</dc:creator>
				<category><![CDATA[SEOTech Talk]]></category>
		<category><![CDATA[enquisite]]></category>
		<category><![CDATA[search engine referrals]]></category>
		<category><![CDATA[search engine spiders]]></category>
		<category><![CDATA[search traffic]]></category>
		<category><![CDATA[web traffic]]></category>

		<guid isPermaLink="false">http://www.metamend.com/blog/2007/11/21/search-engine-traffic-and-website-problems/</guid>
		<description><![CDATA[Temporary problems with your website can cause the search engines to temporarily punish your pages in the rankings that results in a significant loss of traffic.]]></description>
			<content:encoded><![CDATA[<p>One day last week a situation occurred with a client&#8217;s site that demonstrated how fast the search engines react to problems with a website. This story illustrates the importance of constant vigilance and monitoring of the health of a website.</p>
<p>The website concerned has around 4000+ article pages indexed, with each article page consisting of templated boilerplate sections and the main article text pulled from a HTML include file. Unfortunately on this particular day the directory containing the article include text files was accidentally deleted from the web server. Every article page subsequently served reported an ASP sever execute error as the article text include file directory was missing. The article include directory was only restored from a backup around 12 hours later.</p>
<p>Within several hours of the problem being reported it was obvious that the search engines had taken notice. According to the Enquisite search metrics data for the site, there was a definite and almost immediate reduction in search referrals. As it turned out, there was around 50% less search engine referrals that day compared to the preceding and following days. This demonstrated that the article pages had a temporary reduction in ranking, resulting in the loss of search traffic for that particular day. So what happened from a search engine point of view?</p>
<p>We can assume that if the search spiders visited that day they noticed that the article pages lacked content and provided no value. It is also possible that the search engines took into account the users&#8217; probable immediate and quick bounce from every article back to the search results page. Either of those explanations could result in the temporary loss of ranking witnessed for the article pages. What is certain is that the search engines reacted quickly to the problem by punishing each articles&#8217; ranking which resulted in a devastating loss of traffic.</p>


<!-- Begin SexyBookmarks Menu Code -->
<div class="sexy-bookmarks sexy-bookmarks-expand">
<ul class="socials">
		<li class="sexy-delicious">
			<a href="http://del.icio.us/post?url=http://www.metamend.com/blog/2007/11/21/search-engine-traffic-and-website-problems/&amp;title=Search+Engine+Traffic+and+Website+Problems" rel="nofollow" title="Share this on del.icio.us">Share this on del.icio.us</a>
		</li>
		<li class="sexy-digg">
			<a href="http://digg.com/submit?phase=2&amp;url=http://www.metamend.com/blog/2007/11/21/search-engine-traffic-and-website-problems/&amp;title=Search+Engine+Traffic+and+Website+Problems" rel="nofollow" title="Digg this!">Digg this!</a>
		</li>
		<li class="sexy-reddit">
			<a href="http://reddit.com/submit?url=http://www.metamend.com/blog/2007/11/21/search-engine-traffic-and-website-problems/&amp;title=Search+Engine+Traffic+and+Website+Problems" rel="nofollow" title="Share this on Reddit">Share this on Reddit</a>
		</li>
		<li class="sexy-stumbleupon">
			<a href="http://www.stumbleupon.com/submit?url=http://www.metamend.com/blog/2007/11/21/search-engine-traffic-and-website-problems/&amp;title=Search+Engine+Traffic+and+Website+Problems" rel="nofollow" title="Stumble upon something good? Share it on StumbleUpon">Stumble upon something good? Share it on StumbleUpon</a>
		</li>
		<li class="sexy-technorati">
			<a href="http://technorati.com/faves?add=http://www.metamend.com/blog/2007/11/21/search-engine-traffic-and-website-problems/" rel="nofollow" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="sexy-twitter">
			<a href="http://twitter.com/home?status=Search+Engine+Traffic+and+Website+Problems+-+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="http://www.shareaholic.com/pages/maintenanceapi.php?alias=&amp;url=http://www.metamend.com/blog/2007/11/21/search-engine-traffic-and-website-problems/">here</a>.</p>
</body></html>+" rel="nofollow" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="sexy-comfeed">
			<a href="http://www.metamend.com/blog/2007/11/21/search-engine-traffic-and-website-problems/feed" rel="nofollow" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="sexy-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.metamend.com/blog/2007/11/21/search-engine-traffic-and-website-problems/&amp;t=Search+Engine+Traffic+and+Website+Problems" rel="nofollow" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="sexy-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.metamend.com/blog/2007/11/21/search-engine-traffic-and-website-problems/&amp;t=Search+Engine+Traffic+and+Website+Problems" rel="nofollow" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="sexy-sphinn">
			<a href="http://sphinn.com/index.php?c=post&amp;m=submit&amp;link=http://www.metamend.com/blog/2007/11/21/search-engine-traffic-and-website-problems/" rel="nofollow" title="Sphinn this on Sphinn">Sphinn this on Sphinn</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>
<!-- End SexyBookmarks Menu Code -->

]]></content:encoded>
			<wfw:commentRss>http://www.metamend.com/blog/2007/11/21/search-engine-traffic-and-website-problems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MSN Webmaster Tools Portal Closed Beta Has Landed</title>
		<link>http://www.metamend.com/blog/2007/11/14/msn-webmaster-tools-portal-closed-beta-has-landed/</link>
		<comments>http://www.metamend.com/blog/2007/11/14/msn-webmaster-tools-portal-closed-beta-has-landed/#comments</comments>
		<pubDate>Wed, 14 Nov 2007 20:36:49 +0000</pubDate>
		<dc:creator>Jade Carter</dc:creator>
				<category><![CDATA[SEOTech Talk]]></category>
		<category><![CDATA[msn search]]></category>
		<category><![CDATA[searchers]]></category>
		<category><![CDATA[sitemap submission]]></category>
		<category><![CDATA[webmaster tools]]></category>

		<guid isPermaLink="false">http://www.metamend.com/blog/2007/11/14/msn-webmaster-tools-portal-closed-beta-has-landed/</guid>
		<description><![CDATA[The Metamend team have just joined the private beta group at the new MSN Live webmaster tools portal. C'mon MSN, let's see what you've got!]]></description>
			<content:encoded><![CDATA[<p>The Metamend team have just joined the private beta group at the new MSN Live webmaster tools portal. We&#8217;re eager to see what MSN will toss our way that will differ in any way from what Google and Yahoo have let us play with up &#8217;til now. In the <a title="MSN Announces Webmaster Portal" href="http://blogs.msdn.com/livesearch/archive/2007/08/22/our-new-webmaster-portal-and-an-invitation-to-the-private-beta.aspx">original portal announcement</a> back in August on the LiveSearch blog, a specific feature stood out a bit from the rest. &#8220;Sitemap Creation, Submission and Ping Tools&#8221;. Okay, sitemap submission and ping tools are to be expected, but Sitemap creation? Google passes that one off to the webmasters so that would be a welcome change. Lets see if they deliver.</p>
<p>Live Search obviously has a mountain to climb. Their index has been the brunt of criticism for far a good long time now. So much so that was witness a presenter as SES San Jose in &#8216;06 refer to their search index irrelevant and &#8216;who cares&#8217; -ouch. Still, top positioning doesn&#8217;t mean that you&#8217;ll generate a ton of leads as there just aren&#8217;t enough MSN searchers at the moment. Even though IE ships with Live as the &#8216;default search privider&#8217; it&#8217;s clear that it&#8217;s time for MSN Search to put up or&#8230; well. buy Yahoo! (<a target="_blank" title="MSN to Buy Yahoo?" href="http://money.cnn.com/2007/05/04/technology/msftyhoo_analysis/index.htm">I love that rumour</a>) Hopefully this new buzz will encourage a few of us to wander back to the MSN for a while in hopes that a meaningful algorithm update is also in the works.</p>


<!-- Begin SexyBookmarks Menu Code -->
<div class="sexy-bookmarks sexy-bookmarks-expand">
<ul class="socials">
		<li class="sexy-delicious">
			<a href="http://del.icio.us/post?url=http://www.metamend.com/blog/2007/11/14/msn-webmaster-tools-portal-closed-beta-has-landed/&amp;title=MSN+Webmaster+Tools+Portal+Closed+Beta+Has+Landed" rel="nofollow" title="Share this on del.icio.us">Share this on del.icio.us</a>
		</li>
		<li class="sexy-digg">
			<a href="http://digg.com/submit?phase=2&amp;url=http://www.metamend.com/blog/2007/11/14/msn-webmaster-tools-portal-closed-beta-has-landed/&amp;title=MSN+Webmaster+Tools+Portal+Closed+Beta+Has+Landed" rel="nofollow" title="Digg this!">Digg this!</a>
		</li>
		<li class="sexy-reddit">
			<a href="http://reddit.com/submit?url=http://www.metamend.com/blog/2007/11/14/msn-webmaster-tools-portal-closed-beta-has-landed/&amp;title=MSN+Webmaster+Tools+Portal+Closed+Beta+Has+Landed" rel="nofollow" title="Share this on Reddit">Share this on Reddit</a>
		</li>
		<li class="sexy-stumbleupon">
			<a href="http://www.stumbleupon.com/submit?url=http://www.metamend.com/blog/2007/11/14/msn-webmaster-tools-portal-closed-beta-has-landed/&amp;title=MSN+Webmaster+Tools+Portal+Closed+Beta+Has+Landed" rel="nofollow" title="Stumble upon something good? Share it on StumbleUpon">Stumble upon something good? Share it on StumbleUpon</a>
		</li>
		<li class="sexy-technorati">
			<a href="http://technorati.com/faves?add=http://www.metamend.com/blog/2007/11/14/msn-webmaster-tools-portal-closed-beta-has-landed/" rel="nofollow" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="sexy-twitter">
			<a href="http://twitter.com/home?status=MSN+Webmaster+Tools+Portal+Closed+Beta+Has+Landed+-+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="http://www.shareaholic.com/pages/maintenanceapi.php?alias=&amp;url=http://www.metamend.com/blog/2007/11/14/msn-webmaster-tools-portal-closed-beta-has-landed/">here</a>.</p>
</body></html>+" rel="nofollow" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="sexy-comfeed">
			<a href="http://www.metamend.com/blog/2007/11/14/msn-webmaster-tools-portal-closed-beta-has-landed/feed" rel="nofollow" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="sexy-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.metamend.com/blog/2007/11/14/msn-webmaster-tools-portal-closed-beta-has-landed/&amp;t=MSN+Webmaster+Tools+Portal+Closed+Beta+Has+Landed" rel="nofollow" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="sexy-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.metamend.com/blog/2007/11/14/msn-webmaster-tools-portal-closed-beta-has-landed/&amp;t=MSN+Webmaster+Tools+Portal+Closed+Beta+Has+Landed" rel="nofollow" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="sexy-sphinn">
			<a href="http://sphinn.com/index.php?c=post&amp;m=submit&amp;link=http://www.metamend.com/blog/2007/11/14/msn-webmaster-tools-portal-closed-beta-has-landed/" rel="nofollow" title="Sphinn this on Sphinn">Sphinn this on Sphinn</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>
<!-- End SexyBookmarks Menu Code -->

]]></content:encoded>
			<wfw:commentRss>http://www.metamend.com/blog/2007/11/14/msn-webmaster-tools-portal-closed-beta-has-landed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Web 2.0 and the Search Engine Spiders</title>
		<link>http://www.metamend.com/blog/2007/11/08/web-20-and-the-search-engine-spiders/</link>
		<comments>http://www.metamend.com/blog/2007/11/08/web-20-and-the-search-engine-spiders/#comments</comments>
		<pubDate>Fri, 09 Nov 2007 01:09:51 +0000</pubDate>
		<dc:creator>Alex Hlinski</dc:creator>
				<category><![CDATA[SEOTech Talk]]></category>
		<category><![CDATA[accessibility]]></category>
		<category><![CDATA[ajax]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[linking]]></category>
		<category><![CDATA[metamend tools]]></category>
		<category><![CDATA[search engine spider]]></category>
		<category><![CDATA[search engines]]></category>
		<category><![CDATA[seo]]></category>
		<category><![CDATA[visually impaired]]></category>

		<guid isPermaLink="false">http://www.metamend.com/blog/2007/11/08/web-20-and-the-search-engine-spiders/</guid>
		<description><![CDATA[Google suggests testing your Ajax pages for search engine spider friendliness by turning off JavaScript or by using the Lynx text only browser. But is there a better tool out there? Step up, the Search Engine Spider Simulator.]]></description>
			<content:encoded><![CDATA[<p>With the explosion of &#8220;Web 2.0&#8243; websites,  Google&#8217;s search quality team gave some timely insights as to how search engine spiders will have trouble dealing with <a title="A spider's view of Web 2.0" href="http://googlewebmastercentral.blogspot.com/2007/11/spiders-view-of-web-20.html">page content presented using Ajax</a>. Just like Flash and JavaScript, the spiders are unable to crawl any links and see any content displayed using Ajax. As always there is a straightforward solution to this problem.</p>
<p>As long as you provide a HTML alternative of the same content for the spiders, and non-JavaScript enabled browsers, then the search engines will not have a problem with your Ajax pages. This will also allow you to reach an audience who have accessibility  issues, such as the visually impaired or those using mobile devices.</p>
<p>As part of our initial examination of a client site our SEOs turn off JavaScript whilst browsing or use the Lynx text only browser to determine if all of the content and links can be seen by the spiders. Although I find Lynx to be quite useful for browser accessibility issues, it does not give a true representation of how a search engine spider will see a web page.  By not displaying linked images that have a blank or missing alt attribute, Lynx can give the mistaken impression that some links are not spiderable. To get the most realistic impression, there are many <a title="Search Engine Spider Simulator" href="http://www.metamend.com/seo-tools/search-engine-spider-simulator.html">&#8220;Search Engine Spider Simulators&#8221;</a> that will show the text content and links that are visible to a spider after all of the HTML and JavaScript is removed from the page source code.</p>
<p>Although Ajax facilitates powerfully interactive web sites, the same old problems occur for the search engines as with Flash or JavaScript presented content. &#8220;Web 2.0&#8243; may be the latest buzz word in web site design, but having already dealt with Flash and JavaScript for some time, SEOs know what is required.</p>


<!-- Begin SexyBookmarks Menu Code -->
<div class="sexy-bookmarks sexy-bookmarks-expand">
<ul class="socials">
		<li class="sexy-delicious">
			<a href="http://del.icio.us/post?url=http://www.metamend.com/blog/2007/11/08/web-20-and-the-search-engine-spiders/&amp;title=Web+2.0+and+the+Search+Engine+Spiders" rel="nofollow" title="Share this on del.icio.us">Share this on del.icio.us</a>
		</li>
		<li class="sexy-digg">
			<a href="http://digg.com/submit?phase=2&amp;url=http://www.metamend.com/blog/2007/11/08/web-20-and-the-search-engine-spiders/&amp;title=Web+2.0+and+the+Search+Engine+Spiders" rel="nofollow" title="Digg this!">Digg this!</a>
		</li>
		<li class="sexy-reddit">
			<a href="http://reddit.com/submit?url=http://www.metamend.com/blog/2007/11/08/web-20-and-the-search-engine-spiders/&amp;title=Web+2.0+and+the+Search+Engine+Spiders" rel="nofollow" title="Share this on Reddit">Share this on Reddit</a>
		</li>
		<li class="sexy-stumbleupon">
			<a href="http://www.stumbleupon.com/submit?url=http://www.metamend.com/blog/2007/11/08/web-20-and-the-search-engine-spiders/&amp;title=Web+2.0+and+the+Search+Engine+Spiders" rel="nofollow" title="Stumble upon something good? Share it on StumbleUpon">Stumble upon something good? Share it on StumbleUpon</a>
		</li>
		<li class="sexy-technorati">
			<a href="http://technorati.com/faves?add=http://www.metamend.com/blog/2007/11/08/web-20-and-the-search-engine-spiders/" rel="nofollow" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="sexy-twitter">
			<a href="http://twitter.com/home?status=Web+2.0+and+the+Search+Engine+Spiders+-+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="http://www.shareaholic.com/pages/maintenanceapi.php?alias=&amp;url=http://www.metamend.com/blog/2007/11/08/web-20-and-the-search-engine-spiders/">here</a>.</p>
</body></html>+" rel="nofollow" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="sexy-comfeed">
			<a href="http://www.metamend.com/blog/2007/11/08/web-20-and-the-search-engine-spiders/feed" rel="nofollow" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="sexy-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.metamend.com/blog/2007/11/08/web-20-and-the-search-engine-spiders/&amp;t=Web+2.0+and+the+Search+Engine+Spiders" rel="nofollow" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="sexy-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.metamend.com/blog/2007/11/08/web-20-and-the-search-engine-spiders/&amp;t=Web+2.0+and+the+Search+Engine+Spiders" rel="nofollow" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="sexy-sphinn">
			<a href="http://sphinn.com/index.php?c=post&amp;m=submit&amp;link=http://www.metamend.com/blog/2007/11/08/web-20-and-the-search-engine-spiders/" rel="nofollow" title="Sphinn this on Sphinn">Sphinn this on Sphinn</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>
<!-- End SexyBookmarks Menu Code -->

]]></content:encoded>
			<wfw:commentRss>http://www.metamend.com/blog/2007/11/08/web-20-and-the-search-engine-spiders/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Google Webmaster Tools Sitemap Cross Submissions and Geographic Control</title>
		<link>http://www.metamend.com/blog/2007/11/01/google-webmaster-tools-sitemap-cross-submissions-and-geographic-control/</link>
		<comments>http://www.metamend.com/blog/2007/11/01/google-webmaster-tools-sitemap-cross-submissions-and-geographic-control/#comments</comments>
		<pubDate>Fri, 02 Nov 2007 00:14:25 +0000</pubDate>
		<dc:creator>Alex Hlinski</dc:creator>
				<category><![CDATA[SEOTech Talk]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[google webmaster tools]]></category>
		<category><![CDATA[sitemap submission]]></category>
		<category><![CDATA[sitemaps]]></category>

		<guid isPermaLink="false">http://www.metamend.com/blog/2007/11/01/google-webmaster-tools-sitemap-cross-submissions-and-geographic-control/</guid>
		<description><![CDATA[Google's Webmaster Tools has some new features this week, Sitemap cross submission support and improved geographical control over your content.]]></description>
			<content:encoded><![CDATA[<p>It seems that the &#8220;meet the engineers&#8221; session at the Google Dance during last August&#8217;s SES San Jose  has provided many useful ideas for the improvement of Webmaster Tools. New features are coming thick and fast to Google&#8217;s webmaster tools with two new additions within the last week, cross site submissions and better geographic control. First we&#8217;ll look at cross site submissions.</p>
<p>Do you have a multitude of sites that you administer through Google Webmaster tools? We all know it can sometimes be difficult to keep all the sitemap.xml files up-to-date and uploaded to all those seperate web-server FTP accounts, especially if you do not have any sort of automated system to do it for you.</p>
<p>In the past you could only store a Sitemap on its respective host, but this restriction has now been lifted. As long as you can &#8216;prove&#8217; you control the host, by the verification process in Webmaster tools, you can store the Sitemap on any other host that you control. This means that you could store all the individual Sitemaps on your own server or even have URLs for multiple websites contained within one Sitemap file.<br />
There is one caveat however, in that this will only work for Google at the moment, although they do assure us that they are talking to the other search engines that support the Sitemap Protocol.<br />
I would imagine that the simplest implementation would take the form of a change to the Sitemap declaration within the robots.txt file. As the site &#8216;owner&#8217; would legitimately have access to the robots.txt anyway, this would neatly resolve the security issue that Google was concerned about. Check out the original Google <a title="Sitemap Cross Submissions" href="http://googlewebmastercentral.blogspot.com/2007/10/dealing-with-sitemap-cross-submissions.html">Sitemap Cross Submissions</a> post.</p>
<p>You can now control the country association of your content on a per-domain, per-sub-domain or a per-directory level. It&#8217;s as simple as adding a new website entry to your dashboard for the domain, sub-domain or directory that contains the international content, then using the &#8220;set geographic target&#8221; interface from the &#8220;tools&#8221; menu to specify the country.</p>
<p>Although this will work well for sites that determine their international pages using a separate domain or directory structure, it will not help dynamic sites that use a URL parameter for this purpose. Perhaps this is a future addition that we can look forward to. For more information read the <a title="Better Geographic Choices for Webmasters" href="http://googlewebmastercentral.blogspot.com/2007/10/better-geographic-choices-for.html">Country Associations for your Content</a> post from the Google Blog.</p>


<!-- Begin SexyBookmarks Menu Code -->
<div class="sexy-bookmarks sexy-bookmarks-expand">
<ul class="socials">
		<li class="sexy-delicious">
			<a href="http://del.icio.us/post?url=http://www.metamend.com/blog/2007/11/01/google-webmaster-tools-sitemap-cross-submissions-and-geographic-control/&amp;title=Google+Webmaster+Tools+Sitemap+Cross+Submissions+and+Geographic+Control" rel="nofollow" title="Share this on del.icio.us">Share this on del.icio.us</a>
		</li>
		<li class="sexy-digg">
			<a href="http://digg.com/submit?phase=2&amp;url=http://www.metamend.com/blog/2007/11/01/google-webmaster-tools-sitemap-cross-submissions-and-geographic-control/&amp;title=Google+Webmaster+Tools+Sitemap+Cross+Submissions+and+Geographic+Control" rel="nofollow" title="Digg this!">Digg this!</a>
		</li>
		<li class="sexy-reddit">
			<a href="http://reddit.com/submit?url=http://www.metamend.com/blog/2007/11/01/google-webmaster-tools-sitemap-cross-submissions-and-geographic-control/&amp;title=Google+Webmaster+Tools+Sitemap+Cross+Submissions+and+Geographic+Control" rel="nofollow" title="Share this on Reddit">Share this on Reddit</a>
		</li>
		<li class="sexy-stumbleupon">
			<a href="http://www.stumbleupon.com/submit?url=http://www.metamend.com/blog/2007/11/01/google-webmaster-tools-sitemap-cross-submissions-and-geographic-control/&amp;title=Google+Webmaster+Tools+Sitemap+Cross+Submissions+and+Geographic+Control" rel="nofollow" title="Stumble upon something good? Share it on StumbleUpon">Stumble upon something good? Share it on StumbleUpon</a>
		</li>
		<li class="sexy-technorati">
			<a href="http://technorati.com/faves?add=http://www.metamend.com/blog/2007/11/01/google-webmaster-tools-sitemap-cross-submissions-and-geographic-control/" rel="nofollow" title="Share this on Technorati">Share this on Technorati</a>
		</li>
		<li class="sexy-twitter">
			<a href="http://twitter.com/home?status=Google+Webmaster+Tools+Sitemap+Cross+Submissions+and+Geographic+Control+-+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="http://www.shareaholic.com/pages/maintenanceapi.php?alias=&amp;url=http://www.metamend.com/blog/2007/11/01/google-webmaster-tools-sitemap-cross-submissions-and-geographic-control/">here</a>.</p>
</body></html>+" rel="nofollow" title="Tweet This!">Tweet This!</a>
		</li>
		<li class="sexy-comfeed">
			<a href="http://www.metamend.com/blog/2007/11/01/google-webmaster-tools-sitemap-cross-submissions-and-geographic-control/feed" rel="nofollow" title="Subscribe to the comments for this post?">Subscribe to the comments for this post?</a>
		</li>
		<li class="sexy-facebook">
			<a href="http://www.facebook.com/share.php?v=4&amp;src=bm&amp;u=http://www.metamend.com/blog/2007/11/01/google-webmaster-tools-sitemap-cross-submissions-and-geographic-control/&amp;t=Google+Webmaster+Tools+Sitemap+Cross+Submissions+and+Geographic+Control" rel="nofollow" title="Share this on Facebook">Share this on Facebook</a>
		</li>
		<li class="sexy-myspace">
			<a href="http://www.myspace.com/Modules/PostTo/Pages/?u=http://www.metamend.com/blog/2007/11/01/google-webmaster-tools-sitemap-cross-submissions-and-geographic-control/&amp;t=Google+Webmaster+Tools+Sitemap+Cross+Submissions+and+Geographic+Control" rel="nofollow" title="Post this to MySpace">Post this to MySpace</a>
		</li>
		<li class="sexy-sphinn">
			<a href="http://sphinn.com/index.php?c=post&amp;m=submit&amp;link=http://www.metamend.com/blog/2007/11/01/google-webmaster-tools-sitemap-cross-submissions-and-geographic-control/" rel="nofollow" title="Sphinn this on Sphinn">Sphinn this on Sphinn</a>
		</li>
</ul>
<div style="clear:both;"></div>
</div>
<!-- End SexyBookmarks Menu Code -->

]]></content:encoded>
			<wfw:commentRss>http://www.metamend.com/blog/2007/11/01/google-webmaster-tools-sitemap-cross-submissions-and-geographic-control/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
