I may be missing the point. If so I am keen to learn.

I'm not sure what the notion of 'quality' means for a site map. I would think that once a site map lists all the urls you want indexed it cannot get any better.

I also suspect that if your site is fully linked (Every url reachable by a genuine anchor tag link) then a site map is un-necessary.

I'll grant that a site map may allow the search engine to become aware of those URL's sooner, but, eventually they would be found.

So - what is the point of a site-map?

---

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk

Valid points - I'll give you my take on it and take it for what it's worth...

Quality - I'm looking for an efficient tool that will allow me to create ideally both an xml sitemap and aspx sitemap (list of navigable links) for my site. Xml to be submitted directly to google. I was being a bit vague for my use of quality so I would say something that allows for the priority and frequency to be set, and the ability to exclude certain links.

In the latest version of dnn 6X you do have the ability to control the priority, but in my version of 5x and older sites this doesn't work. Not sure if it is just me or what but all of them default to 0.5 regardless of what I change it to when I update a page and then view the default sitemap.aspx page.

My understanding is that not every link is guaranteed to be indexed or searched without a sitemap. There's a good chance it will over time, but a much better chance if you submit a well organized sitemap directly to the source, aka google, and tell them specifically everything on the site and when to come back. If it has dynamic content or ajax rich features this is even more important.

soo, the point of my sitemap is to gain better rank, quicker, with a more efficient road map submitted to the search engines. Maybe I'm complicating things a bit, but if I have one I want it to be the best one possible.

Thoughts?

cheers. Mike.