このページは大阪弁化フィルタによって翻訳生成されたんですわ。

翻訳前ページへ


Branding Guidelines
The Wayback Machine - http://web.archive.org/web/20110822223611/http://desktop.google.com:80/dev/brandguide.html
Google Desktop Search
 Google Branding Guidelines

For Users
  Download Plug-ins
  Google Desktop Forum

For Developers
  SDK Overview
  Download SDK
  Submit Software
  Developer Forum

Guidelines for integrating Google™ Desktop Search API with your application

Thank you for choosing to become a Google partner. This document is intended for developers integrating a Google Desktop search box and/or search results into their application. This document does not apply to plug-ins that only index new content. We have provided guidelines on how layout, branding, and Google attribution should be handled by your application. If you have any questions regarding these policies, please feel free to contact desktop-feedback+apis@google.com.

Adherence to these guidelines is required prior to the launch of your Google Desktop Search API-integrated application. Please note that your application must also adhere to Google’s Software Principles (http://www.google.com/corporate/software_principles.html).

1. Search Box

2. Google Desktop Search results

1. Search Box

1.1 Labeling the search box

The Google Desktop search box may appear anywhere in your application or page, but there are very specific rules for how it should appear and when it may be used.

If the default search is querying Google Desktop, then the Google Desktop favicon (Google Desktop Search favicon) must be displayed next to the search box (to its left, inside it, or to its right).

Search box

If Google desktop is not the default search, then neither the Google Desktop logo nor any other Google branding should be placed next to the search box.

Search box menu

1.2 Search box menu options

Filetype Restricted Searches

This section applies if your application invokes Google Desktop search results limited to a particular application or subset of applications. If, for example, your application displays only gif files in the search results, please follow these requirements:

  • Search box must provide unrestricted Google Desktop search
    If a search box provides limited Google Desktop searches, such as a search for a predetermined file type, the search box must also contain an option for regular Google Desktop searches.
  • Search box must provide Google WebSearch
    Search boxes that query Google Desktop search must also include an option to search the web using Google WebSearch. Google WebSearch results must be displayed in a browser.
2. Google Desktop search results

Separate and distinct requirements apply to the display of Google Desktop search results in a browser and in applications other than the browser.

2.1 Non-browser display

If you are displaying Google Desktop search results in an application other than a web browser, the following guidelines apply.

Favicon and results header

The results must be titled "Results from Google Desktop Search." The favicon (Desktop Search icon) must be displayed directly to the left or right of the title.

Link to Google WebSearch

The results must contain a conspicuous link to Google WebSearch. The link should be pre-populated with the user’s query and read "Search the web for [user’s query]".

Search Result Ordering

Google Desktop search results are provided to developers via an XML feed. You may integrate the results into a page or application as you see fit, but Google requires that the ordering of the results defaults to Google Desktop’s default sequence (sort-by-date). If your application contains functionality to permit the user to change the default sort order, then the application should also contain an option for resetting the default sort to Google Desktop’s default sort.

Non-browser implementation

2.2 Web browser display

If you are displaying Google Desktop search results in a web browser, the following guidelines apply.

Search Results header

A header must be displayed above the Google Desktop search results containing the following elements:

  • The Google Desktop logo
  • A link to Google WebSearch results, containing the user’s query. If clicked, the link will open a browser page with Google WebSearch results.
  • The Title – "Results from Google Desktop Search."
  • The number of results displayed and the estimated number of matching results with bolding for the figures. Standard formatting would be: "1 - 10 of about 9,240."
  • The length of time the search took, in parenthesis with bolding for the figure. Standard formatting would be: "(0.09 seconds)"
  • Sort options – Links to display the results according to relevance or date.

The format of the text for languages that are written and read from left-to-right (such as English, German, and other common languages) should be right justified in the header. For languages that are written and read from right-to-left (such as Hebrew and Arabic), the format of the text should be left justified.

Partner Logo Location

Your logo or identification may appear beneath the results header, and/or at the bottom of the results page.

"Enhanced by" identification

To avoid user confusion, when adding a partner label or identification to the results page, the text should include "Enhanced by".

Web browser implementation

Search Results Elements
  • Ordering cannot be changed
    Google Desktop search results are provided to developers via an XML feed. You may integrate the results into a page or application as you see fit, but Google requires that the ordering of the results defaults to Google Desktop's default sequence (sort-by-date). If your page contains functionality to permit the user to change the default sort order, then the application should also contain an option for resetting the default sort to Google Desktop's default sort.
  • Required Elements
    All elements from the XML feed, such as those listed below, must be displayed:
    • The result title which includes descriptive text and serves as a hyperlink to the result.
    • The snippet which displays dynamically generated fragments of text from the relevant result. This information helps users better predict if that result will answer their question before clicking the result link.
    • The cached link which provides customers with the ability to access a snapshot of a particular result as it looked when Google Desktop search crawled it (particularly useful if a file has been removed).

Query terms must be bolded whenever they appear in any element (e.g. result title, snippet, description) of all results in order to improve the customer experience. This will happen automatically in the feed received from Google Desktop search.

Search result footer

  • Required Elements
    All elements from the XML feed should be displayed.
Other content

If Google Desktop search results appear on a page in conjunction with other content, then a visual separation must be made between the other content sections and the search results. The layout should clearly identify which elements are unedited Google Desktop search results and which are other content.