<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Google Site Verification</title>
	<atom:link href="http://www.canonicalseo.com/google-web-site-verification/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.canonicalseo.com/google-web-site-verification/</link>
	<description>Learn SEO Free Online</description>
	<lastBuildDate>Tue, 31 Aug 2010 03:03:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Canonical SEO</title>
		<link>http://www.canonicalseo.com/google-web-site-verification/comment-page-1/#comment-438</link>
		<dc:creator>Canonical SEO</dc:creator>
		<pubDate>Fri, 27 Aug 2010 19:21:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.canonicalseo.com/?p=208#comment-438</guid>
		<description>Because Google sees the www and non-www version of your site as different sites.  You have &lt;a href=&quot;http://www.canonicalseo.com/url-canonicalization/&quot; rel=&quot;nofollow&quot;&gt;URL canonicalization&lt;/a&gt; issues because your website is rendering every page on the site both with and without the www.  One external site could be linking to a URL on your site that no longer exists using the non-www version.  Another external site could be linking to a different (or same) URL on your site that no longer exists using the www version.  So the 404 errors will show up under their respective verified sites.

You should decide whether the www or non-www version is you canonical (preferred) version of your site&#039;s URLs and &lt;a href=&quot;http://www.canonicalseo.com/redirecting-web-pages/&quot; rel=&quot;nofollow&quot;&gt;301 redirect&lt;/a&gt; the non-canonical version of all URLs to their corresponding canonical version of the URL.  If your site is hosted on an Apache web server, this is as simple as adding a single RewriteRule in the .htaccess located in the root folder of your web.

For example, if you want the non-www version of your URLs to be the canonical form of your URLs then the following would do the trick:

&lt;blockquote&gt;RewriteCond %{HTTP_HOST} ^www.example.com$ [NC]
RewriteRule (.*) http://example.com/$1 [R=301,L]&lt;/blockquote&gt;

If you want the www version of your URLs to be the canonical form of your URLs then the following should work:

&lt;blockquote&gt;RewriteCond %{HTTP_HOST} ^example.com$ [NC]
RewriteRule (.*) http://www.example.com/$1 [R=301,L]&lt;/blockquote&gt;

The above will fix your URL canonicalization issues for ALL search engines. 

Also, you can fix it just for Google quite easily.  Once you&#039;ve verified both the www and non-www versions of your site, once logged into Webmaster Tools, go to Site Configuration -&gt; Settings and select your Preferred Domain.  

Fixing URL canonicalization issues using 301 redirects is the preferred way because it corrects the problems across all engines, but if you don&#039;t have the tools or skills to implement the 301 redirects then fixing it with Webmaster Tools is the next best thing.</description>
		<content:encoded><![CDATA[<p>Because Google sees the www and non-www version of your site as different sites.  You have <a href="http://www.canonicalseo.com/url-canonicalization/" rel="nofollow">URL canonicalization</a> issues because your website is rendering every page on the site both with and without the www.  One external site could be linking to a URL on your site that no longer exists using the non-www version.  Another external site could be linking to a different (or same) URL on your site that no longer exists using the www version.  So the 404 errors will show up under their respective verified sites.</p>
<p>You should decide whether the www or non-www version is you canonical (preferred) version of your site&#8217;s URLs and <a href="http://www.canonicalseo.com/redirecting-web-pages/" rel="nofollow">301 redirect</a> the non-canonical version of all URLs to their corresponding canonical version of the URL.  If your site is hosted on an Apache web server, this is as simple as adding a single RewriteRule in the .htaccess located in the root folder of your web.</p>
<p>For example, if you want the non-www version of your URLs to be the canonical form of your URLs then the following would do the trick:</p>
<blockquote><p>RewriteCond %{HTTP_HOST} ^www.example.com$ [NC]<br />
RewriteRule (.*) <a href="http://example.com/$1" rel="nofollow">http://example.com/$1</a> [R=301,L]</p></blockquote>
<p>If you want the www version of your URLs to be the canonical form of your URLs then the following should work:</p>
<blockquote><p>RewriteCond %{HTTP_HOST} ^example.com$ [NC]<br />
RewriteRule (.*) <a href="http://www.example.com/$1" rel="nofollow">http://www.example.com/$1</a> [R=301,L]</p></blockquote>
<p>The above will fix your URL canonicalization issues for ALL search engines. </p>
<p>Also, you can fix it just for Google quite easily.  Once you&#8217;ve verified both the www and non-www versions of your site, once logged into Webmaster Tools, go to Site Configuration -&gt; Settings and select your Preferred Domain.  </p>
<p>Fixing URL canonicalization issues using 301 redirects is the preferred way because it corrects the problems across all engines, but if you don&#8217;t have the tools or skills to implement the 301 redirects then fixing it with Webmaster Tools is the next best thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sharon</title>
		<link>http://www.canonicalseo.com/google-web-site-verification/comment-page-1/#comment-437</link>
		<dc:creator>Sharon</dc:creator>
		<pubDate>Fri, 27 Aug 2010 17:26:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.canonicalseo.com/?p=208#comment-437</guid>
		<description>I just ran site verification on the www and non-www version of airdryers.com and they both had different crawling errors.  How could that be?

Sharon</description>
		<content:encoded><![CDATA[<p>I just ran site verification on the www and non-www version of airdryers.com and they both had different crawling errors.  How could that be?</p>
<p>Sharon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Canonical SEO</title>
		<link>http://www.canonicalseo.com/google-web-site-verification/comment-page-1/#comment-302</link>
		<dc:creator>Canonical SEO</dc:creator>
		<pubDate>Sun, 11 Apr 2010 15:42:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.canonicalseo.com/?p=208#comment-302</guid>
		<description>I&#039;m not sure I really understand the question.  Validation and verification are two totally different things.  When people speak of validation they are typically talking about comparing the (X)HTML and CSS used on their site against the W3C standards to see what types of rules they might have broken.  This post was specifically about Google Webmaster Tools site verification... proving to Google that you are, indeed, an authorized webmaster for a given site.

Most people typically verify two versions of their site - the www and non-www version.  Once you get one verified (using the meta tag or HTML file method) all you have to do is ADD the other site in WMT and press the verify button. In 99.999% of the cases it will verify immediately unless you&#039;re doing something &quot;funky&quot; in code so that you&#039;re not rendering the same home page for both (meta tags are different) or somehow the DNS for the www and non-www resolve to different folders on your web server.   If you want to set the preferred domain (www or non-www) in WMT then you have to verify both the www and non-www version of the domain.  So page name, font, case, etc. really have no bearing on verification because people typically verify their domains.

One little known fact, however, that most people don&#039;t know... you CAN verify a file on your site.  Say I&#039;ve verified www.example.com and example.com and I&#039;ve set my preferred domain to www.example.com... I can also add www.example.com/some-folder/ and verify it.  This will automatically verify as well (assuming you&#039;ve already verified www.example.com).  This will allow you to get information specifically about the www.example.com/some-folder/ section of the site (that page and all pages that live under it like www.example.com/some-folder/some-sub-folder/page-name.html).  You&#039;ll notice when you do this a lot of the info in WMT for that &quot;section&quot; of the site are blank because they are real &quot;site&quot; level information... but a lot of the info is there and adjusted so that it is only about that &quot;section&quot; of the site.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure I really understand the question.  Validation and verification are two totally different things.  When people speak of validation they are typically talking about comparing the (X)HTML and CSS used on their site against the W3C standards to see what types of rules they might have broken.  This post was specifically about Google Webmaster Tools site verification&#8230; proving to Google that you are, indeed, an authorized webmaster for a given site.</p>
<p>Most people typically verify two versions of their site &#8211; the www and non-www version.  Once you get one verified (using the meta tag or HTML file method) all you have to do is ADD the other site in WMT and press the verify button. In 99.999% of the cases it will verify immediately unless you&#8217;re doing something &#8220;funky&#8221; in code so that you&#8217;re not rendering the same home page for both (meta tags are different) or somehow the DNS for the www and non-www resolve to different folders on your web server.   If you want to set the preferred domain (www or non-www) in WMT then you have to verify both the www and non-www version of the domain.  So page name, font, case, etc. really have no bearing on verification because people typically verify their domains.</p>
<p>One little known fact, however, that most people don&#8217;t know&#8230; you CAN verify a file on your site.  Say I&#8217;ve verified <a href="http://www.example.com" rel="nofollow">http://www.example.com</a> and example.com and I&#8217;ve set my preferred domain to <a href="http://www.example.com.." rel="nofollow">http://www.example.com..</a>. I can also add <a href="http://www.example.com/some-folder/" rel="nofollow">http://www.example.com/some-folder/</a> and verify it.  This will automatically verify as well (assuming you&#8217;ve already verified <a href="http://www.example.com" rel="nofollow">http://www.example.com</a>).  This will allow you to get information specifically about the <a href="http://www.example.com/some-folder/" rel="nofollow">http://www.example.com/some-folder/</a> section of the site (that page and all pages that live under it like <a href="http://www.example.com/some-folder/some-sub-folder/page-name.html" rel="nofollow">http://www.example.com/some-folder/some-sub-folder/page-name.html</a>).  You&#8217;ll notice when you do this a lot of the info in WMT for that &#8220;section&#8221; of the site are blank because they are real &#8220;site&#8221; level information&#8230; but a lot of the info is there and adjusted so that it is only about that &#8220;section&#8221; of the site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roland King</title>
		<link>http://www.canonicalseo.com/google-web-site-verification/comment-page-1/#comment-301</link>
		<dc:creator>Roland King</dc:creator>
		<pubDate>Sun, 11 Apr 2010 13:32:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.canonicalseo.com/?p=208#comment-301</guid>
		<description>Does the size of the font, small case or uppercase have an effect on validation. If my page name starts with a capital do I have to do the same in the verification? I have not done this reading that it doesn&#039;t matter but since my other pages have not been verified yet i am now wondering.</description>
		<content:encoded><![CDATA[<p>Does the size of the font, small case or uppercase have an effect on validation. If my page name starts with a capital do I have to do the same in the verification? I have not done this reading that it doesn&#8217;t matter but since my other pages have not been verified yet i am now wondering.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
