If you publish Firefox extensions, there are two tiers you should know about: regular listed extensions and Recommended extensions.
Getting Recommended status is the single biggest thing that can happen to an AMO listing short of going viral. This post covers what it takes.
What Recommended Extensions actually means
Mozilla maintains a curated set of Recommended Extensions shown prominently in AMO search results, in the Firefox add-ons manager, and on the AMO homepage. They carry a checkmark badge that signals Mozilla has reviewed and vetted the extension.
Recommended Extensions get:
- A "Recommended" badge in search results (dramatically improves CTR)
- Higher placement in AMO search rankings
- Featured placement in the Firefox add-ons manager (accessible via about:addons)
- A more thorough security review by Mozilla staff
How the nomination process works
The formal process is simpler than you might expect. Send an email to amo-featured@mozilla.org with:
- A link to your extension's AMO listing
- A brief explanation of why it deserves Recommended status
That's it. Mozilla then evaluates the extension against their criteria.
What Mozilla evaluates
From the official documentation:
Single focused purpose — The extension should do one thing and do it well. Multi-function toolbars are not Recommended material; a focused extension that solves a specific user problem is.
Exemplary user experience — The UI should be clean, discoverable, and consistent with Firefox's design language. It doesn't need to be elaborate, but it needs to feel intentional.
Broadly useful — Recommended Extensions are for a general, international audience. Extensions serving very niche audiences are unlikely to be featured.
Actively maintained — Extensions that haven't shipped an update in 2+ years are disqualified. Mozilla wants to feature extensions that will continue working as Firefox evolves.
Security and privacy — All Recommended Extensions undergo technical review. They must not collect data without disclosure, must not have external communications that aren't documented, and must follow Add-on Policies.
What to include in your nomination email
A strong nomination email is short and factual. Here's a structure that works:
Subject: Nomination: [Extension Name] for AMO Recommended Extensions Hi Mozilla Add-ons team, I'd like to nominate [Extension Name] for the Recommended Extensions program. AMO listing: [URL] Why [Extension Name] should be Recommended: - Single focused purpose: [one sentence] - Privacy: [describe data practices, e.g., "no server communication, no telemetry"] - Broad utility: [who is this for] - Active maintenance: [recent update date, roadmap] [Your name and contact] Don't oversell. Mozilla's reviewers have seen thousands of nominations. Clear, factual, specific.
What actually disqualifies extensions
From reviewing community discussions and Mozilla's own guidance:
Missing screenshots — Extensions without AMO screenshots signal low effort. Upload 3-5 screenshots before nominating.
Unclear privacy practices — If your extension has network permissions, explain what they're for in the description. If it's truly no-server, say so explicitly.
Low user base — This isn't an official criterion, but extensions with 0 ADU (average daily users) are harder to evaluate. Build some organic usage first.
Broken experience — Test your extension on the latest Firefox release before nominating. A broken extension wastes reviewer time.
Timeline expectations
Mozilla runs "curatorial projects" periodically — typically every few months — where they process a batch of nominations. Response times can range from weeks to months. Don't expect instant feedback.
If you don't hear back, it doesn't mean your extension was rejected. Keep improving the listing and try again after the next project cycle.
Extensions I've nominated
I build Firefox extensions and recently nominated two of mine:
- NightOwl: auto dark mode at sunset. Single purpose, no server, 13 ADU.
- Voice Notes: browser-side voice memos via MediaRecorder + IndexedDB. No server, no account, 20 ADU.
Whether they get Recommended or not, the nomination forces you to articulate what makes your extension worth using — which is valuable on its own.
The nomination email address is amo-featured@mozilla.org. Mozilla also has a blog post about the community curation process if you want more context.
