# The Firefox Add-ons page should remove the surprise before install > Why naming, no-surprises copy, paid-feature disclosure, reviewable source packages, in-listing privacy text, and channel-tagged AMO links make Firefox add-ons easier to trust and easier to grow. - Canonical HTML: https://growth.iangoh.com/blog/the-firefox-add-ons-page-should-remove-the-surprise-before-install/ - Published: 2026-06-06 - Updated: 2026-06-06T12:04:00Z - Categories: marketplaces, SEO, brand trust - Niches: SaaS, AI products, developer tools, consumer apps, browser extensions ## On this page - The name should be clear enough to survive the copied link - The listing should tell the user what happens before the permission prompt does - Pricing surprises are still surprises - Review readiness is part of the growth system - The privacy answer should live on the page where the buyer is deciding - Attribution should survive the launch week story ## Start with these related tactics - [Firefox Add-ons name earns the slug](/growth-ideas/firefox-add-ons-name-earns-the-slug/): Pick a descriptive add-on name early, because AMO turns that choice into the public slug and a vague title makes both search and trust weaker. - [Firefox Add-ons no-surprises copy before install](/growth-ideas/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. - [Firefox Add-ons paid function disclosed on listing](/growth-ideas/firefox-add-ons-paid-function-disclosed-on-listing/): State on the listing when payment unlocks any feature, so the install does not feel like a bait-and-switch after the review queue clears. A Firefox add-on page does not earn the install by sounding clever. It earns the install by removing the obvious reasons to hesitate. Mozilla makes that explicit. The listing is part product explanation, part privacy disclosure, part review handoff, and part measurement surface. When those jobs get separated across three docs and a launch thread, the buyer ends up doing the stitching. The Firefox Add-ons page should remove the surprise before install. ## The name should be clear enough to survive the copied link [Firefox Add-ons name earns the slug](/growth-ideas/firefox-add-ons-name-earns-the-slug/) is where I would start. Mozilla points out that a unique descriptive name also becomes the AMO slug, which means the title keeps showing up long after the page is published. That belongs beside [Edge Add-ons short description comes from the manifest](/growth-ideas/edge-add-ons-short-description-comes-from-manifest/). Different store, same lesson: the small identity fields are not decoration. They shape what the buyer sees first and what they share later. ## The listing should tell the user what happens before the permission prompt does [Firefox Add-ons no-surprises copy before install](/growth-ideas/firefox-add-ons-no-surprises-copy-before-install/) is the core policy in plain English. Mozilla wants the listing to explain what the add-on does and what information it transmits. I like that because it forces the product story and the privacy story to meet on the same page. It also pairs naturally with [Chrome Web Store single-purpose and permission justification](/growth-ideas/chrome-web-store-single-purpose-and-permission-justification/). In both cases, the install feels safer when the page explains the ask before the browser modal repeats it. ## Pricing surprises are still surprises [Firefox Add-ons paid function disclosed on listing](/growth-ideas/firefox-add-ons-paid-function-disclosed-on-listing/) looks minor until you remember how fast one-star reviews pile up after a bait-and-switch feeling. Mozilla requires teams to say when payment enables any functionality. Good. That gives the buyer a chance to qualify the page honestly, and it keeps the extension from trying to win the install with ambiguity. I would read that beside [HubSpot Marketplace pricing only for integration-enabled plans](/growth-ideas/hubspot-marketplace-pricing-only-for-integration-enabled-plans/). The exact platform changes, but the same trust rule keeps showing up: the shelf should expose the commercial boundary before setup work begins. ## Review readiness is part of the growth system [Firefox Add-ons source package with build steps before review](/growth-ideas/firefox-add-ons-source-package-with-build-steps-before-review/) is the least glamorous tactic in the batch and maybe the most important. Mozilla can reject or block the add-on if the reviewer cannot inspect the source and reproduce the build. That sounds like compliance work. It is also install-path work. Teams that can explain what shipped usually create less mystery for users too. This sits close to [Edge Add-ons test account and live server in certification](/growth-ideas/edge-add-ons-test-account-and-live-server-in-certification/). Review queues punish the same sloppiness that later makes onboarding feel fragile. ## The privacy answer should live on the page where the buyer is deciding [Firefox Add-ons privacy policy in listing details](/growth-ideas/firefox-add-ons-privacy-policy-in-listing-details/) is one of those habits that looks boring until you compare it with the usual detour to a generic legal page. Mozilla recommends including the policy text directly in the listing details, in plain language. That keeps the trust answer attached to the install page instead of sending the user on a side quest. ## Attribution should survive the launch week story [Firefox Add-ons UTM-tagged AMO links by channel](/growth-ideas/firefox-add-ons-utm-tagged-amo-links-by-channel/) is the growth move most teams skip. Mozilla's AMO dashboard can break listing installs out by standard UTM parameters. That means the team can tell whether the install came from the homepage, the release note, a Show HN thread, or a support article instead of guessing from timing. I would pair it with [Reddit answers as AI search knowledge layer](/growth-ideas/reddit-answers-as-ai-search-knowledge-layer/) because both force a better question than did we get traffic. They ask where the useful traffic actually began. This cluster is strongest for SaaS extensions, AI assistants, shopping or workflow helpers, developer tools, and consumer browser utilities that need to qualify the install, explain the permissions, and keep learning which channels bring the right users. If you want help tightening extension listings, trust surfaces, and measured self-serve growth paths, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [Firefox Add-ons name earns the slug](/growth-ideas/firefox-add-ons-name-earns-the-slug/) - Marketplaces, SEO, Brand - [Firefox Add-ons no-surprises copy before install](/growth-ideas/firefox-add-ons-no-surprises-copy-before-install/) - Marketplaces, Brand, Conversion - [Firefox Add-ons paid function disclosed on listing](/growth-ideas/firefox-add-ons-paid-function-disclosed-on-listing/) - Marketplaces, Revenue, Brand - [Firefox Add-ons source package with build steps before review](/growth-ideas/firefox-add-ons-source-package-with-build-steps-before-review/) - Marketplaces, Operations, Engineering - [Firefox Add-ons privacy policy in listing details](/growth-ideas/firefox-add-ons-privacy-policy-in-listing-details/) - Marketplaces, Trust, Conversion - [Firefox Add-ons UTM-tagged AMO links by channel](/growth-ideas/firefox-add-ons-utm-tagged-amo-links-by-channel/) - Marketplaces, Analytics, Distribution ## Essay chronology - [Newer essay: The VS Code extension page should finish the trust check](/blog/the-vs-code-extension-page-should-finish-the-trust-check/) - marketplaces, SEO, brand trust - [Older essay: 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 ## Keep reading - [The Chrome Web Store page should survive the release channel](/blog/the-chrome-web-store-page-should-survive-the-release-channel/) - marketplaces, SEO, brand trust - [The Safari extension page should finish the setup before the install](/blog/the-safari-extension-page-should-finish-the-setup-before-the-install/) - marketplaces, SEO, brand trust - [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 ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path - [developer tools](/blog/#path-developer-tools) - 3 essays in this path ## Sources - [Firefox Extension Workshop: Create an appealing listing](https://extensionworkshop.com/documentation/develop/create-an-appealing-listing/) · [GrowthDex source hub](/sources/firefox-extension-workshop-create-an-appealing-listing-extensionworkshop/) - [Firefox Extension Workshop: Add-on Policies](https://extensionworkshop.com/documentation/publish/add-on-policies/) · [GrowthDex source hub](/sources/firefox-extension-workshop-add-on-policies-extensionworkshop-com/) - [Firefox Extension Workshop: Submitting an add-on](https://extensionworkshop.com/documentation/publish/submitting-an-add-on/) · [GrowthDex source hub](/sources/firefox-extension-workshop-submitting-an-add-on-extensionworkshop-com/) - [Firefox Extension Workshop: Monitoring extension usage statistics](https://extensionworkshop.com/documentation/manage/monitoring-extension-usage-statistics/) · [GrowthDex source hub](/sources/firefox-extension-workshop-monitoring-extension-usage-statistics-extensi/) ## Editing notes - Kept the essay on one claim: the add-on page should remove surprise before install, review, and promotion split apart. - Used concrete objects like slugs, policy text, build steps, paywalls, and UTM tags instead of abstract marketplace language. - Let Mozilla policy details carry the argument and cut any big browser-platform sermonizing. - Ended with practical fit, channel measurement, and the advisory CTA instead of a generic conclusion. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.