<?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: 10 usability guidelines for designing the search interface</title>
	<atom:link href="http://usabilitygeek.com/10-usability-guidelines-for-the-search-interface/feed/" rel="self" type="application/rss+xml" />
	<link>http://usabilitygeek.com/10-usability-guidelines-for-the-search-interface/</link>
	<description>Usability &#38; User Experience (UX) Blog</description>
	<lastBuildDate>Tue, 18 Jun 2013 12:29:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Ecommerce Navigation - A Practical Advice &#124; Usability Geek</title>
		<link>http://usabilitygeek.com/10-usability-guidelines-for-the-search-interface/#comment-1300</link>
		<dc:creator>Ecommerce Navigation - A Practical Advice &#124; Usability Geek</dc:creator>
		<pubDate>Mon, 03 Jun 2013 20:32:15 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitygeek.com/?p=71#comment-1300</guid>
		<description><![CDATA[[...] specific product are more likely to use your website&#8217;s search mechanism. I would recommend to read this article to ensure that your search interface is [...]]]></description>
		<content:encoded><![CDATA[<p>[...] specific product are more likely to use your website&#8217;s search mechanism. I would recommend to read this article to ensure that your search interface is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Parker</title>
		<link>http://usabilitygeek.com/10-usability-guidelines-for-the-search-interface/#comment-708</link>
		<dc:creator>Andy Parker</dc:creator>
		<pubDate>Thu, 29 Mar 2012 15:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitygeek.com/?p=71#comment-708</guid>
		<description><![CDATA[&quot;Its search mechanism should, by default, search your entire site&quot;
You&#039;ve acknowledged the caveat that if you allow search for a specific facet that it is ok.

If you have studied your search logs you should be able to find common search terms and facets.

If people only ever search around one part of the site, say news, would you be better off returning news by default and allow filters to control what they can view after that?]]></description>
		<content:encoded><![CDATA[<p>&#8220;Its search mechanism should, by default, search your entire site&#8221;<br />
You&#8217;ve acknowledged the caveat that if you allow search for a specific facet that it is ok.</p>
<p>If you have studied your search logs you should be able to find common search terms and facets.</p>
<p>If people only ever search around one part of the site, say news, would you be better off returning news by default and allow filters to control what they can view after that?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Database Caching 24/32 queries in 0.016 seconds using disk

 Served from: usabilitygeek.com @ 2013-06-20 06:03:02 by W3 Total Cache -->