← Back to GrowthDex

Growth idea action plan

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.

rare tactic free budget Marketplaces, SEO, Conversion Stages: developer tools, marketplace search, metadata fit, extension discovery

Why this can grow a startup

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.

Key metric to watch

The manifest supports up to 30 keywords, and VS Code uses the display name and description for text search.

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.

Source: Visual Studio Code Docs: Extension Manifest (code.visualstudio.com)

GrowthDex source hub: Visual Studio Code Docs: Extension Manifest

Last checked: 2026-06-06T12:40:00Z

Markdown mirror

Adjacent tactics in the same lane

If this page is close to your problem, these tactic pages usually belong in the same working set.

Related GrowthDex essays

Read GrowthDex essays

The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.

Browse the GrowthDex Blog

Why this is worth your time

GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.

Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.

Want help turning this into a growth system?

If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.

Work with Ian on growth advisory