You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear Developer,Since 2009, developers have been hard at work building extensions that make Chrome more powerful, useful, and personalized for users. The Chrome Web Store aims to make it easy for users to find top quality extensions while recognizing the developers who create them. Today, we're happy to announce two new extension badges to help us deliver on that goal: the Featured badge and the Established publisher badge. Both of these badges will appear in the store in the next few weeks.Developers who earn these badges may receive higher rankings in search and filtering, and may also see their extensions appear in special promotions both on and off Chrome Web Store. Learn more about the new badges below.Featured badgeThe Featured badge will be granted to extensions that follow our technical best practices and meet a high standard of user experience and design. Featured badges will be assigned to qualifying extensions through our extension review system. Chrome staff will manually evaluate each extension before it receives the badge, paying special attention to the following:Adherence to Chrome Web Store's best practices guidelines, including providing a delightful and intuitive experience, using the latest platform APIs, and respecting the privacy of end-users.A store listing page that is clear and helpful to prospective users, with quality images and a detailed description.Established Publisher badgeThe new Established Publisher badge will showcase developers who have verified their identity and demonstrated compliance with the developer program policies. This badge will be granted automatically to publishers who meet the following two conditions:The publisher's identity has been verified.The publisher has established a consistent positive track record with Google services and compliance with the Developer Program Policy.Any extensions built by a developer who follows the Chrome Web Store Developer Program Policies and does not have any unresolved violations will be considered. For new developers, it will take at least a few months of respecting these conditions to qualify. Today, this represents nearly 75% of all extensions in the Chrome Web Store and we expect this number to keep growing.What you need to doThere is no mandatory action, but we recommend that developers review their extension(s) over the next few weeks to ensure they're in line with our best practices guidelines.Note that developers cannot pay to receive either badge, but we aim to provide them with other ways to request consideration. Starting on April 20, 2022 the One Stop Support page will begin trialing an option that allows developers to nominate extensions for the Featured badge. Additional details will be available in the Discovery on the Chrome Web Store documentation.We are excited to recognize extension excellence on the Chrome Web Store through these new badges. Thank you for your participation in the Chrome extension ecosystem!- The Google Chrome Web Store team
Dear Developer,
Since 2009, developers have been hard at work building extensions that make Chrome more powerful, useful, and personalized for users. The Chrome Web Store aims to make it easy for users to find top quality extensions while recognizing the developers who create them. Today, we're happy to announce two new extension badges to help us deliver on that goal: the Featured badge and the Established publisher badge. Both of these badges will appear in the store in the next few weeks.
Developers who earn these badges may receive higher rankings in search and filtering, and may also see their extensions appear in special promotions both on and off Chrome Web Store. Learn more about the new badges below.
Featured badge
The Featured badge will be granted to extensions that follow our technical best practices and meet a high standard of user experience and design. Featured badges will be assigned to qualifying extensions through our extension review system. Chrome staff will manually evaluate each extension before it receives the badge, paying special attention to the following:
Adherence to Chrome Web Store's best practices guidelines, including providing a delightful and intuitive experience, using the latest platform APIs, and respecting the privacy of end-users.
A store listing page that is clear and helpful to prospective users, with quality images and a detailed description.
Established Publisher badge
The new Established Publisher badge will showcase developers who have verified their identity and demonstrated compliance with the developer program policies. This badge will be granted automatically to publishers who meet the following two conditions:
The publisher's identity has been verified.
The publisher has established a consistent positive track record with Google services and compliance with the Developer Program Policy.
Any extensions built by a developer who follows the Chrome Web Store Developer Program Policies and does not have any unresolved violations will be considered. For new developers, it will take at least a few months of respecting these conditions to qualify. Today, this represents nearly 75% of all extensions in the Chrome Web Store and we expect this number to keep growing.
What you need to do
There is no mandatory action, but we recommend that developers review their extension(s) over the next few weeks to ensure they're in line with our best practices guidelines.
Note that developers cannot pay to receive either badge, but we aim to provide them with other ways to request consideration. Starting on April 20, 2022 the One Stop Support page will begin trialing an option that allows developers to nominate extensions for the Featured badge. Additional details will be available in the Discovery on the Chrome Web Store documentation.
We are excited to recognize extension excellence on the Chrome Web Store through these new badges. Thank you for your participation in the Chrome extension ecosystem!
The Google Chrome Web Store team
The text was updated successfully, but these errors were encountered:
Dear Developer,Since 2009, developers have been hard at work building extensions that make Chrome more powerful, useful, and personalized for users. The Chrome Web Store aims to make it easy for users to find top quality extensions while recognizing the developers who create them. Today, we're happy to announce two new extension badges to help us deliver on that goal: the Featured badge and the Established publisher badge. Both of these badges will appear in the store in the next few weeks.Developers who earn these badges may receive higher rankings in search and filtering, and may also see their extensions appear in special promotions both on and off Chrome Web Store. Learn more about the new badges below.Featured badgeThe Featured badge will be granted to extensions that follow our technical best practices and meet a high standard of user experience and design. Featured badges will be assigned to qualifying extensions through our extension review system. Chrome staff will manually evaluate each extension before it receives the badge, paying special attention to the following:Adherence to Chrome Web Store's best practices guidelines, including providing a delightful and intuitive experience, using the latest platform APIs, and respecting the privacy of end-users.A store listing page that is clear and helpful to prospective users, with quality images and a detailed description.Established Publisher badgeThe new Established Publisher badge will showcase developers who have verified their identity and demonstrated compliance with the developer program policies. This badge will be granted automatically to publishers who meet the following two conditions:The publisher's identity has been verified.The publisher has established a consistent positive track record with Google services and compliance with the Developer Program Policy.Any extensions built by a developer who follows the Chrome Web Store Developer Program Policies and does not have any unresolved violations will be considered. For new developers, it will take at least a few months of respecting these conditions to qualify. Today, this represents nearly 75% of all extensions in the Chrome Web Store and we expect this number to keep growing.What you need to doThere is no mandatory action, but we recommend that developers review their extension(s) over the next few weeks to ensure they're in line with our best practices guidelines.Note that developers cannot pay to receive either badge, but we aim to provide them with other ways to request consideration. Starting on April 20, 2022 the One Stop Support page will begin trialing an option that allows developers to nominate extensions for the Featured badge. Additional details will be available in the Discovery on the Chrome Web Store documentation.We are excited to recognize extension excellence on the Chrome Web Store through these new badges. Thank you for your participation in the Chrome extension ecosystem!- The Google Chrome Web Store team
Since 2009, developers have been hard at work building extensions that make Chrome more powerful, useful, and personalized for users. The Chrome Web Store aims to make it easy for users to find top quality extensions while recognizing the developers who create them. Today, we're happy to announce two new extension badges to help us deliver on that goal: the Featured badge and the Established publisher badge. Both of these badges will appear in the store in the next few weeks.
Developers who earn these badges may receive higher rankings in search and filtering, and may also see their extensions appear in special promotions both on and off Chrome Web Store. Learn more about the new badges below.
Featured badge
The Featured badge will be granted to extensions that follow our technical best practices and meet a high standard of user experience and design. Featured badges will be assigned to qualifying extensions through our extension review system. Chrome staff will manually evaluate each extension before it receives the badge, paying special attention to the following:
Adherence to Chrome Web Store's best practices guidelines, including providing a delightful and intuitive experience, using the latest platform APIs, and respecting the privacy of end-users.
A store listing page that is clear and helpful to prospective users, with quality images and a detailed description.
Established Publisher badge
The new Established Publisher badge will showcase developers who have verified their identity and demonstrated compliance with the developer program policies. This badge will be granted automatically to publishers who meet the following two conditions:
The publisher's identity has been verified.
The publisher has established a consistent positive track record with Google services and compliance with the Developer Program Policy.
Any extensions built by a developer who follows the Chrome Web Store Developer Program Policies and does not have any unresolved violations will be considered. For new developers, it will take at least a few months of respecting these conditions to qualify. Today, this represents nearly 75% of all extensions in the Chrome Web Store and we expect this number to keep growing.
What you need to do
There is no mandatory action, but we recommend that developers review their extension(s) over the next few weeks to ensure they're in line with our best practices guidelines.
Note that developers cannot pay to receive either badge, but we aim to provide them with other ways to request consideration. Starting on April 20, 2022 the One Stop Support page will begin trialing an option that allows developers to nominate extensions for the Featured badge. Additional details will be available in the Discovery on the Chrome Web Store documentation.
We are excited to recognize extension excellence on the Chrome Web Store through these new badges. Thank you for your participation in the Chrome extension ecosystem!
The text was updated successfully, but these errors were encountered: