扎克伯格Facebook主页运营:有人帮写稿 有人删评论

Why is Chrome Web Store enforcing on deceptive installation tactics for extensions?

百度 省级先进单位名单:北京市非紧急救助服务中心天津市委办公厅督查室天津市委市政府信访办公室河北省人民政府办公厅山西省委信息综合室(省委社情民意办公室)山西省政府办公厅内蒙古党委督查室内蒙古自治区政府研究室辽宁省委办公厅辽宁省人民政府办公厅吉林省委办公厅吉林省人民政府办公厅浙江省委办公厅浙江省信访局江西省委办公厅江西省人民政府省长手机信箱工作处福建省信访局安徽省委督查室安徽省政府督查室山东省互联网信息办公室山东省委省政府信访局河南省委督查室湖北省信访局湖北省人民政府办公厅湖南省委督查室海南省信访局四川省信访局贵州省委办公厅贵州省人民政府办公厅云南省委省政府信访局西藏自治区党委办公厅信息中心西藏自治区人民政府督查室甘肃省委督查室甘肃省人民政府办公厅青海省委办公厅青海省信访局宁夏回族自治区党委办公厅宁夏回族自治区人民政府办公厅宁夏回族自治区信访局市级先进单位名单:北京市昌平区互联网宣传管理办公室天津市滨海新区信访办公室天津市宝坻区委办公室天津市武清区委督查室天津市静海区行政审批局热线管理办公室石家庄市信息中心秦皇岛市委办公厅邯郸市委社情民意办公室太原市委办公厅太原市人民政府办公厅大同市委办公厅包头市委办公厅沈阳市委督查室大连市委办公厅抚顺市委督查室朝阳市委督查室长春市人民政府办公厅市长公开电话办公室吉林市人民政府市长公开电话办公室合肥市委办公厅合肥市人民政府督查和目标管理办公室淮北市委督查室淮北市人民政府督查室中共淮南市委办公室淮南市市长热线办公室阜阳市委办公室阜阳市人民政府办公室六安市委办公室六安市人民政府办公室亳州市委办公室安庆市委市政府目标绩效督查考核办公室安庆市信访局铜陵市委督查室福州市信访局南昌市委办公厅青岛市委办公厅青岛市人民政府办公厅政务服务热线办公室日照市政务服务中心管理办公室威海市市长公开电话办公室菏泽市人民政府办公室郑州市委督查室郑州市人民政府办公厅濮阳市委市政府督查局平顶山市委办公室平顶山市人民政府办公室新乡市委督查室南阳市委督查室驻马店市委督查室洛阳市委督查室洛阳市110联动办公室商丘市委办公室开封市委市政府督查局开封市人民政府办公室中共安阳市委督查室安阳市长信箱三门峡市人民政府办公室武汉市委办公厅武汉市人民政府督查室孝感市信访局珠海市人民政府办公室南宁市政府督查室南宁市委宣传部南宁市委督查室成都市委市政府信访局南充市委群众工作局自贡市委群众工作局眉山市委群众工作部广安市委群众工作局达州市委宣传部遂宁市人民政府信访局德阳市委群众工作部绵阳市委群众工作局乐山市委群众工作局巴中市委群众工作部宜宾市委群众工作局(宜宾市信访局)贵阳市网格化服务管理指挥调度中心丽江市委市政府信访局西安市委办公厅西安市人民政府办公厅宝鸡市委办公室宝鸡市人民政府办公室铜川市委办公室延安市委督查室咸阳市委、咸阳市人民政府榆林市人民政府办公室兰州市大数据社会服务管理局陇南市委市政府督查考核办公室天水市行政监察投诉中心庆阳市委办公室平凉市督查考核局临夏州委督查室白银市委办公室白银市人民政府信息办公室武威市人民政府西宁市人民政府办公厅乌鲁木齐市委办公厅区县先进单位名单:鸡泽县委群众工作部邯郸市永年区委群众工作部魏县县委群众工作部左云县委办公室大连市普兰店区委员会大连市中山区委沈阳市沈河区督查和绩效考评办公室大连市旅顺口区委办公室太和县委办公室涡阳县委办公室蒙城县委办公室阜南县委肥西县委办公室霍邱县委督查室舒城县机关效能建设工作领导组办公室枞阳县委办公室桐城市委督查室合肥市蜀山区委办公室青岛市黄岛区委区政府莒县政务服务中心管理办公室梁山县社情民意调查受理中心郑州市管城回族区督查办二七区委区政府督查办公室宝丰县委督查室郑州市金水区委督查室汝州市委办公室辉县市委办公室新郑市虞城县委办公室南乐县委县政府督查局永城市委办公室郏县县委县政府督查局范县县委县政府督查局平舆县委县政府督查局唐河县委督查室荥阳市督查办叶县县委办公室中牟县委督查室民权县委办公室武汉市洪山区委办公室深圳市宝安区人民政府成都市金牛区委区政府成都市龙泉驿区成都市双流区委成都市郫都区成都市新都区委区政府成都市青羊区信访和群众工作局成都市锦江区信访和群众工作局金堂县委县政府米易县委群众工作局泸州市龙马潭区委群众工作局剑阁县委宣传部资中县委群众工作局富顺县委群众工作局资阳市雁江区委员会办公室武胜县委群众工作局天全县信访和群众工作局渠县县委宣传部松潘县委群众工作局大竹县网络舆情中心岳池县委群众工作局三台县互联网信息办公室仁寿县委群工部仪陇县委群众工作部巴塘县委群众工作局会东县委群众工作局大方县督办督查局西安市长安区人民政府西安市雁塔区委西安市莲湖区委宣传部西安市未央区委宣传部兰州市城关区委区政府督查室兰州市红古区委宣传部兰州市西固区委宣传部兰州市七里河区委宣传部榆中县委武山县行政监察投诉中心秦安县行政监察投诉中心(杨高宇)

Transparency is critical to ensuring a positive user experience, and developers are accountable for how they market their extensions. Unfortunately, we have seen instances of developers using ads, landing pages, bundled offers, and abusive design patterns to mislead users into installing an extension they may not want or need.

What are some common violations of the Deceptive Installation tactics policy?

Some of the more common violations we see include:

  • Gating advertised features of an extension behind unrelated user action, such as installing other software, or interacting with advertisements.
  • Marketing extensions on typosquatted domains. For example, advertising an extension on googe.com (typo of google.com) with the intent of deceiving users.
  • Abusive design patterns which mislead users into thinking they must first install an extension before continuing to their desired destination.

Are referral pages in scope of this policy?

Yes. Referral pages—web pages that precede an extension's landing page—are considered in scope and must abide by the same disclosure requirements.

What does a compliant "disclosure" consist of?

A compliant disclosure explains to the user what they can expect from your Chrome extension.

A disclosure must include two components, along with any additional information the developer considers necessary for the user.

  • The fact that a user will be installing a Chrome browser extension.

  • What the extension's single purpose is. Content in both the marketing and installation flow of an extension must clearly outline both the principal and significant features of your extension. Burying this information in unrelated text is considered a violation of this policy.

In addition to including these components, the disclosure must comply with the following:

  • Disclosures must be in readable text and utilize contrast to ensure the disclosure is legible. Disclosures in an image or audio form must be accompanied by a text disclosure.

  • The disclosure must be above and clearly associated with the first link or button that leads to the Chrome Web Store.

Additionally, other elements on the referrer page must not mislead the user about the extension's functionality. Images, audio, text or video that imply a functionality that the extension does not provide directly will be considered deceptive, even with a compliant text disclosure.

What is a "misleading interactive element?"

A misleading interaction elicits user engagement (for example, a call-to-action button or form) that implies any outcome other than the installation of a browser extension. An example might be requesting that a user input a tracking ID for a package, but the "Track" button leads to either an extension listing or a landing page for an extension related to package tracking.

Misleading interactive elements are not limited to those that lead to the Chrome Web Store listing. Confusing interactions after a user closes the extension listing are subject to our guidelines.

What are some examples of a compliant Call-to-action (CTA) buttons?

Call-to-action buttons (CTA) cannot be affirmations for irrelevant actions ("Play now," "I'm Human"). All CTAs must explicitly state that an extension is being installed. Here are some examples of compliant CTAs:

  • Install Extension
  • Download Extension
  • Add Extension

What is an "unrelated user action"?

Any interactive elements which require user response or participation, which is not closely related to the primary functionality of the extension, is considered to be an "unrelated user action".

Unrelated user action includes, but is not limited to, requiring users to:

  • Install another app, extension, or other software that is not necessary for the core function of the extension

  • Interact with ads

  • Submit reviews

The following are considered to be related user actions and would be considered compliant:

  • Creating or logging into an account associated with the extension

Can I bundle multiple extensions or offers in the same installation flow?

No. Every extension must have its own, distinct installation flow.

What are the requirements for Chrome Web Store listing windows?

The Chrome listing includes essential information about the extension that the Chrome Web Store is able to review. The window should be sized such that the user can easily review all the content on the extension listing, not just the title and CTA button. Unfortunately, we have seen bad actors make the listing window smaller to trick users into installing an extension.

To comply with this requirement, the referrer page must ensure that the listing window is no smaller than the size of the referrer, and does not have the effect of withholding or hiding extension metadata from the user. Referrer pages cannot utilize distracting elements, such as animations or audio, to interrupt the installation flow.

I comply with Ads policies, do I comply with the Chrome Web Store policy?

Not necessarily. While CWS and Ads policies overlap, they are distinct and impact different components of your extension. It is the responsibility of the developer to comply with both. However, a violation of the Google Ads Misrepresentation Policy or Abusing the ad network does violate Chrome Web Store Developer Program Policies

What if I use affiliates that independently create and advertise my extensions?

Extensions must be marketed responsibly. It is up to the publishing entity to ensure that all parts of your extension and all installation flows are compliant with all Chrome Web Store Developer Program policies. We will remove extensions from the Chrome Web Store irrespective of whether the developer or its contractors or affiliates engage in deceptive installation tactics. Repeated abuse may additionally result in the permanent termination of your publisher account and possibly the termination of any associated publisher account(s).

What happens to an extension found engaging in deceptive installation tactics?

A notification email will be sent to the associated developer account of the extension about the action taken against your extension. Depending on the egregiousness of the deceptive behavior there are different outcomes for your extension:

  • A warning email that deceptive installation tactics for your extension have been identified

  • Immediate removal of the violating extension and disabling of its active user base

  • Repeated abuse may result in the permanent termination of your publisher account and possibly the termination of any associated publisher account(s)

What should I do if I receive a warning email?

Review all of your extension's marketing materials, both developed by you or a 3rd party, for compliance per our program policies. Repeated warnings may result in removal of your extension from the Chrome Web Store, the disabling of your extension's user base, the termination of your publisher account, and possibly the termination of any associated publisher account(s).

Is there a way to appeal this decision?

If you received a warning email or your publisher account was terminated, you can fill out the CWS Support form to receive further clarifications and appeal the decision. To learn more, see the Complaint handling process FAQ.