Chrome Extensions Guidelines

This document outlines the specific requirements & guidelines for the use of the Search API and/ or Search URL licensed to you by CodeFuel as within your extension implementation. These requirements & guidelines do not replace or derogate from any of your obligations in the agreement you signed with CodeFuel; but are intended to provide guidance as to high level do’s and don’ts for Extension(s) on the Chrome Webstore (“CWS”).

The Publisher’s Compliance Guidelines* dated December 2, 2014 and the API Guidelines, where applicable to you, are an integral part of this document. If you have any questions regarding any of these Guidelines, please contact your account manager at CodeFuel.

These guidelines are not an exhaustive list and CodeFuel is entitled to use its discretion when evaluating your website/ application and may replace/edit/expand the guidelines at any time. For further information on how to integrate your product with CodeFuel please reference the corresponding integration guidelines provided by your account manager.

CWS guidelines

Google issued several guidelines regarding extensions on the CWS. It is your responsibly to keep yourself up-to-date with any Google releases, updates, new rules and guidelines. Good resources include (but are not limited to) Google Blog and Google developer’s sites: https://developer.chrome.com/extensionshttps://developer.chrome.com/webstore/program_policies and more.

The descriptions below (in this chapter) is a non exhaustive list, and merely reflects our interpretation to these guidelines:

  1. The publisher’s site/ app must conspicuously display accurate contact information, such as: company name, physical address, phone number and email address, About Us page and publisher’s privacy policy.
  2. The site/ app must comply with Bing Ads User Safety and Privacy Guidelines.
  3. Please note that if the source of your traffic is related to downloadable products, your API implementation must also comply with the Bing Software and Downloads guidelines.

Restriction on activities

  1. Extensions on CWS can only change the user’s search settings via the official Google setting override API.
  2. Single purpose: Extensions on CWS are limited to a single purpose (for example: weather extension). Extensions that provides search or change the user’s search setting, can change only the following settings:
    1. One search assets (setting) only: if the extension comprised of a non search purpose, it can only change one search setting (e.g.: a weather extension can change the user’s NT only).
    2. Multiple search assets: provided that the only purpose of the extension is search, it can change multiple settings (for example: an extension that changes both Newt Tab and provide search from the Omnibox/Default search, and whose sole purpose is to provide these search assets. However, please note that if an extension provides search to both New Tab and Default Search, AND provides weather data, this would not be considered as an extension that meets the guidelines).
  3. Extension must present on the CWS description page a link to its privacy policy. The privacy policy must disclose, among other information, a description of the extension’s data collection practices.
  4. Resizing browser windows without the user’s informed consent is prohibited.
  5. Disabling back buttons, or otherwise interfering with a user’s ability to navigate is not permitted. You must use a clear indication to enable the user to close the browser or any interface window.
  6. An extension cannot collect browsing activity UNLESS it complies with the following:
    1. It is described on the CWS page
    2. The collection of the web browsing activity is done only to the extent required for a user facing feature.

General Do’s and Don’ts

  1. The Extension must not change the user’s search settings or offer any functionality without the user’s explicit consent. Such functionality must be disclosed on the first download interaction with the user (for example: on CWS page, and if the installation occurs from another resource, such as a landing page, it needs to be disclosed on the landing page).
  2. The user MUST be able to modify settings manually from the chrome://settings page, under the following sections: ‘On startup’ ; ‘Appearance’ and ‘Search’ (see images below)
    It is also highly recommended to allow the users to modify settings manually from the extension’s browser action.
  3. A link to the privacy policy must appear on the CWS description page.
    You must provide an explanation to the user on how to uninstall the extension. It is highly recommended to provide the users the ability to access uninstallation (or instructions on how to uninstall) from the extension’s browser action.
  4. TOU/ EULA should describe:
    1. The extension and its value to the user
    2. Which resets are being requested (homepage /New Tab/ Default Search/ All three) and what product offerings are prompting these resets
    3. An explanation on how user can modify settings manually.
  5. A Search product distributed with Yahoo search CAN NOT be offered if the user’s homepage/ new tab and/or default search is already set to Yahoo.com or any other Yahoo search domain (e.g. search.yahoo.com), unless explicitly approved otherwise.
  6. Any change to the user’s search settings (including homepage resets, default search sets and new tab offerings) without the user’s explicit consent- is prohibited
  7. Prompting additional offering dialog after the user has declined the offering for a same extension is not allowed.
  8. Disabling or altering any software on a user’s computer without user consent- is prohibited
  9. Disabling the ability of users to change the default search service selections effectuated by Chrome resets and home page resets – is not allowed
  10. Using the Web Search Provider’s logo (Bing/ Yahoo) is prohibited.
  11. The extension (including its promotion, distribution, domain name, and any part thereof), must not violate any intellectual property or other proprietary rights.


Your extension may be distributed by one or more of the following ways: Landing Page, bundled with other software, banner (ad), or on the CWS.

Landing Page

Any ad unit should be labeled as follows:

  1. A landing Page of an extension must clearly explain what the extension is, including its name, key functionality, main effects on the user’s computer, and whether it includes other monetization methods.
  2. The LP must include links to the extension’s privacy policy, TOU/ EULA, and contact information and ‘About Us’ page.

Offer screen

  1. Each offer screen should provide users with a clear way to accept or decline the offer.
  2. The presentation of the ‘accept and decline’ options within an offer screen shall be of equal prominence.
  3. An offer screen must have the brand of the extension offered in the screen and must not mislead the user as to which product is actually being offered.
  4. The name of the product shown in the offer screen during the installation must be identical to the product name in the OS, browser libraries and removal dialogs, as applicable.
  5. If the bundle has more than one bundled product, then there must be a ‘skip’ option.
  6. Each bundled product should be clearly marked as optional and/or promoted content. For example:
    • Additional offer
    • Promotional offer
    • Optional offer
    • Advertisement
    • Promoted content
  7. For more information on bundling guidelines -see Bundling and Integration Guidelines.

Homepage/ New Tab Pages:

  1. Must include clear and prominent branding of the extension owner. (A copyright notice is not considered as branding).
    1. In some cases, and subject to CodeFuel prior approval, the extension’s brand/ logo can be used (instead of the publisher’s brand).
    2. Branding must be consistent throughout user experience, reset offers, install flow and in settings.
  2. Must include working links to About Us, Privacy Policy, EULA/ TOU and Contact Information.
    Company contact must include: physical address, phone number and email.
  3. Global requests must adhere to local language requirements for international markets.
  4. You must enable the user to turn off or disable the extension features (favorite buttons/ icons) from the New Tab and transform its New Tab to a simple plane page without the additional features.
  5. Any use of a ‘trending now’ feature is subject to CodeFuel’s prior approval.
  6. You should include a clear call to action near or in the searchbox (e.g. ‘Search’. However, you may not use the name of the Web Search Provider, e.g. ‘search with Yahoo’ is not allowed).

Homepage/ New Tab Pages:

For special requirements and guidelines regarding Customized/ Hosted SERP – please see the relevant section in the Search API Guidelines.