Hi, no more configuration should be needed. What kind of setting do you use? Are you using MVC or Webforms on your website? For webforms and if you are using SearchDataSource there are some settings on that webcontrol. If you are using the search as a website search you should make sure the starting point for the search is the startpage and not root since you might get pages that should not be visible for end users.

I use the standard config you get when installing search from deployment center. The site is a mvc site.

The problem is that i want to add custom fields to the index, i would like to do that by modifying the document in the indexingservice.document adding event. But the the only pages i get there is those from root and below, and not the pages from the sites start page and below.  So the index, after initial index, only contains pages from root node - as illustrated in my "sketch" in the first post

Have you had a look at Ted Nybergs blogpost about custom fields in episerver search? 

Yes, thats the guide i am using. And it works perfectly, but only pages under root gets indexed

I "solved" it, by removing the clients part of the configuration, rebuild the solution and paste line back in! It then started indexing the correct pages,

I have no explanation to why this solved it, but it did.

Great, but to bad you did not find the answer to why. My experience with the index is that triggering a reindex or removing index might solve some issues if you get strange results. Maybe this triggerd a rebuild of index or something helpling you solve the issue.

Hello All,

Jannich Ibsen reply is absolutely corrent. rebuild works as expected. And no explanation what so ever...

Thanks,

Ranjit