# Chrome Web Store category choice follows the browsing job

> Pick the category that matches the buyer’s browsing job, because Chrome requires one category and category shelves shape who discovers the extension in the first place.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/chrome-web-store-category-choice-follows-the-browsing-job/
- Source: [developer.chrome.com](https://developer.chrome.com/docs/webstore/best-practices)
- GrowthDex source hub: [Chrome for Developers: Best Practices](/sources/chrome-for-developers-best-practices-developer-chrome-com/)
- Last checked: 2026-06-07T01:06:00Z
- Rarity: uncommon
- Budget: free
- Channels: Marketplaces, SEO, Brand
- Stages: browser extensions, chrome web store, category strategy, discovery


## Why this can grow

Teams often dump an extension into a broad bucket and treat category as admin trivia. Chrome does not. The dashboard requires a category, and the category list is written around concrete user jobs like accessibility, communication, and developer tools. That means the category is part of positioning, not just classification. If the extension is easier to understand in one browsing aisle than another, the category choice should follow that mental model. The wrong category does not only weaken discovery. It makes the listing feel misfiled.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where chrome web store category choice follows the browsing job can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and SEO channel.
3. Use the evidence from developer.chrome.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Chrome’s best-practices guide says the developer dashboard requires a category and tells developers to choose the most appropriate one from job-shaped shelves such as Accessibility, Communication, and Developer Tools.

## Adjacent tactics in the same lane

- [Firefox Add-ons name earns the slug](/growth-ideas/firefox-add-ons-name-earns-the-slug/) - 3 shared channels, 2 shared stages
- [Safari extension Extensions category is a real shelf](/growth-ideas/safari-extension-extensions-category-is-a-real-shelf/) - 3 shared channels, 2 shared stages
- [Chrome Web Store Google sign-in when login is required](/growth-ideas/chrome-web-store-google-sign-in-when-login-is-required/) - same source, 1 shared channel, 1 shared stage
- [Firefox review rejection falls back to the last approved version](/growth-ideas/firefox-review-rejection-falls-back-to-last-approved-version/) - 3 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The Chrome Web Store page should survive the release channel](/blog/the-chrome-web-store-page-should-survive-the-release-channel/) - marketplaces, SEO, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.