<?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: Exact Match Query Bug in Google</title> <atom:link href="http://dejanseo.com.au/exact-match-query-bug-in-google/feed/" rel="self" type="application/rss+xml" /><link>http://dejanseo.com.au/exact-match-query-bug-in-google/</link> <description></description> <lastBuildDate>Fri, 24 May 2013 09:39:00 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: Enrico</title><link>http://dejanseo.com.au/exact-match-query-bug-in-google/#comment-663</link> <dc:creator>Enrico</dc:creator> <pubDate>Tue, 24 Apr 2012 12:40:00 +0000</pubDate> <guid isPermaLink="false">http://dejanseo.com.au/?p=7077#comment-663</guid> <description>Yes, it&#039;s still a bug. The &quot;+&quot; sign inside quotes is still interpreted correctly if associated to non-numbers or if it&#039;s associated to a number as the first or last word of the quoted phrase. This behaviour makes me think that they started to index tha e&quot;+&quot; sign without switching off the handling of the old &quot;+&quot; operator when used inside quotes.</description> <content:encoded><![CDATA[<p>Yes, it&#8217;s still a bug. The &#8220;+&#8221; sign inside quotes is still interpreted correctly if associated to non-numbers or if it&#8217;s associated to a number as the first or last word of the quoted phrase. This behaviour makes me think that they started to index tha e&#8221;+&#8221; sign without switching off the handling of the old &#8220;+&#8221; operator when used inside quotes.</p> ]]></content:encoded> </item> <item><title>By: Dejan SEO</title><link>http://dejanseo.com.au/exact-match-query-bug-in-google/#comment-657</link> <dc:creator>Dejan SEO</dc:creator> <pubDate>Mon, 23 Apr 2012 02:44:00 +0000</pubDate> <guid isPermaLink="false">http://dejanseo.com.au/?p=7077#comment-657</guid> <description>Correct. Still a bug isn&#039;t it, considering people will search for Google+ related things in the future more and more and this may actually happen more frequently now than ever.</description> <content:encoded><![CDATA[<p>Correct. Still a bug isn&#8217;t it, considering people will search for Google+ related things in the future more and more and this may actually happen more frequently now than ever.</p> ]]></content:encoded> </item> <item><title>By: Enrico</title><link>http://dejanseo.com.au/exact-match-query-bug-in-google/#comment-656</link> <dc:creator>Enrico</dc:creator> <pubDate>Sun, 22 Apr 2012 13:22:00 +0000</pubDate> <guid isPermaLink="false">http://dejanseo.com.au/?p=7077#comment-656</guid> <description>Actually, the phrase you tried to search isn&#039;t really expressed in an &quot;exact&quot; form, because the &quot;+&quot; sign is a special operator even if inside quotes. The symbol *is* indexed but you cannot search for it. You can get the expected results if you search for &quot;today we&#039;re improving the performance of the * 1 button&quot;.</description> <content:encoded><![CDATA[<p>Actually, the phrase you tried to search isn&#8217;t really expressed in an &#8220;exact&#8221; form, because the &#8220;+&#8221; sign is a special operator even if inside quotes. The symbol *is* indexed but you cannot search for it.<br /> You can get the expected results if you search for &#8220;today we&#8217;re improving the performance of the * 1 button&#8221;.</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/7 queries in 0.003 seconds using disk: basic
Object Caching 371/375 objects using disk: basic
Content Delivery Network via cdn.dejanseo.com.au

 Served from: dejanseo.com.au @ 2013-05-25 07:24:40 by W3 Total Cache -->