Unreject

Yellow Zinc

Yellow Zinc: Missing or insufficient metadata

Your store listing does not give users enough to understand the item. Something is missing (icon, screenshot, description), or what's there is too vague to say what the extension does.

The fix: rejected → fixed

manifest.json− rejected+ fixed
{  "name": "Tidy",  "description": "Best extension ever!!!",  "name": "Tidy - Group and Save Tabs",  "description": "Group open tabs by site, save the group as a session and restore it later.",  "icons": { "16": "icons/16.png", "48": "icons/48.png", "128": "icons/128.png" },  "manifest_version": 3}

The name now says what it does and the description names the features. A real 128px icon is declared. The store listing needs the same fix: screenshots and a feature list.

Why you got Yellow Zinc

  • No screenshots, or screenshots that don't show the extension in use.
  • A description like "Best productivity tool!" that never says what it does.
  • The default puzzle-piece icon or a blank 128×128 icon.
  • A title that is only a brand name with no hint of function.
  • A detailed description that lists none of the actual features.

Pre-resubmit checklist

Your ticks are saved in this browser.

Common mistake: Fixing the manifest alone is not enough. Most Yellow Zinc rejections are about the listing fields in the Developer Dashboard.

Appeal or resubmission note

Replace the [BRACKETS], then use the appeal link in your rejection email. Keep it short and factual, and list only changes you actually made.

Hello Chrome Web Store team,

My item [EXTENSION NAME] (ID: [ITEM ID]) was rejected with reference Yellow Zinc.

I have reviewed the policy and made the following changes in version [NEW VERSION]:
- Added [N] screenshots showing the main features.
- Rewrote the description to list what the extension does: [FEATURES].
- Replaced the placeholder icon with a 128×128 product icon.

[ONE SENTENCE ON WHAT THE EXTENSION DOES AND WHY IT NEEDS WHAT REMAINS.]

I have resubmitted the updated package. If anything still does not comply, I would appreciate a pointer to the specific file or listing field so I can fix it.

Thank you,
[YOUR NAME]

Google's own wording for this code is on the Chrome Web Store troubleshooting page under "Missing or insufficient metadata".

Other fix guides