John, you have to refine the "query expansion step". That's the step that is pilotted in in Main/LuceneSearch which builds a $query and $extraClause variables which obtain the results at the line below: #set($searchresults = $lucene.getSearchResults("${query}${extraClause}", '', $wikinames, $!languages)) As far as I know, if you put a word in query that, along the Lucene syntax [1] does not contain an explicit field, you obtain a query in the field ft which indexes all the words of any page content, object property or attachments (that's done in subclasses of AbstractIndexData in Lucene plugin). If you can, you should be able to change that behaviour by setting the appropriate fields, setting, for example the full name of your properties. I'm afraid I see nothing for page content. At me, I enriched the Lucene plugin by installing two back-doors: - one, called IndexDoc, to display the lndex documents' fields which helps a lot to see where to search for. - one to allow the search methods to accept Lucene query objects which is useful because I can then create a query in Groovy using the query-parser, in the default field I want, then combine it to another etc... I could try to contribute this. It is visible in i2geo's Lucene plugin (which is for an older xwiki): http://svn.activemath.org/intergeo/Platform/i2gCurriki/plugins/lucene/ . paul Le 20 janv. 2011 à 00:58, John Lantz a écrit :