# VS Code extension display name, description, and keywords fit the job

> Write the display name, description, and keyword list around the exact editor job so the extension can be found by the words the user is already typing.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/vs-code-extension-display-name-description-and-keywords-fit-the-job/
- Source: [code.visualstudio.com](https://code.visualstudio.com/api/references/extension-manifest)
- GrowthDex source hub: [Visual Studio Code Docs: Extension Manifest](/sources/visual-studio-code-docs-extension-manifest-code-visualstudio-com/)
- Last checked: 2026-06-06T12:40:00Z
- Rarity: rare
- Budget: free
- Channels: Marketplaces, SEO, Conversion
- Stages: developer tools, marketplace search, metadata fit, extension discovery
- Key metric: The manifest supports up to 30 keywords, and VS Code uses the display name and description for text search.

## Why this can grow

A lot of extension pages fail before the user reads the README. They fail in search because the name sounds clever, the description sounds broad, and the metadata never names the real task. VS Code's manifest guidance is direct: display name and description matter for Marketplace and product displays, and those strings are also used for text search. The keyword list is part of that same retrieval layer. When the extension keeps repeating the concrete editing or developer job, the shelf behaves less like branding theater and more like navigation.

## 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 vs code extension display name, description, and keywords fit the 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 code.visualstudio.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

VS Code's extension manifest reference says categories and keywords live in package.json, allows up to 30 keywords, and notes that the display name and description are used for Marketplace display and text search.

## Adjacent tactics in the same lane

- [VS Code extension icon, banner, and pricing remove listing ambiguity](/growth-ideas/vs-code-extension-icon-banner-and-pricing-remove-listing-ambiguity/) - same source, 2 shared channels, 1 shared stage
- [Slack Marketplace short description in 10 words](/growth-ideas/slack-marketplace-short-description-in-10-words/) - 3 shared channels
- [Chrome Web Store summary hook in 132 characters](/growth-ideas/chrome-web-store-summary-hook-in-132-characters/) - 3 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

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The VS Code extension page should finish the trust check](/blog/the-vs-code-extension-page-should-finish-the-trust-check/) - 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.