# Edge Add-ons Featured badge earned, not requested

> Treat the Featured badge like a trailing quality signal, not a launch checklist item, because Microsoft awards and revokes it through automated evaluation instead of manual applications.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/edge-add-ons-featured-badge-earned-not-requested/
- Source: [learn.microsoft.com](https://learn.microsoft.com/en-us/microsoft-edge/extensions/)
- GrowthDex source hub: [Microsoft Learn: Overview of Microsoft Edge extensions](/sources/microsoft-learn-overview-of-microsoft-edge-extensions-learn-microsoft-co/)
- Last checked: 2026-06-06T11:04:17Z
- Rarity: epic
- Budget: free
- Channels: Marketplaces, Brand, Retention
- Stages: browser extensions, microsoft edge add-ons, brand trust, quality signals


## Why this can grow

Badges get over-romanticized. Microsoft is unusually clear here: the Featured badge is not something you apply for, it is not permanent, and it can disappear if quality or listing freshness drifts. That makes the right move obvious. Build the store page, extension quality, and review cadence as if the badge were a byproduct. Teams that chase the badge directly usually miss the work that makes the badge plausible.

## 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. 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 edge add-ons featured badge earned, not requested can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Brand 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 Featured badges are awarded to select extensions that align with best practices, are reviewed and selected through an automated system, and can be revoked for degraded metrics, outdated listing information, or changes in evaluation criteria.

## Adjacent tactics in the same lane

- [Chrome Web Store verified publisher URL and support hub](/growth-ideas/chrome-web-store-verified-publisher-url-and-support-hub/) - 2 shared channels, 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/) - 2 shared channels, 2 shared stages
- [Figma Community complete profile with proof links](/growth-ideas/figma-community-complete-profile-with-proof-links/) - 2 shared channels, 1 shared stage
- [Firefox Add-ons name earns the slug](/growth-ideas/firefox-add-ons-name-earns-the-slug/) - 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.