# Edge Add-ons hidden listing before review push

> Keep the extension hidden while certification and setup finish, then unhide after the page, markets, and support surfaces are ready for real discovery.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/edge-add-ons-hidden-listing-before-review-push/
- 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, Launches, Operations
- Stages: browser extensions, microsoft edge add-ons, launch ops, review readiness


## Why this can grow

An extension page can be technically published and still be the wrong thing to show strangers. Edge gives teams a cleaner sequence. Hide the listing, finish the review, confirm the markets, and share the URL only with the testers or customers who should see it first. That prevents search and browse traffic from landing on a page that is still missing the supporting work around the product.

## 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 hidden listing before review push can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Launches 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 Edge Add-ons lets developers switch a listing to Hidden so it is removed from search and browsing, while users who already installed it keep access and updates.

## Adjacent tactics in the same lane

- [Edge Add-ons short description comes from the manifest](/growth-ideas/edge-add-ons-short-description-comes-from-manifest/) - 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
- [JetBrains plugin hidden release before public launch](/growth-ideas/jetbrains-plugin-hidden-release-before-public-launch/) - 3 shared channels, 2 shared stages

## 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.