Unclear Policy of Spam and Placement in the Store

271 views
Skip to first unread message

SmartyList

unread,
Nov 29, 2019, 1:54:14 AM11/29/19
to Chromium Extensions, bnak...@gmail.com, chromium-...@chromium.org, chromewebstor...@google.com, chromewebs...@google.com, chromewebst...@google.com
Hi,

My ambitious and innovative project and its extension SmartyList (http://bit.ly/SmartyListApp) having tough time in getting it published and I am wasting to lots of efforts in trying to justify again and again to Chrome dev team.

My last subsequent packages were rejected to publish stating it is against "Spam and Placement in the Store" which states:
* Do not use irrelevant, misleading, or excessive keywords in item descriptions, titles, or metadata.
* Please ensure that your item has a description that clearly and directly relates to its functionality.

In email they say “Do not use irrelevant, misleading, or excessive keywords in app descriptions, titles, or metadata”.  It is not making any sense because my latest package contains the minimal information for the users as below:



Manifest.json:
Title: “SmartyList”
Description: “Helps you save favorite information and links in an awesome and interactive way.”



App’s Dashboard Description:
 “SmartyList is an innovative information shortlisting tool live on the websites intuitively as a Universal List, and are accessible across other websites as one common list. \n\n Currently, it works on Amazon, Ebay, Facebook, Twitter, Instagram, Linkedin, Youtube, Pinterest, and few more as listed here at http://smartylist.com/platforms.html. \n\n  Why it requires read/write access?
Because it needs to process the content directly on your site and then writes/displays Shortlist buttons and its UI panel. \n\n For use cases, screenshots, demos, help or FAQs, visit - https://smartylist.com/links.html

Other extension which seem to have no objection on the same policy, why and how?

So, can you please answer these and help me out publishing it?

1. What keywords do you think irrelevant, misleading, or excessive?
2. What part of description is not clear and not related to functionality?
3. Why can’t your review team be specific to the issue with exact details, instead of relaying on your abstract policies?
4. Can you define or document some where about the definition and examples of irrelevant, misleading, or excessive keywords?
5. How do you prevent this kind of inefficient reviews from your team going forward?

Please respond me in same order or questions, and let me know when you can review my latest package and approve it if you find everything is good, if not please let me know the specific action item that I can take care of and let the developer community learn and follow it going forward.

Thanks

Dream Kuang

unread,
Dec 3, 2019, 8:06:35 PM12/3/19
to Chromium Extensions
I encountered the same response, and I have no idea how to modify the plugin.
very bad experience, :(
Message has been deleted

Dream Kuang

unread,
Dec 4, 2019, 3:37:38 AM12/4/19
to Chromium Extensions
Hi,

here is my extension.


and the new version I update the description. but rejected. :(

Emoji for Youtube Comment allows you input emojis on the youtube comment.
Emoji for Youtube Comment allows you input emojis on the youtube comment. Emoji for Youtube Comment have 600+ Emoji's for free and 2800+ Emoji's for pro.

Upgrade pro version to get 2800+ emojis.

Emoji Categories support:
* Frequently Used (free)
* Smileys & People (free)
* Animals & Nature (pro)
* Food & Drink (pro)
* Activity (pro)
* Travel & Places (pro)
* Objects (pro)
* Symbols (pro)
* Flags (free)


On Wednesday, 4 December 2019 16:26:57 UTC+8, Simeon Vincent wrote:
SmartyList, I just took a quick look at your extension's listing. The thing that looks like a violation to me is that you've listed the sites the extension works on twice; that seems like a good candidate for violating the "excessive keywords" part of the policy to me. The "Currently it supports following major platforms" section is especially odd as it presents URLs (generally all lower case) in title case.

Dream Kuang, if you share you extension ID I may be able to provide some additional guidance.

Cheers,

Simeon - @dotproto
Extensions Developer Advocate

Simeon Vincent

unread,
Dec 4, 2019, 8:10:40 PM12/4/19
to Chromium Extensions
Dream, I'm going to follow up directly with you.

Simeon - @dotproto
Extensions Developer Advocate

Simeon Vincent

unread,
Dec 4, 2019, 8:14:16 PM12/4/19
to Chromium Extensions
Whoops, I accidentally deleted my reply. Re-posting…

SmartyList, I just took a quick look at your extension's listing. The thing that looks like a violation to me is that you've listed the sites the extension works on twice; that seems like a good candidate for violating the "excessive keywords" part of the policy to me. The "Currently it supports following major platforms" section is especially odd as it presents URLs (generally all lower case) in title case.

Dream Kuang, if you share you extension ID I may be able to provide some additional guidance.

Cheers,

Simeon - @dotproto
Extensions Developer Advocate


On Tuesday, December 3, 2019 at 5:06:35 PM UTC-8, Dream Kuang wrote:

SmartyList

unread,
Dec 11, 2019, 8:04:54 AM12/11/19
to Chromium Extensions, bnak...@gmail.com, chromium-...@chromium.org, chromewebstor...@google.com, chromewebst...@google.com, chromewebs...@google.com
Thanks Simeon for the review.

But you have checked or referred to the previously (v1.1.4) published extension's details, NOT the latest package submitted.  I have fixed them in my latest package (ver 1.1.7) and submitted for review, including shortening the extensions' description in the dashboard, and also replaced the keywords of website links from "Amazon.com, Facebook.com" to just "Amazon, Facebook, etc.", because it is necessary for the users to know where this extensions really works, unlike other extensions that works on every other domains.  There is absolutely no intention to add more keywords, but to state the scope of the extension honestly to the users where it really work.

Please check the attached screenshot "smartylist-ext-screenshot.png", and confirm my changes.  If everything is fine, please either publish the latest (v1.1.7) package uploaded or let me push new package version 1.1.8 and publish it asap.

This is the only help I need to close on this thread.
smartylist-ext-screenshot.png

Aruna Janapati

unread,
Dec 24, 2019, 4:34:52 AM12/24/19
to Chromium Extensions, bnak...@gmail.com, Chrome Web Store Developer Support, chromewebst...@google.com, chromewebs...@google.com
Can you please respond?  I am holding my latest package in the dashboard pending with many important features.

--
You received this message because you are subscribed to a topic in the Google Groups "Chromium Extensions" group.
To unsubscribe from this topic, visit https://groups.google.com/a/chromium.org/d/topic/chromium-extensions/3bMZVW8aGO8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/edb70bf9-11f0-41f5-9a52-090f72b42e98%40chromium.org.

Aruna Janapati

unread,
Jan 2, 2020, 3:29:39 AM1/2/20
to Chromium Extensions, bnak...@gmail.com, Chrome Web Store Developer Support, chromewebst...@google.com, chromewebs...@google.com
Can you please respond? It's been pending close a month now.  I have made all changes as per policy, mostly description and keywords related, and rest of the details are clearly explained in my previous message.

Please approve it asap.

On Wed, Dec 11, 2019 at 6:35 PM SmartyList <draru...@gmail.com> wrote:
Reply all
Reply to author
Forward
0 new messages