Hi guys, 1) First, a claim (you'll tell me if I'm right, but I think so): when you've got a say 100,000 words article to index -in other words, a book-, it is better to split it into as many html files as possible in order to increase your SE presence (of course, each html page containing a decent amount of content). What is exactly the result of splitting ? I know this increases the total pagerank contained within your website, but I'm talking in terms of visits. Is it better to keep a huge html file with a lot of info or many of them with less information ? 2) There is a not so ugly way to index a book using a Javascript menu and frames, but I find it tricky for the SE. Actually, in an optimal situation, all the pages would be indexed while the overall look wouldn't be too ugly (but everything in nice easy HTML with a nice linking scheme). Is there a way to achieve this utopia ?
1) It is best to split the content into as many HTTP addresses as makes good logical and usable sense. From a reader perspective it will be easier to take in individual sections and to bookmark and return to specific pages. From a search engine ranking perspective it affords you the opportunity to create a wealth of anchor text/links and on-page factors that signify yours is a serious resource. 2) I would keep the content in one HTML file and 1) use a transparent scripting language like PHP or Perl to present the content in sections and 2) use mod_rewrite to generate separate search engine friendly addresses for each section. It's a bit of work but I think it would take far less effort than setting-up multiple 'real' HTML files. Even at 100,000 words gross I doubt load time will be a overcoming factor unless you are serving multiple photographs with each page.
Per my previous #2....On second thought I would split the file into chapters, place each chapter into a table in a database (you probably have MySQL) then use a scripting language like PHP or Perl to present it dynamically out of one file (acting as a CMS) and presenting it to several SEO friendly URLs using mod_rewrite. While it is not much different than my previous #2, just the introduction of a database, you will be moving the content out of your CMS which will make it respond faster. Also, by putting the content into a database table you could build a search bar into your CMS.
Yep, that's also the most reasonable solution I could come up with. That's quite some work though, I'm sort of lazy those days ... thanks for the input.