The siteMap remind me of the navigation used in Microsoft UIP (Ages ago)

. âsiteMapâ should have only one <siteMap> node. And one and only main <siteMapNode>. That doesnât mean you cant group your child pages to a logical <siteMapNode>. Its best to show a proper example. Make sure to have the âurlâ attribute unique. That will be the internal unique identifier. Have a look at the bellowing sample.
<?xml version="1.0" encoding="utf-8" ?>
<siteMap xmlns="http://schemas.microsoft.com/AspNet/SiteMap-File-1.0" >
<siteMapNode url="Default.aspx" title="Home" description="The default page" >
<siteMapNode url= "ManageStock/Default.aspx" title="Home2" description="The default page" >
<siteMapNode url="ManageStock/Page1.aspx" title="Run1" description="another page"/>
<siteMapNode url="ManageStock/Page2.aspx" title="Run2" description="another page"/>
</siteMapNode>
<siteMapNode url= "BuyStock/Default.aspx" title="Home3" description="The default page" >
<siteMapNode url="BuyStock/Page1.aspx" title="Run1" description="another page"/>
<siteMapNode url="BuyStock/Page2.aspx" title="Run2" description="another page"/>
</siteMapNode>
</siteMapNode>
</siteMap>