How to Avoid Chrome Web Store 'Red Nickel' Rejection: What I Found After Auditing 18 Extensions
The article discusses the author's experience with a rejection from the Chrome Web Store due to the use of the word 'Free' in their extension listing. Following this, the author conducted an audit of their 18 extensions to identify similar violations related to promotional language. The findings revealed that a significant number of listings contained prohibited terms, prompting the author to develop a framework to avoid future rejections.
- ▪The author was rejected from the Chrome Web Store for using the word 'Free' in their extension listing.
- ▪An audit of 18 extensions revealed that 80% had at least one violation of the Chrome Web Store's promotional language rules.
- ▪The author categorized violations into four patterns, with image badges being the highest risk for rejection.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3680827) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } SHOTA Posted on May 19 How to Avoid Chrome Web Store 'Red Nickel' Rejection: What I Found After Auditing 18 Extensions #chrome #javascript #productivity #webdev I got my Chrome extension rejected from the Chrome Web Store last week for a 4-letter word: "Free." Not a permission issue. Not a CSP violation. Not a manifest field. Just the word "Free" sitting in a small badge on my listing image.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
