Too many Links

I've been playing around with vBulletin templating for a couple of days now, and it has struck me that any given page in a vbulletin installation contains an absurd amount of links - and that number of links is going to inevitably fall outside google's webmaster guidelines which if I recall correctly provides for a reasonable limit of 150 links per page.

So what are vB users to do about this sort of thing?

I honestly have no idea what Google's position is on the matter, but I do see a lot of "junk links" amongst the crowd - links to edit your signature, edit your user profile, etc. I'm wondering what to do about those links - you want to include them because they expect them there. You could insert them with an ajax call and a little bit of javascript - I wonder if IE cache's ajax called pages correctly? It certainly doesn't cache dynamically generated css files or images designated within CSS without a good deal of coaxing. That's a fine solution from a user perspective, but what about web server load and page load times?

If it is cached correctly, then the ajax solution for providing the links may actually serve you better than putting the links into your pages directly - a small page weight reduction, coupled with a very quick javascript call... hmm... But then what about those lynx users, or screen reader users? I'm not sure that VB is very friendly to those environments anyways - but if I'm going to build something, at least that portion of the app should work in all environments - which would mean essentially that I would need to provide alternative access to those links. Come to think of it - that might actually be a better solution for screenreaders and javascript shy browsers - If you are running a screen reader, or a low powered, javascript free browser - you want faster, lighter pages and you want to go looking for those links rather than actually having to go through two pages of text before you actually get to any real content.

Hmmm...

My other alternative was rel="nofollow"-ing the links, but the more I babble, the more I become convinced that a "navlinks" ajax call is the best solution. Now... where is safari at as far as ajax support?