Hmmm... upon reading your response a few more times, I think maybe there is a different interpretation (please forgive my naiveté, the terminology associated with Sitefinity is new to me and I am not yet fully conversant in the architecture). Let me see if I can properly interpret your response line by line.
- "We use Lucene search engine."
Simple enough. The underlying search technology is provided by the open-source Lucene engine, which is part of the Apache project. I presume you are using Lucene.net
- "Out of the box there are two types of search providers - pages and content items."
When you say "search providers", I believe you are referring to something in the Telerik.Search namespace, like subclasses of the IndexDataProvider or IndexFieldsProvider classes.
Question: Does the indexing happen in the background somehow? Does Sitefinity start a separate process for this? (as I don't think you can rely on it running to completion within the IIS AppPool).
- "Both the types uses business object to populate the search segment files that are later used by SearchResult control."
It sounds like these "providers" will enumerate collections of objects, possibly use reflection to get properties from them, and then create "search segment files" somewhere. When the SearchResult control renders the results, it will pull the data from these (presumably XML) files.
Before I interpret any more, am I somewhere close to on target? Also, if there is some existing documentation, forum posts, videos, or whatever that will explain this to me, I am happy to learn this info myself, I just could not find anything to address my specific issue about whether the rendered pages get indexed or not.