not at present - whether content is indexed is controlled by whether it has a relevant businesscontroller that supports indexing. This happens at the module level, so you could do this by cloning the html module, altering it's namespace, removing the businesscontroller, repackaging it and installing it i.e. you would have 2 modules , html and htm_noindex.

FYI  We were asking discussing this just the other day during a core trustee meeting, and one of the trustees had a suggestion for coding a solution to allow it to be enabled at the module instance level i.e. a checkbox in module settings. I believe they are going to try and code this enhancement and submit it for a future release.

Cathal

Thanks for the info Cathal, although it's not what I hoped.  I could clone the module, and other modules that I don't want indexed.  But that means having multiple copies of multiple modules that I have to maintain going forward.... not the most ideal solution.  I guess I'll have to wait for the enhancement to come out, or write my own indexer.

I have written a module for users to select which pages they want to include in a search.  I suppose I could go a similar route and have it for admins only.  It will list all of the modules on a selected page and they can choose if it should/should not be included in the search.  This puts all of the config in one spot rather than at the individual modules. 

Thx again for the info.  It at least gives me a direction to go, a tough direction but a direction none the less.