Google Search Appliance Creating the Search Experience - Manual (Page 22)

Google Search Appliance: Creating the Search Experience Introduction 22
Refining Search Results
Enterprise content often contains information that is not appropriate for serving to all end users.
For example, enterprise content may contain sensitive documents that are appropriate for members of
an organization to view, but not for consumers to view. To ensure that the search appliance serves
appropriate results to end users, you can create filters that prevent the sensitive data from appearing in
search results for a particular front end. In this situation, you would probably create a meta tag filter.
The search appliance includes built-in filters for:
• Duplicate snippets
• Duplicate directories
These filters apply to the entire search index. For an overview of these filters, refer to “Built-In Elements”
on page 27. You can also create filters for specific front ends results based on:
• Language
• Domain
• File type
Unlike Query Expansion and OneBox Modules, filtering is not based on keywords in the search query.
The search appliance filters all results for all end users of a particular front end.
To create filters for a front end, use the Serving > Front Ends > Filters page. For complete information
about the Filters page, click Help Center > Serving > Front Ends > Filters in the Admin Console.
For more information about filters, refer to “Using Filters to Restrict Search Results” on page 54.
Removing Specific URLs from Results
Occasionally, a search index contains URLs that the search appliance should not serve to some or all
end users. For example, an administrator has added jump pages, which are just lists of URLs, to the
enterprise content for the purpose of getting unlinked URLs into the search index. The administrator
wants to keep these jump pages in the search index, but does not want to serve the jump page URLs to
end users. Other examples of URLs that administrators might want to prevent serving include URLs that
are out-of-date and URLs that contain sensitive data.
You can prevent the search appliance from serving URLs that match specific patterns. Take note
that specifying a long list of patterns can cause increased latency at serve time. Because you remove
URLs from results for a front end, you can remove them for specific types of end users.
To specify URLs to remove from results for specific front ends in the Admin Console, use the Serving >
Front Ends > Remove URLs page. For complete information about the Remove URLs page, click Help
Center > Serving > Front Ends > Remove URLs in the Admin Console.
For more information about removing URLS, refer to “Removing URLs from Search Results” on page 57.
Removing URLs from the Search Index
The remove URLs feature affects results only. It does not remove URLs from the search index. To
remove URLs from the search index, enter them in the Do Not Crawl URLs with the Following
Patterns section on the Crawl and Index > Crawl URLs page in the Admin Console. For more
information about removing URLs from the index, refer to Administering Crawl.