# Edge Add-ons short description comes from the manifest

> Write the short description in the extension manifest before upload, because Partner Center uses that package field on the listing and locks it behind a re-upload.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/edge-add-ons-short-description-comes-from-manifest/
- Source: [learn.microsoft.com](https://learn.microsoft.com/en-us/microsoft-edge/extensions/publish/publish-extension)
- GrowthDex source hub: [Microsoft Learn: Publish a Microsoft Edge extension](/sources/microsoft-learn-publish-a-microsoft-edge-extension-learn-microsoft-com/)
- Last checked: 2026-06-06T11:04:17Z
- Rarity: rare
- Budget: free
- Channels: Marketplaces, Copywriting, Conversion
- Stages: browser extensions, microsoft edge add-ons, manifest copy, listing conversion


## Why this can grow

A lot of listing copy gets treated as dashboard text that can be polished later. Microsoft Edge breaks that habit in a useful way. The short description is tied to the package itself, so the first sentence has to be deliberate before the upload starts. That pushes teams to state the job of the extension early instead of patching vague copy after the page is already in review.

## 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. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. For conversion, I would strip the test down to one promise, one proof point, and one next step. Confusion kills good demand. 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 edge add-ons short description comes from the manifest can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Copywriting channel.
3. Use the evidence from learn.microsoft.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

Microsoft says the Name and Description fields from the manifest populate the listing automatically, recommends adding a short description in the manifest, and requires a package re-upload to change that short description later.

## Adjacent tactics in the same lane

- [Edge Add-ons hidden listing before review push](/growth-ideas/edge-add-ons-hidden-listing-before-review-push/) - same source, 1 shared channel, 2 shared stages
- [Edge Add-ons search terms localized but invisible](/growth-ideas/edge-add-ons-search-terms-localized-but-invisible/) - same source, 1 shared channel, 2 shared stages
- [Edge Add-ons duplicate assets across locales after primary proof](/growth-ideas/edge-add-ons-duplicate-assets-across-locales-after-primary-proof/) - same source, 1 shared channel, 2 shared stages
- [Chrome Web Store summary hook in 132 characters](/growth-ideas/chrome-web-store-summary-hook-in-132-characters/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The Microsoft Edge Add-ons page should finish the review before the install](/blog/the-microsoft-edge-add-ons-page-should-finish-the-review-before-the-install/) - 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.