|
|
|
Freeverse, Inc.'s SOUND STUDIO 3.5.5 - Sound Studio is for anyone who needs to record or edit audio with a professional tool, but at a consumer price. Perfect for Podcasts, Music, More! Now updated for OS X 10.5 Leopard. <http://www.freeverse.com/soundstudio> |
Sitemaps
via email
Ref.1: http://emperor.tidbits.com/webx/?13
Ref.2: <a href="/webx?13@@.3c86e808">sub000, "Dates in TidBITS" #, 14 Nov 2006 12:37 pm</a>
On Nov 27, 2006, "infonauts" posted a message (Ref.1) to start a new
thread under the subect "Digest from TidBITS Talk" [subsequently
rethreaded by me -Adam]. Although it was apparently prompted by the
ongoing thread about "Dates in TidBITS" (Ref.2), I was more intrigued
by the concept of Sitemaps, and thus have re-titled this message.
The motivation for Sitemaps, neatly summarized by infonauts' first
paragraph, is laudable. The basic concept and the protocol
description on the Sitemaps Website are straightforward and clear.
The FAQ on the Sitemaps Web site is helpful as far as it goes.
Unfortunately, it does not go far enough, and there is NO point of
contact given for submitting additional questions in hope that they
might eventually find their way into the FAQ. (In fact, the only
place one can find the identity of the Big Three sponsors is in a
disclaimer buried in the Terms of Service.)
What I find missing is a clear statement of why any Webmaster should
expend the resources needed to implement and maintain sitemap files.
In other words, what will a sitemap file enable a Web crawler to do
that it doesn't already do? The news releases don't answer this
question, nor does the Sitemaps Website. Even the "official" blogs
of Google, the developer of the sitemaps protocol, don't answer it.
Given that one part of the sitemap protocol is a frequency-of-update
indicator, it might be reasonable to assume that a sitemeap can
encourage Web crawlers to revisit some parts of the site more
frequently in return for revisiting other parts less frequently. But
I can find no confirmation of such an assumption.
Other questions which I think important but which are not covered in
the FAQ (and which I didn't find answered in Google's blogs):
- Will Web crawlers find a sitemap file if it isn't explicitly
submitted to the various search engines?
- Is it necessary (or at least important, or even just helpful) to
update and/or resubmit an existing sitemap file when one of the files
to which it points has been updated?
- If a Website has a "what's new" page that is regularly updated to
identify changed pages elsewhere on that Website, is it necessary to
mention any page other than this one in the sitemap?
- If a Website is well structured (e.g., according to Google's
Guidelines for Webmasters), is it necessary to list all files on the
Website in sitemap files? If not, how should a Webmaster decide
which files to list and which to omit?
It's unfortunate that the sponsors of the sitemap protocol apparently
didn't put as much effort into making its Website useful as they did
into disclaiming any and all responsibility for the results of using
it. The concept of the protocol seems to be potentially useful in
improving the timeliness and usefulness of search engine results, but
the present inadequacy of documention may well prevent the full
potential from being reached.
Carl
Mark as Read
|
| ||||||||||||||||||||||||||||||
|
TidBITS
TidBITS
TidBITS Talk
Sitemaps
