# Firefox Add-ons no-surprises copy before install

> Write the listing so a user can tell what the add-on does and what data it sends before install, because Mozilla treats that plain disclosure as part of review and consent.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/firefox-add-ons-no-surprises-copy-before-install/
- Source: [extensionworkshop.com](https://extensionworkshop.com/documentation/publish/add-on-policies/)
- GrowthDex source hub: [Firefox Extension Workshop: Add-on Policies](/sources/firefox-extension-workshop-add-on-policies-extensionworkshop-com/)
- Last checked: 2026-06-06T12:04:00Z
- Rarity: epic
- Budget: free
- Channels: Marketplaces, Brand, Conversion
- Stages: browser extensions, firefox add-ons, privacy disclosure, install trust


## Why this can grow

A lot of extension pages still read like teaser copy. Mozilla's policy is stricter and more useful. The listing should let users discern the add-on's function and any transmitted information before they install it. That matters commercially, not just legally. When the page makes the job and data flow obvious, the add-on feels safer, the permission prompt lands with context, and the install click asks for less faith. Teams that hide behind vague copy usually create the exact uncertainty that slows adoption.

## 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 firefox add-ons no-surprises copy before install 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 extensionworkshop.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

Mozilla's Add-on Policies say users should be able to discern an add-on's functionality from the listing, and that the listing should include an easy-to-read description of what the add-on does and what information it transmits.

## Adjacent tactics in the same lane

- [Firefox Add-ons paid function disclosed on listing](/growth-ideas/firefox-add-ons-paid-function-disclosed-on-listing/) - same source, 2 shared channels, 2 shared stages
- [Firefox Add-ons source package with build steps before review](/growth-ideas/firefox-add-ons-source-package-with-build-steps-before-review/) - same source, 1 shared channel, 2 shared stages
- [Safari extension in-use screenshots, not title art](/growth-ideas/safari-extension-in-use-screenshots-not-title-art/) - 3 shared channels, 1 shared stage
- [Firefox Add-ons name earns the slug](/growth-ideas/firefox-add-ons-name-earns-the-slug/) - 2 shared channels, 2 shared stages

## Read GrowthDex essays

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

## Related GrowthDex essays

- [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

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.