Some time ago I posted on the Accessibility forum a question about whether I should make the top-level menu item of an expanding menu a link to a page.
One poster replied with a reason why I should do what I asked about:
One of the biggest reasons is that search engines (and other devices) don't execute JS, and you're missing an opportunity for internal cross linking.
I want to make sure the SEs can spider all my pages and I think the way my menu is built addresses the concern raised above because the raw html document has all the URLs that make up the nav menu in an unordered list. In other words, JS is not required to be called from the server to display the nav menu content.
So, my question is just that - is the way my menu is built taking advantage of the "opportunity for internal cross-linking?"
The following is a partial description of how the menu works:
The menu is based on an unordered list...The layout for the main- and submenu items is specified in the CSS.
If that is not enough information to answer the question, I'll provide a sample of the nav menu.
Msg#: 4343280 posted 1:56 am on Jul 25, 2011 (gmt 0)