<?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>Saint Anselm College Web Redesign &#187; Search</title>
	<atom:link href="http://blogs.saintanselmcollege.net/redesign/tag/search/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.saintanselmcollege.net/redesign</link>
	<description></description>
	<lastBuildDate>Sun, 13 Jun 2010 11:26:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Should We Use Underscores or Hyphens in URLs?</title>
		<link>http://blogs.saintanselmcollege.net/redesign/2009/11/17/should-we-use-underscores-or-hyphens-in-urls/</link>
		<comments>http://blogs.saintanselmcollege.net/redesign/2009/11/17/should-we-use-underscores-or-hyphens-in-urls/#comments</comments>
		<pubDate>Tue, 17 Nov 2009 19:38:06 +0000</pubDate>
		<dc:creator>Doug Minor</dc:creator>
				<category><![CDATA[CMS]]></category>
		<category><![CDATA[Ingeniux]]></category>
		<category><![CDATA[Redesign]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[Search]]></category>

		<guid isPermaLink="false">http://blogs.saintanselmcollege.net/redesign/?p=23</guid>
		<description><![CDATA[As part of our implementation of Ingeniux CMS, we&#8217;ve had to decide how we want URLs to read (i.e., how will the page name read in a browser&#8217;s address bar).
Out of the box, Ingeniux displays page URLs as numbers with an .xml extension (e.g., 345.xml). Although, this method is short and clean, numbers aren&#8217;t real [...]]]></description>
			<content:encoded><![CDATA[<p>As part of our implementation of Ingeniux CMS, we&#8217;ve had to decide how we want URLs to read (i.e., how will the page name read in a browser&#8217;s address bar).</p>
<p>Out of the box, Ingeniux displays page URLs as numbers with an .xml extension (e.g., 345.xml). Although, this method is short and clean, numbers aren&#8217;t real memorable. It&#8217;s much easier for site visitors to remember academics.html or news.html than 345.xml. You have some inclination where academics.html will take you when clicked, whereas 345.xml is pretty vague.</p>
<p>To present more human-readable URLs, Ingeniux allows us to utilize structured URLs using a hyphen or an underscore as a separator and specify .htm or .html as an extension. So which is better, hyphens or underscores? For me it has always come down to usability, something we touch on during each CMS training. It is much easier to read a Web address done in hyphens than underscores, especially when including URLs in print. If URLs appear as underlined text, the underscores are often harder to read.</p>
<p>When it comes down to it, search engines treat both underscores and hyphens differently. Google for example treats hyphens as separators or dividers while underscores are not treated as such as shown below.</p>
<p><strong>Underscores vs. Hyphens</strong></p>
<p>Example 1: <em>www.anselm.edu/my_web_page.html</em><br />
Example 2: <em>www.anselm.edu/my-web-page.html</em></p>
<p><strong>How Google reads these URLs.</strong></p>
<p><strong>Example 1:</strong> <em>mywebpage</em><br />
<strong>Example 2: </strong><em>my web page</em></p>
<p><span id="more-23"></span></p>
<p>Given the Web&#8217;s capacity to evolve, this could easy change at any time. But based on our current understanding, we will be utilizing hyphens as separators for the redesigned site for improved search engine optimization (SEO) and readability.</p>
<p><strong>Sites Referencing the use of Underscores vs. Hyphens</strong></p>
<ul>
<li><a href="http://www.tunnel7.com/blog/article/hyphens-or-underscores">http://www.tunnel7.com/blog/article/hyphens-or-underscores</a></li>
<li><a href="http://pixelposition.com/hyphens-underscores">http://pixelposition.com/hyphens-underscores</a></li>
<li><a href="http://www.youtube.com/watch?v=Q3SFVfDIS5k">http://www.youtube.com/watch?v=Q3SFVfDIS5k</a> (<span class="description">Google software engineer Matt Cutts</span>)</li>
</ul>
<p><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="425" height="350" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="src" value="http://www.youtube.com/v/Q3SFVfDIS5k" /><embed type="application/x-shockwave-flash" width="425" height="350" src="http://www.youtube.com/v/Q3SFVfDIS5k"></embed></object></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.saintanselmcollege.net/redesign/2009/11/17/should-we-use-underscores-or-hyphens-in-urls/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A New and Improved Search Engine</title>
		<link>http://blogs.saintanselmcollege.net/redesign/2009/11/12/a-new-and-improved-search-engine/</link>
		<comments>http://blogs.saintanselmcollege.net/redesign/2009/11/12/a-new-and-improved-search-engine/#comments</comments>
		<pubDate>Thu, 12 Nov 2009 16:59:19 +0000</pubDate>
		<dc:creator>Doug Minor</dc:creator>
				<category><![CDATA[Google Mini]]></category>
		<category><![CDATA[Listening Sessions]]></category>
		<category><![CDATA[Redesign]]></category>
		<category><![CDATA[Search]]></category>

		<guid isPermaLink="false">http://blogs.saintanselmcollege.net/redesign/?p=21</guid>
		<description><![CDATA[One of the most requested new Web site features we heard from faculty, staff, and students during our redesign discovery process was improved search. To paraphrase some of the comments we heard &#8211; &#8220;when I search the college site I get a bunch of results that have nothing to do with what I&#8217;m searching for.&#8221;
So [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignright alignnone" style="float: right;" src="http://blogs.saintanselmcollege.net/redesign/wp-content/uploads/1109/googlemini.jpg" alt="" width="250" height="111" />One of the most requested new Web site features we heard from faculty, staff, and students during our redesign discovery process was improved search. To paraphrase some of the comments we heard &#8211; &#8220;when I search the college site I get a bunch of results that have nothing to do with what I&#8217;m searching for.&#8221;</p>
<p>So one of the priorities of the redesign project was to improve site search. So after looking at several different options, we purchased a <a title="Link to Google Mini" href="http://www.google.com/enterprise/search/mini_features.html">Google Mini</a> search appliance, which arrived in the mail this week from Google.</p>
<p><span id="more-21"></span></p>
<p>The Google Mini will provide us with everything we currently get with Google search (including a familiar interface), but will provide us with more control over site search as well as more detailed reporting as noted below.</p>
<ul>
<li><strong>Additional Reporting</strong><br />
More detailed reports on what content the Mini&#8217;s crawler has indexed and will index, as well as errors that the Mini found when crawling our site. Also, more detailed reports on what visitors are searching for on our site.</li>
<li><strong>Site Indexing</strong><br />
We can specify which pages or sections of our site are crawled and indexed to show up in search results or not indexed. We can also specify the frequency at which pages on our site are crawled.</li>
<li><strong>Google Analytics Integration</strong><br />
Better understand how visitors are using our public Web site and improve the effectiveness of our search results.</li>
<li><strong>Keyword</strong><br />
Allows us to specify keywords that return specific results when someone searches our site. For example, if someone searches for Dining on our site, we can associate that keyword with Dining Services and the URL for their site (rather than getting a top search result pointing to an academic paper on how to eat healthy when dining out). So whenever someone searches for Dining the link will appear at the top of the search no matter where it would normally appear in the result set.</li>
<li><strong>Synonyms </strong><br />
Synonyms will give alternate terms for your search. For example, when a visitor searches for &#8220;Academic Minors&#8221; we can add suggestions, e.g., &#8220;Academic Certificates,&#8221; to the result set.</li>
<li><strong>Document Types</strong><br />
The Google Mini, like our current Google search, will search for multiple document types and display the document types in the results. The Mini can search more than 220 file types, including html, aspx, php, pdf, office documents, etc.</li>
</ul>
<p>Since 2002, the college has been using Google&#8217;s free custom search engine (formerly Google University Search). It&#8217;s used by many colleges and universities since it&#8217;s free and search results can be served up without displaying ads. However, since it&#8217;s free, it lacks a lot of the more robust features sought by institutions. Features you typically find with a paid search engine, like enhanced reporting, keywords, synonyms, setting site crawl frequency, etc.</p>
<p>We will continue to use Google Custom Search, but only as a back up to our Google Mini appliance should it go down (knock on wood). Once the Mini is installed, we&#8217;ll then need to configure the Mini to output results within our new CMS templates, which is something we will be working on in early December.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.saintanselmcollege.net/redesign/2009/11/12/a-new-and-improved-search-engine/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
