PSA: Chrome WebStore Policy Updates

[Sebastian Benz]

Hey everyone,

the Chrome Web Store team has published a series of updates to our Developer Program Policies page. Read more details about what has changed in the blog post.

If there are any additional questions, please do let us know.

Thanks,

Sebastian on behalf of Chrome Extensions DevRel

[Jordi Salvat i Alabart]

The link leads to a 404

El dia dijous, 11 de juliol del 2024 a les 10:57:54 UTC+2, Sebastian Benz va escriure:

[Sebastian Benz]

Sorry, this is the correct link: https://developer.chrome.com/docs/webstore/program-policies

[Uladzimir Yankovich]

Force use of Chrome.search for new tab extensions. Such an understandable and such a terrible decision for Google.

[Roberto Oneto]

It is not clear.
I have a non -public extension that allows to perform a web search using the most generic engines (Google, Bing, etc.) and also more specific (Wikipedia and local newspapers).
According to these new policies, should I make changes?

[Sebastian Benz]

Thanks for the feedback. Our policy FAQ hopefully makes this more clear:

Can my extension make changes to the default search settings?

Yes. If the only purpose of the extension is to change the default search settings, then it would be compliant with the single purpose policy.

The only supported way to change the default web search settings using an extension is via the Settings Overrides API. Extensions that change the default web search experience in any form, without using the Settings Overrides API, are subject to removal from the Chrome Web Store.

Can my New Tab Page (NTP) extension make changes to the user's search experience?

No. NTP extensions that provide a search experience must respect the user's existing settings by using the Chrome Search API. Altering a user's search experience is considered a standalone functionality and should not be coupled with any other features.

Dr. Sebastian Benz

Developer Relations Engineer

Google Germany GmbH

Erika-Mann-Straße 33

80636 München

Geschäftsführer: Paul Manicle, Liana Sebastian

Registergericht und -nummer: Hamburg, HRB 86891

Sitz der Gesellschaft: Hamburg

Diese E-Mail ist vertraulich. Falls Sie diese fälschlicherweise erhalten haben sollten, leiten Sie diese bitte nicht an jemand anderes weiter, löschen Sie alle Kopien und Anhänge davon und lassen Sie mich bitte wissen, dass die E-Mail an die falsche Person gesendet wurde. 

     

This e-mail is confidential. If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it has gone to the wrong person.

[Roberto Oneto]

Hi, just to have no doubts about it, an extension like this:

home-new-tab-page

is currently violating the policies of the chrome webstore?

[Red ross]

Re: new tab page, does anyone know if this is specific to one / all of these cases -

1. Extensions that make use of both chrome settings overrides > search_provider as well as take over the new tab page?
2. Extensions that take over new tab page and surface a search bar for their own internal search functionality (such as enterprise search extensions).
3. Extensions that take over new tab page but don't have any search bar in the new tab page interface.

[Sean Wilson]

> To further protect our users, we are updating our policies regarding deceptive installation tactics. This update specifies that all advertisements, marketing materials, and referral pages fall within the scope of our policies. Additionally, every call-to-action button must clearly state that an extension is being installed.

I have a homepage for a website testing extension (i.e. the whole page is about why you should install the extension and why it's useful) and the homepage CTA button says "Test your website now" with a Chrome icon. I need to change this to something like "Install extension"?

The "every call-to-action button must clearly state that an extension is being installed" part feels strange because the CTA button won't be directly installing the extension but taking you to a Chrome Web Store page where you then have to click another button to install.

Thanks,

Sean 

[Roberto Oneto]

"Chrome Search API" as it was designed does nothing but mask the URL for searching with the default engine by binding it to the only querystring parameter (the search words) giving the possibility to divert the search results on a newtab or on an already present tab.
Definitely a little little you don't find?

If the API planned to access all the search engines listed here:   chrome://settings/searchEngines
and it also returned some suggestions as the user writes in the search bar then would not be so pathetic.

However, in order not to bother someone, I removed the search bar from my  (not public) extension.
Now let's see how many will do it with their own NTP extension.

Best regards

[Scott Shattuck]

I have an extension in development that leverages local bookmark and history information to help prioritize results more effectively. This functionality is currently planned to be accessible via the omnibox, an extension-specific page opened by the extension action, and the new tab page (subject to users selecting that option). 

All search terms entered also invoke the users' default search via the chrome.search.query() but it'd be hard to argue the extension doesn't "alter the users search experience", that's its "single purpose" in fact, to make search more context-aware relative to a specific users activity.

If I understand this correctly I should stop now and avoid the inevitable rejection and just get on with building the desktop version.

Am I interpreting this correctly?

[Red ross]

Hi Sebastian / Oliver,

Could you add more context on this given the sensitivity of this guideline:

"We are clarifying our Quality Guidelines to ensure a seamless user experience. Specifically, new tab page extensions are now explicitly prohibited from altering a user's search experience unless they use the chrome.search API. This clarification aims to prevent any unexpected or unwanted changes to a user's browsing experience, ensuring that any modifications are clearly communicated and controlled. For more information on the Quality Guidelines policy, see our updated FAQ."

Specifically,
1. If a extension has a override for chrome_url_overrides but does not actually surface any search bar at all, is that in violation of this rule?
2. If an extension is surfacing a search bar for internal enterprise only search on a custom new tab page, does that also fall under the same rule?

[Vanessa Dias]

Hello Team,

I have few doubt on my extension with policy for new tab extension https://chromewebstore.google.com/detail/messenger-central/hhljlkkodanjjefajfnmlihohigmfbbl

We have custom search section on the new tab so how will the new policy affect my extension. Can you guys help me what changes i need to do?

--

Thanks & Regards,
Vanessa Dias
Software Developer

Mobile: +91 7507912150
Email: van...@mediastinct.com
Website: www.mediastinct.com

NOTICE:
This email and any file transmitted are confidential and/or legally privileged and intended only for the person(s) directly addressed. 
If you are not the intended recipient, any use, copying, transmission, distribution,or other forms of dissemination is strictly prohibited. 
If you have received this email in error, please notify the sender immediately and permanently delete the email and files, if any.

--
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/6e112ae3-7fbb-49b0-b164-c316ffd55576n%40chromium.org.

[Sebastian Benz]

Hey everyone,

Thanks for all the feedback! Unfortunately, we can't comment on specific questions about our policies. However, I've collected your feedback and will take it to our policy team to check if there are ways how we could make it more clear how our policies apply to specific use cases.

Thanks,

Sebastian

[Red ross]

Thanks Sebastian. https://developer.chrome.com/blog/cws-policy-updates-2024?hl=en mentions September 9 as the date after which extensions can risk removal from the store.
Is there a different channel we could ask in to get more clarity here as we're on a short-timeline to make adjustments if any are needed.

[Patrick Kettner]

The best option would be to contact One Stop Support (https://support.google.com/chrome_webstore/contact/one_stop_support)

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/7b3632dd-81b1-438f-9a76-c193035e4947n%40chromium.org.

[Eddy DosSantos]

Hi Sebastian, 

Could you please provide more insight on the following?

"We are clarifying our Quality Guidelines to ensure a seamless user experience. Specifically, new tab page extensions are now explicitly prohibited from altering a user's search experience unless they use the chrome.search API. This clarification aims to prevent any unexpected or unwanted changes to a user's browsing experience, ensuring that any modifications are clearly communicated and controlled. For more information on the Quality Guidelines policy, see our updated FAQ."

We have gone through the policy update materials and understand that the recent revision you referred to applies to NTP extensions where users' settings beyond the new tab functionality, specifically search settings, are modified. However, what if the user settings are not being changed and the New Tab includes a search box for a custom search experience, does this situation also fall under the same rule?

Many Thanks--