I tend to implement it as a controller action that returns a View pre-populated with the requested page of results - taking the requested page number as a URL parameter for SEO purposes.

So, for instance if you were making a search results page you could do the following:

public class SearchController : SurfaceController 
{
    public ActionResult DisplayResults(int page, string query)
    {
        // Set your search variables
        var pageSize = 10;

        //Do the search
        searcher = ExamineManager.Instance.SearchProviderCollection["ExternalSearcher"]
        var results = searcher.Search(query, true)
                              .Where(r=> r["__IndexType"].Equals("content"))

        // Work out how many results to skip
        var resultsToSkip = page > 0 ? (page - 1) * pageSize : 0;

        // Take only the results you need
        var resultSet = results.Skip(resultsToSkip)
                               .Take(pageSize)

        return View("SearchResults", resultSet);
    }
}

Then your View just needs to iterate through the result set and display the results however you want.

There's probably simpler ways of doing it but I like that you can essentially go anywhere from here, customising the implementation to your current requirements - and still keep the logic in the controller.

You can further simplify this by putting that logic into the Index method and simply allowing the page to be a simple search engine.

Let me know if you get stuck anywhere :)

/Chris