<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	>
<channel>
	<title>Comments on: Site Maps and Site Indexes, Revisited</title>
	<atom:link href="http://www.uie.com/brainsparks/2006/01/12/site-maps-and-site-indexes-revisited/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2006/01/12/site-maps-and-site-indexes-revisited/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Sat, 20 Mar 2010 07:32:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jared Spool</title>
		<link>http://www.uie.com/brainsparks/2006/01/12/site-maps-and-site-indexes-revisited/comment-page-1/#comment-7936</link>
		<dc:creator>Jared Spool</dc:creator>
		<pubDate>Tue, 09 May 2006 19:37:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=161#comment-7936</guid>
		<description>GW,

The two value points you give them are true, except I&#039;d suggest neither of them benefit the user really. 

There are more effective ways to get the search engine to index deeper *and* benefit the user simultaneously. 

And, haivng a central point for the organization or division is an internal issue, not something the user needs. You could keep it on a private portion of the site without troubling anyone.

That&#039;s my thinking.</description>
		<content:encoded><![CDATA[<p>GW,</p>
<p>The two value points you give them are true, except I&#8217;d suggest neither of them benefit the user really. </p>
<p>There are more effective ways to get the search engine to index deeper *and* benefit the user simultaneously. </p>
<p>And, haivng a central point for the organization or division is an internal issue, not something the user needs. You could keep it on a private portion of the site without troubling anyone.</p>
<p>That&#8217;s my thinking.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GW</title>
		<link>http://www.uie.com/brainsparks/2006/01/12/site-maps-and-site-indexes-revisited/comment-page-1/#comment-7935</link>
		<dc:creator>GW</dc:creator>
		<pubDate>Tue, 09 May 2006 19:23:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=161#comment-7935</guid>
		<description>Sorry I&#039;m a bit late on this, but count me in with the crowd that says site maps do have a great bit of use and worth.  In short, I believe they do the following:  1) help search engines to index the deeper content pages on a site more easily, and 2) help an organization have a central point for the structure and organization of a website... and even they functions of their business in general.  Its sort of an organizational or divisional map.  For huge enterprises it may be more effort than reward, but for small or medium sized businesses/sites I highly recommend it.</description>
		<content:encoded><![CDATA[<p>Sorry I&#8217;m a bit late on this, but count me in with the crowd that says site maps do have a great bit of use and worth.  In short, I believe they do the following:  1) help search engines to index the deeper content pages on a site more easily, and 2) help an organization have a central point for the structure and organization of a website&#8230; and even they functions of their business in general.  Its sort of an organizational or divisional map.  For huge enterprises it may be more effort than reward, but for small or medium sized businesses/sites I highly recommend it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared Spool</title>
		<link>http://www.uie.com/brainsparks/2006/01/12/site-maps-and-site-indexes-revisited/comment-page-1/#comment-949</link>
		<dc:creator>Jared Spool</dc:creator>
		<pubDate>Thu, 19 Jan 2006 00:19:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=161#comment-949</guid>
		<description>As I understand the W3C WAI guidelines, they suggest you just need something that acts like a site map, but doesn&#039;t have to be labeled as such. For example, a home page with the same content would likely meet the spirit of the guidelines, if not the letter.</description>
		<content:encoded><![CDATA[<p>As I understand the W3C WAI guidelines, they suggest you just need something that acts like a site map, but doesn&#8217;t have to be labeled as such. For example, a home page with the same content would likely meet the spirit of the guidelines, if not the letter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Max</title>
		<link>http://www.uie.com/brainsparks/2006/01/12/site-maps-and-site-indexes-revisited/comment-page-1/#comment-945</link>
		<dc:creator>Max</dc:creator>
		<pubDate>Wed, 18 Jan 2006 16:58:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=161#comment-945</guid>
		<description>Thanks for writing about this topic, Jared. Being of the same opinion, I recently went so far as to tell a client to ditch their site map as it was merely a list of links organised to reflect the site hierarchy. The primary navigation was already doing this well (but not showing all links all at once!). My suggestion hit a snag - W3C WAI guidelines:

&quot;13.3 Provide information about the general layout of a site (e.g. a site map or table of contents). [Priority 2] In describing site layout, highlight and explain available accessibility features.&quot;
http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation

Also, see the rationale provided by the RNIB:
http://www.rnib.org.uk/xpedio/groups/public/documents/PublicWebsite/public_sitemaps.hcsp

So, as the client was looking to be Double-A compliant, we had to put the site map back in. I&#039;ve looked at the WCAG 2.0 draft guidelines and it doesn&#039;t look like this requirement will be going away anytime soon.

Any ideas how to be compliant without needing a site map or site index?</description>
		<content:encoded><![CDATA[<p>Thanks for writing about this topic, Jared. Being of the same opinion, I recently went so far as to tell a client to ditch their site map as it was merely a list of links organised to reflect the site hierarchy. The primary navigation was already doing this well (but not showing all links all at once!). My suggestion hit a snag &#8211; W3C WAI guidelines:</p>
<p>&#8220;13.3 Provide information about the general layout of a site (e.g. a site map or table of contents). [Priority 2] In describing site layout, highlight and explain available accessibility features.&#8221;<br />
<a href="http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation" rel="nofollow">http://www.w3.org/TR/WCAG10-CORE-TECHS/#navigation</a></p>
<p>Also, see the rationale provided by the RNIB:<br />
<a href="http://www.rnib.org.uk/xpedio/groups/public/documents/PublicWebsite/public_sitemaps.hcsp" rel="nofollow">http://www.rnib.org.uk/xpedio/groups/public/documents/PublicWebsite/public_sitemaps.hcsp</a></p>
<p>So, as the client was looking to be Double-A compliant, we had to put the site map back in. I&#8217;ve looked at the WCAG 2.0 draft guidelines and it doesn&#8217;t look like this requirement will be going away anytime soon.</p>
<p>Any ideas how to be compliant without needing a site map or site index?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kstruct &#187; Sitemaps and navigational search</title>
		<link>http://www.uie.com/brainsparks/2006/01/12/site-maps-and-site-indexes-revisited/comment-page-1/#comment-910</link>
		<dc:creator>kstruct &#187; Sitemaps and navigational search</dc:creator>
		<pubDate>Fri, 13 Jan 2006 22:03:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=161#comment-910</guid>
		<description>[...] There&#8217;s an interesting comment on Jared Spool&#8217;s Site Maps and Site Indexes, Revisited (a follow up to What about Site Maps and Site Indexes?) that site maps might help search engines &#8216;easily spider your site&#8217;. While I agree that site maps might make a good seed/starting point for a search engine, I don&#8217;t quite see how any crawling engine is going to be taken seriously if it can&#8217;t cope with a sitemap-less site. Getting a good starting point can useful in a multi-domain crawl assuming you only want one connection per domain at a time because it allows you to get up to the maximum number of threads quickly, but this isn&#8217;t usually an issue with individual sites. [...]</description>
		<content:encoded><![CDATA[<p>[...] There&#8217;s an interesting comment on Jared Spool&#8217;s Site Maps and Site Indexes, Revisited (a follow up to What about Site Maps and Site Indexes?) that site maps might help search engines &#8216;easily spider your site&#8217;. While I agree that site maps might make a good seed/starting point for a search engine, I don&#8217;t quite see how any crawling engine is going to be taken seriously if it can&#8217;t cope with a sitemap-less site. Getting a good starting point can useful in a multi-domain crawl assuming you only want one connection per domain at a time because it allows you to get up to the maximum number of threads quickly, but this isn&#8217;t usually an issue with individual sites. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared Spool</title>
		<link>http://www.uie.com/brainsparks/2006/01/12/site-maps-and-site-indexes-revisited/comment-page-1/#comment-909</link>
		<dc:creator>Jared Spool</dc:creator>
		<pubDate>Fri, 13 Jan 2006 18:04:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=161#comment-909</guid>
		<description>Nick,

I fear an automated site map generator would only make a miserable site map easy to maintain. Figuring out the trigger words and clustering is the hard part and I don&#039;t know of an automated way to do that.</description>
		<content:encoded><![CDATA[<p>Nick,</p>
<p>I fear an automated site map generator would only make a miserable site map easy to maintain. Figuring out the trigger words and clustering is the hard part and I don&#8217;t know of an automated way to do that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Besseling</title>
		<link>http://www.uie.com/brainsparks/2006/01/12/site-maps-and-site-indexes-revisited/comment-page-1/#comment-906</link>
		<dc:creator>Nick Besseling</dc:creator>
		<pubDate>Fri, 13 Jan 2006 00:57:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=161#comment-906</guid>
		<description>One of the really good uses of Site maps outside of a navigational sense is that search engines can use the site map (or site index) to easily spider your site. Some search engines do use links as a way to help work out page rankings thus a site map is valaubale in this sense.

And why all this hoopla about keeping sitemaps/indexes up to date. 
Make simple script that dynamically creates site maps or indexs on the fly based on meta or title information or some other page indicator. 
Most web developers could do this within a day. Thus theres no need to worry about it and those users who like site maps and site indexes are still being served.</description>
		<content:encoded><![CDATA[<p>One of the really good uses of Site maps outside of a navigational sense is that search engines can use the site map (or site index) to easily spider your site. Some search engines do use links as a way to help work out page rankings thus a site map is valaubale in this sense.</p>
<p>And why all this hoopla about keeping sitemaps/indexes up to date.<br />
Make simple script that dynamically creates site maps or indexs on the fly based on meta or title information or some other page indicator.<br />
Most web developers could do this within a day. Thus theres no need to worry about it and those users who like site maps and site indexes are still being served.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
