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.
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.
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-reported evidence
Source: Visual Studio Code Docs: Extension Manifest
The manifest supports up to 30 keywords, and VS Code uses the display name and description for text search.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Marketplaces, SEO, Conversion is relevant to developer tools, marketplace search, metadata fit and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Marketplaces and SEO, using evidence from Visual Studio Code Docs: Extension Manifest as context—not as a promised result.
- Record a baseline for: Qualified search visitors who complete the intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.