Google Search Appliance software version 6.0
Posted June 2009
The Google Search Appliance has features that enable system administrators to enhance or personalize the search experience for end users. This chapter provides a quick reference to features, best practices, and Admin Console pages you can use to enhance or personalize the search experience.
The following table lists Google Search Appliance features you can use to enhance or personalize the search experience. For each feature, the table lists the page in the Admin Console where you can use the feature and a reference to a section in this document that describes it.
| Feature | Admin Console Page | Reference |
|---|---|---|
| Alerts, enabling | Serving > Alerts | Enabling Alerts |
| Advanced Search Reporting | Serving > Front Ends > Output Format | Gathering Information about the Search Experience |
| Date biasing | Serving > Result Biasing > Edit | Using Date Biasing |
| Domain filters | Serving > Front Ends > Filters | Restricting Search Results by Domain Name |
| File type filters | Serving > Front Ends > Filters | Restricting Search Results by File Type |
| Filters | Serving > Front Ends > Filters | Using Filters to Restrict Search Results |
| Front ends | Serving > Front Ends | Creating a Front End |
| KeyMatch | Serving > Front Ends > KeyMatch | Using Key Matches to Guide Users to URLs |
| Language bundles | Serving > Language Bundles | Changing Languages for Query Expansion and Spelling Suggestions |
| Language filters | Serving > Front Ends > Filters | Restricting Search Results by Language |
| Meta tag filters | Serving > Front Ends > Filters | Restricting Search Results by Meta Tag |
| Metadata biasing | Serving > Result Biasing > Edit | Using Metadata Biasing |
| My Alerts link, showing | Serving > Front Ends > Output Format | Showing the My Alerts Link |
| OneBox modules, defining or importing | Serving > OneBox Modules | Using OneBox Modules to Integrate Structured Results |
| OneBox modules, selecting | Serving > Front Ends > OneBox Modules | Using OneBox Modules to Integrate Structured Results |
| Page layout helper | Serving > Front Ends > Output Format | Working with the Page Layout Helper |
| Query expansion policy | Serving > Front Ends > Filters | Setting the Query Expansion Policy for a Front End |
| Query expansion, configuring | Serving > Query Expansion | Using Query Expansion to Widen Searches |
| Query suggestions | Serving > Front Ends > Output Format | Providing Query Suggestions |
| Related queries | Serving > Front Ends > Related Queries | Using Related Queries to Suggest Alternative Searches |
| Remove URLs | Serving > Front Ends > Remove URLs | Removing URLs from Search Results |
| Result biasing | Serving > Front Ends > Filters | Working with Result Biasing |
| Result biasing policy, creating | Serving > Result Biasing | Working with Result Biasing |
| Source biasing | Serving > Result Biasing > Edit | Using Source Biasing |
| User-Added Results | Serving > OneBox Modules and Serving > Front Ends > OneBox Modules |
Providing User-Added Results |
| XSLT stylesheet editor | Serving > Front Ends > Output Format | Working with the XSLT Stylesheet Editor |
The following table lists best practices for creating the search experience. For each best practice, the table gives a reference to a section in this document that describes it, as well as the page in the Admin Console that you use to accomplish it.
| Best Practice | Reference | Admin Console Page |
|---|---|---|
| Enable advanced search reporting | Gathering Information about the Search Experience | Serving > Front Ends > Output Format |
| Allow users to choose search results by topic | Using Dynamic Result Clusters to Narrow Searches | Serving > Front Ends > Output Format |
| Restrict search results by domain name, language, file type, or meta tag | Using Filters to Restrict Search Results | Serving > Front Ends > Filters |
| Present recommended links above search results | Using Key Matches to Guide Users to URLs | Serving > Front Ends > KeyMatch |
| Add structured, real-time application data to search results | Using OneBox Modules to Integrate Structured Results | Serving > OneBox Modules and Serving > Front Ends > OneBox Modules |
| Provide your own synonyms for use in query expansion | Using Query Expansion to Widen Searches | Serving > Query Expansion |
| Set the query expansion policy for a front end | Setting the Query Expansion Policy for a Front End | Serving > Front Ends > Filters |
| Install and activate a language bundle | Changing Languages for Query Expansion and Spelling Suggestions | Serving > Language Bundles |
| Present alternative search terms above search results | Using Related Queries to Suggest Alternative Searches | Serving > Front Ends > Related Queries |
| Prevent specific URLs from appearing in search results | Removing URLs from Search Results | Serving > Front Ends > Remove URLs |
| Influence the order of documents in search results | Using Result Biasing to Influence Result Ranking | Serving > Result Biasing |
| Enable or disable result biasing for a front end | Working with Result Biasing | Serving > Front Ends > Filters |
| Identify problematic query topics for related queries, KeyMatches, and query expansion synonyms | Analyzing Searches that Do Not Return Results | Status and Reports > Search Report |
| Create a user interface that focuses on your users | Customizing the User Interface | Serving > Front Ends > Output Format |
| Divide the search index into meaningful partitions | Segmenting Data in the Search Index | Crawl and Index > Collections |
| Enable users to set up alerts | Providing Alerts for End Users | Serving > Alerts |
| Enable users to add search results for certain keywords in a specific front end | Providing User-Added Results | Serving > OneBox Modules and Serving > Front Ends > OneBox Modules |
| Enable search queries to auto-complete and query suggestions to appear as a user types in the search box. | Providing Query Suggestions | Serving > Front Ends > Output Format |
The following table lists search appliance Admin Console pages that are used to create the search experience. For each Admin Console page, the table provides a reference to a section in this document that describes using the page.