Just wanted to clarify that this statement is not correct.  Many people continue to assert that solpart is not search engine friendly but fail to understand how the menu is designed.  The will menu detect if the browser hitting it is a crawler/spider, and if so, it renders downlevel.  These forums contain many similar posts and I am growing tired of needing to restate the same thing over and over again. 

DNNMenu, by default uses the same design.  Sends down the raw data, not the HTML, as it is a smaller payload, UNLESS a spider/crawler, or downlevel browser is detected (this logic is configurable via the config file).  The newest version of the menu will be xhtml compliant (it doesn't use expandos for its properties) and support an unordered list approach to hopefully pacify the crowd that does not believe the original design worked.  This rendering mode, however, will not be as efficient (bigger payload since it includes html) as the original.  You can see the comparison in sizes by looking at http://webcontrols.dotnetnuke.com

The dropdown at the top of the page shows the rendering mode (Unordered list).  Using fiddler you can see that the page size is 18,888.  When switched to the Normal mode the page size is reduced to 14,087.  The new menu and webcontrols will be part of the Cambrian release as the code requires MSAJAX to be installed (something that we cannot do in the 4.x codebase).  The code is currently beta, but can be downloaded and installed in the 4.x codebase.

Additional information

• http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1675/Default.aspx
• http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1487/Default.aspx
• http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1580/Default.aspx
• http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1532/Default.aspx
• http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1511/Default.aspx
• http://webcontrols.dotnetnuke.com/documents.aspx

Jon,

Thanks for the clarification, I had been working under this premise because of all the talk I had seen regarding SOLPART's issues, many of which were issues with SEO. I was unaware the system detected a bot and rendered differently. Following DNNCreative's newsletters, I was under the assumption (in error, of course) that SOLPART would not render S.E. friendly code and would usually opt for HouseMenu based on this information which I now understand as faulty.

Apologies for spreading misinformation.

~SB

You could also create two skins, one for the portal without the NAV menu and one for the admin with the NAV menu.
You can then set the skins from the admin | site settings page or from admin | skins.