Chrome Web Store Listing Checklist: Every Field, and What to Write

A rejected or ignored listing usually fails on small, fixable things. Use this as a pre-submission checklist. Limits in this post are the ones published in Chrome's own documentation at the time of writing; check the developer dashboard if a number looks different to you, because requirements can change.

Name

• Limit: up to 75 characters in the manifest name field.
• Write: your brand plus the job, in plain words people search ("Export Group Members to Excel | Brandname").
• Avoid: another company's trademark, and a pile of keywords separated by pipes. Both are common reasons for rejection or takedown.

Short description (manifest description)

• Limit: 132 characters.
• Write: one sentence on the job, one on the difference. This is the text shown in search results.
• Avoid: marketing adjectives with no content ("powerful, amazing, best").

Detailed description

Describe the extension in plain sentences in this order:

1. What it does, in one paragraph.
2. How to use it, in three or four short steps.
3. What it deliberately does not do (this builds trust and reduces bad reviews).
4. Pricing, if there is a paid tier, stated honestly.

The part that gets extensions rejected: keyword spam

This is the most common avoidable rejection we have seen, and we have had it twice. The description was fine except for one block. Two real examples:

• A paragraph listing a long row of brand names the extension worked with (every app and website, comma-separated).
• A "who it's for" section listing professions and audiences.

Both were rejected under the keyword spam policy. The fix was to delete the lists and describe the behaviour in sentences. If you need to name a site for a permission, put it in the permission justification, which is where reviewers expect it, not in the public description.

Screenshots

• Size: 1280 by 800 pixels (or 640 by 400).
• Count: at least one, up to five.
• Content: show the real interface at a realistic state. Use sample data that contains no real people's information.
• Order: the first image carries most of the weight. Put the finished result there.
• Do not crop in a way that hides what the extension actually looks like. A screenshot that does not match the product leads to refunds, bad reviews and sometimes rejection.

Promo images

• Small promo tile: 440 by 280.
• Marquee: 1400 by 560.

These are used when the store features extensions. They are optional for submission but worth preparing.

Category and language

Pick the category where a person looking for your tool would browse, not the one that sounds most impressive. Add translations only if you can maintain them; a listing in a language you cannot support produces support requests you cannot answer.

Permissions and the justification form

For each permission, the dashboard asks you to justify it. Write one honest sentence naming the feature that needs it. Request only what you use. "Access to all websites" for an extension that works on one site is the fastest way to a long review.

Privacy

If your extension collects or transmits any user data, publish a privacy policy and link it. State plainly:

• What is stored on the user's device only.
• What is sent to your servers, and why.
• What you never collect.
• Which third parties, if any, receive data (for example a payment provider).

Then make sure the dashboard's data-use disclosures match the policy and the code. Inconsistencies are a rejection reason.

The final check

Before pressing submit, load the unzipped package into Chrome yourself and click every feature. Every missing file or broken screen found by a reviewer costs you a review cycle that can take days. A build script that refuses to package an extension when a referenced file is missing pays for itself the first time it fires.

After it is live

Add the listing to your website, then launch it on directories and track your keywords. You can list your extension on Extension Club in about a minute: paste your store link and the listing fills itself in.