# The VS Code extension page should finish the trust check > Why sharper search metadata, shelf-fit categories, a real README, visible support, honest listing signals, and a verified publisher track make VS Code extensions easier to install without doubt. - Canonical HTML: https://growth.iangoh.com/blog/the-vs-code-extension-page-should-finish-the-trust-check/ - Published: 2026-06-06 - Updated: 2026-06-06T12:40:00Z - Categories: marketplaces, SEO, brand trust - Niches: Developer tools, AI products, SaaS, Open-source software, B2B software ## On this page - Search fit starts with naming the job in plain editor language - The category should place the extension on the right shelf - The detail page should teach the workflow and prove the shipping cadence - Support metadata is part of the install decision now - Visual and pricing clarity should remove easy reasons to hesitate - Trust proof and release risk should not be mixed together ## Start with these related tactics - [VS Code extension display name, description, and keywords fit the job](/growth-ideas/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. - [VS Code extension category picks the right shelf](/growth-ideas/vs-code-extension-category-picks-the-right-shelf/): Choose the narrowest allowed category instead of dumping the extension into a generic bucket, because VS Code users browse and filter by category before they trust a new publisher. - [VS Code extension README and CHANGELOG finish the detail page](/growth-ideas/vs-code-extension-readme-and-changelog-finish-the-detail-page/): Treat the README and changelog as sales and trust assets, because the details view shows them where the install decision happens. A VS Code extension page gets judged before the extension gets to do any work. The user sees a name, a small tile, a publisher, install counts, reviews, a README, and now a trust decision for third-party publishers. If that page feels vague or sloppy, the install dies before the command palette ever gets a chance to help. The VS Code extension page should finish the trust check. ## Search fit starts with naming the job in plain editor language [VS Code extension display name, description, and keywords fit the job](/growth-ideas/vs-code-extension-display-name-description-and-keywords-fit-the-job/) is where I would begin. VS Code uses those fields for Marketplace display and text search, which means a vague title is not just bland branding. It is a discoverability bug. This sits close to [JetBrains plugin name states the IDE job](/growth-ideas/jetbrains-plugin-name-states-the-ide-job/) and [Firefox Add-ons name earns the slug](/growth-ideas/firefox-add-ons-name-earns-the-slug/). Different shelves, same rule: the title should say what work gets done. ## The category should place the extension on the right shelf [VS Code extension category picks the right shelf](/growth-ideas/vs-code-extension-category-picks-the-right-shelf/) looks minor until you remember how many users browse by language, workflow, or tool type before they trust a new publisher. If a testing tool hides in Other or a formatter pretends to be generic utility, the page loses both search fit and buyer confidence. I would read it beside [monday Marketplace keyword synonyms across indexed fields](/growth-ideas/monday-marketplace-keyword-synonyms-across-indexed-fields/). Classification is part of acquisition on these shelves. ## The detail page should teach the workflow and prove the shipping cadence [VS Code extension README and CHANGELOG finish the detail page](/growth-ideas/vs-code-extension-readme-and-changelog-finish-the-detail-page/) is the practical move. The details view already shows both. That means the README should explain the first useful path, and the changelog should make recent maintenance visible without forcing the user into GitHub archaeology. It belongs with [GitHub Marketplace feature card preview before brand refresh](/growth-ideas/github-marketplace-feature-card-preview-before-brand-refresh/). The marketplace surface has to carry more of the product story than teams usually admit. ## Support metadata is part of the install decision now [VS Code extension SUPPORT.md before review friction](/growth-ideas/vs-code-extension-support-md-before-review-friction/) matters more because VS Code now asks users to confirm trust for first-time third-party publishers. The buyer is already checking whether the team answers questions, keeps an issue path alive, and looks like it will still exist next month. That pairs naturally with [GitHub security policy link before public bug report](/growth-ideas/github-security-policy-link-before-public-bug-report/) and [Slack Marketplace public support path with 2-day SLA](/growth-ideas/slack-marketplace-public-support-path-with-2-day-sla/). The support surface is part of the product surface. ## Visual and pricing clarity should remove easy reasons to hesitate [VS Code extension icon, banner, and pricing remove listing ambiguity](/growth-ideas/vs-code-extension-icon-banner-and-pricing-remove-listing-ambiguity/) is the shelf hygiene most teams postpone. Good. That usually means competitors still leave it undone. A real icon, a deliberate banner, and a plain Free or Trial label make the extension feel finished before the user inspects the code path. I would pair that with [Firefox Add-ons paid function disclosed on listing](/growth-ideas/firefox-add-ons-paid-function-disclosed-on-listing/). Commercial honesty compounds trust faster than polish alone. ## Trust proof and release risk should not be mixed together [VS Code extension verified publisher and pre-release track](/growth-ideas/vs-code-extension-verified-publisher-and-pre-release-track/) may be the strongest move in the batch. Verified publisher status answers who you are. The pre-release channel answers how you test. Those are different jobs, and VS Code gives teams a clean way to separate them. It also links neatly to [JetBrains plugin hidden release before public launch](/growth-ideas/jetbrains-plugin-hidden-release-before-public-launch/). The shelf gets better when trust and rollout discipline are both visible. This cluster is strongest for developer tools, AI coding products, open-source extensions, team productivity add-ons, and B2B software that needs to earn install trust before the product can demonstrate its depth. If you want help tightening extension pages, trust signals, and distribution surfaces that keep working after launch, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [VS Code extension display name, description, and keywords fit the job](/growth-ideas/vs-code-extension-display-name-description-and-keywords-fit-the-job/) - Marketplaces, SEO, Conversion - [VS Code extension category picks the right shelf](/growth-ideas/vs-code-extension-category-picks-the-right-shelf/) - Marketplaces, SEO, Brand - [VS Code extension README and CHANGELOG finish the detail page](/growth-ideas/vs-code-extension-readme-and-changelog-finish-the-detail-page/) - Marketplaces, Brand, Trust - [VS Code extension SUPPORT.md before review friction](/growth-ideas/vs-code-extension-support-md-before-review-friction/) - Trust, Support, Marketplaces - [VS Code extension icon, banner, and pricing remove listing ambiguity](/growth-ideas/vs-code-extension-icon-banner-and-pricing-remove-listing-ambiguity/) - Brand, Conversion, Marketplaces - [VS Code extension verified publisher and pre-release track](/growth-ideas/vs-code-extension-verified-publisher-and-pre-release-track/) - Trust, Retention, Operations ## Essay chronology - [Newer essay: The Google Chat app should survive the first admin and the first space](/blog/the-google-chat-app-should-survive-the-first-admin-and-the-first-space/) - marketplaces, onboarding, brand trust - [Older essay: The Firefox Add-ons page should remove the surprise before install](/blog/the-firefox-add-ons-page-should-remove-the-surprise-before-install/) - marketplaces, SEO, brand trust ## Keep reading - [The JetBrains plugin page should finish the IDE trust check](/blog/the-jetbrains-plugin-page-should-finish-the-ide-trust-check/) - marketplaces, SEO, brand trust - [The Shopify app page should win the search result before the install](/blog/the-shopify-app-page-should-win-the-search-result-before-the-install/) - marketplaces, SEO, brand trust - [The GitHub release page should finish the upgrade decision](/blog/the-github-release-page-should-finish-the-upgrade-decision/) - brand trust, retention, SEO ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path ## Sources - [Visual Studio Code Docs: Extension Manifest](https://code.visualstudio.com/api/references/extension-manifest) · [GrowthDex source hub](/sources/visual-studio-code-docs-extension-manifest-code-visualstudio-com/) - [Visual Studio Code Docs: Publishing Extensions](https://code.visualstudio.com/api/working-with-extensions/publishing-extension) · [GrowthDex source hub](/sources/visual-studio-code-docs-publishing-extensions-code-visualstudio-com/) - [Visual Studio Code Docs: Use Extensions in VS Code](https://code.visualstudio.com/docs/configure/extensions/extensions) · [GrowthDex source hub](/sources/visual-studio-code-docs-use-extensions-in-vs-code-code-visualstudio-com/) - [Visual Studio Code Docs: Extension Runtime Security](https://code.visualstudio.com/docs/configure/extensions/extension-runtime-security) · [GrowthDex source hub](/sources/visual-studio-code-docs-extension-runtime-security-code-visualstudio-com/) ## Editing notes - Kept the essay on one claim: the extension page has to finish the trust check before install. - Used concrete VS Code mechanics like keyword limits, category shelves, README and changelog tabs, support metadata, pricing labels, and verified publisher rules. - Cut broad platform talk and tied each section back to an install decision or trust decision the user makes on the page. - Closed with where the batch fits and the advisory CTA instead of a padded summary. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.