Sorry for the DB link not working... probably irrelevant at this point. Judging by the responses, I see I should have been more clear in my initial posts. It sounds like there is no option short of a fully custom solution at this point, but I'll elaborate on my previous example just to make sure we are all on the same page.
I guess what I am kind of surprised about is that at the Page (doc) Type level we can specify which fields to index, but there is no way to specify on a new instance of that document type to NOT index that particular page w/out adding the URL to the web part filter. That may seem logical, but in my experience, allowing a CMS editor access to the configuration of a web part could be disastrous.
We structure out projects in such a way that anything that is not of type Menu Item gets put into a directory we call "Page Elements." That can include any Page Type, custom or from Kentico.
- Page Elements (just a folder)
- Calendar Items
- News Items
- FAQ Items
Then, as pages get built out, CMS editors can us out custom or Kentico widgets to load the data from these directories. Above is a very basic example, but I just want to convey the idea. So, our only option is to tell the system to only index from specific directories, which in the long term is not really a good solution, b/c there may be instances of a calendar item that we want indexed... but not ALL calendar items. But, since they reside in the calendar item directory, they will all be wrapped up into the results.
Hope that makes sense... any ideas, or am I just wasting everyone's time :-)