Listing status and availability
In the Developer Dashboard, read the status next to the item. Google’s review-status guide names Published, Pending, Rejected and Taken Down. For a rejection, open the item’s Status tab and keep the notification’s explanation with your record.
Then open Distribution and check Visibility and geographic availability. The distribution guide distinguishes:
| Setting | Documented access | Check |
|---|---|---|
| Public | Listed for users to see and install | Selected regions and publication status |
| Unlisted | Installation through the item's store URL | Direct URL access separately from search |
| Private | Installation limited to specified users | Whether the test account is included |
Illustrative diagnostic example: an Unlisted item opens through its URL but is absent from store search. Its visibility setting explains that observation; keyword changes are not the first check.
Google’s discovery guidance also says a newly published extension may take a few hours to be indexed. Save the publication time before repeating the search.
Name, description and localization
Compare the published name, description, icon and screenshots with the extension’s actual behavior in each language you offer. Keep the language of the listing and the exact search query in the record.
Chrome says listing metadata contributes to search results. Its discovery guide places the Category selector on Store Listing, under Product Details. Choose a category that describes the extension’s main task.
If a review notice identifies misleading metadata or missing functionality, use the relevant section of Google’s troubleshooting guide. Correct the stated mismatch and record the affected package or listing field.
Use the store listing definition to keep metadata separate from the installed product.
How to check discovery and first use
Run a repeatable check:
- Open the exact published store URL. Record the item ID, status, visibility, region and account context.
- Search the Chrome Web Store with the saved query and language. Record whether the item appears and when you checked.
- For a recently published item, allow for indexing. Google’s “a few hours” is not a guaranteed deadline. If a Public item opens by URL but is missing for your saved query, record those two results separately.
- Test the published build in the intended browser. Follow the action promised by the listing and record the expected and observed result.
Store appearance, installation and useful product activity answer different questions. The guide to Chrome Web Store users and installs explains the metric boundary.
For a product failure, save the build, browser version and reproduction steps for extension development.
How to compare visibility before and after a change
Keep one record before changing the listing:
| Area | What to save |
|---|---|
| Item and release | Store URL, item ID, published version and current review status |
| Access | Visibility, selected regions and account context |
| Search | Exact query, language, observed result and capture time |
| Change | The metadata field or build changed, its publication time and the later check |
| First use | Expected action, observed behavior and unresolved issue |
Extcorp’s extension growth review covers listing clarity, localization, onboarding and product signals. Store positions are not guaranteed.
Extension install campaigns have a separate scope: advertising, with price and test terms on request. Share the listing and the problem you observed to discuss a growth review.
Extcorp is independent of Google and Chrome Web Store.