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

- Canonical HTML: https://growth.iangoh.com/growth-ideas/firefox-add-ons-name-earns-the-slug/
- Source: [extensionworkshop.com](https://extensionworkshop.com/documentation/develop/create-an-appealing-listing/)
- GrowthDex source hub: [Firefox Extension Workshop: Create an appealing listing](/sources/firefox-extension-workshop-create-an-appealing-listing-extensionworkshop/)
- Last checked: 2026-06-06T12:04:00Z
- Rarity: rare
- Budget: free
- Channels: Marketplaces, SEO, Brand
- Stages: browser extensions, firefox add-ons, naming, discovery


## Why this can grow

Firefox Add-ons buyers often meet the product through a search result or a copied marketplace link before they meet the team. Mozilla's listing guidance makes the naming decision do more work than most extension teams expect: a unique descriptive name not only tells the user what the add-on does, it also becomes the AMO slug. That means the name keeps showing up in the URL, screenshots, support threads, and shared links. A tighter name improves recall and makes the listing feel less like a random package upload.

## 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. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. 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 name earns the slug can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and SEO 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

Firefox Extension Workshop says a unique, descriptive add-on name gives users a good indication of the add-on's job and also creates a matching unique slug on addons.mozilla.org.

## Adjacent tactics in the same lane

- [Firefox Add-ons privacy policy in listing details](/growth-ideas/firefox-add-ons-privacy-policy-in-listing-details/) - same source, 1 shared channel, 2 shared stages
- [Safari extension Extensions category is a real shelf](/growth-ideas/safari-extension-extensions-category-is-a-real-shelf/) - 3 shared channels, 2 shared stages
- [Chrome Web Store category choice follows the browsing job](/growth-ideas/chrome-web-store-category-choice-follows-the-browsing-job/) - 3 shared channels, 2 shared stages
- [Firefox review rejection falls back to the last approved version](/growth-ideas/firefox-review-rejection-falls-back-to-last-approved-version/) - 3 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.