# Chrome Web Store summary hook in 132 characters

> Write the 132-character summary as the buyer's first job-to-be-done sentence, because Chrome shows it on the homepage, category pages, and search results before the long description gets a chance.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/chrome-web-store-summary-hook-in-132-characters/
- Source: [developer.chrome.com](https://developer.chrome.com/docs/webstore/best-listing)
- GrowthDex source hub: [Chrome for Developers: Creating a great listing page](/sources/chrome-for-developers-creating-a-great-listing-page-developer-chrome-com/)
- Last checked: 2026-05-30
- Rarity: uncommon
- Budget: free
- Channels: Marketplaces, SEO, Conversion
- Stages: browser extensions, metadata, search snippet, positioning
- Key metric: Chrome limits the summary to 132 characters and uses it on the homepage, category pages, and search results.

## Why this can grow

A lot of extension teams treat the summary like a metadata field and save the actual explanation for the full description. Chrome does the opposite. It pushes that short line into the main discovery surfaces where the buyer decides whether to click. That means the summary is closer to a search snippet than a subtitle. A plain sentence about the core job usually beats a stuffed list of features because it tells the user whether this extension belongs in their workflow at all.

## 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 summary hook in 132 characters 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 listing guide says the summary is the main description users see from the homepage, category pages, and search results, and limits it to 132 characters.

## Adjacent tactics in the same lane

- [Slack Marketplace short description in 10 words](/growth-ideas/slack-marketplace-short-description-in-10-words/) - 3 shared channels, 3 shared stages
- [Chrome Web Store long description opens with the job](/growth-ideas/chrome-web-store-long-description-opens-with-the-job/) - same source, 2 shared channels
- [Safari extension first three screenshots show the enable path](/growth-ideas/safari-extension-first-three-screenshots-show-the-enable-path/) - 3 shared channels, 1 shared stage
- [Zoom Marketplace short description as search snippet](/growth-ideas/zoom-marketplace-short-description-as-search-snippet/) - 2 shared channels, 2 shared stages

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The extension listing should earn the install before the permission prompt](/blog/the-extension-listing-should-earn-the-install-before-the-permission-prompt/) - 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.