<?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>The Dào of Search &#187; pagination</title>
	<atom:link href="http://blog.twigkit.com/tag/pagination/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.twigkit.com</link>
	<description>A blog about search, user experience, and development.</description>
	<lastBuildDate>Wed, 01 Sep 2010 21:26:15 +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>Pagination: Common Problems</title>
		<link>http://blog.twigkit.com/pagination-common-problems/</link>
		<comments>http://blog.twigkit.com/pagination-common-problems/#comments</comments>
		<pubDate>Mon, 14 Dec 2009 09:27:10 +0000</pubDate>
		<dc:creator>Tyler Tate</dc:creator>
				<category><![CDATA[User Experience]]></category>
		<category><![CDATA[pagination]]></category>

		<guid isPermaLink="false">http://blog.twigkit.com/?p=22</guid>
		<description><![CDATA[<div id="attachment_32" class="wp-caption alignright" style="width: 285px"><img class="size-full wp-image-32  " title="Google's Pagination" src="http://blog.twigkit.com/wp-content/uploads/2009/12/pagination_google.png" alt="Google have given their &#34;next&#34; button a prominent graphic and bold text." width="275" height="60" /></div>
The purpose of search is to help people find what they're looking for as quickly as possible. Search engines attempt to facilitate this by taking the user's query and responding with results, placing what it thinks are the most relevant results first.

Unfortunately, pagination doesn't always do the best job of guiding the user through the search results in the most beneficial manner. I've noticed three common problems.]]></description>
			<content:encoded><![CDATA[<p>The purpose of search is to help people find what they&#8217;re looking for as quickly as possible. Search engines attempt to facilitate this by taking the user&#8217;s query and responding with results, placing what it thinks are the most relevant results first.</p>
<p>Unfortunately, pagination doesn&#8217;t always do the best job of guiding the user through the search results in the most beneficial manner. I&#8217;ve noticed three common problems.</p>
<h2>Problem 1: The &#8220;Last&#8221; button</h2>
<div id="attachment_31" class="wp-caption alignright" style="width: 285px"><a href="http://www.timeout.com/london/"><img class="size-full wp-image-31 " title="Time Out's Pagination" src="http://blog.twigkit.com/wp-content/uploads/2009/12/pagination_timeout.png" alt="Time Out's Pagination" width="275" height="30" /></a><p class="wp-caption-text">Time Out&#39;s pagination includes a link to the very last page of results.</p></div>
<p>If the first page of results is the engine&#8217;s best guess at what the user is interested in, the last page of results is inherently the engine&#8217;s worst guess. Which begs the question: why do you often see a link to the last page of results?</p>
<p>For the user to find what they&#8217;re looking for, it&#8217;s important to get highly relevant results in front of them. Encouraging users to look at irrelevant results is simply counter-productive. Avoid having a &#8220;last&#8221; link.</p>
<h2>Problem 2: Pagination above results</h2>
<div id="attachment_30" class="wp-caption alignright" style="width: 285px"><a href="http://www.careerbuilder.co.uk/"><img class="size-full wp-image-30 " title="Pagination on Career Builder" src="http://blog.twigkit.com/wp-content/uploads/2009/12/pagination_careerbuilder.png" alt="Pagination on Career Builder" width="275" height="115" /></a><p class="wp-caption-text">Career Builder&#39;s search page has pagination above the results.</p></div>
<p>A second harmful practice is placing the pagination above the search results. Again, the purpose of search is to present the most relevant results first. It doesn&#8217;t make sense to encourage users to skip to page 2 before they&#8217;ve encountered all of page 1.</p>
<h2>Problem 3: Next</h2>
<p>If the first two problems are akin to sending the user on unnecessary detours, the third problem is like not giving the user a green light when we should.</p>
<div id="attachment_32" class="wp-caption alignright" style="width: 285px"><a href="http://www.google.com/search?q=avocado"><img class="size-full wp-image-32  " title="Google's Pagination" src="http://blog.twigkit.com/wp-content/uploads/2009/12/pagination_google.png" alt="Google have given their &quot;next&quot; button a prominent graphic and bold text." width="275" height="60" /></a><p class="wp-caption-text">Google, not surprisingly, got it right by giving their &quot;next&quot; button a prominent graphic and bold text.</p></div>
<p>Imagine you enter a query, scroll down the page as you look over the results, and reach the bottom of the page without finding what you&#8217;re looking for. What would you want to do next? Go to page 7? No, you&#8217;ll most likely want to go to the next page of results. So, why doesn&#8217;t the pagination always offer us a big, whopping &#8220;Next&#8221; button?</p>
<h2>In Summary</h2>
<div id="attachment_43" class="wp-caption alignright" style="width: 285px"><img class="size-full wp-image-43" title="TwigKit's default pagination." src="http://blog.twigkit.com/wp-content/uploads/2009/12/pagination_twigkit1.png" alt="TwigKit's default pagination." width="275" height="50" /><p class="wp-caption-text">TwigKit&#39;s default pagination.</p></div>
<p>All three of these side effects are the result of one illness: forgetting to optimize pagination for helping users move from highly relevant results to less relevant results in a proper progression.</p>
<p>For TwigKit, we also wanted to make it easy for people to get back to the earlier pages of more relevant results once they have navigated to a later page.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.twigkit.com/pagination-common-problems/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>
