1<h1>Extensions Quality Guidelines FAQ</h1> 2 3<h2 id="one">1.) What is the new policy?</h2> 4 5<p> 6To maintain the quality of the Chrome user experience, 7we recently launched a new policy requiring Chrome extensions 8to have a single purpose. 9We are also introducing the new 10<a href="http://blog.chromium.org/2014/03/protecting-user-settings-on-windows.html">Settings Override API</a> 11to allow extensions to manage important Chrome settings on Windows. 12Beginning with the July release of Chrome, 13the Settings Override API will be the only approved path 14for offering settings changes to Chrome users on Windows. 15In addition, starting with the May 20, 2014 release of Chrome, 16we <a href="http://blog.chromium.org/2014/02/make-sure-to-get-your-extension-in.html">have begun to require</a> 17that extensions in Chrome for Windows be hosted in the Chrome Web Store. 18</p> 19 20<h2 id="two">2.) Why did Google launch a “single purpose” Chrome extensions policy?</h2> 21 22<p>For an overview of the policy announcement, please read this 23<a href="http://blog.chromium.org/2013/12/keeping-chrome-extensions-simple.html">Chromium blog post</a>.</p> 24 25<p>We launched this policy because 26multi-purpose extensions can crowd your browser UI 27and slow down your web browsing - sometimes significantly. 28Speed and simplicity have always been part of Chrome's core principles, 29so this policy will help us get back to the design that was originally intended. 30Also, unexpected changes to browser functionality and 31settings have become the number one user complaint for Chrome users, 32and this policy helps minimize the problem by ensuring 33that users understand what extensions are doing. 34</p> 35 36<h2 id="three">3.) Where can I find the “single purpose” policy?</h2> 37 38<p> 39Please refer to the 40<a href="https://developer.chrome.com/webstore/program_policies?csw=1#extensions">Extensions Quality Guidelines</a> 41section of the Chrome Web Store Developer Program Policies. 42</p> 43 44<h2 id="four">4.) What does “single purpose” actually mean?</h2> 45 46<p> 47“Single purpose” can refer to one of two aspects of an extension: 48</p> 49 50<p> 51An extension can have a single purpose limited to a narrow 52<strong>focus area or subject matter</strong> 53(for example, news headlines", "weather", "comparison shopping"). 54If the extension has a narrow focus area or subject matter, 55then it can offer various functions related 56to that focus area or subject matter. 57For example, a news headlines extension could have a browser action button 58that allows users to see news stories and replace the new tab page 59with news-only content, 60so long as all of those functions are narrowly focused 61on the news headline focus area. 62</p> 63 64<p> 65Or, an extension can have a single purpose limited 66to a narrow <strong>browser function</strong> 67(for example, "new tab page", "tab management", or "browser history"). 68If the extension is implemented in a single function, 69then it can offer content or features related to different areas or subjects. 70For example, an extension that replaces the new tab page could offer 71multiple unrelated features on the new tab page 72(for example, weather forecast, news headlines, search engine, and so on), 73but it can’t also provide a browser action button, 74change the browser’s homepage, or 75make any other changes to browser functionality. 76</p> 77 78<h2 id="five">5.) Will this policy affect my extension?</h2> 79 80<p> 81It depends. 82Particularly if your extension offers multiple features, 83please make sure that it has a single purpose. 84Ask yourself these questions: 85</p> 86 87<ul> 88 <li>Does my extension have a narrow focus area 89 or a narrow function as described above?</li> 90 <li>If my extension has a narrow focus area, 91 are all of the features directly related to that single purpose?</li> 92 <li>If my extension has multiple features, 93 does it only affect a narrow function of the browser?</li> 94 <li>Does my extension modify Chrome’s behavior in a predictable way, 95 in line with the extension's narrow, stated purpose?</li> 96</ul> 97 98<p> 99If you’re unsure, you can email 100<a href="mailto:chromewebstore-policy@google.com">chromewebstore-policy@google.com</a> 101with your extension ID, 102and we’ll take a look and try to provide feedback within a week. 103If your extension does not have a single purpose, 104then you will need to remove functionality 105or split your extension into different extensions. 106</p> 107 108<h2 id="six">6.) What will happen 109if I don’t make my extension compliant with this policy?</h2> 110 111<p> 112If you created your extension after December 19, 2013, 113your extension will not be permitted in the Chrome Web Store. 114If you created your extension prior to December 19,2013, 115your extension may be removed from the Chrome Web Store starting July 22, 2014, 116although you will still be able to update the extension and file appeals. 117Please keep in mind that 118your re-published item will not be immediately published live in the store. 119The re-published item will undergo a compliance review 120before it can be restored. 121</p> 122 123<p> 124In order to minimize disruption for users, 125we recommend that you take a moment to carefully review your extensions 126and make necessary updates as soon as possible. 127You can email us at 128<a href="mailto:chromewebstore-policy@google.com">chromewebstore-policy@google.com</a> 129with your extension ID, and we’ll try to provide feedback within a week. 130</p> 131 132<h2 id="seven">7.) Can my extension make changes to the start page, 133homepage, and new tab settings?</h2> 134 135<p> 136Yes. 137If the purpose of your extension is to modify one narrow function 138of the browser (either the start page, homepage or new tab page, for example), 139and it does only that, then it would be compliant with the single-purpose policy. 140Additionally, if the purpose of your extension is limited 141to one focus area or subject matter, 142then you can have various functions related to that one area or subject matter, 143including changes to start page, homepage and new tab page. 144</p> 145 146<p> 147Beginning with the July release of Chrome, 148the only way to programmatically change the homepage, search provider, 149and startup page settings in Chrome on Windows will be via an extension 150that uses the Settings Override API. 151Where more than one extension modifies these Chrome settings, 152the most recently installed extension will manage the settings it has modified 153via the Settings Override API. 154Extension developers can modify the new tab page 155(and a few other Chrome pages) using the same 156<a href="https://developer.chrome.com/extensions/override">override method</a> 157as before. 158</p> 159 160<p> 161In addition, 162if you want to publish an extension that modifies Chrome settings, 163you must either control any domains you wish to set in any changed browser settings 164or redistribute an extension created by the entity that controls those domains. 165For example, you could distribute an extension that changes the homepage 166to wikipedia.org if the Wikimedia Foundation originally created and 167published the extension in the Chrome Web Store, 168and gave you the right to distribute it. 169</p> 170 171<p> 172Please see this 173<a href="http://blog.chromium.org/2014/03/protecting-user-settings-on-windows.html">Chromium blog post</a> 174for more information. 175</p> 176 177<h2 id="eight">8.) Can my extension make changes to the default search settings?</h2> 178 179<p> 180Yes. 181If the only purpose of the extension is to change the default search settings, 182then it would be compliant with the single purpose policy. 183Additionally, 184if the single purpose of your extension is search as the narrow focus area, 185and nothing else, then you can offer various functions related to search, 186including changes to default search settings. 187</p> 188 189<h2 id="nine">9.) How will users be notified of settings changes in new versions of Chrome?</h2> 190 191<p> 192If an extension changes Chrome settings via the Settings Override API, 193the user will be notified of the settings changes prior to installation, 194when they encounter the settings change for the first time, 195and via an indicator next to each changed setting on the Chrome settings page. 196From these notifications, 197users will have the option to reverse the settings changes 198by disabling the extension. 199</p> 200 201<h2 id="10">10.) What happens to settings when an extension is disabled?</h2> 202 203<p> 204All Chrome settings changed by an extension will be reverted 205when that extension is disabled. 206All other settings 207(for example, those changed directly by a Windows binary) 208will remain unchanged. 209</p> 210 211<h2 id="eleven">11.) Will users’ existing homepage, search provider or 212startup pages be affected by the introduction of the Settings Override API?</h2> 213 214<p> 215No. 216A user’s existing homepage, search provider or startup settings will 217remain unchanged by the introduction of Settings Override API. 218Following the launch of the Settings Override API, 219only extensions can programmatically change these settings and 220only through the Settings Override API. 221But all changes to a user’s homepage, search provider or 222startup pages made prior to the launch of the Settings Override API, 223including any that may have been made by Windows binaries, 224will remain unchanged until the user manually updates those settings or 225installs an extension that uses the Settings Override API to change them. 226</p> 227 228<h2 id="twelve">12.) Is this new policy Windows-only?</h2> 229 230<p> 231The <a href="https://developer.chrome.com/extensions/hosting_changes">requirement</a> 232that Chrome extensions be hosted in the Chrome Web Store 233initially applies only to Windows extensions. 234Likewise, the new Settings Override API will initially be made available 235only on Chrome for Windows. 236However, the single-purpose policy will apply to all Chrome extensions. 237</p> 238 239<h2 id="thirteen">13.) Does this policy apply to Chrome apps too?</h2> 240 241<p> 242At this time, Chrome apps (as distinguished from extensions) 243are not required to be distributed through the Chrome Web Store, 244or to have a single purpose. 245Chrome apps are currently not capable of changing Chrome settings. 246</p> 247 248<h2 id="fourteen">14.) Can I bundle ad injection with some other type of functionality?</h2> 249 250<p> 251No. 252This violates the single purpose policy. 253However, if injecting ads is the single purpose of the extension and 254the extension is otherwise compliant with Chrome policies, 255then it would be acceptable. 256For example, a “related articles” extension that adds sponsored links 257to articles related to a page the user is visiting would be compliant 258with the single purpose policy because it has a single purpose limited 259to a narrow function of the browser. 260You also might want to explore the other monetization options described 261<a href="https://developer.chrome.com/webstore/money">here</a>. 262</p> 263 264<h2 id="fifteen">15.) Are toolbars permitted under this policy?</h2> 265 266<p> 267It depends on what the toolbar does. 268As described in 269<a href="#four">answer #4</a>, 270it must adhere to the narrow single purpose of the extension. 271Broad, multi-purpose toolbars are not allowed and 272toolbars that are implemented using content scripts 273to inject UI into every page are not recommended because 274they slow down every page load, clutter the UI, 275and can lead to security problems for users. 276Instead, consider using a 277<a href="https://developer.chrome.com/extensions/browserAction">browser action popup</a>, 278which was designed to solve this very problem. 279It's a better user experience, with no performance or security downsides. 280</p> 281 282<h2 id="sixteen">16.) What will happen to non-compliant extensions 283that were already installed by users?</h2> 284 285<p> 286All extensions will need to comply with the Extension Quality Guidelines. 287If a user installed a non-compliant extension, 288then you will need to update them to a compliant extension 289that is hosted in the Chrome Web Store. 290If the user is not updated to a compliant extension 291that is hosted in the Chrome Web Store, 292then the extension will be automatically disabled. 293As noted above, 294any settings or behaviours controlled by the extension, 295including any settings controlled by the Settings Override API, 296will be reverted when the extension is disabled. 297You can find more information 298<a href="http://blog.chromium.org/2014/02/make-sure-to-get-your-extension-in.html">here</a>. 299</p> 300 301<h2 id="seventeen">17.) If my extension is rejected from the Chrome Web Store 302because it doesn’t comply with the single purpose policy, 303what will happen after the requirement to host extensions 304in the Chrome Web Store comes into effect?</h2> 305 306<p> 307If your extension is rejected from the Chrome Web Store, 308you will need to make changes or appeal the decision. 309After the requirement to host extensions 310in the Chrome Web Store comes into effect in late May 2014, 311your extension must be hosted in the Chrome Web Store or 312it will be automatically disabled from the users’ browsers. 313</p> 314 315<h2 id="eighteen">18.) If my extension gets flagged for review under the single purpose policy, 316what will happen?</h2> 317 318<p> 319Our team will review it, 320and it may be removed from the Chrome Web Store. 321You’ll have a chance to make changes and appeal the decision. 322As noted above, 323if you created your extension before we announced the policy on December 19, 2013, 324you have until July 22, 2014 to make changes. 325If your extension was created after the policy was announced, 326it needs to be compliant now. 327You can temporarily unpublish it and contact us at 328<a href="mailto:chromewebstore-policy@google.com">chromewebstore-policy@google.com</a> 329with your extension ID if you’d like feedback. 330We’ll try to respond within a week. 331</p> 332 333<h2 id="nineteen">19.) I need help. Who should I contact?</h2> 334 335<p> 336You can email 337<a href="mailto:chromewebstore-policy@google.com">chromewebstore-policy@google.com</a> 338with your extension ID, 339and we’ll take a look and try to provide feedback within a week. 340This is a lightweight review intended to give you an indication 341of whether your extension will comply with the new policy. 342</p> 343 344<h2 id="appendix">Appendix: Examples of extensions that comply with the quality guidelines</h2> 345 346<p> 347An extension that adds features to Chrome’s browser history. 348All of the features are contained in a single browser function. 349</p> 350 351<img src="{{static}}/images/history-extension.png" 352 width="680" 353 height="385" 354 alt="Image of browsing history extension"> 355 356<p> 357An extension with a single subject matter: 358It provides dropdown information about the weather. 359Because it is focused on one type of content, 360this extension could also change browser settings, like the new tab page, 361where the extension displays weather conditions and offers a weather search. 362</p> 363 364<img src="{{static}}/images/extension.png" 365 width="680" 366 height="425" 367 alt="Image of weather extension"> 368 369<img src="{{static}}/images/search-extension2.png" 370 width="680" 371 height="425" 372 alt="Image of weather extension showing new tab page"> 373 374<p> 375A search extension. 376It has multiple features, including this dropdown, 377but all of them are related to the narrow subject matter of search. 378</p> 379 380<img src="{{static}}/images/extension2.png" 381 width="680" 382 height="425" 383 alt="Image of search extension"> 384 385