Extension has descriptive name and short_name in manifest
Why it matters
A missing or generic name like "Extension" or "App" fails Chrome Web Store review outright — the store rejects submissions where the name field is absent or indistinguishable from the category. Beyond rejection, a non-descriptive name tanks organic discoverability; Chrome Web Store search indexes the name field directly, so a vague name means users searching for your specific functionality simply won't find you. The chrome-cws-naming policy enforces this at submission time, making a bad name a hard gate, not a soft warning.
Severity rationale
Critical because a missing or generic name causes Chrome Web Store rejection, blocking distribution entirely.
Remediation
Set a specific, descriptive name in manifest.json (32 characters max for the store) and add short_name if the full name exceeds 12 characters. Both must be distinct.
{
"name": "Tab Manager Pro",
"short_name": "Tab Mgr",
"manifest_version": 3
}
Avoid single-word names like "Helper" or "Tool" — Chrome Web Store reviewers flag these as non-descriptive. Your name is also your primary search signal, so make it match the words users type.
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-naming — Chrome Web Store — Extension Name Policy
Taxons
History
- 2026-04-18·v1.0.0·Initial import from extension-store-readiness·automated