I put this in my razor vie:

@Umbraco.RenderMacro("FullTextSearch", new
{
    queryType = "MultiRelevance",
    titleProperties = "metaTitle,navName,nodeName",
    bodyProperties = "FullTextSearch",
    summaryProperties = "metaDescription,FullTextSearch",
    titleLinkProperties = "",
    rootNodes = site.Id.ToString(),
    contextHighlighting = "false",
    summaryLength = "",
    pageLength = "20",
    fuzzyness = "0.5",
    useWildcards = "0"
})

Documentation from FullTextSearch:

PARAMETERS:

queryType 

Type of search to perform. Possible values are:

MultiRelevance ->
  The default.
  The index is searched for, in order of decreasing relevance
    1) the exact phrase entered in any of the title properties
    2) any of the terms entered in any of the title properties
    3) a fuzzy match for any of the terms entered in any of the title properties
    4) the exact phrase entered in any of the body properties
    5) any of the terms entered in any of the body properties
    6) a fuzzy match for any of the terms entered in any of the body properties

MultiAnd ->
  Similar to MultiRelevance, but requires all terms be present

SimpleOr->
  Similar to MultiRelevance again, but the exact phrase does not
  get boosted, we just search for any term

AsEntered->
  Search for the exact phrase entered, if more than one term is present
______________________________________________________________________    

titleProperties

A comma separated list of properties that are part of the page title,
these will have their relevance boosted by a factor of 10
defaults to nodeName. Set to "ignore" not to search titles.
______________________________________________________________________    

bodyProperties 

A comma separtated list of properties that are part of the page body.
These properties and the titleProperties will be searched. 

defaults to using the full text index only
______________________________________________________________________

summaryProperties

The list of properties, comma separated, in order of preference,
that you wish to use to create the summary to appear under
the title. All properties selected must be in the index, cos that's
where we pull the data from.

Defaults to Full Text
______________________________________________________________________    
titleLinkProperties

The list of properties, comma separated, in order of preference,that you 
wish to use to create the title link for each search result. 

Defaults to titleProperties, or if that isn't set nodeName
______________________________________________________________________            
rootNodes

Comma separated list of root node ids
Only nodes which have one of these nodes as a parent will be returned.
Default is to search all nodes
______________________________________________________________________

contextHighlighting

Set this to false to disable context highlighting
in the summary/title. You may wish to do this if you are having
performance issues as context highlighting is (relatively)
slow.
Defaults to on.

______________________________________________________________________

summaryLength

The maximum number of characters to show in the summary.
Defaults to 300

______________________________________________________________________

pageLength

Number of results on a page. Defaults to 20. Set to zero to disable paging.

______________________________________________________________________

fuzzyness

Lucene Queries can be "fuzzy" or exact.
A fuzzy query will match close variations of the search terms, such as 
plurals etc. This sets how close the search term must be to a term in
the index. Values from zero to one. 1.0 = exact matching.
Note that fuzzy matching is slow compared to exact or even wildcard
matching, if you're having performance issues this is the first thing
to switch off.

Defaults to 0.8
______________________________________________________________________

useWildcards

Add a wildcard "*" to the end of every search term to make it match 
anything starting with the search term. This is a slightly faster, but
less accurate way of achieving the same ends as fuzzy matching. 
Note that fuzzyness is automatically set to 1.0 if a wildcards are enabled.

Defaults to off
______________________________________________________________________