Skip to main content

Manifest description matches store listing intent

ab-001342 · extension-store-readiness.store-listing.manifest-description
Severity: mediumactive

Why it matters

The manifest description is the first copy Chrome Web Store renders below the extension name in search results. A vague or absent description like "A useful extension" gives reviewers and users no signal about what the extension actually does, depressing install rates and creating friction in review. Chrome Web Store uses this field in its keyword index, so a weak description directly limits organic discoverability. Descriptions under 10 words fail the chrome-cws-listing-requirements threshold and are flagged during review.

Severity rationale

Medium because a vague description harms discoverability and slows review approval but does not block submission outright.

Remediation

Add a clear, action-oriented description to manifest.json. Stay under 140 characters and lead with the user benefit, not the technical approach.

{
  "description": "Organize and manage your browser tabs efficiently with one-click groups and quick access."
}

Avoid openers like "This extension helps you…" — lead with the verb. The description should answer "what does this do for me?" in under 15 words.

Detection

  • ID: extension-store-readiness.store-listing.manifest-description

  • Severity: medium

  • What to look for: Check the description field in manifest.json and count the character length. It should be a concise summary of what the extension does (up to 132 characters in Chrome Web Store). Cross-reference with any README, documentation, or store listing description to verify consistency.

  • Pass criteria: A description field exists, is non-empty, is under 140 characters, and clearly describes the extension's primary purpose in at least 10 words. Quote the actual description value found.

  • Fail criteria: No description field, or description is empty, fewer than 10 words, overly vague (e.g., "A useful extension"), or inconsistent with the extension's actual functionality.

  • Skip (N/A) when: Never — every extension should have a description.

  • Detail on fail: "Manifest description is empty" or "Description is vague: 'Helps you browse better' — doesn't explain what it does".

  • Remediation: Add a clear, concise description to your manifest:

    {
      "description": "Organize and manage your browser tabs efficiently with one-click groups and quick access."
    }
    

    Keep it under 140 characters and focus on the user benefit, not technical details.

External references

Taxons

History