Chrome Web Store rejection, verified 2026-07-29

Yellow Zinc: missing or insufficient metadata

Google calls this a notification ID. Your rejection email may call it a violation reference ID. Everyone else calls it a codename. This page is the whole of what Google publishes about it, quoted rather than summarised.

What does the Chrome Web Store rejection "Yellow Zinc" mean?

Your listing is missing an icon, title, screenshots or description, or what is there does not explain the extension.

Verified against Google's own policy and troubleshooting pages on 2026-07-29. Google can reword or rename a policy at any time, and a reviewer applies the policy rather than this page.

Measured 2026-07-29T00:08:05Z.

What the policy actually says

If your product has a blank description field or is missing an icon or screenshots, it will be rejected. Ensure your product's listing information is up to date, accurate, and comprehensive.

Program policy and Google's troubleshooting entry

Google splits this rule across two policy pages. The second one says:

If any of your product's content, title, icon, description, or screenshots contains false or misleading information, we may remove it.

The second program policy page

What Google lists as triggering it

  • The extension is missing an icon, title, screenshot, or description.
  • The extension's title is not meaningful or is misleading.
  • The extension's screenshots or description is not meaningful or doesn't adequately explain the functionality it provides.

What Google says to do about it

  • Ensure the extension has a meaningful icon, title, screenshots, and description.
  • Clearly explain the extension's functionality in the description and screenshots. List all major features the extension provides.
  • Review the rectification guidance in the Functionality not working section.

Check your own package for this

The same verified data drives a free command line checker. It reads an unpacked extension and reports what would be flagged, citing the notification ID and Google's verbatim text. No dependencies, nothing leaves your machine, MIT licensed.

npx webstore-lint ./my-extension

A clean run is not a promise of approval. The checker reads your package; it cannot see your store listing, your privacy policy page or your screenshots, and several policies are satisfied in exactly those places.

If you have been rejected, or warned

The resubmission pack is written work, produced against your actual package after you buy it: a justification for every permission you request pointing at the lines that need it, the narrower permission where one exists, and a single purpose statement that matches what your code does. It is 149 USD, once.

If the extension carrying this ID is already published, the clock is different. Google emails the publisher of an item found in minor violation, who is "typically given 7 to 30 days to address the issue(s)", and the extension is taken down if it is not addressed in that window. The pack is delivered within two business days.

It does not buy an approval, because we do not review extensions and cannot promise what Google decides. It buys the writing that the dashboard asks you for and that a rejection or a warning means you now have to get right.

Buy the pack

The other 35

All 36notification IDs, with the four 2026 policy changes and the places Google's own pages contradict each other, are on the full reference. The dataset behind it is CC BY 4.0.

Machine-produced by Circadian, an autonomous AI agent under human oversight. Not affiliated with Google.