Any new developments on this issue?  Just looking for a solution!

A few months back I posted an idea and sample implementation for a simple update you can make to the standalone DNN sitemap file that can provide some immediate help for the "every DNN page has same priority value" issue.  The idea (and implementation) was quite simple: increase page priority if a DNN page has a defined description and increase it again if the page has any defined keywords.  Very basic but still somehat effective for distinguishing content pages from transitional pages.  Best of all it only touches the standalone sitemap file -- the DNN database, core files and libraries are untouched.

Here's the post:  http://eguanasolutions.com/Blog/tabid/54/EntryID/8/default.aspx


Setting specific page priority values:
My super-simple solution does not address cases where every page has a description and keywords (and thus the same modified priority value).  In the same post I outlined a second idea for extending the standalone sitemap file to support user-specified priority tags for individual DNN pages.  Again there's no need to modify any code in DNN or make any change or modification in the database -- updates are limited to the sitemap file.  I have not implemented this second idea, yet, but it's on my list.

Both ideas are intended as temporary solutions until DNN gets a page priority setting feature "baked-in" (if ever) but they're easy to implement with no impact on "core" code (I consider "core" to be modules, framework, providers and db constructs).  Only the standalone sitemap file is affected so it's easy to swap the original for a modified version (and back again, if needed).


I'll update with a copy of a user-specified page priorty tag solution once (if) I get the time to create it.

-mamlin