Single purpose is clearly described in store listing or README
Why it matters
Chrome Web Store enforces a single-purpose policy (chrome-cws-single-purpose): extensions that claim to do three or more unrelated things — tab management AND ad blocking AND password management — are rejected or removed from the store. Even if the extension passes initial review, Google's automated systems flag multi-purpose behavior post-publication, which can result in suspension. A clearly stated singular purpose also reduces user confusion about what permissions the extension actually needs, decreasing install abandonment.
Severity rationale
Medium because multi-purpose descriptions risk post-publication removal under the chrome-cws-single-purpose policy, not just initial rejection.
Remediation
State your extension's single purpose explicitly in both the manifest description and the README. Limit feature claims to one primary domain.
In manifest.json:
{
"description": "Organize and manage your browser tabs efficiently."
}
In README.md:
## Purpose
This extension focuses exclusively on tab management. It does not modify web pages, inject ads, or access passwords.
If you have secondary features, frame them as supporting tools for the primary purpose, not independent feature domains.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Chrome Web Store Readiness Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- external · chrome-cws-single-purpose — Chrome Web Store — Single Purpose Policy
Taxons
History
- 2026-04-18·v1.0.0·Initial import from extension-store-readiness·automated