Violation of Chrome Web Store policies (law). Keyword spam. 30 extensions.

Kempe

unread,

Mar 27, 2023, 12:16:58 AM3/27/23

to Chromium Extensions

Hello,

Chrome Web Store policies

https://developer.chrome.com/docs/webstore/program-policies/listing-requirements/

Keyword Spam is the practice of including irrelevant or excessive keywords in an extensions description in an attempt to manipulate its ranking, resulting in a spammy, negative user experience. We don't allow extensions with misleading, improperly formatted, non-descriptive, irrelevant, excessive, or inappropriate metadata, including but not limited to the extension's description, developer name, title, icon, screenshots, and promotional images. Developers should focus on providing a clear and well-written description that uses keywords appropriately and in context.

Some examples of Keyword Spam include:

- Lists of sites/brands/keywords without substantial added value

- Lists of regional locations

- Unnatural repetition of the same keyword more than 5 times

How many sites/keywords/brands can be listed in the metadata?
https://developer.chrome.com/docs/webstore/spam-faq/

This depends on how relevant the keywords are in context, however, it's best to keep instances of a specific keyword to under 5. Keywords must be relevant to the extension's purpose and not unnecessarily repeat in an unnatural way. Including more than 5 instances of a single keyword may result in increased scrutiny of your extensions, but will be allowed if its use is considered appropriate and relevant.

From Gmail email

Announcement: Updates to Our Extension Policies for a More Consistent Web Store
Keyword Spam Update:
Some examples of Keyword Spam include:
Unnatural repetition of the same keyword more than 5 times

Enforcement Circumvention:
Any attempt to circumvent intended limitations or enforcement actions will result in the immediate termination of your developer account, and possibly related developer accounts.

Why do hundreds of developers have to follow the rules and follow them, while some outright violate them?
I ask to consider these cases and remove extensions that violate the rules as well as consider the removal of developer accounts.

Extension URL - Number of repetitions of the word Aliexpress

https://chrome.google.com/webstore/detail/find-amazon-products-on-a/dakplbpelpkfglcnhmconkppkglphgcj - 6

Thank you in advance for considering this issue and removing extensions. We want the same conditions for all developers and rule following.

Stefan Van Damme

unread,

Mar 28, 2023, 2:42:41 PM3/28/23

to Chromium Extensions, Kempe

Hi there,

If you find that it violates a program guideline. Please use the abuse link on that Chrome Web Store page. The Chrome Web Store team will then investigate and take appropriate action

Thanks,
Stefan vd

Kempe

unread,

Apr 1, 2023, 1:58:21 PM4/1/23

to Chromium Extensions, Stefan Van Damme, Kempe

Simeon Vincent ( @dotproto )

Created this post and sent a message on this page https://support.google.com/chrome_webstore/contact/one_stop_support marked "An item that should not be on the store" and indicating this post. Simeon, please tell me, is that not enough to consider these violations?

Simeon Vincent

unread,

Apr 3, 2023, 6:55:52 PM4/3/23

to Kempe, Chromium Extensions, Stefan Van Damme

I'm not sure why you're tagging me, but I'll do my best to help.

Created this post and sent a message on this page https://support.google.com/chrome_webstore/contact/one_stop_support marked "An item that should not be on the store" and indicating this post. Simeon, please tell me, is that not enough to consider these violations?

In the future I'd recommend including the information you want to share with support directly rather than linking to an external resource. Putting the information behind a link means that the people working on your ticket have manually followed the link to see this info rather than seeing it directly in the ticket itself. If you do need to link to something else, it would be better to collect the information in a Google document or post it to your website – this group isn't really intended for CWS policy violation reports.

Simeon - @dotproto

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, 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/584e3e83-e750-47bd-9f11-71c51ef3dd2an%40chromium.org.

Kempe

unread,

Apr 4, 2023, 4:12:24 AM4/4/23

to Chromium Extensions, Simeon Vincent, Chromium Extensions, Stefan Van Damme, Kempe

Hi Simeon,

Thank you for the response.

I'll do my best to help

As I understand it, you will help to address this issue. I would be grateful to you for for your help, because today is the ninth day and nothing has changed. I also sent three reports for the first three extensions using the "Report abuse" links on the pages of those extensions as Stefan Van Damme recommended.

In the future I'd recommend including the information you want to share with support directly rather than linking to an external resource...

I will take your advice and no longer create lists here with extensions that violate your rules.

I'm not sure why you're tagging me

You are a well-known person here and have the most knowledge. So I decided to ask you if I have done everything right and if it is enough.

I also found a case https://twitter.com/alitools_/status/1506333870769254407 where you were contacted for help by the developer of one of the extension on my list. Their extension and developer account were removed due to malware and apparently you helped them restore the extension and the developer's account despite the fact that they had already been told that it was impossible due to the seriousness of the violation. Some time after recovery, they made another violation, which according to Chrome Web Store policies should lead to the immediate termination of the extension and the developer's account.

I would like the same conditions for all developers according to the Chrome Web Store policies and other rules and don't know other people here who could help bring this message to those who view the reports.

Simeon Vincent

unread,

Apr 5, 2023, 1:30:12 AM4/5/23

to Kempe, Chromium Extensions, Stefan Van Damme

I'll do my best to help
As I understand it, you will help to address this issue. I would be grateful to you for for your help, because today is the ninth day and nothing has changed.

To be clear, all I can do to help is talk about the problem and provide advice. I no longer work for Google, so I cannot escalate or take action on the issue myself.

I would like the same conditions for all developers according to the Chrome Web Store policies and other rules and don't know other people here who could help bring this message to those who view the reports.

Oliver Dunk and Patrick Kettner are both members of the Chrome team and are active in this group. They may be able to make sure this information reaches the appropriate Googlers.

Simeon - @dotproto

Kempe

unread,

Apr 13, 2023, 8:46:31 AM4/13/23

to Chromium Extensions, Simeon Vincent, Chromium Extensions, Stefan Van Damme, Kempe

It's been 18 days since I first contacted support through the appropriate form. I still have not received a reply and nothing has changed.

Simeon, could you please invite Oliver Dunk and Patrick Kettner to this thread?

Oliver Dunk

unread,

Apr 13, 2023, 9:03:33 AM4/13/23

to Kempe, Chromium Extensions, Simeon Vincent, Stefan Van Damme

Hi Kempe,

I will check on our side and make sure that your ticket reached the right people internally. I definitely hope we can get you a response at the very least. Unfortunately, there isn't much I can do beyond that.

Reviews are always done on a case by case basis and I hope you can appreciate that it wouldn't be feasible to provide a justification for why each extension is and isn't allowed on the store. Additionally, there's only so much we can share in a public forum like this, especially to people other than the developer of an extension.

I hope that makes sense and do appreciate you sharing these. If you find that an extension of your own is affected by a policy and you think action was taken in mistake, you can absolutely let us know about that through the appeal process.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/7a285fe9-bf6e-4ce4-a993-8a8bb158a560n%40chromium.org.

Ch Ext

unread,

Apr 13, 2023, 11:19:37 AM4/13/23

to Chromium Extensions, Oliver Dunk, Chromium Extensions, Simeon Vincent, Stefan Van Damme, Kempe

Hi Oliver,

I am having a similar issue where I have one extension making 3 or more copies of the tool with minor changes and targeting popular keywords. Is there anyway you can help me escalate it?

I made the initial complaint about this practice 2 months ago and I don't see much actions being taken. I had provided detailed pdf document showing how these are copies and that they are doing this intentionally, but could not get any actions being taken. I did provide the following proof:

- Given screenshot with UI/UX similarity
- How they use the same contact number
- On install page is same
- Code is similar
- How their privacy document is same with only the extension name changed

- How they are making similar changes to the extension at the same time.

It is pretty obvious they violate chrome store policy, but not sure why this is allowed. It is a little discouraging.

My case number is 0-1917000033269

Can you help me with this?

Regards

Cuyler Stuwe

unread,

Apr 13, 2023, 11:28:10 AM4/13/23

to Ch Ext, Chromium Extensions, Kempe, Oliver Dunk, Simeon Vincent, Stefan Van Damme

I would think that “near-identical code submitted across two different CWS accounts” would trigger a red-flag for manual review from the ML component of the review system.

But then again, there are other aspects of the CWS that are less sophisticated than other stores (e.g., the inability to cancel a review, no tracking of previous versions) so maybe this is one of those situations where CWS just doesn’t have the resources to keep up with the state-of-the-art.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/ddf46ba3-2ff4-46a9-8a8e-4ce9c1a43b44n%40chromium.org.

Kempe

unread,

Apr 14, 2023, 2:18:02 AM4/14/23

to Chromium Extensions, Oliver Dunk, Chromium Extensions, Simeon Vincent, Stefan Van Damme, Kempe

Hi Oliver,

Thank you very much for looking into this issue and for your help in reviewing it. I will await the decision on these violations and the response.

I will now add that my extension has never been affected by a policy and I have no issues with it.

Oliver Dunk

unread,

Apr 14, 2023, 11:24:46 AM4/14/23

to Kempe, Chromium Extensions, Simeon Vincent, Stefan Van Damme

Hi all,

I just wanted to follow-up here as promised. Thanks for your patience.

In both instances (the case mentioned in the initial post, and case 0-1917000033269), we sent a reply fairly soon after the ticket was opened.

If either of you didn't receive those, let me know and I can ask for it to be re-sent. As I mentioned I can't talk about specifics here but we definitely appreciate all of the feedback.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

Ch Ext

unread,

Apr 14, 2023, 12:43:26 PM4/14/23

to Chromium Extensions, Oliver Dunk, Chromium Extensions, Simeon Vincent, Stefan Van Damme, Kempe

Hi Oliver,

Thank you for your help with this issue.

The only email I got is just an email confirming the receipt of the complaint and that they are reviewing it. Nothing else. Then a month later I sent another email with additional proof, there also I got an email that they are reviewing.

Was there any other email? Can you resent it if there is other emails?

The spammy extensions (around 4 of the 5) are still there in the chrome store, so was wondering why actions are not being taken? Do you mean they are still in review?

Any information would be very helpful.

Regards

Oliver Dunk

unread,

Apr 18, 2023, 9:44:14 AM4/18/23

to Ch Ext, Chromium Extensions, Simeon Vincent, Stefan Van Damme, Kempe

Hi,

It sounds like you received our emails (we mostly sent confirmation that we'd received your messages and were looking in to it).

Unfortunately, I can't say too much more than that. Not every investigation on our end is going to lead to an extension being removed, and we can't share specifics about why that is, especially since this isn't related to an extension you've published.

We do appreciate the reports and your time making them.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

Kempe

unread,

Apr 25, 2023, 4:54:04 AM4/25/23

to Chromium Extensions, Oliver Dunk, Chromium Extensions, Simeon Vincent, Stefan Van Damme, Kempe, Ch Ext

It's been 30 days now. I only received these two responses at the very beginning and none of the extensions on the list have been removed.

Dear developer,

Thank you for contacting us. One of our associates will be in touch with you shortly.

Sincerely,

Chrome Web Store Developer Support

and

Hey there,

Thank you for reporting the items. Our team will review them and take the action accordingly. Thank you for your contributions to the extensions ecosystem.

Sincerely,

Chrome Web Store Developer Support

Oliver, thank you very much for your responses including this one.

Not every investigation on our end is going to lead to an extension being removed, and we can't share specifics about why that is, especially since this isn't related to an extension you've published.

Not every investigation on our end is going to lead to an extension being removed - I absolutely agree with you here.

we can't share specifics about why that is - extensions are public, Chrome Web Store policies are public and mandatory to everyone, the question was asked publicly. I don't see any valid reason not to make your decision and motivation public. I see only general phrases and unwillingness to explain anything.

We do appreciate the reports and your time making them. - You haven't pointed out to me and all other developers where I'm wrong and why I can't demand that extensions be removed according to Chrome Web Store policies. You simply refuse to explain and follow your own Chrome Web Store policies.

Do you think that makes me want to write you other reports? From my point of view, it just shows that you don't follow your own rules, so you're cheating me and all other developers. It ruins the reputation of Chrome Web Store, Google employees, your personal reputation. Since one of the extensions on the list was previously removed for malware along with the developer account with the wording - no possibility of being restored, but then it was restored, this may indicate that it was done illegally. Now, you continue to commit violations and do nothing with them. You cannot expect a positive reaction from me and other developers in this case.

Alexander Gerber

unread,

Feb 21, 2025, 2:03:58 PMFeb 21

to Chromium Extensions, Kempe, Oliver Dunk, Chromium Extensions, Simeon Vincent, Stefan Van Damme, Ch Ext

Hi Oliver, I'm running into the same situation. Are you able to look at case [7-1853000038343] to see if it's being looked at?

In the case of [7-1853000038343] both extensions are using the EXACT same code base. I'm hoping you can help remove the spam from the webstore.

Thanks, let me know.

Reply all

Reply to author

Forward