Posted by Duncan Morris
Over the past couple of days I have been putting together some internal guidelines on various aspects of our jobs. This should ensure that we are giving consistent information to our various clients. Most of these guidelines have been fairly straightforward with nothing in them to write home about. However, one of the hardest guidelines to write has been the one talking about xml sitemaps. So, rather than horde my thoughts, I’m going to open them up to all of you.
What are xml sitemaps?
Sitemaps are an easy way for webmasters to inform search engines about pages on their sites that are available for crawling. In its simplest form, a Sitemap is an XML file that lists URLs for a site along with additional metadata about each URL… http://www.sitemaps.org
On the surface this seems to be a great addition to any website’s armoury. However, before you rush away and create your sitemap, there are a number of pros and cons you should be aware of.
Benefits to using a xml sitemap
The first set of benefits revolve around being able to pass extra information to the search engines
- Your sitemap can list all URLs from your site. This could include pages that aren’t otherwise discoverable by the search engines.
- Giving the search engines priority information. There is an optional tag in the sitemap for the priority of the page. This is an indication of how important a given page is relevant to all the others on your site. This allows the search engines to order the crawling of their website based on priority information.
- Passing temporal information. Two other optional tags (lastmod, and changefreq) pass more information to the search engines that should help them crawl your site in a more optimal way. “lastmod” tells them when a page last changed and changefreq indicates how often the page is likely to change.