<?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 removes &#8216;Not Selected&#8217; from Index Status</title> <atom:link href="http://dejanseo.com.au/google-removes-not-selected-from-index-status/feed/" rel="self" type="application/rss+xml" /><link>http://dejanseo.com.au/google-removes-not-selected-from-index-status/</link> <description></description> <lastBuildDate>Sun, 26 May 2013 08:26:00 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: Michael Kohlfürst</title><link>http://dejanseo.com.au/google-removes-not-selected-from-index-status/#comment-1341</link> <dc:creator>Michael Kohlfürst</dc:creator> <pubDate>Fri, 08 Feb 2013 15:20:00 +0000</pubDate> <guid isPermaLink="false">http://dejanseo.com.au/?p=10736#comment-1341</guid> <description>BUT, Not Selected was such a good feature, when I started my work with a new customer. Not happy with that.</description> <content:encoded><![CDATA[<p>BUT, Not Selected was such a good feature, when I started my work with a new customer. Not happy with that.</p> ]]></content:encoded> </item> <item><title>By: Peter Mead</title><link>http://dejanseo.com.au/google-removes-not-selected-from-index-status/#comment-1339</link> <dc:creator>Peter Mead</dc:creator> <pubDate>Fri, 08 Feb 2013 08:23:00 +0000</pubDate> <guid isPermaLink="false">http://dejanseo.com.au/?p=10736#comment-1339</guid> <description>Thanks for the heads up Dan. I agree, prefer it was still there. My background being involved in software design, I am not a fan of things changing too often. Particularly careful of feature removal, no matter how small, is always a negative thing for users. Unless the feature is clearly giving wrong or misleading information.Great info, I would have missed this until later on then wondered why it was gone.</description> <content:encoded><![CDATA[<p>Thanks for the heads up Dan. I agree, prefer it was still there. My background being involved in software design, I am not a fan of things changing too often. Particularly careful of feature removal, no matter how small, is always a negative thing for users. Unless the feature is clearly giving wrong or misleading information.</p><p>Great info, I would have missed this until later on then wondered why it was gone.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: basic
Database Caching 1/13 queries in 0.002 seconds using disk: basic
Object Caching 366/376 objects using disk: basic
Content Delivery Network via cdn.dejanseo.com.au

 Served from: dejanseo.com.au @ 2013-05-26 19:32:55 by W3 Total Cache -->